Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=3.1.16 2026-02-17T10:38:48Z 2026-02-17T10:38:48Z Julian Andres Klode jak@debian.org 2026-02-17T10:38:32Z urn:sha1:02f2b0abd713d3e475f0d91e9eb0199df4b8de13 2026-02-17T10:35:26Z Julian Andres Klode jak@debian.org 2026-02-17T10:35:26Z urn:sha1:3016ed130c0160b37ec9194288fa10ddaf06831f bash-complete search patterns for more commands See merge request apt-team/apt!543 2026-02-17T10:35:22Z Ville Skyttä ville.skytta@iki.fi 2026-01-06T11:32:07Z urn:sha1:7b2673ace64d70a056041c487480d087f19030a8 2026-02-17T10:34:54Z Julian Andres Klode jak@debian.org 2026-02-17T10:34:54Z urn:sha1:bed35523705eb21a6a2e5bfa45dcabd91d50ef21 Prevent sleep while running dpkg. See merge request apt-team/apt!554 2026-02-17T10:34:47Z Nathan Pratta Teodosio nathan.teodosio@canonical.com 2026-02-17T09:42:13Z urn:sha1:c1607f538559a0b7a1d3f9dc01e88190e543053d As long as we are running dpkg, keep an inhibitor that blocks us from sleeping. 2026-02-17T10:32:20Z Julian Andres Klode jak@debian.org 2026-02-17T10:32:20Z urn:sha1:a33e3e3db6adcc7f324081afbb7e2510aec2002c debian: Trigger apt-daily on AC plug event See merge request apt-team/apt!547 2026-02-17T10:32:07Z Alessandro Astone alessandro.astone@canonical.com 2026-01-23T13:29:57Z urn:sha1:31cbb48a36060e59e5e05a718553334c74e20286 Because the service has ConditionACPower=true, it would be nice to try and start it when plugging-in the AC power in case that an earlier timer trigger was missed due to not being plugged-in. It is not a problem that we may be invoking the service multiple times a day, because it keeps track of its own timestamp file to run up to once every "APT::Periodic::Update-Package-Lists" days Related: https://launchpad.net/bugs/2089151 2026-02-17T09:58:46Z Julian Andres Klode jak@debian.org 2026-02-17T09:58:46Z urn:sha1:f6adace8d302fb72ab92646cbd49f9560fa1ad6a solver3: Upgrade by source package See merge request apt-team/apt!553 2026-02-17T09:28:17Z Julian Andres Klode jak@debian.org 2026-02-17T09:28:17Z urn:sha1:9f3ecca2b32e4fe56a05811392e01416092f85fa Implement the "APT::Get::Upgrade-By-Source-Package" option as the classic solver does. Here this is equally straight forward now: We enqueue optional, but eager, clauses of the form foo=2 -> foo-data=2 for each sibling in the source version, assuming they are currently installed, and the selection is not the current version. This softly enforces upgrades of already installed siblings, but in non-strict-pinning mode it will not affect the selection of new packages to be installed. A more complete solution to version selection by source package also seems feasible, where we change the "priority" of versions in the solver dynamically - currently they are statically evaluated. Such that, when you select foo=2, and something installs foo-data, foo-data would be installed in version 2 even if version 3 were its candidate. 2026-02-10T19:59:11Z Julian Andres Klode jak@debian.org 2026-02-10T19:59:11Z urn:sha1:1275e2e0ec45e9cdbfeedfa2c069274d80499fa8 Introduce JSONL performance counter logging and constexpr-ify the solver and cache See merge request apt-team/apt!551