Your message dated Thu, 4 Jul 2024 20:21:31 +0100 with message-id <752bf9d7-d6c7-7dcf-b829-465562688...@debian.org> and subject line re: Bug#1074713: rust-debian-analyzer: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101 has caused the Debian Bug report #1074713, regarding rust-debian-analyzer: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1074713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: rust-debian-analyzer Version: 0.156.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240702 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > dh_auto_test -- test --all > debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] > ['-j8'] 0 > debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, > x86_64-linux-gnu > debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', > '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', > '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {} > error: failed to get `breezyshim` as a dependency of package `debian-analyzer > v0.156.0 (/<<PKGBUILDDIR>>)` > > Caused by: > failed to load source for dependency `breezyshim` > > Caused by: > Unable to update registry `crates-io` > > Caused by: > failed to update replaced source registry `crates-io` > > Caused by: > failed to parse manifest at > `/<<PKGBUILDDIR>>/debian/cargo_registry/pyo3-filelike-0.2.0/Cargo.toml` > > Caused by: > dependency (pyo3) specified without providing a local path, Git repository, > version, or workspace dependency to use > dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code > 101 The full build log is available from: http://qa-logs.debian.net/2024/07/02/rust-debian-analyzer_0.156.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&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.
--- End Message ---
--- Begin Message ---This was fixed by the upload of rust-pyo3-filelike 0.2.0-2
--- End Message ---
