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

Bug#954819: marked as done (lintian: Please update the old and ancient python-versions tags to warn about py3versions -r)



Your message dated Wed, 25 Mar 2020 11:04:45 +0000
with message-id <E1jH3q1-0009E3-SJ@fasolo.debian.org>
and subject line Bug#954819: fixed in lintian 2.60.0
has caused the Debian Bug report #954819,
regarding lintian: Please update the old and ancient python-versions tags to warn about py3versions -r
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
954819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954819
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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 the correct behavior, but it has unfortunate
consequences.

I think it would be good to help mitigate future instances of these
problems if we addeed information to the tags to also check for
py3verions -r and see if it still gives what's needed for the package.

Please see the attached patch.  I'm not set on the wording, but I
believe it's in the ball park.

Scott K
diff -Nru lintian-2.59.0/debian/changelog lintian-2.59.0+/debian/changelog
--- lintian-2.59.0/debian/changelog	2020-03-22 16:22:08.000000000 -0400
+++ lintian-2.59.0+/debian/changelog	2020-03-23 20:55:28.000000000 -0400
@@ -1,3 +1,10 @@
+lintian (2.59.0+) UNRELEASED; urgency=medium
+
+  * Update old and ancient python-version-field tag text to suggest also
+    checking for incorrect use of py3verions -r 
+
+ -- Scott Kitterman <scott@kitterman.com>  Mon, 23 Mar 2020 20:55:28 -0400
+
 lintian (2.59.0) unstable; urgency=medium
 
   [ Chris Lamb ]
diff -Nru lintian-2.59.0/tags/a/ancient-python-version-field.desc lintian-2.59.0+/tags/a/ancient-python-version-field.desc
--- lintian-2.59.0/tags/a/ancient-python-version-field.desc	2020-03-22 16:22:08.000000000 -0400
+++ lintian-2.59.0+/tags/a/ancient-python-version-field.desc	2020-03-23 20:55:28.000000000 -0400
@@ -7,4 +7,7 @@
  associated Python version is satisfied by the current "oldstable"
  distribution of Debian and is therefore unnecessary.
  .
- Please remove or update the reference.
+ Please remove or update the reference.  If removing, please also check
+ for the use of py3versions -r in debian/control, debian/rules, and debian/
+ tests/.  Without an operative Python3-Version field py3versions will fall
+ back to all supported versions, which may not be appropriate.
diff -Nru lintian-2.59.0/tags/o/old-python-version-field.desc lintian-2.59.0+/tags/o/old-python-version-field.desc
--- lintian-2.59.0/tags/o/old-python-version-field.desc	2020-03-22 16:22:08.000000000 -0400
+++ lintian-2.59.0+/tags/o/old-python-version-field.desc	2020-03-23 20:55:28.000000000 -0400
@@ -8,4 +8,7 @@
  distribution of Debian and may be unnecessary.
  .
  Please remove or update the reference. This warning should be ignored
- if you wish to support "sloppy" backports.
+ if you wish to support "sloppy" backports.    If removing, please also check
+ for the use of py3versions -r in debian/control, debian/rules, and debian/
+ tests/.  Without an operative Python3-Version field py3versions will fall
+ back to all supported versions, which may not be appropriate.

--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.60.0
Done: Chris Lamb <lamby@debian.org>

We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954819@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb <lamby@debian.org> (supplier of updated lintian package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 25 Mar 2020 10:56:21 +0000
Source: lintian
Built-For-Profiles: nocheck
Architecture: source
Version: 2.60.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Closes: 954146 954484 954763 954798 954803 954819
Changes:
 lintian (2.60.0) unstable; urgency=medium
 .
   * Summary of tag changes:
     + Added:
       - runtime-test-file-uses-installed-python-versions
       - upstream-metadata-not-yaml-mapping
 .
   [ Chris Lamb ]
   * Do not check the length of Checksums-Sha256 fields. (Closes: #954798)
   * Don't check for an md5sums control files in udebs. (Closes: #954803)
   * Expand possible-missing-colon-in-closes to also check for semicolons
     used in place of colons. (Closes: #954484)
   * Check for calls to py3versions -i in autopkgtests. (Closes: #954763)
 .
   [ Felix Lechner ]
   * Do not run the fields/length check on .changes or .buildinfo files.
     (Closes: #954146)
   * Check for upstream metadata without a YAML mapping at the "document"
     level.
 .
   [ Scott Kitterman ]
   * Update "old" and "ancient" python-version-field tags descriptions to
     suggest also checking for incorrect use of "py3versons -r".
     (Closes: #954819)
Checksums-Sha1:
 d464ad2c2eddc0726fdcc21255f771b6912e3a73 4158 lintian_2.60.0.dsc
 f435612f2d277df5b4e58e07827d6242254a4bec 1876580 lintian_2.60.0.tar.xz
 715c4da25e7dbdbf615a736281dd8ba584695f1c 6095 lintian_2.60.0_amd64.buildinfo
Checksums-Sha256:
 438712d6fe9bee09cd19376c4f310950218fd0bd382f39e9e535a9cfb0b54dd3 4158 lintian_2.60.0.dsc
 703943a1dc31db92d399435fc9cd40d77a538c11db6dcc0004353dfaa7dd81c3 1876580 lintian_2.60.0.tar.xz
 1d8562f549936f63285294643c82f473be27632144b0099cc29e0c1a97009b4a 6095 lintian_2.60.0_amd64.buildinfo
Files:
 c3dcd758ed3466e5e695bab4d4f1b813 4158 devel optional lintian_2.60.0.dsc
 5d1ef57cfeefc13788876372dba66a3d 1876580 devel optional lintian_2.60.0.tar.xz
 996c7890e7e2ffad3ea16f9a24916cac 6095 devel optional lintian_2.60.0_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl57OWgACgkQHpU+J9Qx
Hlia4RAAtBFS5yIVaU/JuuDfsNoAe+l5LboYU42/Q5uj0SjlycgLp9e+5kRgkqOx
NV6usRsYUfKW8/I53bN0YnOapZKKp5ghKvJSPsMigaQ6uOYz+wcP6fgGJj3i+WtE
oo+qmVS+rSC1YF3W4jxfteyxRiwoSQWyN4tRc/kZnoAKrfSljRhBLssMQPv6M8vS
suHkhv8evu9mBu6IbBOk9rKBOwOpLR+QctZ01RjIfrXP08WVBcZCWGq3qV5PXYda
SwDZrbIaBmWz4xIQdRT7gNLbTDMCVIVIiRpnW4SEFqzx0sjRFqXghW2R7YQDS7hs
hWAysAVYvfn60khwdbS6oL6LxUL1WG4ACIQp0Op+xX/2mRt3Gv7t+njqUHkiEJO5
EawlGPI11zgwatb3PNeB44Dp2bdcmS2QfvGeMDZeVIj5b88pi2VusTh2oznew7h6
sZgEw/GXMf6rTh8DnODMY3fNNidCVH7LNEj/vol1/uxmyIEOKX3CBTSO8WSyUHZT
kKtb/8thU7iRBBi/mQTsHJefWeVfpkUCZk9x2EioM+WiG3hpNB+3DX2FV4cFUe3u
yTaeln/P8oCy1NbzOQuOsCpHfelife881+oNHv1zl6OWPacRyMCziJBwTtapZuuk
oKRviKZms9BEl9VwcrgTpUc9gVy/QGA9edLpNJOM8SSX6S5NCxQ=
=5/tq
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: