apt/doc/apt_preferences.5.xml, branch 3.1.11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=3.1.112025-05-19T17:14:52ZRelease 3.1.02025-05-19T17:14:52ZJulian Andres Klodejak@debian.org2025-05-19T17:14:11Zurn:sha1:5bfea97d7b3c6f4fcaa56c24d6f3591b1862b86bapt_preferences(5): Specify the order in which files are parsed2025-05-19T16:05:40ZSimon McVittiesmcv@debian.org2024-12-24T13:53:48Zurn:sha1:49681c12b124e236731524b6fbbab7f91147295b
The order of preference stanzas matters, but this man page did not
previously define whether /etc/apt/preferences was parsed before or
after the fragment files in preferences.d. Giving a concrete example
also provides a hint that numeric prefixes are a useful way to force a
particular sort order, and clarifies that the presence or absence of
the .pref extension is less important than lexicographic order.
Signed-off-by: Simon McVittie <smcv@debian.org>
Release 2.9.92024-10-17T07:42:00ZJulian Andres Klodejulian.klode@canonical.com2024-10-17T07:41:51Zurn:sha1:fcccd7fb5ed74ae00c9d675667017d9c84838f69Implement 'Pin: source-version <foo>'2024-08-22T14:11:38ZJulian Andres Klodejulian.klode@canonical.com2024-08-22T14:10:58Zurn:sha1:67070389f3752f6f23d1fb0c06bd963464aa8bca
As wondered about by Paride some minutes ago.
Release 2.3.142022-01-06T19:58:15ZJulian Andres Klodejak@debian.org2022-01-06T19:58:15Zurn:sha1:b89ab5f07e979902da17f23db56cd42ca068ae21doc/apt_preferences.5.xml: document Package field syntax2022-01-05T13:17:57ZJohannes Schauer Marin Rodriguesjosch@mister-muffin.de2022-01-03T10:53:40Zurn:sha1:8d15f117b87a3907e31d3c7e380b67fd85c013dfRelease 2.1.172021-01-11T11:11:10ZJulian Andres Klodejulian.klode@canonical.com2021-01-11T11:11:10Zurn:sha1:e9d659be2ac4772a19c10b6cea91687fe084876eFixup manual page docbook syntax2021-01-08T21:17:12ZJulian Andres Klodejulian.klode@canonical.com2021-01-08T21:13:15Zurn:sha1:580880b051492fb1e47bcb4eaaacec3a2807d140
No idea why we don't have manual page syntax check (what prepare-release
post-build does) in CI. Should fix that eventually.
Gbp-Dch: ignore
Add support for Phased-Update-Percentage2021-01-08T13:48:47ZJulian Andres Klodejulian.klode@canonical.com2020-08-10T18:16:11Zurn:sha1:c5bc86d45e003905ef411146e66b414d26fb1ff8
This adds support for Phased-Update-Percentage by pinning
upgrades that are not to be installed down to 1.
The output of policy has been changed to add the level of
phasing, and documentation has been improved to document
how phased updates work.
The patch detects if it is running in a chroot, and if so, always
includes phased updates, restoring classic apt behavior to avoid
behavioral changes on buildd chroots.
Various options are added to control this all:
* APT::Get::{Always,Never}-Include-Phased-Updates and their legacy
update-manager equivalents to always or never include phased updates
* APT::Machine-ID can be set to a UUID string to have all machines in a
fleet phase the same
* Dir::Etc::Machine-ID is weird in that it's default is sort of like
../machine-id, but not really, as ../machine-id would look up
$PWD/../machine-id and not relative to Dir::Etc; but it allows you to
override the path to machine-id (as opposed to the value)
* Dir::Bin::ischroot is the path to the ischroot(1) binary which is used
to detect whether we are running in a chroot.
Release 1.9.112020-02-26T20:31:05ZJulian Andres Klodejulian.klode@canonical.com2020-02-26T20:30:15Zurn:sha1:de9762d5443b8a957fae781bbdc4a740cc6c4e6f