Santiago Vila <sanvila@debian.org> writes: > El 12/5/25 a las 20:13, Otto Kekäläinen escribió: >> Having a bunch of outdated cruft adds unnecessary toil and distraction >> to people trying to maintain current packages, so cleaning away old >> stuff can help make current contributors more active. For example >> Santiago spent today time debugging the Go CI job test_the_archive, >> which in fact seems useless and should be deleted and replaced with >> Salsa CI. > > Hi. I'm just an occasional contributor here, as I split my time > between several other teams, but after the issue with gocryptfs > pipelines today I see how using the same Salsa CI setup as everybody > else in Debian would be a clear advantage. +1 I think some people are against this (or?), even if I never managed to understand the reason. Could we reach some compromise and progress on this? For example at least a way to opt-in on the Salsa CI scheme? I've never found any use of the Go default pipeline. When it (very rarely) fails I never understand why. Usually it won't fail even on serious errors. So I always setup a fork'ed project and run the standard Salsa CI pipeline there, to have CI testing that is relevant for me. /Simon
Attachment:
signature.asc
Description: PGP signature