Bug#759099: libcdio-dev: Causes every apt command to argue about unknown Multi-Arch type
Hi,
Julian Andres Klode wrote:
> >> > > 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"
JFTR, this seems to refer to https://wiki.ubuntu.com/MultiarchSpec and
it indeed claims "none".
> >> > first time I heard of "no". When was that changed, why, and why
> >> > do I hear of it the first time today?
[...]
> > 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),
vorlon seems to have already reverted some of these changes, but not
that one.
> OK thanks, it's always been called none outside of dpkg, though, as
> far as I can remember, the earliest source being from February 2011:
> https://lists.debian.org/debian-dpkg/2011/02/msg00051.html
So can please someone with the appropriate write permissions fix it in
the Ubuntu wiki to avoid further such damage in Debian? Thanks.
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
Reply to: