| |||||||||||||
Debian "sid" users beware of the dpkg 1.16.2 uploadDebian "sid" users beware of the dpkg 1.16.2 uploadPosted Mar 15, 2012 12:34 UTC (Thu) by Jonno (subscriber, #49613)In reply to: Debian "sid" users beware of the dpkg 1.16.2 upload by rhertzog Parent article: Debian "sid" users beware of the dpkg 1.16.2 upload 2/ While it is not possible to have different versions of a package installed, you could have more than one package configured, by simply first removing the old version without using --purge, and then installing the new version from another arch. If one of these versions are Multi-arch: same while the other isn't, you get the problem he describes.
(Log in to post comments)
Debian "sid" users beware of the dpkg 1.16.2 upload Posted Mar 15, 2012 13:23 UTC (Thu) by rhertzog (subscriber, #4671) [Link]
Indeed, thank you, that's a way to get in the situation described.
But realistically for this to happen, it means that either have you have removed (without purging) the native version of the package while it wasn't multi-arch aware yet and you later installed a foreign version of the package once it has been converted to multi-arch.
Or you had only a foreign version of the package installed (before its conversion to multi-arch), that you removed and now you installed the native one after its conversion.
Because as soon as you have two versions co-installed at a given time, it means that the field was present.
Anyway, I just reproduced it here (need squeeze + wheezy in sources.list):
So the two problems are real even if relatively unlikely on a typical usage of multiarch.
Again thank you, at least I could test that my script was working as expected :-)
|
|||||||||||||