-
Notifications
You must be signed in to change notification settings - Fork 11
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
Upgrade to Python3 #11
Comments
The longer this issue remains unaddressed, the more it is becoming critical. According to this correspondence dated 2020-09-16, "The python package is now removed in testing": I found this out the hard way when updating packages on a Debian "testing" system, and aptitude wanted to "fix" the issues by removing the gandi-vm-config2 package. Fortunately I caught it, and pinned these 3 packages at their last version that is depended upon by the Anyhow, if gandi-vm-config doesn't update to python3, I'd hope that switching the |
Issue: Gandi#11
The PR #26 is a first draft to remove Python3, but only a limited testing was done on it. I issued an nmu version (non-maintainer upload) on my fork 2.41+nmu1, to be packaged with: (tested on Debian 11, the building might be executed on a developer machine) sudo apt-get install build-essential devscripts
git clone -b debian/2.41+nmu1 https://github.com/Seb35/gandi-vm-config
cd gandi-vm-config
dpkg-buildpackage -us -uc The .deb is in the parent directory ( |
Due to this issue, So this is a pretty critical issue. I’m now forced to install unsupported Python 2 binaries on my Gandi Cloud server to make it work… Or is |
As a quick solution you can remove |
My impression is that |
Currently on Debian 10 this package depends on the package
python
, which ispython2
(which reached its end-of-life on January 1, 2020). It should be upgraded to Python3.On a fresh Debian 10, it is the only package depending on python2.
The text was updated successfully, but these errors were encountered: