Bug#1009967: lintian: improbable-bug-number-in-closes produces incorrect results
On Fri, Apr 22, 2022 at 10:05 PM Mattia Rizzolo <mattia@debian.org> wrote:
>
> On Fri, Apr 22, 2022 at 09:59:50PM +0300, Martin-Éric Racine wrote:
> > On Fri, Apr 22, 2022 at 3:57 PM Mattia Rizzolo <mattia@debian.org> wrote:
> > >
> > > Control: notfound -1 2.114.163
> > > Control: found -1 2.111.0
> > > Control: close -1 2.113.0
> > >
> > > On Thu, Apr 21, 2022 at 03:38:32PM +0300, Martin-Éric Racine wrote:
> > > > Package: lintian
> > > > Version: 2.114.163
> > >
> > > What version is this?! ...
> >
> > The one reported when someone clicks on the line below.
>
> Ah, now I found the number.. That's the version that is used on
> lintian.debian.org, which is unrelated to what mentors.d.n reports.
Noted.
> > > This bug has long long been fixed, but lintian is not migrating and as
> > > such no backport to bullseye can be done.
> > > (plus I notice lintian hasn't been uploaded _at all_ for many months…)
> >
> > Something tells me that the Lintian version found on Mentors is
> > unrelated to Testing migrations.
>
> It is very relevant instead, as on mentors we run whatever is on
> bullseye-backports.
Noted.
Martin-Éric
Reply to: