apt, branch 2.7.11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.7.112024-02-13T15:31:44ZRelease 2.7.112024-02-13T15:31:44ZJulian Andres Klodejulian.klode@canonical.com2024-02-13T15:31:44Zurn:sha1:8e60b18f9b583dcd252f962b06905d99043a27d1Merge branch 'phasing-api' into 'main'2024-02-13T15:30:21ZJulian Andres Klodejak@debian.org2024-02-13T15:30:21Zurn:sha1:3749cda6af91e495650018bae39185c2589c9bd7
Add public phased update API and separate message list
See merge request apt-team/apt!327Show a separate list of upgrades deferred due to phasing2024-02-13T14:08:57ZJulian Andres Klodejulian.klode@canonical.com2024-02-13T11:54:07Zurn:sha1:1a0882558da05eaf471c2b4049ae27305e7c70ec
This introduces a new line:
The following upgrades have been deferred due to phasing
This is any kept back package that is also phasing. This may
not be 100% accurate as we have kept it back due to other reasons
in an install command, for example, but we don't track for which
packages we applied phasing in reality.
If additional packages are kept back that are not phasing, show
a a notice
"N: Some packages may have been kept back due to phasing."
LP: #1988819
Add the ?security pattern2024-02-13T13:28:06ZJulian Andres Klodejulian.klode@canonical.com2024-02-13T11:33:51Zurn:sha1:82f4cfc971ef6a2e56b34227d9e0b1a594dc2265Add a new ?phasing pattern2024-02-13T13:28:06ZJulian Andres Klodejulian.klode@canonical.com2024-02-13T11:29:28Zurn:sha1:422e68f569f374f697b84332f7e68c6fe5f7389f
This selects all packages that are being kept back due to phasing
on your system.
Add public phased update API2024-02-13T13:27:27ZJulian Andres Klodejulian.klode@canonical.com2024-02-12T13:48:48Zurn:sha1:a8352c2859a6f84b36fa5cd0af89231cb656b1ce
This moves the functions of the PhasedUpgrader class into
various other classes so they can be publicly exposed.
This introduces three new functions:
pkgDepCache::PhasingApplied() tells you whether phasing should
be applied to the package.
pkgProblemResolver::KeepPhasedUpdates() keeps back updates that
have phasing applied.
pkgCache::VerIterator::IsSecurityUpdate() determines whether this
version contains security fixes.
For phasing, check if current version is a security update, not just previous ones2024-02-13T13:13:56ZJulian Andres Klodejulian.klode@canonical.com2024-02-13T12:58:40Zurn:sha1:26e0e9b76fb06afe5250eeb8e5b3d069d4793432
We only considered an update a security update if a previous update
is a security update but not the update in question itself.
LP: #2051181
Support -a for setting host architecture in apt-get source -b2024-01-19T17:28:31ZDavid Kalnischkiesdavid@kalnischkies.de2024-01-19T16:06:04Zurn:sha1:2845127968cda30be8423e1d3a24dae0e797bcc8
It is documented and the code supports it, but the command line parsing
actually refuses -a/--host-architecture=arch … probably a sign how much
"apt-get source -b" is (not) used in practice.
Setting via -o APT::Get::Host-Architecture=arch (which -a is just a
shorthand for) works as it did before and can be used if backward
compatibility is important.
Remove erroneous -a flag from apt-get synopsis in manpage2024-01-19T17:27:52ZDavid Kalnischkiesdavid@kalnischkies.de2024-01-19T15:47:49Zurn:sha1:87ce5f60e70c32dcefc46692212c7405d79703c3
The -a flag exists for apt-cache (--all-versions) and -a=arch is
actually an (also documented) option to set host architecture – as the
apt-get manpage documents further below setting a host arch makes sense
only for those commands that actually need one set like source and
build-dep, so other commands keep refusing the option as unsupported as
they should be.
So this commit does indeed just remove a single character from
documentation with no other practical effect.
See: #1061148
Release 2.7.102024-01-19T08:33:31ZJulian Andres Klodejulian.klode@canonical.com2024-01-19T08:31:50Zurn:sha1:3663365969a496e590bc70f448dbdf0bec52f2a2