Your message dated Thu, 18 Jan 2024 17:06:33 +0000
with message-id <50056ac8-ef62-47b3-98b0-457ae964d...@p10link.net>
and subject line re: [Pkg-rust-maintainers] Bug#1061112:
src:rust-cargo-auditable: unsatisfied build dependency in testing:
librust-object-0.31+write-dev
has caused the Debian Bug report #1061112,
regarding src:rust-cargo-auditable: unsatisfied build dependency in testing:
librust-object-0.31+write-dev
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.)
--
1061112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-cargo-auditable
Version: 0.6.1-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency (or actually, the right version if I understand the
rust ecosystem well enough). Obviously your build dependencies shouldn't
be removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.
Can you please investigate the situation and figure out how to resolve
it? I note that this package already has a newer version in unstable,
but that fails to migrate to testing because it's coupled to another
Build-Depends that isn't ready to migrate. Regularly, if the build
dependency is available in unstable, helping the maintainer of your
Build-Depends to enable migration to testing is a great way to solve the
issue. If your build dependency is gone from unstable and testing,
you'll have to fix the build process in some other way.
Paul
Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.
[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.6.1-3
Can you please investigate the situation and figure out how to resolve
it?
The bug is fixed in unstable, but is failing to migrate because it
has picked up a "built-using" on the new version of rust-ahash-0.7
which in turn has failing autopkgtests.
I'll go investigate and file a bug.
--- End Message ---
