Force python2 usage and provide Ubuntu install scripts for Focal #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
neilsummers
force-pushed
the
python2_ubuntu_focal
branch
from
0504aa1
to
5c5b5f0
Compare
|
Thanks for your submission! With 1.43.8-rc1 released that is now Python 3 and GTK 4 compatible, we should no longer have to worry about Python 2 back-compat (and fwbackups will no longer support Python 2). |
stewartadam
added a commit
that referenced
this pull request
Jul 3, 2024
stewartadam
added a commit
that referenced
this pull request
Jul 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I ran into the same issue as #13 and have been trying to find a good solution since upgrading to Ubuntu Focal 20.04. Previously had it working on Ubuntu 18.04 (Bionic) with no problems.
Python2 and Python3 can both coexist on the same system without conflict as all libraries are installed in separate site-packages directories and only the Python? directories are used in the Python path when invoking the correct interpreter version. It is Ubuntu's package management system that will not allow both to coexist, by using the python-is-python? package to force one version or the other. You can get this to work quite easily by adding bionic sources and using python-is-python2 and then continuing with install as before, but then everything on your system is limited to python2, which is not a good solution.
Therefore I managed to install fwbackups by installing the dependencies and hacking the dependencies file to remove the dependencies which forced the python2 version. Then with just some simple modifications to the fwbackups scripts to point explicitly to python2, and making sure python2 is specified when running configure, and everything now worked as usual. The method was quite tricky so I made a script to automate it and made this PR for visibility in case anyone else wants to follow the same procedure.