apt/doc/apt_preferences.5.xml, branch 2.7.12Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.7.122022-01-06T19:58:15ZRelease 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:de9762d5443b8a957fae781bbdc4a740cc6c4e6fpolicy: Implement pinning by source package2020-01-17T12:24:39ZJulian Andres Klodejulian.klode@canonical.com2020-01-17T12:18:03Zurn:sha1:450af26202424bef33e0c58f3f99dfd0c21e7297
This implements the src: syntax inside policy, allowing you to
pin by source package. This by default only pins the native
architecuture, use src:pkg:any to pin for all architectures
in your cache.
Closes: #166032
change debian related entities to a more explicit name2016-01-14T16:33:58ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-14T15:11:28Zurn:sha1:9feb98eb0aeed775f78cb4afbf6bc0e3a90e9fed
Git-Dch: Ignore
update manpage last-modified from git via pre-export hook2015-11-25T14:20:10ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-22T18:02:13Zurn:sha1:ab5b1d0d31b2fbdc4896f8a107611ff056d6a668
Never updating this information is wrong, updating it automatically
isn't super correct either, but it seems conventional to have it and
updating it more often than needed seems better than updating it never.
Git-Dch: Ignore
Document the general effect of the comma operator2015-08-15T13:33:40ZJulian Andres Klodejak@debian.org2015-08-15T13:33:40Zurn:sha1:35ea8b154b105727cf0a0f0238d51b82a0d7c045
Closes: #574939