* Russ Allbery [151005 18:24]:
> I'm also in favor. However, this is a very substantial change to Debian
> practice, and I'm not sure what process should be used for making this
> kind of decision. This wasn't a gap in our specification; rather, the
> previous standard was explicitly chosen (by
> "Russ" == Russ Allbery writes:
Yeah, but there's a significant factor that reduces things somewhat.
In the past, /etc/init.d/foo failing would often cause postinst to
break.
However, in the past, there were a lot of failures that were not
detected by the init.d script.
We have two intention
On Mon, Oct 05, 2015 at 03:20:34PM -0700, Russ Allbery wrote:
> Sam Hartman writes:
> >> "Marvin" == Marvin Renich writes:
>
> > Marvin> As discussed on debian-devel starting at [1], I would like a
> > Marvin> comment added to Section 6.4 "Best practices for maintainer
> > Marvin
Sam Hartman writes:
>> "Marvin" == Marvin Renich writes:
> Marvin> As discussed on debian-devel starting at [1], I would like a
> Marvin> comment added to Section 6.4 "Best practices for maintainer
> Marvin> scripts" that recommends preventing the postinst script from
> Marvi
Here is a condensation of the discussion prior to filing this bug. I
have removed all quotes of previous messages (e.g. msg [2] contained
quotes from msg [1] that have been removed). I have tried to identify
when a message is a reply to parts of several messages or to a message
that is not the pr
> "Marvin" == Marvin Renich writes:
Marvin> As discussed on debian-devel starting at [1], I would like a
Marvin> comment added to Section 6.4 "Best practices for maintainer
Marvin> scripts" that recommends preventing the postinst script from
Marvin> returning failure when a se
Package: developers-reference
Version: 3.4.16
Severity: wishlist
As discussed on debian-devel starting at [1], I would like a comment
added to Section 6.4 "Best practices for maintainer scripts" that
recommends preventing the postinst script from returning failure when a
service fails to start.
A
7 matches
Mail list logo
