On 21/08/14 00:21, Guillem Jover wrote: > Control: forcemerge 684625 -1 > > On Tue, 2014-08-19 at 11:25:19 +0200, Emilio Pozuelo Monfort wrote: >> Package: dpkg >> Version: 1.17.11 >> Severity: wishlist > >> Currently M-A:same packages with different versions can't be co-installed. >> That prevents packages that have been binNMUed in one architecture but not >> another to be co-installed, e.g. >> >> libfoo_1.1-1:i386 >> libfoo_1.1-1+b1:amd64 >> >> or >> >> libfoo_1.1-1+b1:i386 >> libfoo_1.1-1+b2:amd64 >> >> Can't be co-installed. >> >> This is problematic because packages get binNMU on a subset of architectures >> very often (whenever it's not needed to binNMU them everywhere). >> >> See e.g. #758527. > > Yes, extensively discusssed in the mailing lists and already filed, > this is just a different side of the same assumptions. Merging.
I saw #684625 but thought it was the old problem that installing +b1:i386 and +b1:amd64 failed because of the different changelogs, problem that was solved / worked around by adding binnmu changelog entries in separate changelogs. Anyway, can you provide an update on this? Has there been any progress? Thanks, Emilio -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
