Package: src:sourmash Version: 4.8.14-3 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:sourmash, so that this is still visible in the BTS web page for this package. Thanks. -------------------------------------------------------------------------------- [...] debian/rules clean dh clean --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild pybuild --clean -i python{version} -p 3.13 rm -rf .pybuild/ find . -name \*.pyc -exec rm {} \; debian/rules execute_after_dh_auto_clean make[1]: Entering directory '/<<PKGBUILDDIR>>' rm -rf debian/cargo_registry make[1]: Leaving directory '/<<PKGBUILDDIR>>' dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild rm -f debian/debhelper-build-stamp rm -rf debian/.debhelper/ rm -f -- debian/sourmash.substvars debian/files rm -fr -- debian/sourmash/ debian/tmp/ find . \( \( \ \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o -type f -a \ \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \ -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \ -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \ -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \ \) -exec rm -f {} + \) -o \ \( -type d -a \( -name autom4te.cache -o -name __pycache__ \) -prune -exec rm -rf {} + \) \) debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild debian/rules execute_before_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 # needed because we patch Cargo.toml cargo generate-lockfile --manifest-path src/core/Cargo.toml --offline 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', 'generate-lockfile', '--manifest-path', 'src/core/Cargo.toml', '--offline'],) {} error: failed to select a version for the requirement `typed-builder = "^0.20"` candidate versions found which didn't match: 0.21.2 location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` (which is replacing registry `crates-io`) required by package `sourmash v0.18.0 (/<<PKGBUILDDIR>>/src/core)` perhaps a crate was updated and forgotten to be re-vendored? As a reminder, you're using offline mode (--offline) which can sometimes cause surprising resolution failures, if this error is too confusing you may wish to retry without the offline flag. make[1]: *** [debian/rules:35: execute_before_dh_auto_configure] Error 101 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:23: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------
