Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Andrew Shadura
Hello, On Wed, 29 Feb 2012 00:47:57 +0100 m...@linux.it (Marco d'Itri) wrote: > > Yes, that's probably a reasonable threshold. What should packages > > like miredo and wide-dhcpv6-client do? Both of these hooks have to > > do with > Maybe they could stop pretending that the ifupdown configurat

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Marco d'Itri
On Feb 28, Steve Langasek wrote: > Yes, that's probably a reasonable threshold. What should packages like > miredo and wide-dhcpv6-client do? Both of these hooks have to do with Maybe they could stop pretending that the ifupdown configuration model can properly support multiple address familie

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Michael Biebl
On 28.02.2012 23:29, Steve Langasek wrote: > On Tue, Feb 28, 2012 at 08:47:16PM +0100, Michael Biebl wrote: >>> subsequent hooks. OTOH, there might be cases where that's beneficial >>> because it lets a critical hook declare that an interface bring-up hasn't >>> succeeded and the interface bring-u

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Ben Hutchings
On Tue, Feb 28, 2012 at 10:59:42PM +0100, Andrew Shadura wrote: > Hello, > > On Tue, 28 Feb 2012 22:37:29 +0100 > Holger Levsen wrote: > > > (And I'd prefer this bug to be one against ifupdown and not > > general, but YMMV.) But, definitly, filing a bug against general > > saying these and these

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Andrew Shadura
Hello, On Tue, 28 Feb 2012 14:27:15 -0800 Steve Langasek wrote: > > When failure to execute a hook leads to interface being > > non-operational. > Yes, that's probably a reasonable threshold. What should packages > like miredo and wide-dhcpv6-client do? Both of these hooks have to > do with r

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Steve Langasek
On Tue, Feb 28, 2012 at 08:47:16PM +0100, Michael Biebl wrote: > > subsequent hooks. OTOH, there might be cases where that's beneficial > > because it lets a critical hook declare that an interface bring-up hasn't > > succeeded and the interface bring-up should be rolled back so the admin can > >

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Steve Langasek
On Tue, Feb 28, 2012 at 09:09:22PM +0100, Andrew Shadura wrote: > On Tue, 28 Feb 2012 11:27:37 -0800 > Steve Langasek wrote: > > > However, it's been reported that some scripts return wrong exit > > > codes sometimes, causing failure during network configuration. > > My doubt here is: what is th

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Andrew Shadura
Hello, On Tue, 28 Feb 2012 22:37:29 +0100 Holger Levsen wrote: > (And I'd prefer this bug to be one against ifupdown and not > general, but YMMV.) But, definitly, filing a bug against general > saying these and these package need to be fixed wont do it. Also, I find it fits general perfectly,

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Andrew Shadura
Hello, On Tue, 28 Feb 2012 22:37:29 +0100 Holger Levsen wrote: > just from what I've read in those two replies to this bug yet, I > think I agree that this change should be reverted. > And if you really want/need/do this change which needs changes in 30 > (or so) other packages, then please fil

Processed: Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 661591 ifupdown Bug #661591 [general] packages providing ifupdown scripts must have those scripts fixed if needed Bug reassigned from package 'general' to 'ifupdown'. > thanks Stopping processing here. Please contact me if you need assi

Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Holger Levsen
reassign 661591 ifupdown thanks Hi, just from what I've read in those two replies to this bug yet, I think I agree that this change should be reverted. And if you really want/need/do this change which needs changes in 30 (or so) other packages, then please file 30 bugs against those package an

Re: Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Michael Biebl
On 28.02.2012 20:27, Steve Langasek wrote: > subsequent hooks. OTOH, there might be cases where that's beneficial > because it lets a critical hook declare that an interface bring-up hasn't > succeeded and the interface bring-up should be rolled back so the admin can > try again. If that is the

Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Steve Langasek
Hi Andrew, On Tue, Feb 28, 2012 at 11:24:43AM +0100, Andrew O. Shadura wrote: > Starting with the last beta, ifupdown calls run-parts for if-*.d scripts > with --exit-on-error, so if the script fails, interface isn't marked as > configured (see #547587). > However, it's been reported that some sc

Bug#661591: packages providing ifupdown scripts must have those scripts fixed if needed

2012-02-28 Thread Andrew O. Shadura
Package: general Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Starting with the last beta, ifupdown calls run-parts for if-*.d scripts with --exit-on-error, so if the script fails, interface isn't marked as configured (see #547587). However, it's been reported that some scrip