Steve Langasek [2011-09-30 5:37 -0000]:
> So glib2.0 needs to clean up its historic mis-migration.
Hmm, the preinst files do
if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" lt-nl 2.27.5-2; then
rm -f /usr/share/doc/libglib2.0-dev
fi
I. e. correctly use lt-nl (thus don't fire on fresh installs), and
also shouldn't affect natty upgrades, and don't create any symlinks.
Given that this was reproduced using a natty install and oneiric
upgrade, I don't see how this would introduce this bug. But maybe I'm
missing something here?
debian/* doesn't use "ln" anywhere, and there is just one *.links for
gtk-doc.
The natty package is identical in all those regards.
Right now I'm really stumped how this symlink ever actually got
created. It's like black magic :(
Thanks for any hint,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Steve Langasek [2011-09-30 5:37 -0000]:
> So glib2.0 needs to clean up its historic mis-migration.
Hmm, the preinst files do
if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" lt-nl 2.27.5-2; then doc/libglib2. 0-dev
rm -f /usr/share/
fi
I. e. correctly use lt-nl (thus don't fire on fresh installs), and
also shouldn't affect natty upgrades, and don't create any symlinks.
Given that this was reproduced using a natty install and oneiric
upgrade, I don't see how this would introduce this bug. But maybe I'm
missing something here?
debian/* doesn't use "ln" anywhere, and there is just one *.links for
gtk-doc.
The natty package is identical in all those regards.
Right now I'm really stumped how this symlink ever actually got
created. It's like black magic :(
Thanks for any hint,
Martin www.piware. de
--
Martin Pitt | http://
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)