On Tue, Aug 20, 2024 at 06:35:52PM -0700, Otto Kekäläinen wrote: > Hi! > > In short: > I would very much like to see all top-150 packages run Salsa CI at > least once before being uploaded to unstable. What people think is a > reasonable way to proceed to reach this goal? > > > Background: > We have had several cases recently where an upload to Debian unstable > causes widespread failure in unstable, and it could have been easily > prevented if Salsa CI pipeline had run for the package and revealed > the problem before upload to archive for everyone to suffer. > > This message was prompted by the fact that right now we have a massive > large of Python packages affected by the "No module named 'packaging'" > bug [1] which would have been caught by Salsa CI running the > autopkgtest job before upload [2]. I don't want to blame maintainers > for missing on some details while doing new releases - it happens. But > systematically not using available and easy testing facilities does > annoy me.
Or, if your package has autopkgtests, you could actually run them as a part of your local building and testing workflow, but (as I'm whining for maybe a 3rd time here) this is apparently unpopular nowadays so I'm looking forward to suggestions for integrating non-local checks into the old style workflow. -- WBR, wRAR
signature.asc
Description: PGP signature
