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

Bug#1081516: marked as done (unblock: rust-jiter/0.5.0-3)

Your message dated Thu, 12 Sep 2024 13:12:01 +0200
with message-id <d52cc594-7edf-4789-acf4-bdf55b3bf5d6@debian.org>
and subject line Re: Bug#1081516: unblock: rust-jiter/0.5.0-3
has caused the Debian Bug report #1081516,
regarding unblock: rust-jiter/0.5.0-3
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.)


-- 
1081516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081516
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

A few Rust packages are currently blocked from migrating to testing due
to what appears to be a bug in piuparts scheduling.  I filed
https://bugs.debian.org/1081420 about this.  However, I particularly
care about rust-jiter, because pydantic-core and pydantic and a bunch of
other things are stuck behind it.  Would it be possible to unblock this?
There should still be enough material in the queue to debug whatever's
going wrong with the piuparts scheduler.

I've run piuparts over librust-jiter-dev locally and it seems fine.

Thanks,

-- 
Colin Watson (he/him)                              [cjwatson@debian.org]

--- End Message ---
--- Begin Message --- 
Hi Colin,

On 12-09-2024 13:02, Colin Watson wrote:

I've run piuparts over librust-jiter-dev locally and it seems fine.


I've added:
ignore-piuparts rust-jiter/0.5.0-3

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: