Bug#759101: lintian: Error level warning for unknown "Multi-Arch" field values in source and binary packages

[Axel Beckert <abe@debian.org>]

Control: retitle -1 Minor warning if "Multi-Arch: no" is used as it's the default

Axel Beckert wrote:
> the recent upload of libcdio 0.92-1 to experimental causes nearly every
> APT-based command (at least "apt-get update", "apt-cache policy foobar",
> "apt-get source libcdio=0.92-1", and "aptitude" to argue about an
> unknown Multi-Arch type:
> 
> $ 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'
> W: You may want to run apt-get update to correct these problems
> N: Unable to locate package foobar
> $
> 
> (See https://bugs.debian.org/759099 for the according report.)

This turned out to be an apt issue. "no" is acutally a valid value,
but yet unused as it's the default.

And since dpkg-deb seems to bail out on any non-valid value, there's
no need for an lintian error level warning. A pedantic level warning
about explicitly setting a default value may be still helpful. See
Jakub's comment in #759099.

		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