apt/test, branch 2.9.2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.22024-04-20T12:15:47Zbuild: test: Silence warnings in GTest code2024-04-20T12:15:47ZJulian Andres Klodejulian.klode@canonical.com2024-04-20T12:09:37Zurn:sha1:4e9a9dbf9bd52d38ab5818f3eb32c8189fd25671
GTest has a lot of broken things with signed vs unsigned,
and double integer promotions, let's silence them.
test: configuration: color: reset _config after tests2024-04-20T12:15:47ZJulian Andres Klodejulian.klode@canonical.com2024-04-20T11:45:55Zurn:sha1:1350ca686ba2557dd8e2c17eab367bfbfe9b389a
This avoids us polluting the configuration for later tests, since
the test order apparently is not deterministic. We probably should
fix some common test case thingy instead.
Add APT::Configuration::color helper to colorize things2024-04-19T14:58:24ZJulian Andres Klodejulian.klode@canonical.com2024-04-19T13:57:23Zurn:sha1:58ee0fabc9028fcdf86faab3bb9c1db2b27e3644Allow no spaces for the last dependency in ParseDepends, too2024-04-17T09:12:58ZDavid Kalnischkiesdavid@kalnischkies.de2024-04-17T08:19:40Zurn:sha1:633f6d67a28b375cf1f225f14d3c926e618d46af
All other entries in a dependency line get substantial leeway about the
amount of spaces surrounding the entry itself and its individual parts,
but the very last entry was required to have a version constraint be
at least 4 chars long (excluding opening bracket and spaces following
it), so if the version is short and a single-char relation used a space
had to make up for it. This is a bit unfair in comparison to the other
entries who do not have such unreasonable demands, so we reduce our
demand to 3 chars or longer, which is satisfied by "=1)".
If it is a good idea to hate spaces that much remains unanswered by this
commit, but in practice most tools (re)writing the files we parse will
include spaces, so its only in files (or on the satisfy command line)
directly edited by users that we can encounter such a situation, which
is a relatively new development given this line came unchanged from
the introduction of this method in 1998.
LP: #2061834
apt: Use unicode install progress bar on UTF-8 locales2024-04-13T21:59:41ZJulian Andres Klodejak@debian.org2024-04-13T21:59:41Zurn:sha1:ac8fe4b030754584cda9cb1707fc3d9f0d792366
This produces a much more appealing progress bar and it can even
show parts of the progress being done.
Only show Recommends/Suggests for new installs, not upgrades2024-04-12T14:01:02ZJulian Andres Klodejulian.klode@canonical.com2024-04-12T13:10:20Zurn:sha1:275ee5afe968e77d8379f0f3b6dc54c6239aa4f6
This makes things more useful in combination with the upgrade
command, but introduces a subtle change seen in the test suite
when you use the install command to upgrade packages.
apt: Introduce the new terse apt output format 3.02024-04-12T13:57:36ZJulian Andres Klodejulian.klode@canonical.com2024-04-11T21:04:43Zurn:sha1:abfae1aec588c1b4ae46f229d8312a3c5e6b8b7a
The key talking points here are:
1. Instead of long sentences, we use short concise messages,
e.g. "The following NEW packages will be installed" becomes
"Installing".
2. Dependencies are only listed once. We removed the
"The following additional packages will be installed" section
in favor of splitting up the "Installing" section into
"Installing" and "Installing dependencies" (like dnf)
3. The order of the output is different:
1. Packages to be installed manually
2. Packages to be installed automatically
4. Weak dependencies of new packages not installed
3. Packages to be upgraded
4. Packages to be downgraded
5. Packages that have been kept back / are on hold
6. Removals
7. Essential removals
i.e. we logically show you the action that is being
done, followed by lists related to the action.
4. As requested by popey, we have colorful UI, with green for
packages being installed and red for packages being removed.
Caveats:
- The list of recommends and suggests has not been updated yet,
it should move to after the packages being installed (as they
are what triggers them)
This also introduces output format versioning, configured by the
APT::Output-Format option. The default value is 0, except for the
apt(8) binary where it is 30 - which enables the new style.
Columnar output for package lists similar to 'ls'2024-04-12T13:56:56ZChristian Blichmannmail@blichmann.eu2022-02-01T19:59:57Zurn:sha1:690993b1b9b4a932ca5bf5374c59e4cf88f18732
This change makes it a bit easier to quickly grasp the changes
about to be performed by apt.
It displays package lists in a columnar format by default,
similar to what `ls` produces for files.
A new long option `--no-list-columns` and an associated
`APT::Get::List-Columns` config setting control the behavior.
Usage example, with 60 column wide terminal:
```
$ sudo apt upgrade |
Reading package lists... Done |
Building dependency tree... Done |
Reading state information... Done |
Calculating upgrade... Done |
The following packages were automatically installed and are |
no longer required: |
libappindicator1 libindicator7 |
libdbusmenu-gtk4 linux-image-5.14.0-4-amd64 |
Use 'sudo apt autoremove' to remove them. |
The following packages have been kept back: |
criu linux-headers-amd64 nvidia-settings |
libxnvctrl0 nvidia-modprobe xwayland |
0 upgraded, 0 newly installed, 0 to remove and 6 not upgrade|
d. |
```
The effect becomes more pronounced with more packages (e.g. when
doing a dist-upgrade).
Revert "Temporarily downgrade key assertions to "soon worthless""2024-04-09T17:59:52ZJulian Andres Klodejulian.klode@canonical.com2024-04-09T17:56:26Zurn:sha1:81c65f7e86b8f16eaaa91d9c205a594b0ebde159
We temporarily downgraded the errors to warnings to give the
launchpad PPAs time to be fixed, but warnings are not safe:
Untrusted keys could be hiding on your system, but just not
used at the moment. Hence revert this so we get the errors we
want.
This reverts commit 66998ed3d299bede651ad40368bdb270f5f5b0f9.
LP: #2060721
Gbp-Dch: full
Ignore umask of leftover diff_Index in failed pdiff test2024-03-30T15:59:57ZDavid Kalnischkiesdavid@kalnischkies.de2024-03-20T12:30:19Zurn:sha1:e62162d010fc7d6374067964ced3ac227b0440b2
We don't store .diff_Index files anymore and so libapt cares even less
about these purposefully leftover files from the testcases than it did
previously. On a successful apt run they would just be deleted, but as
we are testing a failed run they are not touched at all.
Testing the file access bits then means we check with whatever umask
they were created which might very well be different to what apt decides
these files to have if it had touched them, so for this test we just
delete them. For the other case we set it completely wrong just in case,
but they will (hopefully) be non-existent anyhow as tested first.
References: afcdbcf895284efd76903b2b3ba5cc849059ce50