Source: rust-coreutils
Version: 0.0.24-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64.


Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> cargo test  --features "base32 base64 basename cat chgrp chmod chown cksum 
> comm cp csplit cut date dircolors dirname echo env expr factor false fold 
> hashsum head install link ln ls mkdir mktemp mv nl numfmt od paste pathchk 
> pinky pr printf ptx pwd readlink realpath rm rmdir seq sort split stat stdbuf 
> sum tac tail test touch tr true truncate tsort uname unexpand uniq unlink wc 
> who " --no-default-features 
> error: failed to select a version for the requirement `uutils_term_grid = 
> "^0.3"`
> candidate versions found which didn't match: 0.6.0
> location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` 
> (which is replacing registry `crates-io`)
> required by package `uu_ls v0.0.24 (/<<PKGBUILDDIR>>/src/uu/ls)`
> perhaps a crate was updated and forgotten to be re-vendored?
> make[2]: *** [GNUmakefile:289: test] Error 101


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/rust-coreutils_0.0.24-2_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240420&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to