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

[Julian Andres Klode <jak@debian.org>]

Control: clone -1 -2
Control: reassign -2 src:libcdio
Control: retitle -2 libcdio-dev: Causes every apt command to argue about unknown Multi-Arch type
Control: severity -2 minor

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").

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.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

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

Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
    - If you don't I might ignore you.