apt, branch 2.7.7

Release 2.7.7

2023-11-22T15:46:03Z

Fix the test suite by adding new "m" flags to debug output

2023-11-22T15:33:45Z

In "Restore ?garbage by calling MarkAndSweep before parsing" I made install code run MarkAndSweep before parsing arguments such that the "?garbage" pattern works correctly. This caused test suite breakage because packages now ended up with marked flags in the debug output. Hence add "m" to the output we assert where necessary. In a nicer world we might want to just do MarkAndSweep if we actually have a ?garbage pattern to evaluate but that is a bit unpredictable in terms of performance expectations and because a "read-only" construct modifies the depcache, so let's go with the more expected option for now Regression-of: b6f362e8013b03efce54e7381e0e22fac1fa1539

Merge branch 'fix-time-unit-comment' into 'main'

2023-11-20T09:10:54Z

Fix incorrect time unit comment for PulseInterval See merge request apt-team/apt!304

Merge branch 'Peutch-guest-main-patch-29453' into 'main'

2023-11-20T09:09:36Z

Update fr.po (add a missing dot) See merge request apt-team/apt!306

Restore ?garbage by calling MarkAndSweep before parsing

2023-11-20T09:04:05Z

This ensures that things work correctly. LP: #1995790

Use different variable name in GTest source path detection

2023-11-18T13:40:40Z

We used GTEST_ROOT, which becomes an issue with 3.27 as that variable would influence find_package behaviour by providing PREFIXES – introduced with potentially mixed-cased name in 3.12. CMake Warning (dev) at test/libapt/CMakeLists.txt:8 (find_package): Policy CMP0144 is not set: find_package uses upper-case _ROOT variables. Run "cmake --help-policy CMP0144" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMake variable GTEST_ROOT is set to: /usr/src/googletest/googletest For compatibility, find_package is ignoring the variable, but code in a .cmake module might still use it. As using this new feature isn't what we wanted at all, we just use a different variable name to avoid the warning and potential future problems if we would keep using this name.

Raise cmake_minimum_required to 3.13 to avoid warnings

2023-11-18T13:10:05Z

CMake Deprecation Warning at CMakeLists.txt:6 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. Picking 3.13 here is a semi-random choice to avoid raising the requirement too much needlessly while also hopefully avoiding needing to raise it soon again based on the referenced mail. While we are at it, lets also fix the other spewed warning: CMake Warning (dev) at CMakeLists.txt:5 (project): cmake_minimum_required() should be called prior to this top-level project() call. Please see the cmake-commands(7) manual for usage documentation of both commands. References: https://lists.debian.org/msgid-search/20230617162957.6pklb6632zf4nijc@mail.gaussglocke.de

Dutch program translation update

2023-11-18T12:35:13Z

Closes: #1055178

Bump Priority to required to match Debian archive

2023-11-15T12:39:40Z

This unbreaks mmdebstrap scenarios if you mirror Debian or use a distro where apt did not get overridden to required. Reported-By: josch on IRC, following discovery by helmut Gbp-Dch: full

s/AlreadDownloaded/AlreadyDownloaded/ in doc/progress-reporting.md

2023-10-11T13:41:17Z

Thanks: jwilk for suggestion