apt/cmdline, branch 3.1.13

solver3: Extract DependencySolver

2026-01-05T21:20:24Z

Extract almost all dependency logic into a subclass

solver3: Refactor to use a namespace

2026-01-05T21:20:24Z

This removes the need for the forward references, thus fixing part of the libc++ issues pointed out in [merge-511]. [merge-511] https://salsa.debian.org/apt-team/apt/-/merge_requests/511/diffs

fix compiling with musl

2025-10-06T15:27:14Z

In case apt is compiled against musl-libc, then compilation fails with the following error: cmdline/apt-internal-solver.cc:122:20: error: 'basename' was not declared in this scope; did you mean 'rename'? | 122 | if (strcmp(basename(argv[0]), "solver3") == 0) | | ^~~~~~~~ | | rename To fix it, include libgen header where musl can find this function also. Once this is fixed, compilation fails once again with musl-libc, because the basename function takes *char argument instead of const *char: this is because the musl implementation cuts off the trailing slashes of the path, in case the argument is a folder path. To account for this, instead of passing argv[0] directly, create a non-const string copy of it, and pass that to base. Signed-off-by: Gyorgy Sarvari

Add history undo, redo, and rollback features

2025-10-02T10:49:58Z

History Command and Parsing

2025-09-26T16:18:42Z

Introduce apt why, apt why-not

2025-05-19T15:20:09Z

These are implemented somewhat differently from aptitudes why and why-not commands: They produce the actual solver trace for why a particular decision has been taken. For the why-not case, we need to explicitly discover our specified package, as if nothing else depends on it in our graph, it would otherwise always be undiscovered and conflicts not detected (see e.g. level-3 in the test).

cmdline/apt-get.cc: emit Signed-By field and support $(SIGNED_BY) in apt-get indextargets --format

2025-03-14T08:29:23Z

refactor: Deduplicate and Move SectionInSubTree to Configuration

2025-02-18T09:56:45Z

Deduplicate the copies in a central one, mark it unavailable to external users.

cache: Introduce partial SourceVersion support

2025-02-15T15:37:19Z

This is the first step that introduces a 1:1 mapping between version and source version. In a future version this can use the fields currently marked unavailable to deduplicate the SourceVersion objects across the group. The policy gains a member for storing pins for sourceversions. Together, in the future we should be able to determine candidates for source versions.

Record all available sources for descriptions

2025-01-30T23:10:02Z

Avoiding duplications is one thing, but it could also be handy to know all sources for a description so that you can e.g. avoid opening another file or similar such if its also present in one you already have open. Given how the structures were set up this was probably intended all along and either worked at some point or was abandoned for the duplicates that we started culling heavily with the introduction of MultiArch as at that point they blew up the cache and needed to be dealt with.