Can you elaborate on this please? It seems as though you meant to say "Forky since a few hours", not Trixie, since this entire topic is about Trixie becoming the new Debian Stable (or am I totally misunderstanding the situation??).So it is about how well RPL patches work with Debian Testing (Trixie since a few hours).
I have an RPi 4 on which I've had "pure" Trixie (not RPiOS) fully up and running well for about a year or two (so long that I can't remember how long lol). I did this by manually updating my 'sources.list' to point to 'trixie', not 'testing' or anything else that may be unsupported.
So imagine my surprise when an in-place upgrade attempt seems to have left me with an unbootable system, where there are no systemd, init, udevd or modprobe binaries to be found in the expected places (although they do still exist in their old locations).
This is still my own fault (and partially OpenAI's fault) since:
- I should have followed the golden rule and backed up before I did anything!
- I shouldn't have asked an AI chatbot how to complete such a complex and unsupported process.
- Said chatbot shouldn't have led me down the garden path and made me think that I could do this by using a complex Bash script to exclude system-level packages from a 'sudo apt install <packages>' command (about a day of my life wasted there).
- I probably should have just followed the official documentation re: upgrading from Bookworm - although does this apply if you're actually upgrading from an existing Trixie install, but just from when it was Debian Testing instead of Debian Stable?
Statistics: Posted by CoopMeisterFresh — Mon Oct 20, 2025 5:17 am