Your message dated Wed, 10 Mar 2021 23:17:02 +0000 with message-id <11a93d7a-3209-08a5-f443-58dc980cf...@p10link.net> and subject line re: rust-sequoia-autocrypt: autopkgtest needs update for new version of rust-sequoia-openpgp: output changed has caused the Debian Bug report #984730, regarding rust-sequoia-autocrypt: autopkgtest needs update for new version of rust-sequoia-openpgp: output changed 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.) -- 984730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: rust-sequoia-autocrypt Version: 0.23.0-2 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:rust-sequoia-openpgp [X-Debbugs-CC: debian...@lists.debian.org, rust-sequoia-open...@packages.debian.org] Dear maintainer(s), With a recent upload of rust-sequoia-openpgp the autopkgtest of rust-sequoia-autocrypt fails in testing when that autopkgtest is run with the binary packages of rust-sequoia-openpgp from unstable. It passes when run with only packages from testing. In tabular form: pass fail rust-sequoia-openpgp from testing 1.1.0-1 rust-sequoia-autocrypt from testing 0.23.0-2 all others from testing from testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of rust-sequoia-openpgp to testing [1]. Of course, rust-sequoia-openpgp shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in rust-sequoia-openpgp was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from rust-sequoia-openpgp should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=rust-sequoia-openpgp https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-sequoia-autocrypt/10911145/log.gz failures: ---- test::autocrypt_header_new stdout ---- thread 'test::autocrypt_header_new' panicked at 'assertion failed: `(left == right)` left: `"3E8877C877274692975189F5D03F6F865226FE8B"`, right: `"3E88 77C8 7727 4692 9751 89F5 D03F 6F86 5226 FE8B"`', src/lib.rs:1058:9 stack backtrace: 0: rust_begin_unwind at /usr/src/rustc-1.48.0/library/std/src/panicking.rs:483 1: std::panicking::begin_panic_fmt at /usr/src/rustc-1.48.0/library/std/src/panicking.rs:437 2: sequoia_autocrypt::test::autocrypt_header_new at ./src/lib.rs:1058 3: sequoia_autocrypt::test::autocrypt_header_new::{{closure}} at ./src/lib.rs:1034 4: core::ops::function::FnOnce::call_once at /usr/src/rustc-1.48.0/library/core/src/ops/function.rs:227 5: core::ops::function::FnOnce::call_once at /usr/src/rustc-1.48.0/library/core/src/ops/function.rs:227 note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. failures: test::autocrypt_header_new test result: FAILED. 6 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Version: 0.23.1-1 Tests for the new version of rust-sequoia-autocrypt pass with both the new and old versions of rust-sequoia-openpgp.
--- End Message ---
