Confirmed that in bionic it offers this Origins-Pattern in the
"Configuring unattended-upgrades" debconf question:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
That should be Ubuntu, or ${distro_id} perhaps. That being said, it
doesn't seem to be used in the end, because my 50unattended-upgrades
file has no mention of Debian and uses ${distro_id} everywhere.
--
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/1577215
Title:
Origin pattern is unexpected on dpkg-reconfigure
Status in unattended-upgrades package in Ubuntu:
Confirmed
Bug description:
In testing out the new unattended-upgrades behaviour I was asked an
unexpected question about the "unattended-upgrades Origin-Pattern".
This is not a great experience, it doesn't match anything other than
internal code patterns.
For example, the default offered does NOT look like a sensible Ubuntu
default for Ubuntu users:
"origin=Debian,codename=${distro_codename},label=Debian-
Security";___
Is that correct, or a mistake?
What I would expect is simply this:
Install security updates (Y/N)
Install performance and reliability updates (Y/N)
Install updates from unofficial archives (Y/N)
The latter would map to all PPAs etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1577215/+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
