Package: dpkg
Version: 1.16.8
Severity: important
Dear Maintainer,
during an update I run into th following situation:
---8<---
libqtcore4 : Breaks: libqtcore4:i386 (!= 4:4.8.2-2) but 4:4.8.2-2+b1 is
installed
libqtcore4:i386 : Breaks: libqtcore4 (!= 4:4.8.2-2+b1) but 4:4.8.2-2 is
installed
---8<---
Trying to install libqtcore4 by hand results in:
---8<---
# LANG=C dpkg -i /var/cache/apt/archives/libqtcore4_4%3a4.8.2-2+b1_amd64.deb
(Reading database ... 328035 files and directories currently installed.)
Preparing to replace libqtcore4:amd64 4:4.8.2-2 (using
.../libqtcore4_4%3a4.8.2-2+b1_amd64.deb) ...
Unpacking replacement libqtcore4:amd64 ...
dpkg: error processing
/var/cache/apt/archives/libqtcore4_4%3a4.8.2-2+b1_amd64.deb (--install):
trying to overwrite shared
'/usr/share/doc/libqtcore4/changelog.Debian.gz', which is different
from other instances of package libqtcore4:amd64
Errors were encountered while processing:
/var/cache/apt/archives/libqtcore4_4%3a4.8.2-2+b1_amd64.deb
#
---8<---
It seems to me, that dpkg is unable to handle the "+bX" version in
a correct manner. For my understanding the version "a.b.c+bX" should be
handled as eaqual to version "a.b.c" in this case.
Regards
Bene
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.6-4
ii libc6 2.13-35
ii liblzma5 5.1.1alpha+20120614-1
ii libselinux1 2.1.9-5
ii tar 1.26-4
ii zlib1g 1:1.2.7.dfsg-13
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 0.9.7.4
-- no debconf information
--
Linutronix GmbH
Phone: +49 7556 91 98 91; Fax.: +49 7556 91 98 86
Firmensitz: D-88690 Uhldingen, Auf dem Berg 3
Registergericht: Freiburg i. Br., HRB 700 806;
Geschäftsführer: Heinz Egger, Thomas Gleixner
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]