| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| |
| | |
solver3: Fix Recommends/Suggests vs Enhances confusion
See merge request apt-team/apt!461
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reorder the if branches a bit to simplify the understanding
of the promotions, and allow us to keep track of which
dependency existed in the installed version.
Change the rule for promoting new recommends to only promote
new recommends to depends in *upgrade* and not *dist-upgrade*
per the test-resolve-by-keep-new-recommends test case.
This makes some sense: In a dist-upgrade, the solver could
otherwise decide to remove an installed package if both the
following hold:
(1) something needs the upgraded version | something else
(2) the upgraded version is not installable due to unsat recommends
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We accidentally considered an Enhances a reason to keep
a package installed, which of course it is not, fix the
determination of "existing soft dependency" to only include
soft dependencies that should keep a package installed in
the autoremover to solve the issue.
This also fixes edsp/mantic-upgrade-rel-to-2024-05-29.edsp
to not install llvm-13-dev for clang-13 which is an installed
package with no upgrade.
Also ensure we stop after the first match; the DependsList()
is ordered by decreasing priority and we don't want to override
Recommends by Suggests in case a package declares both...
LP: #2101800
|
| |/ |
|
| |\
| |
| |
| |
| | |
solver3: Various bug fixes
See merge request apt-team/apt!459
|
| | |
| |
| |
| |
| |
| | |
We incorrectly used the DependencyData of the first or group
member, however that only checked that the first or group member
was the same and that both either had a next member or not.
|
| | |
| |
| |
| | |
This is relevant when debugging common dependencies.
|
| | |
| |
| |
| | |
This only worked for version literals lol
|
| |/
|
|
|
|
|
|
| |
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
|
| | |
|
| |\
| |
| |
| |
| | |
solver3: Do not prefer new installs over manually installed obsoletes
See merge request apt-team/apt!458
|
| |/
|
|
|
|
|
|
|
|
| |
Only move obsolete packages last that are automatically installed,
as we don't want to remove manually installed obsolete packages.
Add some missing const annotations to the operator[] arguments as
well that were needed.
LP: #2100247
|
| |\
| |
| |
| |
| | |
Run 3.0 solver if internal is unsuccessful or we have apport for automatic solver evaluation
See merge request apt-team/apt!446
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This can provide useful additional context.
To avoid updating the whole test suite for it, introduce a new
option `quiet::NoSolver3Explanation` and set it by default. All
the other tests that assert output will already have matching
tests for --solver 3.0 with the correct messages asserted, it
makes no sense to duplicate them.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Always run the 3.0 solver after the internal solver. If the internal
solver failed, and the 3.0 solver did not, use the 3.0 result.
If 3.0 solver failed or produced a worse result than the internal
solver, write an apport crash dump.
We exclude situations which we now the solver can't handle, i.e.
removals are forbidden and you requested removals, and stuff like
that.
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
solver3: Verbose error messages and some bugfixes
See merge request apt-team/apt!457
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Introduce a new function, LongWhyStr() that returns a longer
reason for why something is being installed (or not).
This does the same path walk as the other function does, but
it renders the clauses at each level, and one per line, so
the whole output is a lot more informative.
It is a separate function to keep the existing debug messages
use the simple single line implication graph
We remove the other special case in AddWork() for empty solutions
to mke use of the general case in Solve() instead, and then adapt
the case in Solve() to the same case as in Enqueue(). This also
happens to fix the bug that when we encountered an empty clause
we just printed the clause had no solution, but not how we got
to install the package with the clause.
Adapt the test suite for the changes which is an annoying amount
of paperwork.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I marked exim4-daemon-light for install, which marked
exim4-daemon-heavy for not install, but now in
postfix Conflicts: mail-transport-agent
we saw "not exim4-daemon-heavy" as the reason for not installing
postfix. Oh noes.
|
| | |
| |
| |
| |
| | |
This will print the underlying dependency which is nicer to
read.
|
| | |
| |
| |
| | |
Particularly, use single line and implement operator!=
|
| | |
| |
| |
| |
| | |
This avoids relying on the inserted clause being at the back
of the clauses vector.
|
| |/
|
|
|
|
|
|
| |
Use an integer and tag the lowest bit manually. This makes it
much easier to next convert this into a literal.
Add some constexpr and remove an unnecessary assertion on
CastPkg().
|
| |\
| |
| |
| |
| | |
test: Grep continuation lines in error messages
See merge request apt-team/apt!456
|
| |/
|
|
|
| |
This is important for upcoming multi-line solver error message
work.
|
| |\
| |
| |
| |
| | |
Replace "GPG error" with "OpenPGP signature verification failed"
See merge request apt-team/apt!455
|
| |/
|
|
| |
Reported-by: cacin on irc
|
| |\
| |
| |
| |
| | |
Consider 0-size debs not downloadable, set a size in EDSP
See merge request apt-team/apt!454
|
| | |
| |
| |
| |
| |
| | |
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 dumps all appear as a single file, so we cannot determine
correctly if a package is obsolete. We can fix this by ensuring
that only debs with a size are downloadable, and then by faking
a size in EDSP: The size is 1 if APT-Release is set (there is
a source to download it from) or 0 otherwise.
This ensures that the obsolete logic in solver3 works correctly,
as well as the obsolete patterns, if anyone could actually use
it on the EDSP files.
|
| |/ |
|
| |\
| |
| |
| |
| | |
Add doc/design/install.md: Installation design
See merge request apt-team/apt!449
|
| |/
|
|
|
|
| |
This documents the user interface for apt install, currently
only the solution screen as implemented in the 3.0 output
format.
|
| | |
|
| |
|
|
| |
Gbp-Dch: ignore
|
| |
|
|
| |
Gbp-Dch: ignore
|
| |
|
|
| |
Closes: #1099118
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
apt-ftparchive skips regenerating Contents if they are newer than
the Packages files. Most of the time, the test ended up generating
Contents and Packages files with the same-second timestamp; so we
ended up regenerating them and passing the test.
However, sometimes, the timestamp of the Contents file was 1s
higher and we ended up not regenerating the Contents file and
hence failed the test case.
Ensure the timestamps actually are the same to avoid the race
condition and make this stable.
|
| |
|
|
| |
Closes: #1098937
|
| |\
| |
| |
| |
| | |
Fix crash in VersionExtra using --with-source etc
See merge request apt-team/apt!453
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
VersionExtra holds, at runtime, the SHA256 of the packages being
added to try to avoid deduplicating obviously different packages;
the SHA256 itself is too large to store in the cache.
When volatile sources are used, the VersionExtra array is not
initialized, or rather it used to be initialized to 32*1024
zero elements as a performance optimization.
This meant that specifying --with-source with a package that
looks like a duplicate of a version with an ID >= 32*1024 triggered
the assertion; so we could not reproduce it easily in the test
suite.
Remove the optimized initialization to make the behavior more
uniform; and treat too large version IDs as having no SHA256.
Closes: #1098702
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removal of std::to_string avoids the temporary std::string,
but it leads to locale-dependent output that parsers (including ours)
are not prepared to encounter especially as number formatting
can be highly ambiguous due to different rules surrounding '.' and ','.
In the distant future (c++20) this could be replaced with a variant of
std::format, which incidentally is also what std::to_string becomes
an alias for in an even more distant future (c++26).
Regression-of: 729a5c8f4fb8c841497d26170e1a47c41617ecd9
Reported-By: Stefan Lippers-Hollmann and Kel Modderman on IRC
|
| |
|
|
| |
Closes: #1098456
|
| |
|
|
| |
Closes: #1095976
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We don't really care about solver progress messages in testing;
hide them when comparing output, and hide them better than before.
Previously testsuccessequal ... --solver 3.0 behaved differently
than tests run with globally forced on 3.0 solver.
Stop cleaning up autoremovals, but do clean up "Calculating upgrade"
as well.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Pushing the stack in push and popping it in pop did not
really work correctly and is more complex than needed.
Instead, push the error stack at the start of the Solve()
method and revert at the end, such that we leave exactly
at the same error stack level we entered.
To handle error clearing on backtracking, just discard any
pending errors.
|
| | |
| |
| |
| |
| | |
Implement the moving of the auto bit. The whole auto-bit management
is not entirely optimal yet, but this works.
|