Hello,
the no-upgrade-base-files and no-upgrade-software-properties-gtk files located
inside /etc/apt/preferences.d/ create the following inconveniences:
no-upgrade-base-files:
Prevents base-files from being updated, which blocks a cascade of security
updates, some of which can be critical:
libc6, libc-bin, libc-dev-bin, libc6-dev, locales, and recommends.
libc6 is one of the most fundamental libraries on the system, and blocking its
updates along with its dependencies means missing potentially critical security
patches.
no-upgrade-software-properties-gtk:
Prevents software-properties-gtk from being updated, blocking in cascade:
python3-software-properties and software-properties-common, among else.
I am not sure what the base-files package update caused in your system, in mine,
it has not caused any issue after removing its pinning and updating it (tested then
in VirtualBox and on bare metal in a laptop).
As for software-properties-gtk, maybe did you want to block the Ubuntu Pro packages?
If so, a less invasive approach can be applied: neutralizing the file
/etc/apt/update-notifier/20apt-esm-hook.conf by replacing its content with a
comment is what I have been doing for several years now.
This prevents the recurring Ubuntu Pro registration prompts without blocking
legitimate security updates. And keeping it, with an explicit comment lets the users
be informed.
This is what I wrote in my personal file:
# If prompted to choose a new file when updating or upgrading,
# the package keep this file if you don't want systematic invitations to
# register to Ubuntu Pro when updating the system.
Best regards and thanks for your work.
Hello,
the no-upgrade-base-files and no-upgrade-software-properties-gtk files located
inside /etc/apt/preferences.d/ create the following inconveniences:
no-upgrade-base-files:
Prevents base-files from being updated, which blocks a cascade of security
updates, some of which can be critical:
libc6, libc-bin, libc-dev-bin, libc6-dev, locales, and recommends.
libc6 is one of the most fundamental libraries on the system, and blocking its
updates along with its dependencies means missing potentially critical security
patches.
no-upgrade-software-properties-gtk:
Prevents software-properties-gtk from being updated, blocking in cascade:
python3-software-properties and software-properties-common, among else.
I am not sure what the base-files package update caused in your system, in mine,
it has not caused any issue after removing its pinning and updating it (tested then
in VirtualBox and on bare metal in a laptop).
As for software-properties-gtk, maybe did you want to block the Ubuntu Pro packages?
If so, a less invasive approach can be applied: neutralizing the file
/etc/apt/update-notifier/20apt-esm-hook.conf by replacing its content with a
comment is what I have been doing for several years now.
This prevents the recurring Ubuntu Pro registration prompts without blocking
legitimate security updates. And keeping it, with an explicit comment lets the users
be informed.
This is what I wrote in my personal file:
Best regards and thanks for your work.