| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
As the FTP method is dropped it is probably better to use an example
that actually works. We use https here as that requires no other text
changes as there is a HTTPS session to reuse similar to FTP usage ~ that
is the case for our HTTP, too, but the concept of a session isn't
usually known there and servers who close the connection after every
request are more common.
|
| |
|
|
| |
References: fd3684cdbc165ceaa635ed19fcbd231f509b0179
|
| |
|
|
| |
References: a00fbbdb28cc31e78882301c2efe7218583ab4cb
|
| |
|
|
|
|
|
|
|
| |
They were implemented to help a tiny bit in notifying users even if they
didn't read the Release notes (or didn't realize it would apply to them)
that they likely have to change their sources.list entries, but that
transition is now over for a while, so everyone who should have seen it
has hopefully reacted to it and so all this code now does is waste
space, time and idly waiting for false positives.
|
| |
|
|
|
|
| |
We updated po/ with libunistring 1.3 as before, but had no
doc changes since the manual update with libunstring 1.2,
so no churn there. Hooray.
|
| |
|
|
| |
With libunistring5 to avoid https://bugs.debian.org/1091871
|
| |
|
|
|
|
|
|
|
|
|
| |
s#ftp://ftp.debian.org#ftp://example.org#g
s#at ftp.debian.org#at ftp.example.org#
s#debian-non-US/ stable/(non-US/)?#debian/ stable/#g
s#debian-non-US/ unstable/(non-US/)?#debian/ unstable/#g
s#stable/ Packages#stable/main Packages#g
s#http://ftp.de.debian.org/debian,#http://deb.debian.org/debian,#g
s#testing non-US#testing#
s#ftp.debian.org#ftp.example.org#
|
| |\
| |
| |
| |
| | |
Cleanup non-US and ftp references from code and documentation
See merge request apt-team/apt!231
|
| | |
| |
| |
| |
| |
| |
| | |
While the ftp.debian.org URLs are still functional in Debian, they
can confuse people as the protocol is mismatched. Using the
deb.debian.org frontend should also generally give generally good
performance regardless of the client location.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Although Debian does not support FTP, this might still be used by other
organizations, or local users, so replaced these instances with an
example.org URL.
Ref: https://lists.debian.org/debian-announce/2017/msg00001.html
|
| | |
| |
| |
| |
| | |
This has long been obsoleted, and there have been previous patches
cleaning them up, but some left overs remained.
|
| |\ \
| |/
|/|
| | |
apt Debian release 2.9.20
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
This matches the filename used by default in Ubuntu since Ubuntu 24.04,
and in Debian cloud images and the Debian images provided by docker.io
since Debian 12 (although not currently used in new installations via
debian-installer).
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Automatically show the output of `show`, `policy`, `list`,
`search`, `showsrc` in a pager.
The pager setup is inspired by git's pager setup. Notably,
the pager is found using APT_PAGER and PAGER variables.
We wait for the pager to be setup somewhat correctly by
using a notify pipe to figure out whether execvp() was
succesful - then the pipe will read EOF as the other end
got closed by CLOEXEC during exec - or not, then the pipe
will contain an errno.
We set up the correct handlers for signals and exit to close
the fds and wait for the pager. Notably inside the signal
handler we cannot flush our streams, only close them, so
there is some duplication.
We call the InitOutputPager() function from inside the
various Do...() functions rather than setting it up
generally in InitOutput(). Doing so allows us to first
render the progress without a pager, and then setup
the pager for the content only which improves user
experience.
When we setup a pager we also take care to disable
standard input, as we should not be prompting users
while a pager is running (the pager will be reading
from the tty directly). We do this by dup2-ing() a
/dev/null over it; if we just close()d the fd, another
open() might reuse the fd number and problems could
occur.
|
| | |
|
| |
|
|
|
|
|
| |
We move the user configuration section to the top of the manual
page as that is going to be what most are interested in and rewrite
it to cover all the modern ways to configure keys in a succinct
way.
|
| | |
|
| | |
|
| |
|
|
|
| |
Oh well I accidentally committed everything from my work email
today but I'm off today ...
|
| |\
| |
| |
| |
| | |
Support uncompressed indexes from partial file:/ mirrors
See merge request apt-team/apt!235
|
| | |
| |
| |
| |
| |
| |
| |
| | |
It is a bit unfair for third-party methods wrapping e.g. http to not
have access to such tools, same for our old ftp and e.g. our tor even
if in practice this isn't used much even for http.
At least that is one less FIXME in the code.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The previous version allowed only foo::*::bar as a pattern, now you can
have as many starred parts as you want allowing for a finer control
instead of hardcoding specific common star-values or giving up with **.
It also adds a new INVALID type for an option to mark options which
should not be used, but are covered by a pattern which would normally
allow it.
Our tests are more or less the only users of this hidden feature making
this change not very risky even through it has no dedicated test itself.
|
| |/
|
|
|
|
|
|
|
|
|
| |
CMake 3.31 is very noisy about our manpage (and to a lesser extend
documentation in general) building as we used "//" and "/../" there.
`cmake --help-policy CMP0177` documents the warning, so we could just
decide on a value and deal with it, but given our usage is not really
needed and rather trivial to change lets not pick a value and instead
use a normalized path so we don't use different code paths in CMake
depending on which CMake version we happen to be build with.
|
| |
|
|
| |
Closes: #1087461
|
| | |
|
| |
|
|
| |
Suggested-by: mhoye on IRC
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some mirrors like snapshot.debian.org apply strict http rate limits.
While apt already has an exponential backoff mechanism implemented, this
is not sufficient due to the following reasons:
1. all retries happen roughly at the same time
2. the retry-after information from the server is not used
We fix this by improving the algorithm: First, if present, the timestamp
or duration of the Retry-After header is added to the exponential
backoff, optimizing for success-on-second-try. Second, a random delay is
added (delay += [0, delay]) to distribute the retries to not immediately
run into the limit again. To avoid super-long delays, this is capped by
the configured maximum delay. This logic only becomes active if the
option Acquire::Retries::HandleRetryAfter is enabled.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
|
| | |
|
| |\
| |
| |
| |
| | |
JSON: Pass options to hooks in hello message
See merge request apt-team/apt!389
|
| | |
| |
| |
| |
| | |
See the attached documentation. Note that defaults are missing,
so using this is not particularly easy so far.
|