[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: binNMUing on some architectures breaks Multi-arch: same

On Sat, Apr 07, 2012 at 10:56:27AM +0100, Adam D. Barratt wrote:
> On Sat, 2012-04-07 at 11:52 +0200, Julian Andres Klode wrote:
> > it seems that libffi5 received a binNMU on armhf. As libffi5 is
> > marked Multi-arch: same, it is now not possible to have the armhf
> > version installed on an amd64 system, as the armhf version has a
> > binNMU and the amd64 one does not have one.
> fwiw, although you say "now not", the binNMU was scheduled in early
> December so "has not been possible for more than five months" would be
> more accurate.

Right, but I only started playing with multi-arch in Debian today, so
I did not notice it before. And the problem did not appear in Ubuntu
either, since there are no binNMUs in Ubuntu.

Discussion in Bug#595139 led to the conclusion that packages which are
Multi-arch: same must not be binNMUed (or in fact, binNMUed on all

So, a solution would be to add code to your tools to prevent Multi-arch:
same packages from being binNMUed on a subset of the architectures (or at
all) and upload sourceful NMUs for the affected packages.

Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Reply to: