Hi! On Mon, 2012-08-13 at 20:45:08 +0200, Ralf Jung wrote: > Package: dpkg > Version: 1.16.4.3 > Severity: normal
> when an MA: same package contains a conffile, re-installing it causes dpkg to > error out, complaining that the content of the conffile differs between the > architectures - even though it does not. > > To reproduce (on current testing): > I assume an amd64 system with i386 as foreign architecture. libpam- > modules:amd64 is installed, libpam-modules:i386 is not. > $ sudo dpkg --install libpam-modules_1.1.3-7.1_i386.deb > (working all right - the dependencies must already be installed) > $ sudo dpkg --install libpam-modules_1.1.3-7.1_amd64.deb libpam- > modules_1.1.3-7.1_i386.deb > (Reading database ... 227374 files and directories currently installed.) > Preparing to replace libpam-modules:amd64 1.1.3-7.1 (using libpam- > modules_1.1.3-7.1_amd64.deb) ... > Unpacking replacement libpam-modules:amd64 ... > Preparing to replace libpam-modules:i386 1.1.3-7.1 (using libpam- > modules_1.1.3-7.1_i386.deb) ... > Unpacking replacement libpam-modules:i386 ... > dpkg: error processing libpam-modules_1.1.3-7.1_i386.deb (--install): > trying to overwrite shared '/etc/security/limits.conf', which is different > from other instances of package libpam-modules:i386 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > Setting up libpam-modules:amd64 (1.1.3-7.1) ... > Processing triggers for man-db ... > Errors were encountered while processing: > libpam-modules_1.1.3-7.1_i386.deb > > Interesting enough, if I reinstall just one of the two packages, things work > fine. Only if I tell dpkg to reinstall both architectures at the same time, > above error shows up. > This is not specific to libpam-modules (for which I reported this as bug [1]), > it also happens in my local multiarched version of libxvmc [2], which has a > conffile as well. Yeah, reproduced here, and looking into it right now. I have a hunch I've already fixed this in my 1.17.x branch, though. thanks, guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
