[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1082798: marked as done (unblock: rust-sequoia-keystore-tpm/0.1.0-2)

Your message dated Thu, 3 Oct 2024 10:55:00 +0200
with message-id <10bbd31b-1681-4e74-ae5e-604d9de11de9@debian.org>
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 owner@bugs.debian.org
immediately.)


-- 
1082798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082798
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
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 --- 
Hi,

On 27-09-2024 03:44, Peter Green wrote:

I added a hint for riscv64.

Can you bump the hint for the new upload?
Turns out that the hint was wrong (because it was versioned, which doesn't work for infrastructure blocked packages).
Anyways, I lifted the rust block some days ago to see how thing go and in the mean time the package got tested and migrated. 

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: