| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
Closes: #1104313
|
| |
|
|
| |
Closes: #1103760
|
| |
|
|
| |
Closes: #1103640
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This reverts commit 66ec0dfad8ac1d4d8646a4734eb9353f3ebc0a91.
This creates too much churn in the translation.
|
| |
|
|
|
|
| |
Closes: #310975
Signed-off-by: Daniel Lublin <daniel@lublin.se>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The order of apt sources can matter, but this man page did not
previously define whether /etc/apt/sources.list was parsed before or
after the fragment files in sources.list.d. Giving a concrete example
also provides a hint that numeric prefixes are a useful way to force a
particular sort order, and clarifies that the .list or .sources extension
is less important than lexicographic order.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
The order of preference stanzas matters, but this man page did not
previously define whether /etc/apt/preferences was parsed before or
after the fragment files in preferences.d. Giving a concrete example
also provides a hint that numeric prefixes are a useful way to force a
particular sort order, and clarifies that the presence or absence of
the .pref extension is less important than lexicographic order.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
|
|
| |
Recognize the method and update the documentation and prompts.
|
| |
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
'Include' allows limiting a repository to a allowlist of packages,
'Exclude' allows removing packages from a repository.
Implementation wise this is not the nicest as it goes via the
IndexTarget options, so we first parse our option value into a
vector, then we turn the vector into a string, and then vectorize
it again. That said, we support both "," and " " as separators due
to the construction (we split by "," then we join using " ").
Gbp-Dch: full
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The check option discovers broken format string translations as
well as other issues like broken headers, enable it.
The Japanese translation was discovered to both use the wrong
ordering for %.*s translations with different positions, and
missing the dot, e.g.
%1$*2$s should have been %2$.*1$s
(the number after % matches the string and the number after
.* the size)
|
| | |
|
| | |
|
| |
|
|
| |
And so it begins.
|
| |
|
|
| |
Closes: #1100801
|
| | |
|
| | |
|
| |
|
|
|
| |
* rephrase information about possible snapshot values
* add snapshot example configurations
|
| |
|
|
| |
indextargets --format
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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
|
| | |
|
| | |
|
| |
|
|
|
| |
A SAT solver can run more or less forever, but that's not a good
user experience.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If a dependency can be satisfied by all versions of a package,
add the package to the clause instead of the version object.
This works only if there are no providers for the package: Providers
are quite hard to enumerate over and make sure that all versions of
a package satisfy the provider dependency.
Implement arbitrary selection between packages and versions for
the CompareProviders class: We pick the best version for each package
and then pit them against each other.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
A clean build fails due to issues in the translated apt.ent,
but I "only" tested a dirty build which didn't cause the file
to be regenerated and hence an old valid file to be used.
Ignored for the changelog as this is just a fixup of a
previous commit that never shipped to anyone except CI.
Regression-Of: 2d3f4654cd6a70c3fa1a40ec423a19b101ea5307
Git-Dch: Ignore
|
| |
|
|
|
|
|
| |
Note: Committer fixed `fr.po:1833: end-of-line within string` error
reported by `msgfmt --check`.
Closes: #1088326, #1050876
|
| |
|
|
|
|
| |
Note: Committer fixed two accidentally translated closing tags
Closes: #1095411
|
| | |
|
| | |
|
| |
|
|
|
| |
This reflows the documentation po files now using the latest
gettext.
|
| | |
|
| |
|
|
|
|
| |
Schedule the removal not before 2029.
Gbp-Dch: full
|
| | |
|
| | |
|
| | |
|
| | |
|
