On Mon, 22 Jul 2013, Charles Plessy wrote: > Nevertheless, please let me try to refocus on the question of whether > the Policy can be updated or not.
I believe we can update the policy whatever the status of this specific bug. > Here is what is written in the Policy about "postinst configure": > > The files contained in the package will be unpacked. All package > dependencies will at least be unpacked. You're missing the important sentence that follows: “If there are no circular dependencies involved, all package dependencies will be configured.” > I propose to go ahead with the following: > > <tag><var>postinst</var> <tt>triggered</tt> > "<var>trigger-name</var> <var>trigger-name</var> ..."</tag> > <item> My suggestion: <prgn>postinst configure</prgn> was already run and the dependencies ought to be configured. However, dpkg currently suffers of a bug which means that <prgn>postinst triggered</prgn> can be called while some dependencies are being upgraded (see bug <url id="http://bugs.debian.org/671711"; name="671711">). You should thus only rely on the fact that the dependencies are at least unpacked and were already configured once (similar to what <tt>Pre-Depends</tt> ensures for <prgn>preinst</prgn> maintainer scripts). > I would like to go ahead and close this bug. If Raphaël confirms that he > still > seconds the patch, I would much appreciate if I could either have support or > actionable objection from others (preferably in the form of "unless X is done, > the patch should not be applied", rather than "it would be good to do Y"). I maintain my second provided that you fix the above. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130722070059.gb24...@x230-buxy.home.ouaza.com
