Re: Using Salsa-CI as pre-upload QA for Bullseye and Buster uploads: Lintian and Piuparts
> > 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:
> … variable?
So for example in
the Lintian job
Lintian v2.115.3 and fails on issues that are not relevant for the
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
as pointed out by Santiago.