Le Mon, Jul 22, 2013 at 09:00:59AM +0200, Raphael Hertzog a écrit : > > I believe we can update the policy whatever the status of this specific > bug. > You're missing the important sentence that follows: “If there are no > circular dependencies involved, all package dependencies will be > configured.”
Ahem... That is embarassing. Thanks for your patience. Now I understand why I did not understand. > 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 maintain my second provided that you fix the above. Great, and thanks for your suggestion, which I will apply. More seconds or objections from others ? What are the other Policy editors thinking about this patch ? Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- 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/20130722224732.ga2...@falafel.plessy.net
