Twoja nowa STRONA lub SKLEP internetowy
Dzień dobry,
zajmujemy się budową profesjonalnych stron i sklepów internetowych dla firm.
Jeśli mogę przesłać Państwu naszą aktualną propozycję proszę o odpowiedź "TAK" na ten e-mail.
Pozdrawiam
Re: Proposal: Repository for fast-paced package backports
Thomas Goirand schrieb: > And for a start, I don't think you really need a buildd network, just amd64 > is ok-ish. Agreed. If there's actual demand for further architecture support, it will appear naturally by people offering to do the necessary setup. Cheers, Moritz
Re: Would be possible to have a ".treeinfo" file added to the installers' page?
People, Let me revive this thread. :-) After a nice pub conversation a friend of mine suggested that *maybe* the .treeinfo changes could be done as part of Google Summer of Code. As a GNOME student/mentor/admin from previous years, I sincerely think it may be a good idea *if* the work is not too short and/or something else could be added to the same project in order to make it solid enough for 3-ish months of work. In case this idea is really too short ... what if someone spend some time to briefly guide me through the relevant codebase so I could provide the needed patch? What would be the specific codebase that I could open an RFE kind of issue just to keep track of this? Paul mentioned in his last answer: > I'm not involved in the affected teams but I guess it would depend on > someone being willing and able to implement the requested changes. In > case anyone not in those teams is interested, I think these are the > relevant codebases: > > The archive: > > https://salsa.debian.org/ftp-team/dak > > The ISO images: > > https://salsa.debian.org/images-team/debian-cd > > The website: > > https://salsa.debian.org/webmaster-team/webwml > Could someone confirm that he's accurate on his answer or point me to right direction? Best Regards, -- Fabiano Fidêncio
Bug#917543: ITP: butt -- multi OS streaming audio tool easy to use
Package: wnpp Severity: wishlist Owner: "Paulo Henrique de Lima Santana (phls)" * Package name: butt Version : 0.1.17 Upstream Author : Daniel Noethen * URL : https://danielnoethen.de * License : GPL-2+ Programming Lang: C Description : multi OS streaming audio tool easy to use butt (broadcast using this tool) is an easy to use, multi OS streaming tool. It supports ShoutCast and IceCast and runs on Linux, MacOS and Windows. The main purpose of butt is to stream live audio data from your computers Mic or Line input to an Shoutcast or Icecast server. Recording is also possible. It is NOT intended to be a server by itself or automatically stream a set of audio files. . * It Works with SHOUTcast and Icecast. * It runs on all three major operating systems. Mac OS X, Linux and Windows. * It supports aac+, mp3, ogg/vorbis, ogg/opus and flac for streaming. * It supports aac+, mp3, ogg/vorbis, ogg/opus, flac and wav for recording. * It is able to connect to a server after starting up automatically. * It is able to start a recording after connecting to a server automatically. * Recording can be split after a user defined amount of time. * Current song can either be updated manually or automatically by reading a file. * Configuration files can be imported and exported. * Status display shows infos about the current state (click on it). * Automatically reconnects in case the connection was interrupted. * It has a VU Meter with peak hold. * It is able to attentuate and amplify the input volume. * It has a 5-band EQ. * It can read song names from different apps in MacOS and Linux. * Display colors can be changed as desired.
Bug#917546: ITP: binutils-xtensa-lx106 -- GNU binary utilities, for Xtensa lx106 core
Package: wnpp Severity: wishlist Owner: Jonathan McDowell * Package name: binutils-xtensa-lx106 Version : 2.31.1-11+1 * URL : https://www.gnu.org/software/binutils/ * License : GPL Programming Lang: C Description : GNU binary utilities, for Xtensa lx106 core Bare metal binutils for chips using the Xtensa lx106 core, such as the Espressif ESP8266 wireless modules. The programs in this package are used to manipulate binary and object files that may have been created for the Xtensa architecture. This package is primarily for those developing for the ESP8266 platform and is not needed by normal users or developers. The ESP8266 is a commonly used component in the IoT ecosystem; devices such as the SonOff power switches and various wifi lightbulbs are all based upon it, as well as a full Arduino stack being available. Espressif have committed to availability until at least 2026. As this is targeted towards embedded platforms it will be maintained within the Debian Electronics Team. It is built using the binutils-source base package rather than pulling in an additional copy of binutils.
Bug#917547: ITP: gcc-xtensa-lx106 -- GNU C compiler for Xtensa lx106 core
Package: wnpp Severity: wishlist Owner: Jonathan McDowell * Package name: gcc-xtensa-lx106 Version : 8.2.0-13+1 * URL : http://gcc.gnu.org/ * License : GPL Programming Lang: C Description : GNU C compiler for Xtensa lx106 core Bare metal C cross compiler for chips using the Xtensa lx106 core, such as the Espressif ESP8266 wireless SoCs. This package is primarily for those developing for the ESP8266 platform and is not needed by normal users or developers. This is the counterpart to the binutils-xtensa-lx106 ITP (#917546). As stated there the ESP8266 is a commonly used component in the IoT ecosystem; devices such as the SonOff power switches and various wifi lightbulbs are all based upon it, as well as a full Arduino stack being available. Espressif have committed to availability until at least 2026. As this is targeted towards embedded platforms it will be maintained within the Debian Electronics Team. It is built using the gcc-8-source base package rather than pulling in an additional copy of gcc-8.
Bug#917557: O: reportbug-ng -- Easy to use alternative to Debian's classic reportbug
Package: wnpp Severity: normal I intend to orphan the reportbug-ng package. I've been asking for help maintaining it years ago without response, so I'm now orphaning it. The current popcon value is around 300, so it may be save to just get rid of it. Also reportbug gained a lot more user friendly GUI since I wrote reportbug-ng so removing it from the archive might not be a big loss. The package description is: Reportbug-NG is a graphical interface using Qt for searching, filtering, reporting or manipulating bugs in Debian's Bug Tracking System.
Questions about VRF function in /etc/network/interfaces
Hi all, I'm working on SONiC project management vrf function under debian with kernel 4.3. This is my OS: > # uname -a > Linux dut211 4.9.0-7-amd64 #1 SMP Debian 4.9.110-3+deb9u2 (2015-12-19) > x86_64 GNU/Linux This is SONiC project management vrf function: > https://www.youtube.com/watch?v=uAHmZKEdqDE&feature=youtu.be Now I have to rewrite /etc/network/interfaces to implement this function, but I got errors, so I want to know if there is demo about how to define VRF interface and implement VRF function in /etc/network/interfaces. As I follow your man file, I don't know how to do, and gots errors. This is my try on this feature, rewrite /etc/network/interfaces like this iface eth0 inet static > address 172.18.8.211 > netmask 255.255.255.0 > ## management network policy routing rules > # management port up rules > up ip -4 link add mgmtvrf type vrf table 10 > up ip -4 link set dev mgmtvrf up > up ip -4 link set dev eth0 master mgmtvrf > up ip -4 route add default via 172.18.8.1 dev eth0 table 10 > up ip -4 route add 172.18.8.0/24 dev eth0 table 10 > up ip -4 rule add from 172.18.8.211/32 table 10 > post-up sysctl -w net.ipv4.tcp_l3mdev_accept=1 > # management port down rules > down ip -4 route delete default via 172.18.8.1 dev eth0 table 10 > down ip -4 route delete 172.18.8.0/24 dev eth0 table 10 > down ip -4 rule delete from 172.18.8.211/32 table 10 > down ip -4 link set dev eth0 nomaster This is errors I got Dec 29 02:38:48 dut211 ifup[8690]: RTNETLINK answers: File exists > Dec 29 02:38:48 dut211 ifup[8690]: ifup: failed to bring up eth0 > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Main process > exited, code=exited, status=1/FAILURE > Dec 29 02:38:48 dut211 systemd[1]: Failed to start Raise network > interfaces. > -- Subject: Unit networking.service has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- Unit networking.service has failed. > -- > -- The result is failed. > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Unit entered failed > state. > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Failed with result > 'exit-code’. Thank you. Simon Jones
Re: Questions about VRF function in /etc/network/interfaces
On Sat, Dec 29, 2018 at 01:36:37PM +0800, Simon Jones wrote: > Hi all, > > I'm working on SONiC project management vrf function SONiC: https://azure.github.io/SONiC/ Software for Open Networking in the Cloud, SONiC VRF: https://en.wikipedia.org/wiki/Virtual_routing_and_forwarding > under debian with kernel 4.3. > > This is my OS: > > > # uname -a > > Linux dut211 4.9.0-7-amd64 #1 SMP Debian 4.9.110-3+deb9u2 (2015-12-19) > > x86_64 GNU/Linux Euh, that 4.9 is not 4.3 ... > This is SONiC project management vrf function: > > > https://www.youtube.com/watch?v=uAHmZKEdqDE&feature=youtu.be > > > Now I have to rewrite /etc/network/interfaces to implement this function, > but I got errors, so I want to know if there is demo about how to define > VRF interface and implement VRF function in /etc/network/interfaces. > > As I follow your man file, I don't know how to do, and gots errors. > > This is my try on this feature, rewrite /etc/network/interfaces like this > > iface eth0 inet static > > address 172.18.8.211 > > netmask 255.255.255.0 > > ## management network policy routing rules > > # management port up rules > > up ip -4 link add mgmtvrf type vrf table 10 > > up ip -4 link set dev mgmtvrf up > > up ip -4 link set dev eth0 master mgmtvrf > > up ip -4 route add default via 172.18.8.1 dev eth0 table 10 > > up ip -4 route add 172.18.8.0/24 dev eth0 table 10 > > up ip -4 rule add from 172.18.8.211/32 table 10 > > post-up sysctl -w net.ipv4.tcp_l3mdev_accept=1 > > # management port down rules > > down ip -4 route delete default via 172.18.8.1 dev eth0 table 10 > > down ip -4 route delete 172.18.8.0/24 dev eth0 table 10 > > down ip -4 rule delete from 172.18.8.211/32 table 10 > > down ip -4 link set dev eth0 nomaster > > > This is errors I got > > > Dec 29 02:38:48 dut211 ifup[8690]: RTNETLINK answers: File exists That means "defining something twice is not allowed". See if you can find what is being defined for a second time. > > Dec 29 02:38:48 dut211 ifup[8690]: ifup: failed to bring up eth0 > > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Main process exited, > > code=exited, status=1/FAILURE > > Dec 29 02:38:48 dut211 systemd[1]: Failed to start Raise network interfaces. > > -- Subject: Unit networking.service has failed > > -- Defined-By: systemd > > -- Support: https://www.debian.org/support > > -- > > -- Unit networking.service has failed. > > -- > > -- The result is failed. > > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Unit entered failed > > state. > > Dec 29 02:38:48 dut211 systemd[1]: networking.service: Failed with result > > 'exit-code???. > > > Thank you. > Groeten Geert Stappers -- Leven en laten leven
