Your message dated Fri, 03 Jan 2020 01:34:54 +0000 with message-id <[email protected]> and subject line Bug#945560: fixed in rust-debcargo 2.4.1-1 has caused the Debian Bug report #945560, regarding debcargo autopkgtests are broken for many packages with multiple features 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.) -- 945560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945560 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: debcargo Version: 2.4.0-1 i'm starting to see a pattern of autopkgtest failures for crates with multiple features. rust-bindgen and rust-buffered-reader both show this kind of failure in their autopkgtest suite. In particular, the autopkgtest logs indicate that: "/usr/share/cargo/bin/cargo-auto-test $CRATE $VERSION --all-targets --features foo" will fail because no matching package named `bar` found and then conversesly: "/usr/share/cargo/bin/cargo-auto-test $CRATE $VERSION --all-targets --features bar" will fail because no matching package named `foo` found infinity0 says: i have general logic in debcargo to add the right dependencies and skip the test if they aren't met but somehow the features running that tests are looking for external deps that they ought not need. if it was just one package or upstream, i'd say it was most likely a bug in that package or upstream. But buffereed-reader and bindgen have different upstreams, and yet they have the same pattern of autopkgtest failures -- feature foo fails claiming "missing bar" and feature bar fails claiming "missing foo". So i think that cargo-auto-test might be common factor. infinity0 says: i think this might be cargo bug https://github.com/rust-lang/cargo/issues/5133 . It is cargo itself that wants the presence of those extra dev-dependencies even when they are not actually needed. in which case, perhaps we need to work-around it and have debcargo actually generate these extra dependencies for now in debian/tests/control in general, cargo requires the presence of optional dependencies in the registry even when they are not needed for the current command invocation. this is ok when syncing the full registry from crates.io in your $HOME but not in debian where the registry is populated by the currently-installed packages I've reported this to buffered-reader upstream over here, and they can't seem to replicate it: https://gitlab.com/sequoia-pgp/sequoia/issues/386, but infinity0 suggests that this isn't likely to be their probelm becauseit only affects distros like debian that don't use a full registry for its distro rust packages. infinity0 says: for now you can work-around it in your package by setting test_is_broken, feel free to file a debcargo issue for the more general workaround "have debcargo actually generate these extra dependencies for now in debian/tests/control" So that's what this bug report is :) --dkg
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: rust-debcargo Source-Version: 2.4.1-1 We believe that the bug you reported is fixed in the latest version of rust-debcargo, 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. Ximin Luo <[email protected]> (supplier of updated rust-debcargo 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: Fri, 03 Jan 2020 01:19:34 +0000 Source: rust-debcargo Architecture: source Version: 2.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers <[email protected]> Changed-By: Ximin Luo <[email protected]> Closes: 945436 945499 945560 947088 Changes: rust-debcargo (2.4.1-1) unstable; urgency=medium . * Package debcargo 2.4.1 from crates.io using debcargo 2.4.1 * Closes: #945436, #945499, #945560, #947088. Checksums-Sha1: e023059efd60ebe89167a58708d4c5dda1b9237d 2320 rust-debcargo_2.4.1-1.dsc e6d9e644d029700e9105ab32f186080aa0cb90da 69549 rust-debcargo_2.4.1.orig.tar.gz 69fa859c82efee89be086187169d8dd7d11a41e5 3140 rust-debcargo_2.4.1-1.debian.tar.xz e42ee6ef639b085f9523cf28cfff7acbc372614e 6687 rust-debcargo_2.4.1-1_source.buildinfo Checksums-Sha256: 35a394e61096389292e08ef32d10db116944e7eca2f8056ad18d50a28b3e1121 2320 rust-debcargo_2.4.1-1.dsc 76bbc737a8c47a2508dd0ef28e2f338521902c16620ff0cb22b2a51e9cc957fb 69549 rust-debcargo_2.4.1.orig.tar.gz b8015f732add0ec17f611fafee0d80d50185c1940ce1801b82db8b2581c9e3b7 3140 rust-debcargo_2.4.1-1.debian.tar.xz 391a9ec3677ba9eb59f8a1103b01dd07c682d0828b4cee32af420b50d96f22b7 6687 rust-debcargo_2.4.1-1_source.buildinfo Files: abb373dbca9ec31452ca2158bf8dce31 2320 rust optional rust-debcargo_2.4.1-1.dsc b7205dc722744805264fd92ef0043d7d 69549 rust optional rust-debcargo_2.4.1.orig.tar.gz 7ea203fb43b573b8867b04978ec865dc 3140 rust optional rust-debcargo_2.4.1-1.debian.tar.xz 54854ea19126ebafa8349ff3399410a5 6687 rust optional rust-debcargo_2.4.1-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXg6WqQAKCRDrH8jaRfsp MMShAP4tg+7e1+9zPUFiucTxgU4n/eqGa4n1NLeWFBn/W64RtAEA4rCyg5eYj+hB udt4cjKuhw8M4fh0Mhd+OT9XU86togo= =pYUN -----END PGP SIGNATURE-----
--- End Message ---
