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

Bug#633057: marked as done (lintian: Add a central place to list Python versions)

Your message dated Tue, 07 Aug 2018 15:22:36 +0100
with message-id <1533651756.1977417.1466278680.0F047E5C@webmail.messagingengine.com>
and subject line Re: lintian: Add a central place to list Python versions
has caused the Debian Bug report #633057,
regarding lintian: Add a central place to list Python versions
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.)


-- 
633057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633057
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: lintian
Version: 2.5.2
Severity: wishlist
The are currently (at least?) 2 places where lintian lists Python versions: checks/rules ($PYTHON2X_DEPEND, $PYTHON3X_DEPEND) and checks/fields ($PYTHON_DEV). Theses lists can quickly get out of sync and out of date. It'd nice if lintian could have a central place (somewhere in /u/s/lintian/data/?) to list Python version.
Also, we should decide *which* versions we are actually interested in? All currently supported in unstable? All currently existing in unstable? Maybe all supported either in unstable or stable? 

(debian-python@ CCed.)

--
Jakub Wilk

--- End Message ---
--- Begin Message --- 
Version: 2.5.93

> Add a central place to list Python versions

Since:

  https://salsa.debian.org/lintian/lintian/commit/8b3cd0bf04eb99131e21891573b821147298c2bd

... we have had this. :)


Best wishes,

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

--- End Message ---
Reply to: