Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Felix Lechner
Hi, On Mon, Sep 6, 2021 at 3:42 PM Jelmer Vernooij wrote: > > something needs to tell the maintainer their package is wrong. I struggle with telling anyone that "their package is wrong," when a maintainer, possibly overwhelmed by zealous metadata collection (hello, DuckDuckGo), added a defensibl

Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Jelmer Vernooij
On Mon, Sep 06, 2021 at 03:10:05PM -0700, Felix Lechner wrote: > On Mon, Sep 6, 2021 at 2:26 PM Jelmer Vernooij wrote: > > It won't provide maintainers of packages that use > > invalid settings that they are. Isn't that purpose of lintian? > I am not sure. Is it perhaps a gray zone the Janitor cou

Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Felix Lechner
Hi, On Mon, Sep 6, 2021 at 2:26 PM Jelmer Vernooij wrote: > > It won't provide maintainers of packages that use > invalid settings that they are. Isn't that purpose of lintian? I am not sure. Is it perhaps a gray zone the Janitor could fill? There are a few open questions: Why for example does

Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Jelmer Vernooij
On Mon, Sep 06, 2021 at 01:44:31PM -0700, Felix Lechner wrote: > On Mon, Sep 6, 2021 at 12:56 PM Jelmer Vernooij wrote: > > it would simply be a list of > > known bad values > > I am not sure I agree with the hardcoding of those values unless they > create legal issues like license violations or

Processed: Re: Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 lintian: export upstream metadata in classification tag Bug #993813 [lintian] lintian: synchronize upstream metadata Changed Bug title to 'lintian: export upstream metadata in classification tag' from 'lintian: synchronize upstream metadata'. -- 993813:

Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Felix Lechner
Control: retitle -1 lintian: export upstream metadata in classification tag Hi, On Mon, Sep 6, 2021 at 12:56 PM Jelmer Vernooij wrote: > > it would simply be a list of > known bad values I am not sure I agree with the hardcoding of those values unless they create legal issues like license viola

Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Jelmer Vernooij
On Mon, Sep 06, 2021 at 12:51:43PM -0700, Felix Lechner wrote: > On Mon, Sep 6, 2021 at 12:24 PM Jelmer Vernooij wrote: > > > > Registration: https://github.com/join > > As a tool without network access, Lintian may not be well-suited to > synchronize upstream metadata. This wouldn't require net

Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Felix Lechner
Hi, On Mon, Sep 6, 2021 at 12:24 PM Jelmer Vernooij wrote: > > Registration: https://github.com/join As a tool without network access, Lintian may not be well-suited to synchronize upstream metadata. Kind regards Felix Lechner

Bug#993813: warn about known invalid fields in debian/upstream/metadata

2021-09-06 Thread Jelmer Vernooij
Package: lintian Version: 2.104.0 Severity: wishlist Some packages have known incorrect values in debian/upstream/metadata. For example: Registration: https://github.com/join is certain to be incorrect - as we don't package GitHub. It would be great if lintian could warn about these. -- Syste