Package: src:bpftop Version: 0.5.2.20.gc23a822-2 Severity: serious Tags: ftbfs forky sid
Dear maintainer: During a rebuild of all packages in unstable, your package failed to build. Below you will find how the build ends (probably the most relevant part, but not necessarily). If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202509/ 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:bpftop, so that this is still visible in the BTS web page for this package. Thanks. -------------------------------------------------------------------------------- [...] debian/rules clean dh clean --buildsystem=cargo dh_auto_clean -O--buildsystem=cargo debian cargo wrapper: options = ['parallel=2'], profiles = [], 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 debian/rules execute_after_dh_auto_clean make[1]: Entering directory '/<<PKGBUILDDIR>>' 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 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 debian/cargo_registry --link-from-system debian cargo wrapper: options = ['parallel=2'], profiles = [], 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'], profiles = [], 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_auto_test -O--buildsystem=cargo debian cargo wrapper: options = ['parallel=2'], profiles = [], 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', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j2', '--target', 'x86_64-unknown-linux-gnu'],) {} error: failed to select a version for the requirement `libbpf-rs = "=0.25.0-beta.1"` candidate versions found which didn't match: 0.26.0-beta.1 location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` (which is replacing registry `crates-io`) required by package `bpftop v0.5.2 (/<<PKGBUILDDIR>>)` if you are looking for the prerelease package it needs to be specified explicitly libbpf-rs = { version = "0.26.0-beta.1" } perhaps a crate was updated and forgotten to be re-vendored? dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 make: *** [debian/rules:15: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------
