Backport never pinning and Packages-Require-Authorization
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
These are not driven from a direct user experience, but are related to other developments:
(1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit.
(2) Packages-
[Test case]
Tests are included in autopkgtests and cover the common scenarios
https:/
(1) Add repository with Packages-
(2) Add repository with Packages-
(3) As (2), but a custom pin still applies
https:/
(1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins
(2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins
[Regression potential]
The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing.
CVE References
description: | updated |
description: | updated |
Changed in apt (Ubuntu Trusty): | |
status: | New → In Progress |
Changed in apt (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in apt (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in apt (Ubuntu Cosmic): | |
status: | New → In Progress |
Changed in apt (Ubuntu Disco): | |
status: | New → In Progress |
Is this fixed in Disco yet?