[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#582109: debian-policy: document triggers where appropriate



Le Tue, Jul 16, 2013 at 05:09:08PM +0200, Julien Cristau a écrit :
> On Thu, Jul  4, 2013 at 11:26:01 +0900, Charles Plessy wrote:
> > 
> >     http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=87;filename=policy-triggers.diff;att=1;bug=582109
> > 
> That patch has a bunch of typos (I noticed a few in spelling "package").

> Also it doesn't seem to warn against triggers being called with Depends
> not satisfied, which caused no end of trouble for upgrades to wheezy,
> and which is probably going to bite us again for jessie.

Hi Julien,

thank you for your comments and sorry for forgetting to run a spellchecker.  I
will make the following spelling corrections. 

    s/wich/which/
    s/activations/activation/
    s/packges/packages/
    s/unnecessarly/unnecessarily/
    s/mechanims/mechanism/

About the problem of triggers being called with Depends not satisfied, can you
give more explanations or suggest some text for the warning ?  Would it be
enough to add a notice that the triggered postinst script may be called when
the package is "Unpacked", which is a state that does not require that the
packages that are depended on are configured ?

Also, if you think that triggers will give us problems for the Jessie release,
may I suggest that you give it a broad audience on debian-devel ?  As a
maintainer of a package that has triggers, I am definitely interested to learn
if there is something I should give particular attention there.

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


Reply to: