Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.7.9 2023-11-20T09:04:05Z 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. 2023-05-02T13:16:54Z Julian Andres Klode julian.klode@canonical.com 2023-04-11T14:37:51Z urn:sha1:3625351722e67903dc34993fe318e50863bd2d31 This runs update before opening the cache and sources.list for installing/upgrading. 2022-09-02T21:37:58Z David Kalnischkies david@kalnischkies.de 2022-09-02T09:07:58Z urn:sha1:e1f332324f81b589561a9d9bce8a55d4895f26ec The command line is evaluated in two steps: First all packages given are marked for install and as a second step the resolver is started on all of them in turn to get their dependencies installed. This is done so a user can provide a non-default choice on the command line and have it respected regardless of where on the command line it appears. On the other hand, the order in which dependencies are resolved can matter, so instead of using a "random" order, we now do this in the order given on the command line, so if you e.g. have a meta package pulling in non-default choices and mention it first the choices are respected predictably instead of depending on first appearance of the package name while creating the binary cache. I might have "broken" this more than a decade ago while introducing the reworked command line parsing for Multi-Arch, which also brought in the split into the two steps mentioned above which was the far more impactful 'respect user choice' change. This one should hardly matter in practice, but as the tests show, order can have surprising side effects. 2022-09-02T20:32:59Z David Kalnischkies david@kalnischkies.de 2022-08-31T14:08:54Z urn:sha1:009cf61122b7a0ac22b541035a26e6092c9ac529 Reported-By: gcc Gbp-Dch: Ignore 2022-07-11T14:37:35Z Julian Andres Klode julian.klode@canonical.com 2022-07-08T11:37:41Z urn:sha1:e481022470322b50a3289d2397b42b6eeacfc6e7 Because the auto installer now also marks other binaries in the package for upgrade, we do need to run it or we don't mark those for upgrade. 2021-11-27T10:22:38Z Ville Skyttä ville.skytta@iki.fi 2021-11-03T22:08:07Z urn:sha1:01eed4234440d82fc52c8186cf4268517bcd28bc 2021-11-17T16:21:03Z Julian Andres Klode julian.klode@canonical.com 2021-11-17T16:20:29Z urn:sha1:21cc694f55de7caede8dcef3831236b6ca855cd7 Let's make this one step harder. 2021-07-01T09:34:04Z Julian Andres Klode julian.klode@canonical.com 2021-07-01T09:34:04Z urn:sha1:690f6191a4332123a912c812a19a37cef253e90c We just used the pointer returned which might be nullptr, properly call BuildSourceList() and check the result first. Closes: #990518