Package: src:ifupdown-ng Version: 0.12.1-7 Severity: serious Tags: ftbfs trixie sid
Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: -------------------------------------------------------------------------------- [...] Metadata: allowed_architectures is empty allowed_platforms is empty description is empty has_cleanup = false is_exclusive = false required_configs is empty required_disk_space = 0 required_files is empty required_memory = 0 required_programs is empty required_user is empty timeout = 300 Standard output: Executing command [ ifupdown ifquery -F ] Standard error: atf-check: ERROR: Caught unexpected error: cannot create std::vector larger than max_size() ===> Failed tests tests/multicall_test:regress_getopt -> failed: atf-check failed; see the output of the test for details [0.010s] ===> Summary Results read from /<<PKGBUILDDIR>>/debian/.debhelper/generated/_source/home/.kyua/store/results.build_ifupdown-ng-WTdaGr_ifupdown-ng-0.12.1.20250507-080533-512860.db Test cases: 185 total, 0 skipped, 0 expected failures, 0 broken, 1 failed Start time: 2025-05-07T08:05:33.534515Z End time: 2025-05-07T08:05:37.038130Z Total time: 2.999s make[2]: *** [Makefile:146: check] Error 1 make[2]: Leaving directory '/<<PKGBUILDDIR>>' dh_auto_test: error: make -j2 check returned exit code 2 make[1]: *** [debian/rules:72: override_dh_auto_test] Error 25 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:8: 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/202505/ 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:ifupdown-ng, so that this is still visible in the BTS web page for this package. Thanks.