apt, branch 2.1.12Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.1.122020-11-23T16:53:10ZRelease 2.1.122020-11-23T16:53:10ZJulian Andres Klodejak@debian.org2020-11-23T16:53:10Zurn:sha1:1077af2e635df738f351d5ea3515804a4de367eaDo not immediately configure m-a: same packages in lockstep2020-11-06T09:51:06ZJulian Andres Klodejulian.klode@canonical.com2020-10-08T09:50:19Zurn:sha1:2b13473a9b9947f55a0871d146e4fee456b0af60
In LP#835625, it was reported that apt did not unpack multi-arch
packages in the correct order, and dpkg did not like that. The fix
also made apt configure packages together, which is not strictly
necessary.
This turned out to cause issues now, because of dependencies on
libc6:i386 that caused immediate configuration of that to not
work.
Work around the issue by not configuring multi-arch: same packages
in lockstep if they have the immediate flag set. This will be the
pseudo-essential set, and given how essential works, we mostly need
the native arch to work correctly anyway.
LP: #1871268
Regression-Of: 30426f4822516bdd26528aa2e6d8d69c1291c8d3
Refresh lintian-overrides of apt and libapt-pkg-doc2020-11-05T08:40:50ZDavid Kalnischkiesdavid@kalnischkies.de2020-11-05T01:26:45Zurn:sha1:645ad0c97334265bbfef82a4bdfdc8337cdd0630Update libapt-pkg6.0 symbols file2020-11-05T08:40:50ZDavid Kalnischkiesdavid@kalnischkies.de2020-11-05T00:22:22Zurn:sha1:1761dfa9f87eb4a4444d80cbb5a25c7a07f0bb64
That mostly means deleting symbols which went private or have
disappeared and were previously compiler artefacts.
Remove ancient versions support from apts postinst2020-11-05T08:40:50ZDavid Kalnischkiesdavid@kalnischkies.de2020-11-04T23:37:22Zurn:sha1:938889b20268ec92be1bff67750f7adf03f52c1b
The versions "needing" these fixes are at least five years old, so in an
effort to save massive amounts of runtime and disk space (on aggregate at
least) we can drop these lines.
Reported-By: lintian maintainer-script-supports-ancient-package-version
Install translated apt-patterns(7) man pages2020-11-05T08:40:50ZDavid Kalnischkiesdavid@kalnischkies.de2020-11-04T23:24:05Zurn:sha1:02b904e7e8aba6adf2e872306a0a2f7793b6670e
Reported-By: dh_missing
Rename CMake find_package helpers to avoid developer warnings2020-11-05T08:40:50ZDavid Kalnischkiesdavid@kalnischkies.de2020-11-04T23:14:32Zurn:sha1:287912d6fc7ab0ab0b5f69a4a5260b5bf53121ba
| CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message):
| The package name passed to `find_package_handle_standard_args` (Berkeley)
| does not match the name of the calling package (BerkeleyDB). This can lead
| to problems in calling code that expects `find_package` result variables
| (e.g., `_FOUND`) to follow a certain pattern.
| Call Stack (most recent call first):
| CMake/FindBerkeleyDB.cmake:57 (find_package_handle_standard_args)
| CMakeLists.txt:83 (find_package)
| This warning is for project developers. Use -Wno-dev to suppress it.
And indeed, we checked for BERKLEY_DB_FOUND which was not defined so our
HAVE_BDB was not set – just that it is never used, so it wasn't noticed.
Portuguese manpages translation update2020-11-04T15:05:28ZAmérico Monteiroa_monteiro@gmx.com2020-11-04T14:49:58Zurn:sha1:e748e07aaab817b3ada3a1b01bf80dbe52852952
Closes: #968414
Remove expired domain that became nsfw from debian/changelog2020-10-30T20:15:21ZJulian Andres Klodejulian.klode@canonical.com2020-10-30T20:15:21Zurn:sha1:304bfc20644f06d675de276f1e9783459647803a
mirror.fail points to porn now apparently.
Cc: stable
pkgnames: Do not exclude virtual packages with --all-names2020-10-26T13:39:44ZJulian Andres Klodejulian.klode@canonical.com2020-10-26T13:39:44Zurn:sha1:681f74a8bd5beaad5b821a5c4eb3c0bc1c471669
We accidentally excluded virtual packages by excluding every
group that had a package, but where the package had no versions.
Rewrite the code so the lookup consistently uses VersionList()
instead of FirstVersion and FindPkg("any") - those are all the
same, and this is easier to read.