severity 671711 important affects 671711 mono-tools found 671711 dpkg/1.14.17 notfound 671711 monodoc-clutter-manual/1.0.0~alpha3~git20090817.r1.349dba6-8 notfound 671711 mono-tools/2.10-3 notfound 671711 octave-vrml/1.0.13-1 thanks
On Fri, 2012-06-08 at 07:09:56 +0200, Guillem Jover wrote: > Hmmm, so I had prepared a patch which basically checks if the package > has its dependencies fulfilled before calling the postinst script with > "triggered", and otherwise defers the trigger processing for later (but > only as long as it is not running from inside the deferred trigproc run). > > This fixes this specific case just fine (t-triggers-depends test > case in dpkg/pkg-tests.git), but this in turn creates problems with > packages with pending triggers depending on packages awaiting them, > as it forces breaking trigger cycles, which is not really a nice > upgrade path. > > An immediate example of this is man-db and dpkg itself. While this > specific case could be fixed by removing the old versioned dpkg > dependency from man-db, I'm assuming other such cases might exist > on the archive, and I'm not prepared to add any such fix to dpkg > w/o further analysis. > > In any case, this and most other similar cases would just disappear > by switching those triggers to the noawait variants, but that's not > supported by dpkg in stable so that would need to wait until after > wheezy. 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. thanks, guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
