Hi, >> Current unstable and sid. > > probably "wheezy and sid" which both have dpkg 1.16.8 Uhm, sorry, you are right of course.
> To avoid this bug, there is still a possibility to split out a -common > package. The bug is only triggered by calling dpkg with both architectures of the package at once, so most people will not hit it initially but only on the first succeeding package upgrade. But yes, splitting the conffile would be possible, though I am not sure it's a good idea to complicate the package so much for working around a dpkg bug. I had already done that before the dpkg guys told me that conffile in MA: same are actually supported, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640499#41 > I'm now trying another approach (that will need a minor modification of > n-g-d, too) > > http://bugs.debian.org/688861 > > http://mentors.debian.net/debian/pool/main/libx/libxvmc/libxvmc_1.0.7-1.1.dsc Interesting, so you think this has a better chance than multiarchifying libxvmc itself? However, in n-g-d I think it should be something like libxvmc1-i386 [i386] | libxvmc1 as dependency since the first alternative is what apt-get and aptitude usually try to install (and I don't think they are smart enough to re-try another alternative if a conflict arises). Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
