| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
This reflows the documentation po files now using the latest
gettext.
|
| |\
| |
| |
| |
| | |
apt: Introduce the modernize-sources command
See merge request apt-team/apt!438
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Schedule the removal not before 2029.
Gbp-Dch: full
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This handles rewriting .list entries to .sources ones; the
only options handled are
- signed-by => Signed-By
- trusted => Trusted
The options to specify architectures, check-valid-until, etc.
are not supported as they are not exposed in the code. We
probably should refactor the parser at some point so we can
actually read the parsed entry rather than the abstract objects
we create from it.
This can be improved further:
- Keyrings from /etc/apt/trusted.gpg.d should be moved to
/etc/apt/keyrings.
- automatic detection by trying to verify using each keyring
in trusted.gpg.d until we find the right one and then using
that for Signed-By rather than leave some sources empty.
|
| |/ |
|
| |\
| |
| |
| |
| | |
apt-secure manual page is in manual section 8
See merge request apt-team/apt!434
|
| |/ |
|
| |\
| |
| |
| |
| | |
Fix regression that prevented sending intermediate client certificates
See merge request apt-team/apt!437
|
| |/
|
|
|
|
|
|
|
|
|
| |
The change from the GNUTLS backend to the OpenSSL backend only loads
the first certificate from a client certificate file. As a result it
is no longer possible to send intermediate client certificates to the
server to assist in certificate verification. Instead call
ssl_ctx_use_certificate_chain_file so intermediate certificates can be
sent.
Signed-off-by: Sam Hartman <hartmans@debian.org>
|
| | |
|
| |\
| |
| |
| |
| | |
sqv, gpgv: Do not fail if Dir::Etc::Trusted is set and trusted.gpg.d is missing
See merge request apt-team/apt!433
|
| |/
|
|
|
|
|
|
|
|
| |
This should remain a warning case for now. So push the errors
to a stack and see if we can find any file.
Explictly warn again if Dir::Etc::trusted is set, as it is like
_super_ deprecated.
Reported-By: Cyril Brulebois <kibi@debian.org> in Bug#1032131
|
| | |
|
| |\
| |
| |
| |
| | |
Warn about missing Signed-By in .list format
See merge request apt-team/apt!431
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The trusted.gpg file has been deprecated since February 2022
and can no longer be managed easily without apt-key, so we
should not be falling back to it by default.
We do not remove the actual code to fall back to it, such that
code that passes Dir::Etc::trusted explicitly continues to work
for the time being (with the warnings in update), as the overhead
is now rather trivial.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This warning has been superseded by the missing sources.list
notice (which will also become a warning shortly)
Adjust the sqv exit to avoid introducing a new spurious
"No good signature" that we did not reach before.
moo
|
| |/
|
|
|
|
| |
Warn about the missing field there and suggest the transition
to deb822 .sources files if we found any non-deb822 source
without signed-by.
|
| |
|
|
| |
This is more generic, allowing us to use jak's runner again.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gcc 14.2.0-9 causes vector instructions to be emitted in the
constructor when it is being inlined into BaseHttpMethod::Loop(),
which seemingly only on Graviton instances, causes the field to
be initialized to 0 (Chunked) instead of 2 (Closes), causing the
code to fail later when it tries to interpret file data as the
chunk size. It's plausible we are missing some register saving
here - that is, the q31 register overrides an x register.
Work around this by making Closes element 0, such that 0
initialisation results in the correct Closes value.
Reported-By: Myon on IRC
|
| |
|
|
|
|
|
|
| |
The test was failing for me as the PGP signature contained "GeviljGB"
which is clearly not the evil we are looking for. Sadly, reproducing
this is hard, but random failures of the test suite are annoying, so
lets grep for a bit longer strings that can't happen in the signature
block to avoid this particular problem.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
For some reason ~ that I don't know and can't come up with on the spot ~
we output the Pre-Depends field as PreDepends in the translated
user-visible output and I accidentally copied that over to the
untranslated variant that replaced the embedded copy (with a dash)
in the EDSP generator.
Code-copies and implementation details littered all over the place are
apparently sometimes a good bug-free thing, too…
Regression-of: 6828ae2c2f9268c8187f0fa91b3c464ed84a8476
Closes: #1093254
|
| | |
|
| |
|
|
|
|
| |
This allows us to register workers that can only run amd64
images like mine which runs on podman and podman does not
allow pulling i386/ without specifying --arch i386
|
| | |
|
| |
|
|
|
| |
Check for empty string_view instead of first byte being '\0';
this otherwise breaks when compiling with higher ABI version.
|
| |
|
|
|
| |
Add some more test cases where only one of the sources is bad;
and switch to htp to make the order more reliable.
|
| |\
| |
| |
| |
| | |
apt-pkg/deb/debsystem.cc: Fall back to "dpkg" when Dir::Bin::dpkg is not found
See merge request apt-team/apt!419
|
| | |
| |
| |
| |
| |
| | |
The custom dpkg binary may be removed by apt and that breaks the end of
the operation. This can be observed when using eatmydata as dpkg and
removing the symlink to eatmydata when removing the apt-eatmydata package.
|
| |\ \
| | |
| | |
| | |
| | | |
d/t/control: Don't depend on gdb-minimal.
See merge request apt-team/apt!429
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
gdb-minimal will soon be dropped from the archive; it doesn't offer
any advantages over the gdb binary package. Just depend on gdb
directly.
Signed-off-by: Sergio Durigan Junior <sergiodj@debian.org>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Drop unused and obsolete macros as well as documentation
See merge request apt-team/apt!428
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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: f4e0e9daf221e840e122b0ffa97007aa512020a6
Closes: #1091344
|
| | | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Even the long form isn't used much (or currently not at all), but given
that the short form is not really working even if it would be used…
lets drop it and use the long form if we have to.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
nodiscard is a C++17 feature and already used (not just due to my recent
changes) in our codebase, so lets drop the last remaining holdouts.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
C++14 includes the standard attribute, so we can use that instead.
Note that we drop the deprecation of {Pkg,Dep}Iterator::operator<< as
this is ignored (a friends declaration must be a definition to have
attributes) very noisily by GCC >= 12 and the methods can be somewhat
useful in debugging if you are to lazy to get APT::Pretty{Pkg,Dep}.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
[[noreturn]] is a C++11 feature and so we can just use it
unconditionally.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
They are rather generic names for macros and have no usage in our
codebase at all, so lets remove them for good now.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
That macro is not that useful as it might perhaps once was. Lets prepare
dropping it now in favour of more standard ways of working with arrays
now.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We were rather inconsistent in using it and as our public headers
contain deduction guides (a c++17 feature) it seems silly to try to hide
a c++11 feature in a macro, so lets stop this charade and drop the
macro and while we are changing all these lines lets apply [[nodiscard]]
(another c++17 feature) and other suggestions from clang-tidy and
formatting for a little more consistency.
|