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

Bug#788233: marked as done (lintian: Requirements version mismatches with archive python module versions)

Your message dated Sat, 30 Dec 2017 22:17:21 +0000
with message-id <1514672241.866354.1219852248.57260AFB@webmail.messagingengine.com>
and subject line Re: lintian: Requirements version mismatches with archive python module versions
has caused the Debian Bug report #788233,
regarding lintian: Requirements version mismatches with archive python module 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.)


-- 
788233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788233
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.5.30+deb8u3ubuntu2
Severity: normal

Dear Maintainer,

Python modules often declare version requirements for dependencies, either in setup.py/cfg or requirements.txt (see most of the OpenStack python packages for examples).

A check (probably informational) that validates that the version of a python module in archive falls in the upstream version bounds would be useful, as its often a good indicator of integration issue between python modules, or dependencies on new features.

I'd be willing to help test any proposed solution, but my Perl foo is not up to scratch to actually write this myself.

Thanks

James

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), (100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-20-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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.25-8ubuntu1
ii  bzip2                          1.0.6-8
ii  diffstat                       1.59-1
ii  file                           1:5.22+15-2ubuntu1
ii  gettext                        0.19.2-2ubuntu1
ii  hardening-includes             2.7ubuntu1
ii  intltool-debian                0.35.0+20060710.2
ii  libapt-pkg-perl                0.1.29build2
ii  libarchive-zip-perl            1.39-1
ii  libclass-accessor-perl         0.34-1
ii  libclone-perl                  0.38-1
ii  libdpkg-perl                   1.17.25ubuntu1
ii  libemail-valid-perl            1.195-1
ii  libfile-basedir-perl           0.03-1fakesync1
ii  libipc-run-perl                0.94-1
ii  liblist-moreutils-perl         0.33-2build1
ii  libparse-debianchangelog-perl  1.2.0-1.1
ii  libtext-levenshtein-perl       0.12-1
ii  libtimedate-perl               2.3000-2
ii  liburi-perl                    1.64-1
ii  man-db                         2.7.0.2-5
ii  patchutils                     0.3.4-1
ii  perl [libdigest-sha-perl]      5.20.2-6
ii  t1utils                        1.38-4

Versions of packages lintian recommends:
ii  libperlio-gzip-perl             0.18-3build1
ii  perl                            5.20.2-6
ii  perl-modules [libautodie-perl]  5.20.2-6

Versions of packages lintian suggests:
pn  binutils-multiarch     <none>
ii  dpkg-dev               1.17.25ubuntu1
ii  libhtml-parser-perl    3.71-2
ii  libtext-template-perl  1.46-1
pn  libyaml-perl           <none>
ii  xz-utils               5.1.1alpha+20120614-2ubuntu2

-- no debconf information

--- End Message ---
--- Begin Message --- 
tags 788233 + wontfix
thanks

Hi,

> lintian: Requirements version mismatches with archive python module versions

Unfortunately, Lintian does not have access to the versions in the
archive so unfortunately we cannot satisfy your request here.

(In addition, I worry about the practicality of re-implementing the
requirements.txt parser, especially as the primary entry point is
not always ./requirements.txt)


Best wishes,

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

--- End Message ---
Reply to: