Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.7.14 2024-02-20T12:49:04Z 2024-02-20T12:49:04Z Julian Andres Klode julian.klode@canonical.com 2024-02-20T12:43:08Z urn:sha1:40a75722c43ae24cb9a99d6730a3b25b65819c49 This was automated with sed and git-clang-format, and then I had to fix up the top of policy.cc by hand as git-clang-format accidentally indented it by two spaces. 2024-02-13T14:08:57Z Julian Andres Klode julian.klode@canonical.com 2024-02-13T11:54:07Z urn:sha1:1a0882558da05eaf471c2b4049ae27305e7c70ec This introduces a new line: The following upgrades have been deferred due to phasing This is any kept back package that is also phasing. This may not be 100% accurate as we have kept it back due to other reasons in an install command, for example, but we don't track for which packages we applied phasing in reality. If additional packages are kept back that are not phasing, show a a notice "N: Some packages may have been kept back due to phasing." LP: #1988819 2024-01-19T17:28:31Z David Kalnischkies david@kalnischkies.de 2024-01-19T16:06:04Z urn:sha1:2845127968cda30be8423e1d3a24dae0e797bcc8 It is documented and the code supports it, but the command line parsing actually refuses -a/--host-architecture=arch … probably a sign how much "apt-get source -b" is (not) used in practice. Setting via -o APT::Get::Host-Architecture=arch (which -a is just a shorthand for) works as it did before and can be used if backward compatibility is important. 2024-01-03T16:59:11Z David Kalnischkies david@kalnischkies.de 2024-01-03T16:25:35Z urn:sha1:afcdbcf895284efd76903b2b3ba5cc849059ce50 Nowadays we only download the index file if we have a non-current file on disk which we want to patch. If that is the case, any index file for patches we could have stored is by definition outdated, so storing those files just takes up disk space. At least, that is the case if we have a Release file – if we don't this commit introduces a needless redownload for such repositories but such repositories are an error by default and if they can't be bothered to provide a Release file its very unlikely they actually ship diffs, so adding detection code for this seems pointless at best. 2024-01-03T13:53:09Z David Kalnischkies david@kalnischkies.de 2024-01-03T13:53:09Z urn:sha1:c82f96210eb62c92d31ded7073f4cf5371cc9485 The implementation as-is as various smaller/esoteric bugs and inconsistencies like apt-get not supporting them, the option -s being supported in code but not accepted on the command line, the regex not escaping the dot before the file extension and exposing more implementation details to public headers than we actually need. Also comes with a small test case to ensure it actually works. References: bd7c126e3fb1b94e76e0e632c657cea854586844 2023-12-08T13:14:07Z Julian Andres Klode jak@debian.org 2023-12-08T13:14:07Z urn:sha1:c555d8f1ae31d1f511bf811640423231b75a8e13 Add 'dist-clean' command to remove packages and list files See merge request apt-team/apt!290 2023-11-22T10:05:28Z Gábor Németh homar@riseup.net 2023-03-06T15:19:14Z urn:sha1:bd7c126e3fb1b94e76e0e632c657cea854586844 We assume all files in the 'listsdir' are candidates. Keep only files ending with Release, Release.gpg, and InRelease. Closes: #959093 2023-11-20T09:04:05Z Julian Andres Klode julian.klode@canonical.com 2023-11-20T09:02:21Z urn:sha1:b6f362e8013b03efce54e7381e0e22fac1fa1539 This ensures that things work correctly. LP: #1995790 2023-09-20T07:47:47Z Julian Andres Klode julian.klode@canonical.com 2023-09-20T07:46:51Z urn:sha1:925ada57d999a502dc2342092f32232b803be254 One warning will be issued before the Y/n prompt, the other will be issued at the end after package installs have been attempted or if there were other failures, such that the last line you see is warnings about unmerged-usr I do not anticipate this to be the final version either, but there we go. Closes: #1052058 2023-09-16T10:37:31Z Julian Andres Klode julian.klode@canonical.com 2023-09-16T10:34:48Z urn:sha1:99c888b5eabbb7008bf4451bc62c277f28bb925f As of bookworm, merged-usr is mandatory, and people got caught in the crosshairs of the dpkg fsys-unmessusr debacle and inadvertently reverted back to an unmerged configuration and continue to remain on an unsupported system unknowingly. Help them by erroring out when they are installing packages on /, they are not in a chroot, and a usrmerge package is available.