Automatic builds on Salsa show ramdom build failure.

This is now fixed upstream in version 5.5.

severity 1139337 serious
thanks

Hello.

I'm raising the severity because in some cases those test failures
prevent the package from being built at all (I'm getting a 100%
failure rate here in some AWS instances).

I see you have 5.5-1 ready in a salsa branch. Instead of replacing
Alejandro as a maintainer, I suggest you add yourself as an Uploader
and write something like this in the changelog:

* Team upload (salsa debian group).

That's what the debian group was created, I think. This way, you don't
need to become the (sole) maintainer to do the upload, but also you
don't need to version the upload as a NMU.

(I still would like to hear from Alejandro).

Thanks.

Hello,

* Santiago Vila <sanvila@debian.org> [2026-06-26 22:25]:

I had prepared an ITS 21 days ago, but for some reason, it was never
received by the BTS, I should have checked it.

Actually, Alejandro did not push direvent to Salsa, Andreas did it when
an NMU was pushed some months ago, there is no signal from Alejandro
that he would accept a team upload. At least that’s my understanding.

I can push an NMU if you feel this needs to be fixed urgently before the
21 + 7 days ITS delay.

That would be the best outcome indeed.

Thanks for your message, and sorry for my mistake with the ITS.

Nicolas.