Hi Sebastian, Thank you.
What confused me was that: 1. The python-sqlite-dbg_1.0.1-9_amd64.deb I have lying around does not contain the symlink. This is the exactly the file I uploaded to the archive on 2011-12-09. and 2. My attempted piuparts command did not trigger the error. On a closer look at the log, that's because it didn't even try to install python-sqlite-dbg since it apparently doesn't work to run piuparts in a chroot. -- Joel On 5 February 2014 17:50, Sebastian Ramacher <sramac...@debian.org> wrote: > Hi Joesl > > On 2014-02-01 11:45:44, Joel Rosdahl wrote: > > As far as I can tell, neither python-sqlite-dbg nor python-sqlite in > > neither wheezy nor jessie contain symlinks for (or in) /usr/share/doc and > > don't create any symlinks in preinstall/postinstall scripts. > > python-sqlite-dbg in wheezy contains a symlink: > > $ dpkg -l python-sqlite-dbg > ... > ii python-sqlite-dbg 1.0.1-9 amd64 ... > > $ file /usr/share/doc/python-sqlite-dbg > /usr/share/doc/python-sqlite-dbg: symbolic link to `python-sqlite' > > However, python-sqlite-dbg in jessie ships a directory. After a fresh > install: > > $ dpkg -l python-sqlite-dbg > ... > ii python-sqlite-dbg 1.0.1-10 amd64 ... > > $ file /usr/share/doc/python-sqlite-dbg > /usr/share/doc/python-sqlite-dbg: directory > > You can see the problem if you install python-sqlite-dbg in wheezy, > upgrade to the version from jessie and then remove it (without removing > python-sqlite). /usr/share/doc/python-sqlite no longer contains any > files apart from README.Debian. copyright and changelog.Debian.gz are > missing. > > So for upgrades this conversion from a symlink to a directory needs > special handling: either handle the removal of the symlink in maintainer > scripts or use dpkg-maintscript-helper's symlink_to_dir command to do > that. > > Regards > -- > Sebastian Ramacher >
