Package: dpkg
Version: 1.15.8.3
Severity: normal

Recently there was a file conflict between kdelibs{,5}-data.

# find /usr -name "*.dpkg-tmp" | wc -l
0
# dpkg -i /var/cache/apt/archives/kdelibs-data_4%3a3.5.10.dfsg.1-4_all.deb 
(Reading database ... 217862 files and directories currently installed.)
Preparing to replace kdelibs-data 4:3.5.10.dfsg.1-3 (using 
.../kdelibs-data_4%3a3.5.10.dfsg.1-4_all.deb) ...
Unpacking replacement kdelibs-data ...
dpkg: error processing 
/var/cache/apt/archives/kdelibs-data_4%3a3.5.10.dfsg.1-4_all.deb (--install):
 trying to overwrite '/usr/share/doc/kde/HTML/en/common/6.png', which is also 
in package kdelibs5-data 4:4.4.5-1
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for desktop-file-utils ...
Errors were encountered while processing:
 /var/cache/apt/archives/kdelibs-data_4%3a3.5.10.dfsg.1-4_all.deb
# find /usr -name "*.dpkg-tmp" | wc -l
4217
#

So dpkg litters dpkg-tmp files. Note that no packages are in a state other than
ii, rc or pn. Removing the dpkg-tmp files and unpacking again yields the same
result.

Helmut

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages dpkg depends on:
ii  coreutils         8.5-1                  GNU core utilities
ii  libbz2-1.0        1.0.5-4                high-quality block-sorting file co
ii  libc6             2.11.2-2               Embedded GNU C Library: Shared lib
ii  libselinux1       2.0.96-1               SELinux runtime shared libraries
ii  xz-utils          4.999.9beta+20100713-1 XZ-format compression utilities
ii  zlib1g            1:1.2.3.4.dfsg-3       compression library - runtime

Versions of packages dpkg suggests:
ii  apt                           0.7.25.3   Advanced front-end for dpkg




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to