[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#840085: xauth FTCBFS: unsatisfiable cross Build-Depends: cmdtest



Hi,

2016-10-08 11:47 Julien Cristau:
Control: tag -1 moreinfo

On Sat, Oct  8, 2016 at 08:12:57 +0200, Helmut Grohne wrote:

xauth cannot satsify its cmdtest dependency during cross building,
because cmdtest is Architecture:all Multi-Arch:no. Fortunately, cmdtest
is only needed for testing, so we can simply annotate it with <!nocheck>
profile. After doing that, it cross builds just fine. Please consider
applying the attached patch.

Hi Helmut,

Is there a reason cmdtest can't be m-a: foreign?  Wouldn't that fix the
issue as well?

I'm not sure how the situation with cmdtest evolved since this bug was
reported, it seems like it was not marked "Multi-Arch: foreign" in the
end.

Independently of that, I think that the request to annotate with
<!nocheck> is a more correct solution no matter what happens with
cmdtest, because adding the profile info to the dependency avoids having
to install dependencies which are not actually needed if one uses for
DEB_BUILD_OPTIONS=nocheck, for example, which is a quite established
method and covered in Policy.

This is a common scenario when bootstrapping new architectures,
"cmdtest" might not be available for multiple reasons -- e.g. python,
python-markdown or any of the other dependencies might not be available
at the time when one wants to build xauth.

In any case, if one wants to build with "nocheck" options, Python would
not have to be installed as build-depends, which is a quite significant
saving.

From the point of view of xauth itself, is there any reason against
using this solution?


Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo@gmail.com>


Reply to: