Le mercredi 07 mai 2008 à 08:23 +0200, Raphael Hertzog a écrit : > On Wed, 07 May 2008, Josselin Mouette wrote: > > However this is not always the case when the object is deleted: > > * Let's say package bar has set interest on /usr/share/bar. > > * Package foo_0.1 contains /usr/share/bar/foo.xml. > > * Package foo_0.2 does not contain any file in /usr/share/bar. > > * When upgrading from foo_0.1 to foo_0.2, package bar is not > > triggered. > > Can you do a "dpkg -l foo bar" just after the apt/dpkg run that lead you > to that conclusion and show us the result? Did you use apt or dpkg > directly?
I used dpkg directly, and after that both packages are in the installed (ii) state. > Do you have the (real) packages where this happened just for test purpose? Sure, everything is there: http://malsain.org/~joss/debian/ There, you have a triggers-enabled python-support package, and two versions of python-gmenu, one built against python-central and one built against python-support. If you upgrade from 2.22.1-1 to 2.22.1-2, you'll see the trigger is correctly run and the modules are byte-compiled. If you upgrade from 2.22.1-2 to 2.22.1-2+bzzt (which is the same as -1 but with a higher number), you'll see the trigger is not run, and the modules are not cleaned from /var/lib/python-support/python2.5/GMenuSimpleEditor/. If you then run 'update-python-modules -p' (the command that is launched by the trigger) by hand, they are correctly cleaned. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
