Le Sun, Jul 15, 2012 at 06:40:22PM +0200, Guillem Jover a écrit : > > Given the above, i.e. the fact that this behaviour, even if rather > unfortunate has been present since the introduction of triggers and > as such makes affected packages having to workaround the problems for > now, and that fixing it now would introduce regressions in other > situations I don't consider it RC, and I'm postponing the fix for > after wheezy, after the aforementioned regressions have been fixed > first.
Hi Guillem, what is the state of this bug now that Wheezy has been released ? Do you think that you will have soon opportunities to resume the work ? Or would it make sense to call for contributions on debian-dpkg or debian-devel, for instance ? The reason I ask is that this bug seems to have chilling effects regarding documenting triggers in the Policy, which I think is unfortunate since the proposed addition to the Policy will, in my opinion, make it easier for our developers to use and understand triggers. Have a nice Sunday, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
