-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python3 console_scripts file name conflict #7
Comments
hrudham
pushed a commit
to hrudham/wheel2deb
that referenced
this issue
Jul 9, 2020
…version appended for python3
hrudham
pushed a commit
to hrudham/wheel2deb
that referenced
this issue
Jul 9, 2020
…ersion appended for python3
hrudham
added a commit
to hrudham/wheel2deb
that referenced
this issue
Jul 10, 2020
hrudham
pushed a commit
to hrudham/wheel2deb
that referenced
this issue
Jul 10, 2020
…version appended for python3
hrudham
pushed a commit
to hrudham/wheel2deb
that referenced
this issue
Jul 10, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If
wheel2deb
is used to build a Debian package for a project that has aconsole_scripts
entry point, you may find yourself in a position where you cannot install a package.For example, the
pyjwt
package has two existing (official) Debian packages provided:python-jwt
, which installs thepython2
version, andpython3-jwt
for thepython3
version. Both of these Debian packages create a file in the/usr/bin
directory. In the case ofpython-jwt
, this is/usr/bin/pyjwt
, and in the casepython3-jwt
, this is/usr/bin/pyjwt3
.However, when building these packages via
wheel2deb
, both of them end up creating/usr/bin/pyjwt
. This causes problems specifically with thepython3
version if the official (orwheel2deb
generated)python2
version is already installed:The text was updated successfully, but these errors were encountered: