Package: dpkg Version: 1.14.18 Severity: serious (I'm marking this bug RC because this could lead to very nasty bugs during some upgrades of packages using triggers, although I don't know of a package in the archive for which the issue would be critical yet.)
The triggers specification says the following:
File triggers have names of the form
/path/to/directory/or/file
and are activated when the specified filesystem object, or any object
under the specified subdirectory, is created, updated or deleted by
dpkg during package unpack or removal. The pathname must be absolute.
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.
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
