I am shocked and appalled at the level of "blame the victim" (*) that is going on here.
It is 100% clear to me that if apt thinks uninstalling systemd is the right thing to do - and is what the user wants to happen - then something is wrong. That should cause apt (and/or apt-get) to put up a red flag that says "I'm not doing this".
BTW, I got burned by this recently. Luckily, it was a pretty much fresh install, so little was lost.
It boils down to: If you are doing anything with apt more complicated than a simple "apt install something", you should run it first with -s and see what it plans to do. That's the lesson I learned from my recent adventure.
(*) And "circle the wagons".
It is 100% clear to me that if apt thinks uninstalling systemd is the right thing to do - and is what the user wants to happen - then something is wrong. That should cause apt (and/or apt-get) to put up a red flag that says "I'm not doing this".
BTW, I got burned by this recently. Luckily, it was a pretty much fresh install, so little was lost.
It boils down to: If you are doing anything with apt more complicated than a simple "apt install something", you should run it first with -s and see what it plans to do. That's the lesson I learned from my recent adventure.
(*) And "circle the wagons".
Statistics: Posted by BigRedMailbox — Wed May 29, 2024 2:16 am