Re: Activating t-p-u by default (was: Re: For those who care about their packages in Debian)
2010/8/26 Carsten Hey : > * David Kalnischkies [2010-08-26 17:43 +0200]: >> Long story short: >> If you want to get updates from an archive only if you pushed a version >> previously from it: 100 => pin > 500. > > Wouldn't adding a new field to Release files similar to 'Not-Automatic' > but pin to 101 instead of 1 if this new field is set to yes an option > for apt/Squeeze+1? This has been reported in #186767. Well, yes and no. Technical more or less no problem, but… As far as i understand t-p-u i don't understand why the default should be < 500. If i am adding it (or let a piece of software add it for me) i guess i want these packages on my system: proposed-updates at least suggests for me, that they will be soon in testing anyway, just, that they are tested now before they enter "real" testing in an overlay archive. If i don't want to participate in this testing, i should remove the archive from my sources. If i just want to grab some versions from it, t-p-u doesn't get much testing in general as you must care for this specific package enough to get a new version for it: So new iceweasels are maybe tested a bit, but packages like tzdata will not get any testing through t-p-u… The problem with this is also, which is why i don't think it would be suitable for backports, is that these archives mixing minor only-bugfix releases and new groundbreaking upstream releases… E.g.: I maybe want to get bugfix releases for iceweasel through backports automatically, but what i don't want is an automatic 3.6 -> 4.0 upgrade, but such pinning i need to define by hand anyway. Regarding the bug: What do you do if two non-debian archives provide such a package -- and, do they "fight" against each other now that they can by changing their DefaultPriority? The cleaner way for the user would it be to declare: I don't want to get this package from this archive ever and i care only for these packages from this archive, ignore the rest. You can say that with -1 and Co, but it is a bit harder than needed… So, again in short: I don't see a reason backports shouldn't be pinned to 1 by default and t-p-u by default not pinned at all to get the default 500 pin… Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikbzjm8cb9fgg_vtki2h8xjk-7_fpv-e9pmm...@mail.gmail.com
Bug#594699: ITP: libtest-regression-perl -- test library for comparing output against normative output
Package: wnpp Severity: wishlist Owner: Nicholas Bamber * Package name: libtest-regression-perl Version : 0.5 Upstream Author : Nicholas Bamber * URL : http://search.cpan.org/dist/Test-Regression/ * License : Perl Programming Lang: Perl Description : test library for comparing output against normative output Needed for upgrade of existing modules -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100828134246.18047.52193.report...@leonhartsberger.periapt
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
On Sat, 2010-08-28 at 12:33 +0200, Patrick Matthäi wrote: > Am 28.08.2010 12:11, schrieb Roy Marples: > >>>dhcpcd is a one stop IPv4 network management daemon which includes > >> > >> It only supports IPv6? > > > > Only IPv4 at present. > > IPv6 support, at least for RA is planned for the next major version, > > possibly with support for the experimental RFC5006 (DNS in IPv6 RA). > > Whops, s/IPv6/IPv4/ in my message, please. :) > > IMHO it shouldn't uploaded to Debian, without missing IPv6 support. What makes you think IPv6 support is required? It does not touch any existing IPv6 and neither does dhcpcd3. As such it co-exists just fine with kernel based RA solicitation. Thanks Roy -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282998574.1700.136.ca...@uberpc
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
On Sat, 2010-08-28 at 13:13 +0200, Mehdi Dogguy wrote: > On 08/28/2010 12:44 PM, Julien Cristau wrote: > > On Sat, Aug 28, 2010 at 09:35:29 +0100, Roy Marples wrote: > > > >> * Package name: dhcpcd5 > >> Version : 5.2.7 > >> Upstream Author : Roy Marples > >> * URL : http://roy.marples.name/projects/dhcpcd > >> * License : BSD-2 > >> Programming Lang: C, Shell > >> Description : dhcpcd5 - a DHCP client > >> > > What's the difference with the existing dhcpcd package? > > > > It's the same project (according to [1]). It's essentially an upgrade, however it's not 100% compatible with the commandline from dhcpcd3 and it uses a method similar to dhclient for configuring the system - aside from IP and routing which is managed internally. However, it's a new package. See bug #551034. Also, dhcpcd5 is designed to be run as a system daemon instead of per interface. This is so it can react to kernel level events and manage routing on a multi interface system a lot better (esp important for BSD system as they lack route metrics). Essentially it's like NetworkManager in this respect but a lot lot smaller. However unlike NetworkManager dhcpcd does not handle link setup and relies on something else to configure wpa_supplicant, ppp, etc. You can also configure an interface based on ARPping a host, wireless SSID. By this, I mean choose to run DHCP or a static IP, or override key DHCP values. Lastly, it works fine on BSD based systems which finally gives them an alternative. Infact, dhcpcd has been merged into the NetBSD base system since 5.0. I only mention this as Debian has kFreeBSD. I'm sure I missed some features out that maybe important to someone :) There are also related side projects which will find their way into Debian also - dhcpcd-dbus and dhcpcd-ui (GTK+ systray moniter/interface) and openresolv (resolvconf alternative, doesn't appear to suffer from the Debian resolvconf reported bugs). dhcpcd-dbus also talks to wpa_supplicant so that dhcpcd-ui can attempt to configure it. Thanks Roy -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282998474.1700.134.ca...@uberpc
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
Philipp Kern writes: > DHCPv4 and DHCPv6 are sufficiently different protocol-wise to warrant two > different clients. (The v6 people might not want to deal with the cruft > of DHCPv4 too...) Absolutely! Create a new DHCPv6 client, cleanly implementing the protocol without having to carry all the unnecessary DHCPv4 baggage. Or even better: Work on improving some of the *existing* DHCPv6 clients. Maybe we can get at least one of them in good enough shape to be actually usable. I tried to summarize the situation here in December: http://www.gossamer-threads.com/lists/nsp/ipv6/20683 I don't think much has changed since then. The ISC has already demonstrated that combining the clients is a big mistake, no matter how big your existing IPv4 codebase is. Their IPv6 support is still not usable in some for what will be the most common DHCPv6 scenario due to the lack of ppp support (which of course is completely unnecessary for IPv4). An example: xs4all has recently announced native IPv6 access for all their users (opt-in), using DHCPv6-PD on top of PPP: http://www.xs4all.nl/klant/ipv6/ This is exactly what the ISP I'm working for will do when we get that far, and I assume many other ISPs will do something similar. DHCPv6-PD is essantial. And using PPP for the link simplifies a lot in a world where most layer 2 equipment is still unprepared for IPv6. Bjørn -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vd6v3p21@nemi.mork.no
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
On 2010-08-28, Patrick Matthäi wrote: > Am 28.08.2010 12:11, schrieb Roy Marples: dhcpcd is a one stop IPv4 network management daemon which includes >>> It only supports IPv6? >> Only IPv4 at present. >> IPv6 support, at least for RA is planned for the next major version, >> possibly with support for the experimental RFC5006 (DNS in IPv6 RA). > Whops, s/IPv6/IPv4/ in my message, please. :) > IMHO it shouldn't uploaded to Debian, without missing IPv6 support. DHCPv4 and DHCPv6 are sufficiently different protocol-wise to warrant two different clients. (The v6 people might not want to deal with the cruft of DHCPv4 too...) Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrni7hu85.dgv.tr...@kelgar.0x539.de
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
On 08/28/2010 12:44 PM, Julien Cristau wrote: > On Sat, Aug 28, 2010 at 09:35:29 +0100, Roy Marples wrote: > >> * Package name: dhcpcd5 >> Version : 5.2.7 >> Upstream Author : Roy Marples >> * URL : http://roy.marples.name/projects/dhcpcd >> * License : BSD-2 >> Programming Lang: C, Shell >> Description : dhcpcd5 - a DHCP client >> > What's the difference with the existing dhcpcd package? > It's the same project (according to [1]). [1] http://packages.debian.org/changelogs/pool/main/d/dhcpcd/current/copyright Cheers, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c78ef53.6040...@dogguy.org
Re: 38
On 27 August 2010 18:20, Adam Borowski wrote: > On Fri, Aug 27, 2010 at 10:09:49AM +0200, posion bit wrote: >> > (/etc/mc/mc.menu) >> > case "$i" in >> > *.tar.gz) D="`basename $i .tar.gz`";; >> >> In that case, name-spaced filenames should work, because the >> string is a _quoted_ multi-word string. > > i="cat's meow.tar.gz" > > basename: extra operand `.tar.gz' > Try `basename --help' for more information. When the solution is easy I don't see why we don't just do it. br...@andean:~$ i="cat's meow.tar.gz" br...@andean:~$ echo "`basename "$i" .tar.gz`" cat's meow (yes, the nested quotes don't seem to matter) -- Brian May -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikb9edowrojto8hhbkios6mn6tqsepj9mmoy...@mail.gmail.com
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
On Sat, Aug 28, 2010 at 09:35:29 +0100, Roy Marples wrote: > * Package name: dhcpcd5 > Version : 5.2.7 > Upstream Author : Roy Marples > * URL : http://roy.marples.name/projects/dhcpcd > * License : BSD-2 > Programming Lang: C, Shell > Description : dhcpcd5 - a DHCP client > What's the difference with the existing dhcpcd package? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
On Sat, 2010-08-28 at 11:19 +0200, Patrick Matthäi wrote: > Am 28.08.2010 10:35, schrieb Roy Marples: > > Package: wnpp > > Severity: wishlist > > Owner: Roy Marples > > > > > > * Package name: dhcpcd5 > >Version : 5.2.7 > >Upstream Author : Roy Marples > > * URL : http://roy.marples.name/projects/dhcpcd > > * License : BSD-2 > >Programming Lang: C, Shell > >Description : dhcpcd5 - a DHCP client > > > > dhcpcd is a one stop IPv4 network management daemon which includes > > It only supports IPv6? Only IPv4 at present. IPv6 support, at least for RA is planned for the next major version, possibly with support for the experimental RFC5006 (DNS in IPv6 RA). Thanks Roy -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282990309.1700.104.ca...@uberpc
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
Am 28.08.2010 12:11, schrieb Roy Marples: dhcpcd is a one stop IPv4 network management daemon which includes It only supports IPv6? Only IPv4 at present. IPv6 support, at least for RA is planned for the next major version, possibly with support for the experimental RFC5006 (DNS in IPv6 RA). Whops, s/IPv6/IPv4/ in my message, please. :) IMHO it shouldn't uploaded to Debian, without missing IPv6 support. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c78e5f6.6090...@debian.org
Re: Bug#594672: ITP: dhcpcd5 -- a DHCP client
Am 28.08.2010 10:35, schrieb Roy Marples: Package: wnpp Severity: wishlist Owner: Roy Marples * Package name: dhcpcd5 Version : 5.2.7 Upstream Author : Roy Marples * URL : http://roy.marples.name/projects/dhcpcd * License : BSD-2 Programming Lang: C, Shell Description : dhcpcd5 - a DHCP client dhcpcd is a one stop IPv4 network management daemon which includes It only supports IPv6? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c78d4b7.2000...@debian.org
Bug#594672: ITP: dhcpcd5 -- a DHCP client
Package: wnpp Severity: wishlist Owner: Roy Marples * Package name: dhcpcd5 Version : 5.2.7 Upstream Author : Roy Marples * URL : http://roy.marples.name/projects/dhcpcd * License : BSD-2 Programming Lang: C, Shell Description : dhcpcd5 - a DHCP client dhcpcd is a one stop IPv4 network management daemon which includes * RFC2131 compliant DHCP client * IPv4LL (aka ZeroConf) support * ARP address conflict resolution * Link carrier detection * Wireless SSID profiles * ARP ping profiles -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100828083529.2072.9723.report...@uberpc
