apt/debian/NEWS, branch 2.1.20Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.1.202021-01-08T21:18:01ZRelease 2.1.16 - "Happy build-essential freeeze" release2021-01-08T21:18:01ZJulian Andres Klodejulian.klode@canonical.com2021-01-08T20:58:58Zurn:sha1:3f9e5bedf1c9b15db8960d2daa32f703c3cc2346Add 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.
Automatically remove unused kernels on dist-upgrade2021-01-04T09:54:42ZJulian Andres Klodejulian.klode@canonical.com2020-12-17T14:19:53Zurn:sha1:944baec85a7496c1595242a31f6b1b37530451a5
Kernels clutter /boot and /boot is small size, so we need to take
extra care to remove kernels when possible.
Release 1.9.112020-02-26T20:31:05ZJulian Andres Klodejulian.klode@canonical.com2020-02-26T20:30:15Zurn:sha1:de9762d5443b8a957fae781bbdc4a740cc6c4e6fapt(8): Wait for frontend and cache lock2020-02-26T19:36:52ZJulian Andres Klodejulian.klode@canonical.com2020-02-26T19:31:03Zurn:sha1:93e1565796b61eb44bec39f50e09a34cbe090178
This is a rework of !6 with additional stuff for the frontend
lock, so we can lock the frontend lock and then keep looping
over dpkg lock.
Release 1.9.62020-01-15T22:08:38ZJulian Andres Klodejulian.klode@canonical.com2020-01-15T22:07:22Zurn:sha1:799508a65e2df5f4af267f3597ba1117bb3c3eebapt(8): Disable regular expressions and fnmatch2020-01-15T21:19:17ZJulian Andres Klodejulian.klode@canonical.com2020-01-15T21:01:54Zurn:sha1:21cb4a9e513ccb6f376fbcaf67957c4851cbbe32
This is the first step. Next step will be to add warnings to
apt-get and then remove support there as well.
Release 1.9.52019-12-02T17:18:57ZJulian Andres Klodejulian.klode@canonical.com2019-12-02T17:18:57Zurn:sha1:5a98b531f7afcd34367b46ac9e0c7bfe151d6999netrc: Restrict auth.conf entries to https by default2019-12-02T13:27:38ZJulian Andres Klodejulian.klode@canonical.com2019-12-02T10:46:49Zurn:sha1:93f33052de84e9aeaf19c92291d043dad2665bbd
This avoids downgrade attacks where an attacker could inject
Location: http://private.example/
and then (having access to raw data to private.example, for example,
by opening a port there, or sniffing network traffic) read the credentials
for the private repository.
Closes: #945911
Flip /: in documented default value of DPkg::Path2019-04-05T15:52:09ZAlwin Henselerreallynoshame@gmail.com2019-04-05T14:42:54Zurn:sha1:4c27ca80e2de06ab0fd058349f9813b60824cf04
The value as shown in the NEWS file (not in the code) has a typo in
which just a "/" and ":" are swapped.
Closes: #917986