apt/apt-pkg/edsp.cc, branch 2.9.34Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.342025-03-20T09:26:51Zedsp: Dump minimized Dir::Log::Solver logs2025-03-20T09:26:51ZJulian Andres Klodejulian.klode@canonical.com2025-03-13T14:55:50Zurn:sha1:8ed6bea2083e055b50dfbd8bebf1355cce502f3fedsp: Add functionality to only write relevant packages2025-03-20T09:26:51ZJulian Andres Klodejulian.klode@canonical.com2025-03-13T14:15:58Zurn:sha1:11917fa559c6c9bc5b0993b435f295de06bd161c
Add a variant of WriteLimitedScenario that does not take a pkgset,
but creates one on the fly based on the transitive closure of installed
packages, to be installed packages, and their dependencies and provides.
This includes more packages than strictly necessary, i.e. we do not
really need to include foo just because a package we want to install
Conflicts with it, but oh well, this is easy to read.
Trying to extend the filtering is hard as the dependencies being written
are also filtered...
edsp: Set Forbid-New-Install/Forbid-Remove: no if other is set2025-03-10T21:33:05ZJulian Andres Klodejulian.klode@canonical.com2025-03-10T17:37:55Zurn:sha1:1fc8e9eee4d6a81f907b399034f6f82da2e98140
The upgrade code may also set Upgrade: yes, and this sets both to
yes, so `apt upgrade` dumps behave like `apt-get upgrade` ones,
which of course is not intentional.
moo
edsp: Write 'Size' to the EDSP files2025-03-03T10:21:55ZJulian Andres Klodejulian.klode@canonical.com2025-03-03T10:20:52Zurn:sha1:45b04762e1990a761a7c308f9e73a286a92f908a
This allows solvers to optimize by download size; and gives us
a better means of interpreting "downloadable" debs (they must have
a size > 0 after all).
edsp: Use buffered writes for EDSP dumps2025-02-17T15:23:05ZJulian Andres Klodejulian.klode@canonical.com2025-02-17T15:23:05Zurn:sha1:591f178bce5713571d1874b863e9291a795cf5da
This makes the dump almost instant rather than take forever.
solver3: Pass EDSP flags directly rather than via config2025-02-14T18:08:45ZJulian Andres Klodejulian.klode@canonical.com2025-02-11T21:03:03Zurn:sha1:3ae41a76c19e5ad05600188de43b46c3e2800676
This was a rather silly way to communicate state, and it was
in the wrong place. Notably also, multiple calls to the solver
had the options sticky, that is, if you run upgrade and then
it calls ResolveByKeep(), for example.
solver3: Defer 3.0 'deep' autoremoval to 3.1, fix autoremove2025-02-14T18:08:45ZJulian Andres Klodejulian.klode@canonical.com2025-02-11T11:11:20Zurn:sha1:4c48b5618ba15d4e33625cec81843891910e81a2
Restore the depcache's MarkRequired logic for 3.0 solver; and
change the MarkInstall() call to pass a more correct value for
FromUser, to not override an existing automatic status.
Add pkgCache::{Priority,DepType}_NoL10n to avoid duplication2025-01-05T22:16:08ZDavid Kalnischkiesdavid@kalnischkies.de2024-12-26T20:43:34Zurn:sha1:6828ae2c2f9268c8187f0fa91b3c464ed84a8476
We don't have many places, but lets reduce the amount of duplicating
these short strings, so that we may find all the places we have to
change if that ever happens.
apt-pkg/edsp.cc: APT::StringView -> std::string_view2024-11-12T19:23:28Zнабnabijaczleweli@nabijaczleweli.xyz2024-11-12T16:59:21Zurn:sha1:e0c969324c4c1196b5ec31f925c602ffcbe5080cedsp: solver3: Show some progress2024-05-24T10:48:09ZJulian Andres Klodejulian.klode@canonical.com2024-05-19T17:32:05Zurn:sha1:4fc6affafafda1aee4cee86294ce7a2b799e2799
Ignore the Solving dependencies... line in the testing framework
for compatibility with the existing test cases.