Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.9.1 2024-04-13T21:59:41Z 2024-04-13T21:59:41Z Julian Andres Klode jak@debian.org 2024-04-13T21:59:41Z urn:sha1:ac8fe4b030754584cda9cb1707fc3d9f0d792366 This produces a much more appealing progress bar and it can even show parts of the progress being done. 2024-04-12T14:01:02Z Julian Andres Klode julian.klode@canonical.com 2024-04-12T13:10:20Z urn: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. 2024-04-12T13:57:36Z Julian Andres Klode julian.klode@canonical.com 2024-04-11T21:04:43Z urn: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. 2024-04-12T13:56:56Z Christian Blichmann mail@blichmann.eu 2022-02-01T19:59:57Z urn: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). 2024-04-09T17:59:52Z Julian Andres Klode julian.klode@canonical.com 2024-04-09T17:56:26Z urn: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 2024-03-30T15:59:57Z David Kalnischkies david@kalnischkies.de 2024-03-20T12:30:19Z urn: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 2024-03-30T15:59:57Z David Kalnischkies david@kalnischkies.de 2024-03-20T11:47:40Z urn:sha1:0185347265671d0101b0e9c03fcc4e638d660705 We remove the working directory from the found file names as these paths could contain a lot of funny characters confusing the for loop like spaces… we just readd it later in the actual calls to be safe. 2024-02-28T17:22:01Z Julian Andres Klode julian.klode@canonical.com 2024-02-28T16:04:05Z urn:sha1:66998ed3d299bede651ad40368bdb270f5f5b0f9 This will only issue warnings instead of errors while we continue cleaning up our repositories. 2024-02-28T17:22:01Z Julian Andres Klode julian.klode@canonical.com 2024-02-28T15:52:33Z urn:sha1:8a14c18c5b487139948dcb22abd37bffdd9cf5f4 This allows us to render public key algorithms as weak as well. 2024-02-28T17:22:01Z Julian Andres Klode julian.klode@canonical.com 2024-02-28T14:14:43Z urn:sha1:50e3fee26ae843a812b1c9ec8531946931773fd3 The assertion can be overriden using apt::key::assert-pubkey-algo, the default is the most opinionated one. This will inform the user during apt-cdrom add as we do not pass --quiet to user, so adjust test case. Add a simple test case for it to test-method-gpgv. LP: #2055193