Re: Help with understanding piuparts results
Hi,
On Fri, May 9, 2025, at 09:00, Mathias Behrle wrote:
> * Paul Gevers: " Re: Help with understanding piuparts results" (Thu, 8 May 2025
> 10:39:23 +0200):
>
> Hi Paul,
>
>> Hi Nicolas,
>>
>> On 08-05-2025 09:31, Mathias Behrle wrote:
>> > all recent uploads of the Tryton suite migrated now after the current delay
>> > of 10 days, but not tryton-server [0].
>> >
>> > Excuses [0] say:
>> > Waiting for piuparts test results (stalls migration) -
>> > https://piuparts.debian.org/sid/source/t/tryton-server.html
>> >
>> > Piuparts page [1] says:
>> > piuparts summary: unknown
>> >
>> > with the following items:
>> > tryton-server-all-in-one:all "waiting-for-dependency-to-be-tested"
>> > tryton-server-nginx:all "waiting-for-dependency-to-be-tested"
>> > tryton-server-uwsgi:all "waiting-to-be-tested"
>> >
>> > The test dependencies of the first two items result basically also in
>> > tryton-server-uwsgi:all "waiting-to-be-tested"
>> >
>> > So all depends on the result of tryton-server-uwsgi:all [2]
>> > but this page says, that all dependencies were successfully tested.
>> >
>> > Looks like the state of tryton-server-uwsgi was not correctly updated.
>>
>>
>> Can you look behind the curtains to see what's going on? I fear there's
>> not enough information to understand as an outsider. Or am I missing
>> something?
>
> Thanks for taking care. Just in case: Are you able to hint the package for
> migration despite hanging piuparts?
>
> Note:
> tryton-server never had migration problems in the past with piuparts
> and the
> last uploaded changes (s.
> https://salsa.debian.org/tryton-team/tryton-server/-/commit/096dcfcb3302129564896673561c56dee06a895d)
> are small enough and don't target any packaging. I assume that there
> was some
> hickup in the piuparts setup. Anyway I wanted to be done with Tryton
> uploads
> before we enter Hard Freeze and thus I would appreciate to have all
> packages in
> testing in due time.
Hi,
In sid, tryton-server-uwsgi depends on uwsgi-plugin-python3, which depends on uwsgi-abi-fd03c85edfee33327ac760f246543e10, which isn't provided by any package.
So, practically, in sid, piuparts is refusing to test packages that depend on uwsgi-plugin-python3 (which would fail anyway).
There's a bug in that piuparts reports "waiting-to-be-tested" instead of "dependency-cannot-be-tested" for tryton-server-uswgi.
HTH,
--
Nicolas Dandrimont
Reply to: