Your message dated Mon, 29 Jun 2026 19:33:48 +0000
with message-id <[email protected]>
and subject line Bug#1140999: fixed in precious 0.8.0+~0.2.1+20220602+~0.0.2-10
has caused the Debian Bug report #1140999,
regarding precious: FTBFS: error: failed to select a version for the
requirement `md-5 = "^0.10.6"`
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 [email protected]
immediately.)
--
1140999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140999
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:precious
Version: 0.8.0+~0.2.1+20220602+~0.0.2-9
Severity: serious
Tags: ftbfs forky sid
Dear maintainer:
During a rebuild of all packages in unstable, 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/202606/
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:precious, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean
dh_auto_clean --buildsystem=rust
/usr/share/dh-rust/bin/cargo clean
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] []
['-j2'] 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', 'clean', '--verbose', '--verbose'],) {'check': True}
Removed 0 files
dh_clean -XCargo.toml.orig
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=rust
/usr/share/dh-rust/bin/cargo prepare-debian debian/cargo_registry
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] []
['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<<PKGBUILDDIR>>/debian/cargo_registry/
cargo update
error: failed to select a version for the requirement `md-5 = "^0.10.6"`
candidate versions found which didn't match: 0.11.0
location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry`
(which is replacing registry `crates-io`)
required by package `precious-core v0.8.0 (/<<PKGBUILDDIR>>/precious-core)`
perhaps a crate was updated and forgotten to be re-vendored?
dh_auto_configure: error: cargo update returned exit code 101
make: *** [debian/rules:37: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit
status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: precious
Source-Version: 0.8.0+~0.2.1+20220602+~0.0.2-10
Done: Jonas Smedegaard <[email protected]>
We believe that the bug you reported is fixed in the latest version of
precious, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard <[email protected]> (supplier of updated precious package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 29 Jun 2026 21:11:34 +0200
Source: precious
Architecture: source
Version: 0.8.0+~0.2.1+20220602+~0.0.2-10
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard <[email protected]>
Changed-By: Jonas Smedegaard <[email protected]>
Closes: 1140999
Changes:
precious (0.8.0+~0.2.1+20220602+~0.0.2-10) unstable; urgency=medium
.
* tighten (build-)dependencies for crate md-5;
closes: bug#1140999, thanks to Santiago Vila
* use debhelper compatibility level 14 (not 13)
* reorganize patch naming and numbering
Checksums-Sha1:
3f56a80131c7b985c5a0db557347ae9655cbc394 3328
precious_0.8.0+~0.2.1+20220602+~0.0.2-10.dsc
4bb15350f9276e0ba6bf65991228341cfb094a65 10136
precious_0.8.0+~0.2.1+20220602+~0.0.2-10.debian.tar.xz
5c00dd0c4780e741ca6ba0529eb7e207ddcac903 21299
precious_0.8.0+~0.2.1+20220602+~0.0.2-10_amd64.buildinfo
Checksums-Sha256:
7952d7e74b1a3dcb3a0a5b078597bf2a179dc9a13a36d36427adb9e67a575dbc 3328
precious_0.8.0+~0.2.1+20220602+~0.0.2-10.dsc
e859b64e5e6d6a69cbd2808c956cd3a903841098580746e3acd0def99c1d315f 10136
precious_0.8.0+~0.2.1+20220602+~0.0.2-10.debian.tar.xz
23968a744db5150c94e7f1c3bb2715c7cf255beb798b692b636e2c2aee7b7b4f 21299
precious_0.8.0+~0.2.1+20220602+~0.0.2-10_amd64.buildinfo
Files:
b4103dcb6db34b6f03eebdc367674765 3328 devel optional
precious_0.8.0+~0.2.1+20220602+~0.0.2-10.dsc
5d3ab5d8463430440192abe131d8b566 10136 devel optional
precious_0.8.0+~0.2.1+20220602+~0.0.2-10.debian.tar.xz
06743dbdd2dbf6fc7c24f59de2f1baa7 21299 devel optional
precious_0.8.0+~0.2.1+20220602+~0.0.2-10_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmpCxSYMHGRyQGpvbmVz
LmRrAAoJECx8MUbBoAEhaFsP/1K0t4MbZhZ6idQWYC1xnoKgxBptTbgty765sun8
3M8oDLVPqx03jkbqbj4diDjdan1JEHxPAGtPKImPsBb9htwBJoXFp9MyqtsOS1qa
Z8EdxXzauY+KinvymPCLUjGfEgCWBZXR3b+IEiqBYuuF9r1rW9ruqNqXDytdveZo
tc8qZZwvVszEuRgq7Hl6CnA2EMDl/4X1W9X5Xy+BbrIyJ+vRyfdkxvv6rEd9GhPw
+pcEpsx0Ivm6YWMiYV3kK7LAp0I4RrdKO3KFOiNY2XHvIlka4NCeE23LbIVb2ucp
kBCzHPbBxC8ewlaH4tlyyr0dTE4To6pd+J9prbogLNy4div0YoAP06m/m0FlTH6G
Y/t+bCrA9Rd4rSRhk4hc95GI4GXHYu8Q1hLsq3FfrpnBuF65CtOj0/HoZWnaCvmA
NNIl0AEJIYBWS/RCd4PJoQrzotLs2B5ti35OWXDVw9+ziTbRIcOMadLaUg1W9StI
MQIId1RZoRuOZy2PE6lulc7Z8sl1sxWxQqLjX7TM8KcZfgIxxfSyM+1uAXIZjzk2
BHLo+3ALFmFcmARr136QZYmg8tZ8gr3M6NX50jiHEU4/4PY0DUAloGA0t/qC37wy
WmX6hrFD889H4gL0reJg3Tb4Ihq/XAR0n3B0fmRr2wlM4Rrd7k/TwSZ1WCveSAr7
Y9Kj
=ZMCe
-----END PGP SIGNATURE-----
pgpLtRwPwEYi5.pgp
Description: PGP signature
--- End Message ---
