[Pkg-mozext-maintainers] Bug#739145: xul-ext-sieve: directory vs. symlink conflict: /usr/share/xul-ext/sieve/chrome/chromeFiles/content/libs/CodeMirror/lib
anbe at debian.org
Sun Feb 16 03:22:04 UTC 2014
User: debian-qa at lists.debian.org
during a test with piuparts I noticed your package installs files over
an existing symlink shipped or created by another package.
Installing something over existing symlinks is considered bad practice.
See e.g. http://firstname.lastname@example.org
It may break in subtle ways and dpkg cannot detect this as a problem.
* Your package might silently overwrite files installed at the symlink
destination by other packages.
* If the package shipping the symlink decides to make the link point
somewhere else (or turn it into a real directory), the files owned
by your package "will be lost" somewhere in the filesystem.
* Depending on installation order the problematic path will be created
either as a symlink or a directory: the package installed first will
"win" and all others have "lost".
Note that dpkg intentionally does not replace directories with
symlinks and vice versa, see in particular the end of point 4 in
(Note: Adding Pre-Depends is *not* a solution.)
This was observed during an upgrade from jessie to sid.
>From the attached log (usually somewhere in the middle...):
0m41.7s ERROR: FAIL: silently overwrites files via directory symlinks:
0m44.0s ERROR: FAIL: debsums reports modifications inside the chroot:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 20305 bytes
Desc: not available
More information about the Pkg-mozext-maintainers