As each box provide comes into life (they are located in different countries / time zones - so get package update checks at different times) I am getting “package updates are available”
seems rather drastic I have 6 boxes with well over 24 VS live production domains + others pending. Rebooting boxes is such a major task (backups + time + notification) and seems overkill
After an apt-get update, an apt-get upgrade for me shows the following (Ubuntu 22.04.02, VM 7.7 Pro):
$ sudo apt-get upgrade
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
The following packages have been kept back:
linux-generic linux-headers-generic linux-image-generic
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
The simple command-line upgrade does not show the “problem”, only 3 packages that are kept back. This behavior has been discussed earlier at the forum.
Yeah. They were working on a way to get the GUI to just show the ‘recommended’ instead of the ‘available’ I think. Personally I think it is kinda broken behavior on Ubuntu’s part, but, that’s only my opinion. Release it or don’t.
Yes. I have sort of come to rely on that " Package updates All installed packages are up to date" prompt in the dashboard. never having a problem up to now.
Short explanation first. I’ve learned to burn an install DVD prior to updating my desktop Debian. I’ll admit to abusing it so when the update fails (all but once) I just start over and remap my home raid. This causes me to revisit a lot of things I need to redo. Which leads to this question.
I’ve noticed an ‘updates’ in my /etc/apt/source.list
# bookworm-updates, to get updates before a point release is made; # see Chapter 2. Debian package management deb http://deb.debian.org/debian/ bookworm-updates main non-free-firmware contrib non-free
I do not recommend running autoremove without extreme caution! It does not solve dependency problems, and can cause serious problems if you removed (maybe accidentally) the Virtualmin stack packages (or other packages that might have installed dependencies you rely on, without realizing it was installed because of dependencies).
If using autoremove, you must carefully read the list of packages it will be removing, and if some of them are important to you, you need to set them to manually installed with apt install <packagename>.
I mean, it’s a fine practice, as long as you know what you’re doing.
We’ve just had a lot of folks blow up their systems using autoremove, without reading the list of packages being removed. If they’d installed something that removed Postfix, for instance, it would have caused virtualmin-lamp-stack to also be removed…so, an autoremove would remove Apache, MariaDB, and everything else, basically leveling the system. That’s actually happened many times. Like, surprisingly often.
