[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#845280: apt: useless path given in failed install messages



Package: apt
Version: 1.3.1
Severity: normal


Hi!
When installation of a package fails, recent apt makes dpkg print useless
paths in the error message:

dpkg: error processing archive /tmp/apt-dpkg-install-iwKqmD/4-libxtables12_1.6.0+snapshot20161117-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libxtables.so.12.0.0', which is also in package libxtables11:amd64 1.6.0+snapshot20161117-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /tmp/apt-dpkg-install-iwKqmD/4-libxtables12_1.6.0+snapshot20161117-2_amd64.deb

Until recently, the path given was to /var/cache/apt/archives/ where
.deb files are actually kept.  I see they are now copied to
/tmp/apt-dpkg-install-iwKqmD/ and prefixed by ordinal numbers, but that
temporary directory ceases to exist before apt returns, thus is useless to
the user.



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.10+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages apt depends on:
ii  adduser                 3.115
ii  debian-archive-keyring  2014.3
ii  gpgv                    2.1.16-2
ii  init-system-helpers     1.46
ii  libapt-pkg5.0           1.3.1
ii  libc6                   2.24-5
ii  libgcc1                 1:6.2.1-4
ii  libstdc++6              6.2.1-4

Versions of packages apt recommends:
ii  gnupg  2.1.16-2

Versions of packages apt suggests:
pn  apt-doc                      <none>
pn  aptitude | synaptic | wajig  <none>
ii  dpkg-dev                     1.18.15
ii  powermgmt-base               1.31+nmu1
ii  python-apt                   1.1.0~beta5

-- no debconf information


Reply to: