Not sure I can close the bug. Nevertheless it's confusing to have this configuration in two places. Maybe deserves a review.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1849298 Title: unattended-upgrade is checking o=UbuntuESM,a=eoan-security when disabled in config Status in unattended-upgrades package in Ubuntu: New Bug description: My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this: Unattended-Upgrade::Allowed-Origins { "${distro_id}:${distro_codename}"; "${distro_id}:${distro_codename}-security"; // Extended Security Maintenance; doesn't necessarily exist for // every release and this system may not have it installed, but if // available, the policy for updates is such that unattended-upgrades // should also install from here by default. // "${distro_id}ESM:${distro_codename}"; // "${distro_id}ESM:${distro_codename}-security"; "${distro_id}:${distro_codename}-updates"; "${distro_id}:${distro_codename}-proposed"; "${distro_id}:${distro_codename}-backports"; }; Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is allowed for updates despite not being enabled in config: 2019-10-22 08:10:46,075 INFO Initial blacklist : 2019-10-22 08:10:46,077 INFO Initial whitelist: 2019-10-22 08:10:46,077 INFO Starting unattended upgrades script 2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan, o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed, o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1849298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
