Package: src:ipy
Version: 1:1.01-4
Severity: important
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-nocheck-profile
Dear maintainer:
During a rebuild of all packages in unstable using the nocheck build profile,
your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules clean
py3versions: no X-Python3-Version in control file, using supported versions
dh clean --with python3
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
py3versions: no X-Python3-Version in control file, using supported versions
dh_auto_clean
make -j2 clean
make[2]: Entering directory '/<<PKGBUILDDIR>>'
rm -rf IPy.html *.pyc build dist IPy.egg-info
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
rm -rf /<<PKGBUILDDIR>>/build
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_clean
debian/rules binary
py3versions: no X-Python3-Version in control file, using supported versions
make: *** No rule to make target 'test/test-3.13-stamp', needed by
'binary-indep'. Stop.
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202504/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:ipy, so that this is still
visible in the BTS web page for this package.
Notes:
* When a package is built with the nocheck profile, it means:
- DEB_BUILD_OPTIONS=nocheck
(the tests should be skipped during the build)
- DEB_BUILD_PROFILES=nocheck
(Build-Depends marked <!nocheck> are not installed)
- The contents of the package is allowed to be different than normal
* This category of bugs was going to be RC for trixie, but
according to the Release Managers it's a little bit late in the
release cycle to introduce a bunch of RC bugs of this type.
* In addition to the above, this package also fails when
using DEB_BUILD_OPTIONS=nocheck alone. In this mode:
- DEB_BUILD_OPTIONS=nocheck
(the tests should be skipped during the build)
- Build-Depends marked <!nocheck> are installed as normal
- The contents of the package should not change compared
to a regular build
Thanks.
