Skip to content
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

Open
Seb35 opened this issue Mar 28, 2020 · 5 comments
Open

Upgrade to Python3 #11

Seb35 opened this issue Mar 28, 2020 · 5 comments

Comments

@Seb35
Copy link
Contributor

Seb35 commented Mar 28, 2020

Currently on Debian 10 this package depends on the package python, which is python2 (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.

@dholl
Copy link
Contributor

dholl commented Oct 1, 2020

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":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970425

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 python package (2.7.17-2), thus preventing their automatic upgrade 2.7.18 (which python does not depend on):
libpython2-stdlib
python2
python2-minimal

Anyhow, if gandi-vm-config doesn't update to python3, I'd hope that switching the gandi-vm-config2 package to depend on python2 instead of python would ease the transition for everyone in the next Debian stable release.

Seb35 added a commit to Seb35/gandi-vm-config that referenced this issue Nov 9, 2023
@Seb35 Seb35 mentioned this issue Nov 9, 2023
Seb35 added a commit to Seb35/gandi-vm-config that referenced this issue Nov 9, 2023
Issue: Gandi#11
(cherry picked from commit 224ab11)
@Seb35
Copy link
Contributor Author

Seb35 commented Nov 9, 2023

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 (gandi-hosting-vm2_2.41+nmu1_all.deb). Transfer the .deb to the server, then install it with dpkg -i gandi-hosting-vm2_2.41+nmu1_all.deb. This is provided without any guarantee.

@svillemot
Copy link

Due to this issue, gandi-hosting-vm2 is now uninstallable on Debian 12 “bookworm“, since the latter no longer ships Python 2.

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 gandi-hosting-vm2 no longer needed/recommended?

@gdchamal
Copy link
Member

As a quick solution you can remove gandi-hosting-vm2 package before. This package is mostly needed at first boot to configure correctly the VM.

@svillemot
Copy link

My impression is that gandi-hosting-vm2 mounts the virtual disk(s), so I’m not very eager to remove it. But maybe an equivalent solution can be created using entries in /etc/fstab or .mount systemd units.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants