Bug#771877: original symlink target is not an absolute path on libdb5.3-java_5.3.28-7~deb8u1
Tangui, Jan: It is a different (though closely related) bug for which I opened bug #773806 [1]. As soon as that bug is fixed in a new version, it should be possible to upgrade normally. Ulrich [1] http://bugs.debian.org/773806 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771877: original symlink target is not an absolute path on libdb5.3-java_5.3.28-7~deb8u1
I have the same problem. Is there any way this can be fixed given that the buggy version has already been installed? Regards, Jan On Sun, 21 Dec 2014 14:00:11 +0100 Tangui Morlier tan...@tangui.eu.org wrote: The post-removal script fails during the upgrade of libdb5.3-java from version 5.3.28-6 to 5.3.28-7~deb8u1. dpkg-maintscript-helper says « error: original symlink target is not an absolute path ». I assume this is linked to the symlink_to_dir that has been solved but my apt stays blocked on this error, probably because I've installed the buggous version of the package. Is there a way to solve it ? Tangui -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771877: original symlink target is not an absolute path on libdb5.3-java_5.3.28-7~deb8u1
The post-removal script fails during the upgrade of libdb5.3-java from version 5.3.28-6 to 5.3.28-7~deb8u1. dpkg-maintscript-helper says « error: original symlink target is not an absolute path ». I assume this is linked to the symlink_to_dir that has been solved but my apt stays blocked on this error, probably because I've installed the buggous version of the package. Is there a way to solve it ? Tangui -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
