Bug#885432: bugs-field-does-not-refer-to-debian-infrastructure for non-Debian packages

[Russ Allbery]

Package: lintian
Version: 2.5.66
Severity: normal

The new tag bugs-field-does-not-refer-to-debian-infrastructure added in
the most recent version of Lintian is a false positive for non-Debian
packages.  I have a pile of personal packages that I maintain in a separate
archive, but prefer to use all the normal Debian packaging methods and
tools.  This tag will always be a false positive for those packages since
they have:

Bugs: mailto:r...@debian.org

I could add an override to every personal package, but that's a little
annoying to do.

Is there some way that I could tell Lintian that this is a non-Debian
package to suppress this tag?  That might be a useful general feature to
suppress a few other tags too, such as new-package-should-close-itp-bug.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.29.1-12
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.19.0.4
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.60-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.39-1
ii  libdpkg-perl  1.19.0.4
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.1-3
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-2
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-4
ii  patchutils0.3.4-2
ii  perl  5.26.1-3
ii  t1utils   1.41-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.19.0.4
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.47-1

-- no debconf information

Bug#885432: bugs-field-does-not-refer-to-debian-infrastructure for non-Debian packages

[Niels Thykier]

Russ Allbery:
> Package: lintian
> Version: 2.5.66
> Severity: normal
> 
> The new tag bugs-field-does-not-refer-to-debian-infrastructure added in
> the most recent version of Lintian is a false positive for non-Debian
> packages.  I have a pile of personal packages that I maintain in a separate
> archive, but prefer to use all the normal Debian packaging methods and
> tools.  This tag will always be a false positive for those packages since
> they have:
> 
> Bugs: mailto:r...@debian.org
> 
> I could add an override to every personal package, but that's a little
> annoying to do.
> 
> Is there some way that I could tell Lintian that this is a non-Debian
> package to suppress this tag?  That might be a useful general feature to
> suppress a few other tags too, such as new-package-should-close-itp-bug.
> 
> [...]
> 

Hi,

We have the lintian profile system that enables you to process packages
in a different context than "debian" (e.g. "ubuntu" or your own personal
context).  The profiles can enable / disable tags (or even change
severity of the tags).

However, we cannot guess which profile you want based on the package.
Partly, because we select the profile first and then process the
package.  Partly, because (as I recall) we do not have a reliable
indicator of which "derivative" the package is targeting.  In the best
case, we only have the "distribution", but e.g. "jessie" is used both by
Debian but also third-parties (a notably Devuan, but ISVs may also have
their own repositories that mirror the Debian release that they match).

Thanks,
~Niels

Bug#885432: bugs-field-does-not-refer-to-debian-infrastructure for non-Debian packages

[Russ Allbery]

Niels Thykier  writes:

> We have the lintian profile system that enables you to process packages
> in a different context than "debian" (e.g. "ubuntu" or your own personal
> context).  The profiles can enable / disable tags (or even change
> severity of the tags).

> However, we cannot guess which profile you want based on the package.
> Partly, because we select the profile first and then process the
> package.  Partly, because (as I recall) we do not have a reliable
> indicator of which "derivative" the package is targeting.  In the best
> case, we only have the "distribution", but e.g. "jessie" is used both by
> Debian but also third-parties (a notably Devuan, but ISVs may also have
> their own repositories that mirror the Debian release that they match).

Yeah, profiles would definitely work.  I wonder if it would make sense to
have a file in debian/source that indicates the profile in some way?

-- 
Russ Allbery (r...@debian.org)   

Bug#885432: bugs-field-does-not-refer-to-debian-infrastructure for non-Debian packages

[Chris Lamb]

Hi Niels & Russ,

> We have the lintian profile system that enables you to process packages
> in a different context than "debian" (e.g. "ubuntu" or your own personal
> context).  The profiles can enable / disable tags (or even change
> severity of the tags).

FYI bugs-field-does-not-refer-to-debian-infrastructure was disabled for
all !Debian profiles in its initial commit. :)

> However, we cannot guess which profile you want based on the package.

Whilst this might be playing whack-a-mole to some degree, just to be
somewhat complete in the response, you can also globally ignore tags
via your lintianrc.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#885432: bugs-field-does-not-refer-to-debian-infrastructure for non-Debian packages

[Niels Thykier]

Russ Allbery:
> Niels Thykier  writes:
> 
>> We have the lintian profile system that enables you to process packages
>> in a different context than "debian" (e.g. "ubuntu" or your own personal
>> context).  The profiles can enable / disable tags (or even change
>> severity of the tags).
> 
>> However, we cannot guess which profile you want based on the package.
>> Partly, because we select the profile first and then process the
>> package.  Partly, because (as I recall) we do not have a reliable
>> indicator of which "derivative" the package is targeting.  In the best
>> case, we only have the "distribution", but e.g. "jessie" is used both by
>> Debian but also third-parties (a notably Devuan, but ISVs may also have
>> their own repositories that mirror the Debian release that they match).
> 
> Yeah, profiles would definitely work.  I wonder if it would make sense to
> have a file in debian/source that indicates the profile in some way?
> 

Beyond a massive rewrite of how we handle profiles (e.g. load checks,
disable tags, etc.), I do have a concern with placing this in the
package as static maintained metadata:

 * What happens when I add this metadata to e.g. lintian or debhelper
   and set its value to "debian".  Then Ubuntu imports it as-is but
   lintian would no longer choose the ubuntu profile by default (instead
   it would go for the debian profile).
   - This case can also be applied to Ubuntu and their derivatives (i.e.
 further "up" in the chain).

I think I lead towards having a dynamic computed field.  E.g. one the
dpkg inserts during package build (source or/and binary) based on the
current "vendor".  However, that would imply that you need to build your
packages as a different "vendor" than Debian (which you probably do not).

Thanks,
~Niels

Bug#885432: bugs-field-does-not-refer-to-debian-infrastructure for non-Debian packages

[Russ Allbery]

Chris Lamb  writes:

>> However, we cannot guess which profile you want based on the package.

> Whilst this might be playing whack-a-mole to some degree, just to be
> somewhat complete in the response, you can also globally ignore tags
> via your lintianrc.

Yeah, the problem I have is that I do want all the checks when uploading
to Debian.  I suspect the right thing for me to do is make my own profile,
and then just remember to use that profile for local packages.  It's a
little bit awkward, but it's not too bad.

-- 
Russ Allbery (r...@debian.org)   

Processed: Re: Bug#885432: bugs-field-does-not-refer-to-debian-infrastructure for non-Debian packages

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 885432 + wontfix
Bug #885432 {Done: Chris Lamb } [lintian] 
bugs-field-does-not-refer-to-debian-infrastructure for non-Debian packages
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
885432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems