On Wed, Dec 15, 2021 at 2:36 PM Jay Vosburgh <jay.vosburgh@canonical.com> wrote:
> >It's not necessary to remove the unattended-upgrades package in order to
> >achieve this. unattended-upgrades is configurable, and it's sufficient to
> >set 'APT::Periodic::Unattended-Upgrade "0";' in
> >/etc/apt/apt.conf.d/20auto-upgrades (or, in a separate file that sorts
> >lexically after, if that works better for the user's configuration
> >management system) to disable unattended-upgrades at runtime.
> >
> >Therefore I do not think we should relax the dependency for this use case.
>
> It is a change in the expectations and established practice for
> enterprise deployments who manage their own upgrades (i.e., currently
> they can simply remove unattended-upgrades and require no further action
> ever).
>
> Is there a benefit to having u-u dependent on the server-minimal
> metapackage?
>
> Is there a risk that package upgrades to u-u could reenable it?
>
Our Enterprise users with larger deployments may not want to risk having the
package installed, since a package upgrade might overwrite the configuration
file or accidentally trigger the apt-daily-upgrade.timer, which could lead to
unplanned upgrades and service restarts taking place.
I fear that we will just end up with users making master images that just
purge unattended-upgrades, and it will take ubuntu-server-minimal with it,
causing issues down the line if they ever decide to do a in-place release
upgrade.
There is also a distinct lack of consistency as well.
For example, on Jammy Desktop:
$ sudo apt remove unattended-upgrades
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
unattended-upgrades
0 upgraded, 0 newly installed, 1 to remove and 18 not upgraded.
After this operation, 446 kB disk space will be freed.
On Jammy Cloud Images:
$ sudo apt remove unattended-upgrades
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
unattended-upgrades
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 446 kB disk space will be freed.
On Jammy LXD Container Images:
sudo apt remove unattended-upgrades
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
unattended-upgrades
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 446 kB disk space will be freed.
But on Jammy Server, we have ubuntu-server-minimal installed, and thus:
$ sudo apt remove unattended-upgrades
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
ubuntu-server-minimal unattended-upgrades
0 upgraded, 0 newly installed, 2 to remove and 4 not upgraded.
After this operation, 500 kB disk space will be freed.
Why is Jammy Server semantically different from Cloud images or
Container images?
We should absolutely include unattended-upgrades by default in all
installations,
but we should do so via a Recommends instead of Depends relationship on Ubuntu
Server.
Please reconsider your view for the server-minimal metapackage.
Thanks,
Matthew
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
