Package: src:jujutsu
Version: 0.43.0-1
Severity: serious
Tags: forky sid ftbfs
User: [email protected]
Usertags: ftbfs-nocheck-profile

Dear maintainer:

During a rebuild of all packages in unstable using the nocheck build profile,
this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202607/

A wiki page discussing how to reproduce bugs in this category and
possible solutions is available here:

https://wiki.debian.org/qa.debian.org/FTBFS/nocheck

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 cannot 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:jujutsu, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean --buildsystem=cargo --with=shell-completions
   dh_auto_clean -O--buildsystem=cargo
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
   debian/rules execute_after_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -rf debian/cargo_registry debian/man debian/jujutsu.bash-completion
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 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', '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 debian/cargo-checksum.json
touch debian/cargo-checksum.json
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_auto_configure -O--buildsystem=cargo
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/
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
/usr/share/cargo/bin/cargo tree --workspace --color=never
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', 'tree', '--workspace', '--color=never'],) {}
error: no matching package named `assert_cmd` found
location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
required by package `jj-cli v0.43.0 (/<<PKGBUILDDIR>>/cli)`
make[1]: *** [debian/rules:34: override_dh_auto_build] Error 101
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:15: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2
--------------------------------------------------------------------------------

Reply via email to