archygriswald wrote: ↑2022-05-20 10:17When doing
I see that apache2 is going to be installed. I do not want apache on my system, I have nginx already running.
How can I prevent this?
The first step is finding what package pulls apache2. You can add Debug::pkgDepCache::AutoInstall option to your initial command.
'man 5 apt.conf' excerpt:
Debug::pkgDepCache::AutoInstall
Generate debug messages describing which packages are being automatically installed to resolve dependencies. This corresponds to the initial auto-install pass performed in, e.g., apt-get install, and not to the full apt dependency resolver; see Debug::pkgProblemResolver for that.
Code: Select all
apt -o Debug::pkgDepCache::AutoInstall=1 -sV full-upgrade
If you don't know how to asses the result, you can paste here the relevant part.
archygriswald wrote: ↑2022-05-20 10:17Is it safe to do
Code: Select all
apt-mark hold apache2, apt-mark hold apache2-bin, etc.
and then do the upgrade?
According to the
release notes, it is not safe:
It is desirable to remove any holds before upgrading. If any package that is essential for the upgrade is on hold, the upgrade will fail.
archygriswald wrote: ↑2022-05-20 10:17(( Also: I see many packages that the upgrade wants to install, like libdrm & some graphics drivers.
This is frustrating because if I did not have them on buster then why is the upgrade trying to install them for bullseye? This is an internet facing machine that I want to keep as minimal and clean as possible.
Why is Debian doing this? ))
Because package dependencies change over Debian versions. Sometimes packages need new dependencies, sometimes libraries or packages are split into several parts.
Some new dependencies are "only" recommended (field Recommends in package descriptions) and you can ponder whether to keep them.
It is also important to minimize manually installed packages: this means marking as much as possible packages as automatically installed. For instance, if a library is marked as manually installed, the upgrade process will keep it (and its dependencies) even if it is now useless.
In my experience, newer Debian versions always take more disk space and pull new packages though.