[Helmut Grohne]
> I traced down the debhelper git history and it did that since the
> invention of dh_auto_test in version 7.0.0. Support for nocheck came
> later.
Thank you for checking. The build depend is already on dh >= 9, so
there should be no chance of creating a broken package.
--
Happy
On Mon, Nov 13, 2017 at 06:33:20AM +0100, Petter Reinholdtsen wrote:
> I added this in 2014, to ensure it was impossible for a autobuilder to
> build a package that did not handle the test suite, to avoid ending up
> with unbootable systems on some of the less used architectures. I
> believe this
[Helmut Grohne]
> I'm sorry and stand corrected. Thank you for insisting. The patch is
> applied in git and in unstable.
No worries. Then I know we talk about the same thing. No need to
apology.
> The problem now is: Someone added the check target to dh_auto_build
> for running tests. Now tests
On Sun, Nov 12, 2017 at 08:58:44AM +0100, Petter Reinholdtsen wrote:
> I do not understand. The change is in commit
> 82b9903afb8b5d7d5b5d4e44e375d1eedc50 in git, which should have been
> included in 0.59-3.2.
I'm sorry and stand corrected. Thank you for insisting. The patch is
applied in git
[Helmut Grohne]
> The patch was not applied. The changelog entry is simply wrong. It
> still fails in the very same way. You can try yourself with sbuild
> --host or pbuilder --host-arch.
I do not understand. The change is in commit
82b9903afb8b5d7d5b5d4e44e375d1eedc50 in git, which should h
On Sun, Nov 12, 2017 at 08:05:53AM +0100, Petter Reinholdtsen wrote:
> Hi. Why was the cross build bug reopened? Was the fix in 0.59-3.2
> not working?
The patch was not applied. The changelog entry is simply wrong. It still
fails in the very same way. You can try yourself with sbuild --host or
Hi. Why was the cross build bug reopened? Was the fix in 0.59-3.2
not working?
--
Happy hacking
Petter Reinholdtsen
7 matches
Mail list logo
