Package: lintian
Version: 2.59.0
Severity: normal
Tags: patch
Recently we've been seeing a number of autopkgtest failures related to
the python3.8 as default python3 transition due to use of py3versions -r
with no related X-Python3-Version field falling back to all supported
versions. This is
Processing control commands:
> tag -1 pending
Bug #954484 [lintian] lintian: should warn when changelog entry contains
`Closes;` instead of `Closes:`
Added tag(s) pending.
--
954484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954484
Debian Bug Tracking System
Contact
Processing control commands:
> tag -1 pending
Bug #954803 [lintian] lintian: no-md5sums-control-file tag should not be
triggered for udebs
Added tag(s) pending.
--
954803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: lintian
Version: 2.59.0
Severity: normal
The following is not supposed to happen, I think:
,
| $ lintian libtinfo6-udeb_6.2-1_amd64.udeb
| I: libtinfo6-udeb udeb: no-md5sums-control-file
`
AFAIK it is normal for udebs not to ship an md5sums control file, and
dh_md5sums does not
Processing control commands:
> tag -1 pending
Bug #954798 [lintian] lintian: field-too-long checksums-sha256 error
Added tag(s) pending.
--
954798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: lintian
Version: 2.59.0
Severity: normal
Dear Maintainer,
* What led up to the situation?
sbuild -d unstable for the latest version of my package budgie-extras
threw a policy errors for this particular field
E: budgie-extras changes: field-too-long Checksums-Sha256 (5432
6 matches
Mail list logo