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

[Manuel A. Fernandez Montecelo]

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 
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
 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 

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

[Julien Cristau]

Control: tag -1 - moreinfo

On Sat, Oct  8, 2016 at 14:37:16 +0200, Helmut Grohne wrote:

> Hi Julien,
> 
> On Sat, Oct 08, 2016 at 11:47:29AM +0200, Julien Cristau wrote:
> > Is there a reason cmdtest can't be m-a: foreign?  Wouldn't that fix the
> > issue as well?
> 
> I agree that marking cmdtest m-a:foreign would fully resolves this bug.
> 
> I'm less sure that such a marking would be correct. cmdtest includes a
> python module yarnlib, which uses architecture dependent Python
> extensions. It seems to me that putting it in a m-a:foreign package runs
> afoul the multi-arch interpreter problem.
> 
> So the correct solution could be splitting cmdtest into python-yarnlib,
> switching users of yarnlib over to the separate package and then marking
> cmdtest m-a:foreign.
> 
Thanks for the explanation.

Cheers,
Julien

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

[Helmut Grohne]

Hi Julien,

On Sat, Oct 08, 2016 at 11:47:29AM +0200, Julien Cristau wrote:
> Is there a reason cmdtest can't be m-a: foreign?  Wouldn't that fix the
> issue as well?

I agree that marking cmdtest m-a:foreign would fully resolves this bug.

I'm less sure that such a marking would be correct. cmdtest includes a
python module yarnlib, which uses architecture dependent Python
extensions. It seems to me that putting it in a m-a:foreign package runs
afoul the multi-arch interpreter problem.

So the correct solution could be splitting cmdtest into python-yarnlib,
switching users of yarnlib over to the separate package and then marking
cmdtest m-a:foreign.

Given the necessary package split here, I considered annotating
Build-Depends of 5 packages more economical. If you disagree with that
trade-off, I suggest:

tags -1 - moreinfo patch
reassign -1 cmdtest
retitle -1 make cmdtest m-a:foreign

Helmut

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

[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 
> 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?

Cheers,
Julien

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

[Helmut Grohne]

Source: xauth
Version: 1:1.0.9-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

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 
profile. After doing that, it cross builds just fine. Please consider
applying the attached patch.

Helmut
diff -u xauth-1.0.9/debian/changelog xauth-1.0.9/debian/changelog
--- xauth-1.0.9/debian/changelog
+++ xauth-1.0.9/debian/changelog
@@ -1,3 +1,11 @@
+xauth (1:1.0.9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Cross satisfiable Build-Depends: annotate cmdtest with 
+(Closes: #-1).
+
+ -- Helmut Grohne   Sat, 08 Oct 2016 08:09:12 +0200
+
 xauth (1:1.0.9-1) unstable; urgency=medium
 
   * New upstream release.
diff -u xauth-1.0.9/debian/control xauth-1.0.9/debian/control
--- xauth-1.0.9/debian/control
+++ xauth-1.0.9/debian/control
@@ -11,7 +11,7 @@
  libxext-dev (>= 1:1.0.0),
  libxmuu-dev (>= 1:1.0.1),
  xutils-dev (>= 1:7.5+4),
- cmdtest,
+ cmdtest ,
 Standards-Version: 3.9.2
 Vcs-Git: git://git.debian.org/git/pkg-xorg/app/xauth
 Vcs-Browser: http://git.debian.org/?p=pkg-xorg/app/xauth.git