I'd disagree on the severity of this bug.
Tried to create a package with a compatibility symlinks on legacy
pathnames. That proved to be a poor idea, since now I'm getting empty
directories on legacy pathnames instead of symlinks when upgrading the
packages.
No even a warning about this and I would've expected the install process
to halt right there.
The preinst solution could work with moving the old directories
elsewhere and remove them on postinst after a successful installation
(to support rolling back to earlier version).
But is this something we want to do in all packages that have this problem?
Regards,
Jussi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
