Your message dated Thu, 06 Dec 2018 18:27:22 +0100 with message-id <[email protected]> and subject line Re: Bug#915557: libx11-xcb1: changelog.Debian.gz is not deleted when removing packag so next install fails has caused the Debian Bug report #915557, regarding libx11-xcb1: changelog.Debian.gz is not deleted when removing packag so next install fails 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 [email protected] immediately.) -- 915557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915557 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libx11-xcb1 Version: 2:1.6.4-3+deb9u1 Severity: important Dear Maintainer, * What led up to the situation? My installation of `wine` failed because, the installation of `libx11-xcb1` failed. ``` Unpacking libx11-xcb1:i386 (2:1.6.4-3+deb9u1) ... dpkg: error processing archive /tmp/apt-dpkg- install-1cFjeB/052-libx11-xcb1_2%3a1.6.4-3+deb9u1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libx11-xcb1/changelog.Debian.gz', which is different from other instances of package libx11-xcb1:i386 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Selecting previously unselected package libxi6:i386. ``` * What was the outcome of this action? My package database became unstable. * What outcome did you expect instead? Install without error. * Workaround? rm /usr/share/doc/libx11-xcb1/changelog.Debian.gz before installing helped. I assume it was not properly removed from the previous install and this prevented the new install (see error message above). -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libx11-xcb1 depends on: ii libc6 2.24-11+deb9u3 libx11-xcb1 recommends no packages. libx11-xcb1 suggests no packages.
--- End Message ---
--- Begin Message ---Am 04.12.2018 um 20:50 schrieb Sven Joachim: > Control: tags -1 + unreproducible > > Am 04.12.2018 um 21:19 schrieb Jens Getreu: > >> Package: libx11-xcb1 >> Version: 2:1.6.4-3+deb9u1 >> Severity: important >> >> Dear Maintainer, >> >> >> * What led up to the situation? >> >> My installation of `wine` failed because, the installation of `libx11-xcb1` >> failed. >> >> >> ``` >> Unpacking libx11-xcb1:i386 (2:1.6.4-3+deb9u1) ... >> dpkg: error processing archive /tmp/apt-dpkg- >> install-1cFjeB/052-libx11-xcb1_2%3a1.6.4-3+deb9u1_i386.deb (--unpack): >> trying to overwrite shared '/usr/share/doc/libx11-xcb1/changelog.Debian.gz', >> which is different from other instances of package libx11-xcb1:i386 >> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > > I cannot reproduce this. Downloaded both the amd64 and i386 version of > libx11-xcb1 from packages.debian.org, and their > /usr/share/doc/libx11-xcb1/changelog.Debian.gz files are identical: > > ,---- > | $ dpkg-deb -x libx11-xcb1_1.6.4-3+deb9u1_amd64.deb amd64 > | $ dpkg-deb -x libx11-xcb1_1.6.4-3+deb9u1_i386.deb i386 > | $ diff -sq {amd64,i386}/usr/share/doc/libx11-xcb1/changelog.Debian.gz > | Dateien amd64/usr/share/doc/libx11-xcb1/changelog.Debian.gz und > | i386/usr/share/doc/libx11-xcb1/changelog.Debian.gz sind identisch. > `---- And I just installed libx11-xcb1:amd64 and libx11-xcb1:i386 successfully in a stretch chroot. So there definitely was some snafu on your system, rather than a bug in the packages. > Indeed, but it also makes it impossible to get at the corrupted version > of this file on your system. So I think there is not much we can do. I'm closing the bug hereby. Good luck, Sven
--- End Message ---
