apt/doc, 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:8e60b18f9b583dcd252f962b06905d99043a27d1Add 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.
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:3663365969a496e590bc70f448dbdf0bec52f2a2Release 2.7.92024-01-11T09:06:14ZJulian Andres Klodejulian.klode@canonical.com2024-01-11T09:05:29Zurn:sha1:ed053de346d92c1a4218a7b80a20158f3535fe2aRelease 2.7.82024-01-08T10:46:15ZJulian Andres Klodejulian.klode@canonical.com2024-01-08T10:46:15Zurn:sha1:559ad32ed4d88e3216c3e12197bb54a9364f733fRevert "Merge branch 'distclean-doc-an-test' into 'main'"2024-01-08T09:40:10ZJulian Andres Klodejulian.klode@canonical.com2024-01-08T09:39:46Zurn:sha1:10367ebb0f44cbc61b48fb99e194301c2182fe31
This reverts commit 86e6eace1d50527b5a2396290acd1db819b13e26, reversing
changes made to 6e43eef9ca8250eb561f2c9af2f4890d674f3911.
Test and document 'dist-clean'2023-12-15T11:57:54ZGábor Némethhomar@riseup.net2023-12-15T11:57:54Zurn:sha1:b3a430029360800e1b2cb6dfc385c5182f74fcb8Have Grp.FindPreferredPkg return very foreign pkgs as last resort2023-12-04T23:35:04ZDavid Kalnischkiesdavid@kalnischkies.de2023-12-04T19:49:33Zurn:sha1:0abf584b283e3e0f040b9ec0e7153c6e52291b2a
Usually this method will return the package in the most preferred
architecture (e.g. native) as that is usually what the user talks about
and also information wise for our internal usage the most dense.
Early on in parsing Packages files through it can happen that we
encounter stanzas about packages in architectures we are not even
configured to know about – we have to collect them anyhow as we might be
requested to show info about them or they could be in the status file
and we can't ignore stanzas in the status file… trouble is that this
method used to not return anything if only such an architecture was
present if we later discover other architectures which causes Provides
and Conflicts which are added lazily on discovery of an architecture
to not be added correctly.
The result is like in the testcase that apt could be instructed to
install a package without respecting its negative dependencies, which is
bad even if its discovered by dpkg and refused. It does only happen with
unknown architectures through which mostly happens if you are unlucky
(amd64 users tend to be very lucky as that sorts early) and use
flat-style repositories containing multiple architectures.
Reported-By: Tianyu Chen (billchenchina) on IRC