Hi! 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 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. On Sun, 15 Jan 2023 at 13:25, Otto Kekäläinen <o...@debian.org> wrote: > > Hi! > > > > Do you use Salsa-CI (and Lintian v2.115.3) for quality assurance of > > > your packages before uploading to Debian Bullseye or Buster? > > > > Until a few minutes ago, no, I did not test using the latest version > > of Lintian from unstable. Rather, I was using the version in > > buster/bullseye/stretch instead, as that was what was so easily > > available inside the chroot. > > > > However, though, I've just spent a few minutes updating my setup such > > that I will use the version from unstable instead. > > Thanks for the info. Thus I will also use the Lintian 2.115 from > unstable to test all of my uploads. > > This means that I will need to do override updates that add the > brackets (example [1]) to paths in packages that are intended for > Buster/Bullseye because their Lintian overrides are intended for > v2.115. I am fine doing this now that I know that others are also > using latest Lintian for all packaging QA. > > Hopefully current Lintian maintainers will keep backwards > compatibility in mind and not introduce too many changes that make old > packages that were Lintian clean to error too much. > > [1] > https://salsa.debian.org/mariadb-team/galera-3/-/commit/e00e6b67e189ac2c93ba3bc87f4cdf202d8937af
