Hi,

Wrong Nic(h)olas ;-)

On Wed, Oct 9, 2024, at 18:00, Paul Gevers wrote:
> @olasd, please check at the bottom, item nr 2.
>
>> 2. rust-debversion seems to be stuck on
>>     "Waiting for piuparts test results" for nearly a
>>     fortnight, can you either figure out what is
>>     stalling it or add an override?
>
> olasd maintains the infrastructure (a huge thanks to him) and he replied 
> on IRC some days ago that piuparts may have been confused by all the 
> rust* Provides, because there a several librust*-dev packages listed on 
> [1]. olasd, did you already have time to look at that (not expecting you 
> will next coming days)?

This issue has been nagging me for a while (Jelmer pointed it out for packages
around rust-pyo3 a couple of weeks ago) and I've finally had the time to figure
it out:

librust-image-dev and librust-webp-dev depend on one another, via virtual
packages librust-image-0.24-dev and librust-webp-0.2-dev. The piuparts scheduler
has cycle detection (and allows scheduling tests for every package in the
cycle), but that cycle detection didn't take virtual packages into account, so
this whole dependency tree couldn't be scheduled for testing.

I've now committed a fix to piuparts and put it in place on piuparts.d.o, so the
tests for the whole pile of rust packages that are (transitively) depending on
librust-image-dev are being run and should appear in the britney report in the
next few hours.

Cheers,
-- 
Nicolas Dandrimont

Attachment: signature.asc
Description: PGP signature

Reply via email to