Hi Otto,
I do run lintian from the target release before upload (actually on every
build). I don't think running lintian from sid for (old*)stable makes sense as
I'm not interested in newly introduced warnings or errors that affect sid. I'm
interested in having the most stable lintian warnings, so that if there are any
new errors, it's because of changes I made (and I need to look into it).
On 19/03/2023 23:04, Otto Kekäläinen wrote:
Following up on this topic, I noticed that I can't even manually
override the Lintian image version at the moment as the
Buster/Bullseye/Bookworm tags don't exist at
https://salsa.debian.org/groups/salsa-ci-team/-/container_registries/295
To fix this I filed now
https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/407
You can probably use the base:$(RELEASE) image and install lintian yourself.
I am a bit surprised I seem to be the only one running Salsa-CI when
preparing stable/LTS uploads, this issue must have been making the
pipeline red for everybody building RELEASE=bullseye/buster/stretch.
Not the only one! I have been looking at the Salsa CI very recently and have
made improvements to use it for *oldstable, please see [1] and [2]. I'm not
building images for bullseye atm, however if you find this useful, I'll be happy
to add them.
Cheers,
Emilio
[1] https://lists.debian.org/debian-lts/2023/03/msg00021.html
[2] https://salsa.debian.org/lts-team/pipeline
