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

Bug#1003340: marked as done (qa.debian.org: Please agree with salsa on the lintian version to use)



Your message dated Sun, 9 Jan 2022 18:41:14 +0100
with message-id <20220109174114.m4oxksdmcvn4b4gc@begin>
and subject line Re: Bug#1003340: qa.debian.org: Please agree with salsa on the lintian version to use
has caused the Debian Bug report #1003340,
regarding qa.debian.org: Please agree with salsa on the lintian version to use
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1003340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003340
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: important

Hello,

With lintian's current tendency of changing its output, we have to adapt
the suppression rules. But it appears that qa.debian.org and salsa's CI
rules are not using the same version of lintian, so we are stuck with
either having lintian errors showing up on the qa.debian.org page, or
having the CI jobs on salsa fail on the lintian step.

Samuel

--- End Message ---
--- Begin Message ---
Felix Lechner, le dim. 09 janv. 2022 09:32:07 -0800, a ecrit:
> On Sun, Jan 9, 2022 at 8:51 AM Samuel Thibault <sthibault@debian.org> wrote:
> >
> > But what is "latest version"?
> 
> The latest version is the most recent commit on the 'master' branch in
> our public repository. [1] We found it is the fastest way to bring bug
> fixes to the community.

Ok, then I have requested the update on the salsa CI side:

https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/239

Samuel

--- End Message ---

Reply to: