Your message dated Sun, 31 Aug 2014 05:39:09 +0200
with message-id <20140831033909.gb22...@gaara.hadrons.org>
and subject line Re: Bug#758778: dpkg-maintscript-helper: error: original
symlink target is not an absolute path
has caused the Debian Bug report #758778,
regarding dpkg-maintscript-helper: error: original symlink target is not an
absolute path
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
758778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.17.13
Severity: serious
Justification: makes packages uninstallable/unremovable
Affects: autoconf-archive
Dear Maintainer,
the changelog for 1.17.13 contains:
* Fix dpkg-maintscript-helper symlink_to_dir to assure absolute
pathnames arguments.
The problem is that now the following happens, if one tries to install
autoconf-archive:
# dpkg -i autoconf-archive_20140228-1_all.deb
Selecting previously unselected package autoconf-archive.
(Reading database ... 11973 files and directories currently installed.)
Preparing to unpack autoconf-archive_20140228-1_all.deb ...
dpkg-maintscript-helper: error: original symlink target is not an
absolute path
dpkg: error processing archive autoconf-archive_20140228-1_all.deb
(--install):
subprocess new pre-installation script returned error exit status 1
dpkg-maintscript-helper: error: original symlink target is not an
absolute path
dpkg: error while cleaning up:
subprocess new post-removal script returned error exit status 1
Errors were encountered while processing:
autoconf-archive_20140228-1_all.deb
It can't even be removed with normal means:
# dpkg --purge autoconf-archive
dpkg: error processing package autoconf-archive (--purge):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
Errors were encountered while processing:
autoconf-archive
One has to force the removal:
# dpkg --purge --force-remove-reinstreq autoconf-archive
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
(Reading database ... 11973 files and directories currently installed.)
Removing autoconf-archive (20140228-1) ...
I'm not sure why dpkg-maintscript-helper was changed to fail when a
non-absolute symlink was used, but this change should not make it into
testing, unless all packages doing so have been fixed.
Best regards,
Andreas
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set
to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.6-7
ii libc6 2.19-9
ii liblzma5 5.1.1alpha+20120614-2
ii libselinux1 2.3-1
ii tar 1.27.1-2
ii zlib1g 1:1.2.8.dfsg-2
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 1.0.6
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.17.13
On Thu, 2014-08-21 at 12:47:34 +0200, Andreas Cadhalpun wrote:
> Control: affects -1 imagemagick
> On 21.08.2014 12:01, Guillem Jover wrote:
> >The only other affected package is lilypond. I'll check the actual
> >effect from dir_to_symlink too, cook a list and send to debian-devel@.
> >And file some RC bugs at the same time.
>
> There is also imagemagick-doc 8:6.8.9.6-2 in experimental, which fails to
> install [1][2].
There was also autoconf-archive, which I found about the other day,
but didn't get to file a bug report, but others have done so now,
so that's fine.
As it seems dpkg migrated to testing regardless (!?) of the RC bug,
there does not seem to be much point about keeping this one open, so
I'm closing it with this mail.
Thanks,
Guillem
--- End Message ---
