[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Lintian errors on ffmpeg


El 04/05/22 a las 10:14, Enrico Zini escribió:
> On Wed, May 04, 2022 at 08:58:36AM +0100, Neil Williams wrote:
> > > I'm working at a LTS release of ffmpeg, and the CI is failing with
> > > Lintian errors that weren't present in the previous version:
> > 
> > Is the version of lintian in this Salsa CI environment correct for Stretch?
> > 
> > I've seen reports like this in other suites because of problems within
> > the Salsa images with incorrect versions of lintian.
> Thanks, I had a closer look.
> In the pipeline that I've just run[1], I see:
>    $ lintian --version
>    Lintian v2.114.0
> While in the pipeline run one month ago[1] for a previous upload, I see:
>    $ lintian --version
>    Lintian v2.5.50.4

That was due to a broken behaviour on Salsa CI's side.

> This looks like the relevant change:
>    https://salsa.debian.org/salsa-ci-team/pipeline/-/commit/3eab2b9180b052dc7b3e4d7427a1d561214e2b53
>    which references
>    https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/347
> I'm adding Santiago to Cc, as I'm unable to evaluate the bigger picture
> for that change, and so I cannot guess what would be the expected way to
> deal with errors that come as a consequence of it.

The rationale about that change (or rather the decision about how to fix
broken lintian image/job) is here, after input by lechner:

Ideally, I would expect lintian be clever enough to analyse the package
according to the target release. But that's not the case, and I can
image that's not a simple solution, so we are seeing errors like this
you are reporting.

Is the current lintian behaviour in Salsa CI broken?
Should the lintian job run the lintian version found in ${RELEASE}?


 -- Santiago

P.S. No need to CC me, I am subscribed to the list.

Attachment: signature.asc
Description: PGP signature

Reply to: