Bug#759099: libcdio-dev: Causes every apt command to argue about unknown Multi-Arch type

[Guillem Jover <guillem@debian.org>]

Hi!

On Sun, 2014-08-24 at 13:37:40 +0200, Julian Andres Klode wrote:
> On Sun, Aug 24, 2014 at 01:27:34PM +0200, Julian Andres Klode wrote:
> > Am 24.08.2014 11:56 schrieb "Jakub Wilk" <jwilk@debian.org>:
> > >
> > > * Axel Beckert <abe@debian.org>, 2014-08-24, 11:39:
> > >
> > >> $ apt-cache policy foobar
> > >> W: Unknown Multi-Arch type 'no' for package 'libcdio-dev'
> > >> W: Unknown Multi-Arch type 'no' for package 'libiso9660-dev'
> > >> W: Unknown Multi-Arch type 'no' for package 'libudf-dev'
> > >
> > > According to deb-control(5), "no" is a valid value for the Multi-Arch
> > > field. (Although it's the default, so it would be probably better to omit
> > > the field.)
> > 
> > The multi arch spec and APT use "none", not " no" - first time I heard of
> > "no". When was that changed, why, and why do I hear of it the first time
> > today?
> 
> Clarification after checking source code: APT does not parse none
> either. But I still wonder why this was changed to "no" in dpkg when
> anyone else uses none (even APT internally uses none as the term, not
> "no").

dpkg never changed the value, it's been “no” since the beginning, even
the MultiArch spec listed it as “no”, but it had some pretty recent
broken updates which changed that (those need to be reverted as I
mentioned in #732648), it was just not documented in deb-control(5),
which got fixed in dpkg commit c4ce860fdea16610e0c065cb265a24048a04c17c.

See commit e215e2795f47feec839025972ac56e647ab04822 when this got
introduced in dpkg.

> For Nicolas Boullis <nboullis@debian.org>:
> Still, for compatibility with stable, please just remove the multi-arch
> field from libcio. It is entirely useless. Otherwise we just get annoying
> warnings when people upgrade from wheezy.

Those warnings are broken, this has been defined this way since the
beginning.

Thanks,
Guillem