Add multiarch metadata for check

[Wookey]

This package needs to be marked 'Multi-Arch: foreign' for
dependencies and build-depencies to work correctly in all cases.

Any package 'X' build-depending on check cannot be cross-built
because apt-get build-dep -a<arch> cannot satisfy X's
build-dependencies until

Multi-Arch: foreign

is added to check's control file, to indicate that check from
any available arch will satisfy the dependency. (Is is actually the
case that check will always work correctly across architectures - it
looked like it to me but I am not familiar with its operation, so
maybe there could be problems? It worked OK in local tests for the
arm64 bootstrap).

There are 114 packages which can't be cross-built until this change
is made.

[Dimitri John Ledkov (xnox)]

* wrong version number used: should be 0.9.8-2ubuntu1 (for devel release, or 0.9.8-2ubuntu0.1 for sru)
* wrong target distribution: should be raring (for devel release)
* maintainer & original-maintainer fields are not updated

please re-subscribe sponsors team when corrected debdiff is available, or somebody else adjusts the attached patch and uploads this fix.

[Dimitri John Ledkov (xnox)]

also I'm not sure about check, it's a C unit-test framework, and one compiles tests for the --host-arch & then executes them. But in the case of cross-compilation, one will not be able to execute them. Hence the following should be done:
- check properly multiarch (m-a: same)
or
cross-compile with DEB_BUILD_OPTIONS=nocheck and in this case package should be modified not to search for check nor try to statically link it in.

[Wookey (wookey)]

+++ Dmitrijs Ledkovs [2013-01-18 10:49 -0000]:
> also I'm not sure about check, it's a C unit-test framework, and one compiles tests for the --host-arch & then executes them. But in the case of cross-compilation, one will not be able to execute them. Hence the following should be done:
> - check properly multiarch (m-a: same)
> or
> cross-compile with DEB_BUILD_OPTIONS=nocheck and in this case package should be modified not to search for check nor try to statically link it in.

This already seems to work fine in practice (so long as the built
package supports nocheck, which most do).

One we have BUILD PROFILE support we could annotate the dependency not
to be needed at all, but in the meantime not having this marked
foreign means lots of packages can't have their cross- build-deps
installed.

Hmm. I had assumed check was a utility but in fact it's a
library so probably should be MA: same. at which point things will
'just work'. OK. Well spotted.

Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/

[Launchpad Janitor (janitor)]

This bug was fixed in the package check - 0.9.8-2ubuntu1

---------------
check (0.9.8-2ubuntu1) raring; urgency=low

  * Convert to Multi-Arch: same (LP: #1101069).
  * Remove obsolete debian/check.files (since we no longer use
    dh_movefiles), and remove a related hack in debian/rules.
 -- Colin Watson <email address hidden> Thu, 07 Feb 2013 17:01:11 +0000