Your message dated Thu, 26 Sep 2024 17:02:15 +0200 with message-id <[email protected]> and subject line Re: Bug#1082798: unblock: rust-sequoia-keystore-tpm/0.1.0-2 has caused the Debian Bug report #1082798, regarding unblock: rust-sequoia-keystore-tpm/0.1.0-2 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.) -- 1082798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082798 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---
- To: Debian Bug Tracking System <[email protected]>
- Subject: unblock: rust-sequoia-keystore-tpm/0.1.0-2
- From: Peter Green <[email protected]>
- Date: Thu, 26 Sep 2024 15:24:49 +0100
- Message-id: <[🔎] [email protected]>
Package: release.debian.org Severity: normal User: [email protected] Usertags: unblock rust-sequoia-keystore-tpm is blocked from migrating to testing by two issues. I do not believe either of these issues represent real issues in the rust-sequoia-keystore-tpm package and therefore request that the package is allowed to migrate. Firstly britney is scheduling tests with the old version of rust-sequoia-keystore and the new version of rust-sequoia-keystore-tpm, despite the fact that the old version of rust-sequoia-keystore does not depend on rust-sequoia-keystore-tpm at all. The problem with this is that rust-sequoia-keystore-tpm depends on a newer version of rust-sequoia-keystore-backend which does not satisfy the dependencies of the old version of rust-sequoia-keystore. The result of this is that the fallback dependency solver gets invoked leading to a mismatch between the tests and the package being tested and ultimately a "crate directory not found" error. I tried adding a "breaks", but it did not seem to help. The second problem is that the autopkgtests are "blocked-on-ci-infra" on riscv64, since this package is not currently in testing, this counts as a "regression".
--- End Message ---
--- Begin Message ---
- To: Peter Green <[email protected]>, [email protected]
- Subject: Re: Bug#1082798: unblock: rust-sequoia-keystore-tpm/0.1.0-2
- From: Paul Gevers <[email protected]>
- Date: Thu, 26 Sep 2024 17:02:15 +0200
- Message-id: <[email protected]>
- In-reply-to: <[🔎] [email protected]>
- References: <[🔎] [email protected]>
Hi Peter, On 26-09-2024 16:24, Peter Green wrote:Firstly britney is scheduling tests with the old version of rust-sequoia-keystore and the new version of rust-sequoia-keystore-tpm, despite the fact that the old version of rust-sequoia-keystore does not depend on rust-sequoia-keystore-tpm at all. The problem with this is that rust-sequoia-keystore-tpm depends on a newer version of rust-sequoia-keystore-backend which does not satisfy the dependencies of the old version of rust-sequoia-keystore. The result of this is that the fallback dependency solver gets invoked leading to a mismatch between the tests and the package being tested and ultimately a "crate directory not found" error. I tried adding a "breaks", but it did not seem to help.I'm not seeing the Breaks you're talking about. Can you point me where that's added? (I expected it in the librust-sequoia-keystone-tpm-dev stanza in d/control).The second problem is that the autopkgtests are "blocked-on-ci-infra" on riscv64, since this package is not currently in testing, this counts as a "regression".I added a hint for riscv64. PaulAttachment: OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---