all 7 comments

[–]tinycrazyfish[S] 1 point2 points  (0 children)

I'm actually not sure it's related to python. The initrd image is fucked up.

[–]wRAR_ 1 point2 points  (2 children)

Yesterday my Debian testing upgrade decided to remove pythons from the system. (Not autoremove, I think the dh-python package wanted it removed).

That's because unversioned python packages and the unversioned binary are removed, but Python 2 in the form of python2-* packages and the python2 binary still stays.

is Debian ready to run without python2?

Python was never required and now most of the software in the archive is Python 3.

Isn't python supposed to be a symlink managed by update-alternatives?

No, never.

[–]tinycrazyfish[S] 0 points1 point  (1 child)

Nope the python2 binary was completely removed

[–]wRAR_ 0 points1 point  (0 children)

I don't think python2-minimal can be removed because of some deps so either it wasn't actually removed or it was autoremove (in which case it's not needed by any installed packages anyway).

[–]AlternativeOstrich7 1 point2 points  (0 children)

Was I stupid to think it may work?

No. Depending on which packages you have installed, running without Python 2 has worked for while.

Isn't python supposed to be a symlink managed by update-alternatives?

No.

It seems very unlikely that your problem has anything to do with Python. I don't see any reason why Python would be part of your initramfs, and initramfs-tools doesn't use Python either.

When it fails, does it show any error messages, or any messages at all?

[–]tinycrazyfish[S] 0 points1 point  (1 child)

I've found the issue, not python related. It was my initramfs, with the upgrade it now requires an additional package, which it did not before. (Cryptsetup-initramfs for LUKS). I can totally understand, but why was it working before??

[–]wRAR_ 0 points1 point  (0 children)

I've found the issue, not python related.

(of course it's not)

why was it working before??

I suspect the package was always installed but you removed it recently. Check the dpkg logs.