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

Bug#1001399: lintian: adjust backports-upload-has-incorrect-version-number for ubuntu



Sorry, this topic seems to have slipped my mind.

On Thu, Dec 09, 2021 at 08:59:33AM -0800, Felix Lechner wrote:
> On Thu, Dec 9, 2021 at 8:37 AM Mattia Rizzolo <mattia@debian.org> wrote:
> >
> > I believe we shouldn't concern
> > ourselves too much with UNRELEASED (what's the current behaviour here
> > anyway?)
> 
> For the majority of tags, the release is not considered but having
> less concern for UNRELEASED would negatively affect the quality of
> hints issued on Salsa. [1] I expect that to be the primary Lintian
> platform for contributors in the future.

That might even be so, but I don't think it's an interesting concern
when we are talking about the final version string of a package.

I also had a look at the current Distribution.pm which is what is doing
the current check, and that's already skipping UNRELEASED for
everything, special casing squeeze, wheezy and jessie, and doing all
sorts of very target-specific checks.

I think what lintian is currently doing in this check is perfectly fine,
and it should keep doing that.

Different distributions have different version requirements, so tying
the two together only makes sense, and I see no reason why you shouldn't
do that.


You talk about running lintian in CI, which is fine, but then when run
in CI (with UNRELEASED) it's also true that there is no reason for
contributors to bother about the version string, as that's something for
the maintainer/uploader to check, so I think it's kind of out of scope.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
More about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: