Bug 1546814 - python-tld: python3-tld requires both Python 2 and Python 3
Summary: python-tld: python3-tld requires both Python 2 and Python 3
Alias: None
Product: Fedora
Classification: Fedora
Component: python-tld
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: William Moreno
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-02-19 16:24 UTC by Iryna Shcherbina
Modified: 2018-03-16 20:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-03-16 20:12:28 UTC
Type: Bug

Attachments (Terms of Use)

Description Iryna Shcherbina 2018-02-19 16:24:59 UTC
The python3-tld (0.7.9-4.fc28) RPM requires both Python 2 and Python 3:

$  dnf --disablerepo=* --enablerepo=rawhide repoquery --requires python3-tld | grep python
python(abi) = 3.6

This happened due to recently introduced shebangs mangling [0], and you might see the warnings in the build log:

> + /usr/lib/rpm/redhat/brp-mangle-shebangs
> *** WARNING: mangling shebang in ./usr/lib/python3.6/site-packages/tld/bin/update-tld-names from #!/usr/bin/env python to #!/usr/bin/python2. This will become an ERROR, fix it manually!

The executable contains `#!/usr/bin/env python` shebang, which is forbidden by the guidelines and is automatically mangled to `#!/usr/bin/python2` during build. Please fix the shebang to be `#!/usr/bin/python3` explicitly [1].

If anything is unclear, or if you need any kind of assistance, you can
ask on IRC (#fedora-python on Freenode), or reply here. We'll be happy
to help investigating or fixing this issue!

[0] https://pagure.io/packaging-committee/issue/738#comment-490366
[1] http://python-rpm-porting.readthedocs.io/en/latest/application-modules.html#fixing-shebangs

Comment 1 Fedora End Of Life 2018-02-20 15:37:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 2 Jan Beran 2018-03-16 16:29:33 UTC
Hello William,

I have prepared a Pagure PR which fixes the issue:


May I ask to review and merge the PR?

Comment 3 William Moreno 2018-03-16 20:09:37 UTC
have merged it, is building now:


Note You need to log in before you can comment on or make changes to this bug.