This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
the debian packages fail subtly if you install them on the wrong distro #4431
Comments
|
(this confuses users and leads to support overhead) |
richvdh
added a commit
that referenced
this issue
Jan 22, 2019
In the debian package, make the virtualenv symlink python to /usr/bin/python3.X rather than /usr/bin/python3. Also make sure we depend on the right python3.x package. This might help a bit with subtle failures when people install a package from the wrong distro (#4431).
richvdh
added a commit
that referenced
this issue
Jan 23, 2019
In the debian package, make the virtualenv symlink python to /usr/bin/python3.X rather than /usr/bin/python3. Also make sure we depend on the right python3.x package. This might help a bit with subtle failures when people install a package from the wrong distro (#4431).
|
hopefully improved by #4433 |
10 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
if you put the wrong distro name in
sources.list(eg, 'stretch' instead of 'buster'), you get a cryptic error:(The reason for the error is that
bin/pythonis python 3.7, whereas the py files are installed inlib/python3.5, though there are other reasons that the two will be incompatible)Can we make this fail in a more obvious manner?
The text was updated successfully, but these errors were encountered: