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

Bug#708138: marked as done (lintian: python-script-but-no-python-dep should accept python3.3)



Your message dated Sat, 18 May 2013 07:00:28 +0900
with message-id <20130517220028.GA8840@goofy.localdomain>
and subject line Re: Bug#708138: lintian: python-script-but-no-python-dep should accept python3.3
has caused the Debian Bug report #708138,
regarding lintian: python-script-but-no-python-dep should accept python3.3
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.)


-- 
708138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708138
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.10.4
Severity: normal

This may be somewhat similar to bug#673734.

I had script started as:
#!/usr/bin/python3

The python3 setup.py with dh --with python3 seems to convert this to:
#! /usr/bin/python3.3
(Please note space.)

I guess, it substitute with the current default python version 3.3
chosen by the python3 package.

Anyway, I get lintian ERROR with somewhat strange texts with my 
package debmake in NEW.

For dh --with ..., we should use python2 for python 2 series and python3 for
python 3 series. dh_pysupport or dh_pycentral are history.

I have "Depends: python3" in binary and get the following.  This seems to
limit only to python and do not accept python3 variants.

(The same result with version of lintian in testing/sid=2.5.10.5 too)

$ lintian -i debmake_4.0.0-1_amd64.changes 
E: debmake: python-script-but-no-python-dep usr/bin/debmake
N: 
N:    Packages with Python scripts should depend on the package python. Those
N:    with scripts that specify a specific version of Python must depend on
N:    that version of Python (exactly).
N:    
N:    For example, if a script in the package uses #!/usr/bin/python, the
N:    package needs a dependency on python. If a script uses
N:    #!/usr/bin/python2.6, the package needs a dependency on python2.6. A
N:    dependency on python (>= 2.6) is not correct, since later versions of
N:    Python may not provide the /usr/bin/python2.6 binary.
N:    
N:    If you are using debhelper, adding ${python:Depends} to the Depends
N:    field and ensuring dh_pysupport or dh_pycentral are run during the build
N:    should take care of adding the correct dependency.
N:    
N:    In some cases a weaker relationship, such as Suggests or Recommends,
N:    will be more appropriate.
N:    
N:    Severity: important, Certainty: certain
N:    
N:    Check: scripts, Type: binary
N: 

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils                       2.22-8
ii  bzip2                          1.0.6-4
ii  diffstat                       1.55-3
ii  file                           5.11-2
ii  gettext                        0.18.1.1-9
ii  hardening-includes             2.3
ii  intltool-debian                0.35.0+20060710.1
ii  libapt-pkg-perl                0.1.26+b1
ii  libarchive-zip-perl            1.30-6
ii  libc-bin                       2.13-38
ii  libclass-accessor-perl         0.34-1
ii  libclone-perl                  0.31-1+b2
ii  libdpkg-perl                   1.16.10
ii  libemail-valid-perl            0.190-1
ii  libipc-run-perl                0.92-1
ii  libparse-debianchangelog-perl  1.2.0-1
ii  libtimedate-perl               1.2000-1
ii  liburi-perl                    1.60-1
ii  locales                        2.13-38
ii  locales-all [locales]          2.13-38
ii  man-db                         2.6.3-3
ii  patchutils                     0.3.2-1.1
ii  perl [libdigest-sha-perl]      5.14.2-21

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch     <none>
ii  dpkg-dev               1.16.10
ii  libhtml-parser-perl    3.69-2
pn  libperlio-gzip-perl    <none>
ii  libtext-template-perl  1.45-2
ii  man-db                 2.6.3-3
ii  xz-utils [lzma]        5.1.1alpha+20120614-2

-- no debconf information

--- End Message ---
--- Begin Message ---
Thanks for your time and effort. I am closing this bug.

> These warnings should have given you a clue about what's wrong:

I certainly need *clue*.  Thanks.

So I fixed this bug in my package.

But where did this wrong idea of using ${python:Depends} come from :-)

dh_python3 manpage in wheezy has the following:

 --depends=DEPENDS
        translate given requirements into Debian dependencies and add them to ${python:Depends}. Use it for missing items in requires.txt.

 --recommends=RECOMMENDS
        translate given requirements into Debian dependencies and add them to ${python:Recommends}

 --suggests=SUGGESTS
        translate given requirements into Debian dependencies and add them to ${python:Suggests}

No mention of ${python3:Depends} etc. in http://www.debian.org/doc/packaging-manuals/python-policy/ap-packaging_tools.html#s-dh_python2_3 either.

Osamu

--- End Message ---

Reply to: