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 <hol...@layer-acht.org> 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, as it's not a bug in ifupdown,
> but rather a number of bugs in some of the packages in the list.
But then who is to close the bug? How do you track progress?
I would suggest a MBF where each bug requests the maintainer to
review and make sure their hooks return the proper exit codes,
depending on whether the work they do should be considered to
be essential to bringing the interface up/down. Revert (for now) the
change that makes any failure fatal, and block the original bug with
each of the new bugs.
After a month or so you can try to resolve the blocking bugs that are
still open. Hopefully that doesn't leave you with too many difficult
decisions.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
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/20120228232605.gp12...@decadent.org.uk
