Your message dated Tue, 02 Apr 2019 17:34:43 +0800
with message-id <[email protected]>
and subject line Re: Bug#926187: dh-python: dh_python3 replaces shebang with
/usr/bin/python2 not /usr/bin/python3
has caused the Debian Bug report #926187,
regarding dh-python: dh_python3 replaces shebang with /usr/bin/python2 not
/usr/bin/python3
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 [email protected]
immediately.)
--
926187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926187
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dh-python
Version: 3.20190308
Severity: normal
I'm trying to update petsc 3.11 to build with python3 rather than
python2 (petsc 3.11 in the petsc experimental branch on salsa now
supports python3 in its configure script).
Some of petsc's python scripts have a generic shebang,
#!/usr/bin/env python
e.g. PetscBinaryIOTrajectory.py and other scripts in
lib/petsc/bin/ These scripts are installed in package
libpetsc3.11-dev-common, in /usr/share/petsc/3.11/lib/petsc/bin/
I've set petsc's debian/rules to dh $@ --with python3
dh_python3 is invoked by the build, and updates the #!/usr/bin/env python
shebangs.
But dh_python3 updates the shebangs to /usr/bin/python instead of
/usr/bin/python3
I would have expected dh_python3 to update them to /usr/bin/python3,
at least if dh --with python3 is used without python2.
Is this a bug in dh_python3?
(I can override it with dh_python3 --shebang of course, but I'm trying
to use automatic defaults where possible)
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dh-python depends on:
ii python3 3.7.3-1
ii python3-distutils 3.7.3-1
dh-python recommends no packages.
Versions of packages dh-python suggests:
ii dpkg-dev 1.19.6
ii libdpkg-perl 1.19.6
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2019-04-02 03:38, Piotr Ozarowski wrote:
I see. So you mean upstream would need to use
#!/usr/bin/env python3
to get it handled as /usr/bin/python3
yes
(I know some upstreams think /usr/bin/python is Python 3.X…)
Thanks Piotr, that clarifies the situation.
I might as well close this bug then.
Drew
--- End Message ---
