Your message dated Thu, 17 Apr 2025 02:37:20 +0000
with message-id <e1u5f7w-00gury...@fasolo.debian.org>
and subject line Bug#1103300: fixed in rust-ring 0.17.14-2
has caused the Debian Bug report #1103300,
regarding rust-ring:FTBFS:build failed(abort: could not determine
source-distribution conditions of
build/ring-ea02091f2e9fc04e/out/libring_core_0_17_14__test.a）
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.)
--
1103300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-ring
Version: 0.17.14-1
Severity: serious
Tags: FTBFS, patch
Dear rust-ring maintainer,
The package rust-ring build failed on all archs,The crucial buildd log
below:
```
/usr/share/cargo/bin/dh-cargo-built-using: found static lib
ring_core_0_17_14_ at
/build/reproducible-path/rust-ring-0.17.14/target/x86_64-unknown-linux-gnu/debug/build/ring-4884453bb58d7fb6/out/libring_core_0_17_14_.a
/usr/share/cargo/bin/dh-cargo-built-using: static library derived from
/build/reproducible-path/rust-ring-0.17.14 which is the top-level
crate being built, no need to add Built-Using
/usr/share/cargo/bin/dh-cargo-built-using: found static lib
ring_core_0_17_14__test at
/build/reproducible-path/rust-ring-0.17.14/target/x86_64-unknown-linux-gnu/debug/build/ring-4884453bb58d7fb6/out/libring_core_0_17_14__test.a
/usr/share/cargo/bin/dh-cargo-built-using: abort: could not determine
source-distribution conditions of
build/ring-4884453bb58d7fb6/out/libring_core_0_17_14__test.a.
You must patch build.rs of ring to output
'println!("dh-cargo:deb-built-using=ring_core_0_17_14__test=$s={}",
env::var("CARGO_MANIFEST_DIR").unwrap());' where:
- $s is 1 if the license(s) of the included static libs require source
distribution alongside binaries, otherwise 0
dh_auto_test: error: env CARGO_CHANNEL=debug
/usr/share/cargo/bin/dh-cargo-built-using returned exit code 1
make: *** [debian/rules:3: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned
exit status 2
```
The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=rust-ring&arch=amd64&ver=0.17.14-1&stamp=1744757535&raw=0
Problem Analysis:
The Debian packaging helper dh-cargo-built-using requires explicit
information about the licensing terms for static libraries generated during
the build, specifically whether the license mandates source code
distribution alongside binaries derived from the static library.
The script successfully identifies the main static library
(libring_core_0_17_14_.a) but fails on the test-specific static library
libring_core_0_17_14__test.a.
The ring crate's build.rs script does not currently output the required
dh-cargo:deb-built-using directive for this test library.
Proposed Solution:
As suggested by the error message, the fix involves patching the build.rs
script of the ring crate to output the necessary information for
libring_core_0_17_14__test.a.
The ring crate uses a combination of permissive licenses (ISC-like, MIT,
OpenSSL) which do not require source distribution alongside binaries.
Therefore, the $s parameter in the directive should be 0. The debdiff patch
is in the attachment.I have tested that locally,and it works well.Please
let me know whether this solution can be accepted.
Gui-Yue
Best Regards
fix_rust-ring_dh-cargo-test-lib-built-using.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: rust-ring
Source-Version: 0.17.14-2
Done: Peter Michael Green <plugw...@debian.org>
We believe that the bug you reported is fixed in the latest version of
rust-ring, 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 1103...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green <plugw...@debian.org> (supplier of updated rust-ring
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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 17 Apr 2025 02:09:18 +0000
Source: rust-ring
Architecture: source
Version: 0.17.14-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
<pkg-rust-maintain...@alioth-lists.debian.net>
Changed-By: Peter Michael Green <plugw...@debian.org>
Closes: 1103300
Changes:
rust-ring (0.17.14-2) unstable; urgency=medium
.
* Team upload.
* Package ring 0.17.14 from crates.io using debcargo 2.7.8
* Fix library name in built-using (Closes: #1103300)
Checksums-Sha1:
1ecea0f783568e67ea09b896de00af2c57242abf 2451 rust-ring_0.17.14-2.dsc
7f33156acda43b8e4640fb884ea228694b2bfd5a 15784
rust-ring_0.17.14-2.debian.tar.xz
fcbef2922ad1d78aa80f353348313dfa8a94aa93 8511
rust-ring_0.17.14-2_source.buildinfo
Checksums-Sha256:
64a124ce198ee047be16dc8fdb240cd19cb721318010d62cace0ec9f83803579 2451
rust-ring_0.17.14-2.dsc
4ea504720393f39e4d1ff96d8d299c76fec051443b1adf72590f05f28b84b7fe 15784
rust-ring_0.17.14-2.debian.tar.xz
456f348570cc852d11a3689cad60a05a4662fca730435d0a0fe3bdd96323ca90 8511
rust-ring_0.17.14-2_source.buildinfo
Files:
0fcb8b34808bbb8443cb3e45f391139d 2451 rust optional rust-ring_0.17.14-2.dsc
0e1d3b7b2cbe6b6076ff4a474021ce62 15784 rust optional
rust-ring_0.17.14-2.debian.tar.xz
a59e9ee74ebb074100754862848783cb 8511 rust optional
rust-ring_0.17.14-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmgAYywUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xv3cA/8COIro48oiqZHpmrUR4mRoaIjUCL8
Ti0BUwqBzLHXo1Il7XkI51PrO2VK59vRpC7C1REJVpwBrdkPrrcWjzWc4+YCPK9g
Zkw2bnJVOes31xyJnpVKULx1vwjLhwy4HOSz3eL6UIIic7EOK5WQTvDiR5ADRI3+
OtEQ9XbycDN958rUlGATeOPDl0tejoBqB4GjLuqQyxqxq2xuQJL45Hb8eW9TPP9g
MESgjkbTKLhXnjOqOc0Gl/dI01YWPqx2ajpUpFVHHpOrQJ9OzPIZjrJNy/fEL0qX
3NsspTxLchRhtw5/DNZ/8Xtm7eWQaPg93506U8BinwCV7ZaMZNhnRXhHl4a8rn5h
JRRJJc5ohDIFGO8gjP5vuXLeSUOpkfBGDctlcViQfFM3E1ne0LqcRleMZSP84+76
amBEFrIyJ8NvG4VUSGEiFtMkStzfnueAnAQbou/7im6zqHQJMeE/CajP63lpX7z5
af+ZO+uTpNankGBqZTqYSwA1tUfKoxlnekoJo5jSssHyIU8/x9pSXPDUAySIf5eL
bc8gOiP/Y7yi8TWYm9rZfIFC2RXyw2RsC+eO8nkMBkx4+/NK6styk8ETPsV/vj+v
m/+5XGNYedFp0RRgsIQ+lkXTL1LVZDZFsxo+ZxyXSj03OVprvOAFZZDL09YjhSF7
Gw1ZlspWwhLDmO0=
=eoEj
-----END PGP SIGNATURE-----
pgpe5X1lVCTmX.pgp
Description: PGP signature
--- End Message ---
