params: debian default: re-add main origin
In #193, buster was renamed to bullseye, which caused a regression for buster: the main "Debian" origin would now be removed. This commit restores that origin for the default Debian case.
Merge pull request #201 from kenyon/restore-main-origin
params: debian default: re-add main origin
Validate origins and remove legacy origins
To ensure people don't trip over old configs, let's validate that the given origins comply with the current format. Straight-up removed legacy origins as, after checking, none of the Debian-based distributions (and thus their derivates) we support still require legacy-style origin definition. This is a breaking change.
* Leftover legacy formats in tests removed. * A typo in the ESM repositories fixed. * Use correct test specs.
Merge pull request #204 from b1-systems/fix/ubuntu-legacy
Replace legacy Allowed-Origins with Origins-Pattern on all distros
Merge pull request #205 from voxpupuli/readme-remove-legacy_origin
README: remove legacy_origin
Merge pull request #206 from Hufschmidt/pr/always
Add missing 'always' value support to periodic parameters (every n-days)
Merge pull request #208 from jps-help/master
Add only_on_ac_power option to unattended-upgrades.erb
Merge pull request #207 from voxpupuli/modulesync
modulesync 5.3.0
Merge pull request #210 from bastelfreak/lsbfuckup
Cleanup legacy fact usage
unattended-upgrades does *not* need special configuration to `dpkg` for proper operation. It handles those itself. All this does is changes the `dpkg` configuration for *other* `dpkg` runs. This will, for example, affect major upgrades, typically done by hand, and not unattended-upgrades, which was *not* designed for that purpose. In those cases, unsuspecting users will see their old configuration file versions silently kept in place, which most definitely *will* break things on upgrade, rather noisily in the end. People unfamiliar with this mechanism will have a hard time figuring out what has happened, and while recovery is possible, it is tricky without special tooling. I wrote such a tool here: https://gitlab.com/anarcat/koumbit-scripts/-/blob/master/vps/clean_conflicts ... but it not well known and definitely not shipped with Debian by default. While it is nice that the unattended-upgrades module allows users to change dpkg options, this can be more easily (and directly) done with the `apt::conf` parameter in the first place. This reverts commit 3a4abe4 and possibly later ones when the options type was introduced.
Merge pull request #190 from anarcat/no-options
retire options support