[Debian-salsa-ci] Using Salsa-CI as pre-upload QA for Bullseye and Buster uploads: Lintian and Piuparts

[Otto Kekäläinen]

Hello!

I am trying to revive this discussion. I am in particular interested
in this: Do you use Salsa-CI (and Lintian v2.115.3) for quality
assurance of your packages before uploading to Debian Bullseye or
Buster?

Did Lintian authors intend that the latest version in Debian Sid would
be used to QA packages before upload to _any_ Debian release?


On Sun, 20 Nov 2022 at 13:50, Otto Kekäläinen <otto at debian.org> wrote:
>
> > > I do however have some challenges that some of the build jobs don't
> > > honor the RELEASE variable. For example Lintian is run with the latest
> > > 2.115 version and not the Bullseye/Buster version, so it leads to
> > > failures that are not actual regressions.
> >
> > Can you briefly clarify what this reference to RELEASE refers to? I
> > initially thought it was something specific to MariaDB, but your
> > reference to Lintian suggests otherwise. Is it the:
> >
> >   https://salsa.debian.org/salsa-ci-team/pipeline#changing-the-debian-release
> >
> > … variable?
>
> Yes.
>
> So for example in
> https://salsa.debian.org/mariadb-team/mariadb-10.3/-/pipelines/457543
> the Lintian job
> https://salsa.debian.org/mariadb-team/mariadb-10.3/-/jobs/3538211 uses
> Lintian v2.115.3 and fails on issues that are not relevant for the
> Buster release.
>
> I could disable the Lintian check, but then I would miss some
> potential real issues that I might have overlooked while importing a
> new minor maintenance release on the Buster branch.
>
> I commented this in
> https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/347
> as pointed out by Santiago.
>
> - Otto