- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
I’ve been running my home lab since 2021 and honestly thought my update routine was solid: apt update && apt upgrade, reboot, job done.
Turns out I was wrong. I was checking CVE‑2026‑31431 (Copy Fail) this morning and realised that despite my “successful” updates, I was still running a vulnerable kernel from March.
I’ve had to rethink how I handle host updates. If you’re relying on a standard upgrade and a reboot to keep Proxmox or Debian hosts safe, you might want to check if yours is lying to you as well.
apt dist-upgrade is a necessary change to your process in place of just upgrade.
I may be wrong but I think it’s apt-get dist-upgrade. apt full-upgrade does the same too.
apt-get is now deprecated on Debian and Ubuntu. But otherwise, no notes.
When a kernel update requires a change in dependencies, something Proxmox kernels do frequently, apt just quietly “keeps back” the package. It doesn’t fail, it doesn’t break the system, and it doesn’t trigger a rollback. It just waits for me to notice.
This should save a click for hopefully everyone.
Yes obviously, if you do not update the packages then they do not get updated.
If you do not read the output of a command then you will not notuce that.
The standard upgrade command has this behavior though, which is unexpected to people like me and the author. You need a specific flag to tell apt to actually upgrade everything which is not the behavior I expected.
But it is clearly stated in the output that it holds back packages.
Sure in the gigantic wall of text. Also it doesn’t tell you why, or what to do about it. All they’d have to do is say “run dist-upgrade to update these packages.”
Sure in the gigantic wall of text. Also it doesn’t tell you why, or what to do about it. All they’d have to do is say “run dist-upgrade to update these packages.”
It is literally in the summary that gets presented in the last few lines before you have to press Y to continue.
Since you are already overwhelmed by the wall of text, you would probably not read the suggestion antways.
I cross posted this to !selfhosted@lemmy.world, I hope that was ok! I figured it would be good to spread the knowledge
Thanks for sharing this. I’m very confident with Linux, but I hadn’t thought about this!
Your blog post was concise, too. I hate scrolling forever before finding the solution.
Glad you found it useful. I’m the same, I can’t stand those long posts that make you read a life story before getting to the commands, even worse when a page is riddled by ads or behind a paywall!
I figured if I’d missed it, a few other people probably had too.
This is specific to Debian and Ubuntu so why not being more specific in the title?
pacman -Syugoes brrrWould apt-get images of apt have saved you?
No, apt isn’t just a rename. apt upgrade largely replaces apt-get upgrade, but it’s a bit more aggressive: it may install new packages if required as dependencies (it still won’t remove packages). If an upgrade needs to remove packages to resolve dependencies, use apt full-upgrade (same as apt-get dist-upgrade).
Yeah, apt is an unwieldy piece of shit.
I’d say Python is instead.
?
I’m sorry, wrong thread.
is this specific to apt? dnf or pacman dont suffer from this?
I don’t know for certain but this seems pretty apt specific.
I’ve not come across this with my non Debian based systems. Only use Debian for servers because it’s so stable, Arch and Fedora everywhere else!
Uhm, you dont update the host OS??
Why?
Shouldnt an updater run on the host? And Debian should always update the kernel with apt?
I’m the same way. My Debian server is two versions out of date, but it’s still getting security updates and works, so why in the world would I upgrade?
Because the kernel and packages are severely outdated, only getting urgent patches
This seems to me like a pretty urgent patch
Yes but there are tons of others that dont get CVEs lol
Yay!
There’s no point in digital hoarding; it just clutters the boot partition and makes future updates messier.
I feel personally attacked.










