[Python-modules-team] Bug#700782: Bug#700782: python3-cxx-dev: unhandled symlink to directory conversion: /usr/include/python3.2
sramacher at debian.org
Tue Feb 19 20:51:47 UTC 2013
Control: tags -1 + moreinfo
On 2013-02-17 15:02:05, Andreas Beckmann wrote:
> Package: python3-cxx-dev
> Version: 6.2.4-2
> Severity: serious
> User: debian-qa at lists.debian.org
> Usertags: piuparts
> an upgrade test with piuparts revealed that your package installs files
> over existing symlinks and possibly overwrites files owned by other
> packages. This usually means an old version of the package shipped a
> symlink but that was later replaced by a real (and non-empty)
> directory. This kind of overwriting another package's files cannot be
> detected by dpkg.
python3-cxx-dev installs files to /usr/include/python3.2/CXX and
/usr/include/python3.2 is a symlink provided by python3.2-dev. However,
no other package has ever shipped files in /usr/include/python3.2mu/CXX.
Additionally /usr/include/python3.2 always has been a symlink to
python3.2mu . So it's neither an unhandled symlink to directory
conversion nor overwriting files owned by other packages.
Maybe I'm just unable to find the policy section that forbids installing
to locations which contain symlinks in the dirname, so could you please
clarify why you think this bug warrants severity serious? Or am I just missing
something from the bug report?
 Except for some versions that were only in experimental (3.2~something) and
the python3.2-dev's postinst has the code to handle the conversion. So that
shouldn't be a problem for squeeze to wheezy upgrades.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: Digital signature
More information about the Python-modules-team