Package: src:tex-fmt
Version: 0.5.2+dfsg-2
Severity: important
Tags: trixie sid ftbfs
User: debian...@lists.debian.org
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
dh clean --buildsystem=cargo --with shell_completions
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_clean
debian cargo wrapper: options = ['parallel=2', 'nocheck'], profiles =
['nocheck'], parallel = ['-j2'], lto =
debian cargo wrapper: rust_type = x86_64-unknown-linux-gnu, gnu_type =
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', 'clean', '--verbose', '--verbose'],) {'check': True}
Removed 0 files
rm -rf debian/cargo_registry
rm -f debian/cargo-checksum.json
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_autoreconf_clean -O--buildsystem=cargo
dh_clean -O--buildsystem=cargo
debian/rules binary
dh binary --buildsystem=cargo --with shell_completions
dh_update_autotools_config -O--buildsystem=cargo
dh_autoreconf -O--buildsystem=cargo
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
/usr/share/cargo/bin/cargo prepare-debian
/<<PKGBUILDDIR>>/debian/cargo_registry --link-from-system
debian cargo wrapper: options = ['parallel=2', 'nocheck'], profiles =
['nocheck'], parallel = ['-j2'], lto =
debian cargo wrapper: rust_type = x86_64-unknown-linux-gnu, gnu_type =
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<<PKGBUILDDIR>>/debian/cargo_registry/
rm -f Cargo.lock
touch debian/cargo-checksum.json
dh_auto_configure
debian cargo wrapper: options = ['parallel=2', 'nocheck'], profiles =
['nocheck'], parallel = ['-j2'], lto =
debian cargo wrapper: rust_type = x86_64-unknown-linux-gnu, gnu_type =
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<<PKGBUILDDIR>>/debian/cargo_registry/
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build -O--buildsystem=cargo
dh: command-omitted: The call to "dh_auto_test -O--buildsystem=cargo" was
omitted due to "DEB_BUILD_OPTIONS=nocheck"
create-stamp debian/debhelper-build-stamp
dh_testroot -O--buildsystem=cargo
dh_prep -O--buildsystem=cargo
debian/rules execute_before_dh_auto_install
make[1]: Entering directory '/<<PKGBUILDDIR>>'
target/*/debug/tex-fmt --man > debian/tex-fmt.1
/bin/sh: 1: target/*/debug/tex-fmt: not found
make[1]: *** [debian/rules:29: execute_before_dh_auto_install] Error 127
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:15: binary] Error 2
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:tex-fmt, 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.
