Source: barrier
Version: 2.4.0+dfsg-4
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: [email protected]
Usertags: qa-doublebuild

Hi,

This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild

Relevant part of the build log:
> [----------] Global test environment tear-down
> [==========] 20 tests from 5 test suites ran. (2691 ms total)
> [  PASSED  ] 17 tests.
> [  FAILED  ] 3 tests, listed below:
> [  FAILED  ] XWindowsKeyStateTests.mapModifiersToX_zeroMask_resultIsTrue
> [  FAILED  ] 
> XWindowsKeyStateTests.pollActiveModifiers_shiftKeyDownThenUp_masksAreCorrect
> [  FAILED  ] XWindowsKeyStateTests.pollActiveGroup_positiveGroup_returnsGroup
> 
>  3 FAILED TESTS
>   YOU HAVE 1 DISABLED TEST
> 
> make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> make: *** [debian/rules:20: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> 
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -b' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/16/barrier_2.4.0+dfsg-4_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to