| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| |
| | |
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.
|
| | | | | |
|
| | |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
SSL_read() and SSL_write may return 0 for errors, whereas our
callers only expect -1 for errors and 0 for closed connections,
so map this accordingly.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The OpenSSL docs say:
> For socket I/O on Unix systems, consult errno for details
but also:
> This value can also be returned for other errors,
> check the error queue for details.
This means it's possible errno isn't set, in which case
we may appear to have reached an EOF when we did not.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Streamlining the rules around the Section field and especially what
happens if its isn't present are a good idea in general, but for testing
proposes we want a package without a section ~ something dpkg and co do
not want us to have for good reasons (outside of tests).
While a real nosection package would interact with more of our code, for
this test we don't really need a real one and so we can adopt to the new
reality of encountering such packages only if they are already
installed instead of trying to build a sectionless package by hand.
The other failure is a simple and trivial string change around the
formatting of the version number in dpkg error message about file
overrides, which we can resolve by just not looking at the version to
sidestep dealing with the formatting difference.
References: https://lists.debian.org/debian-dpkg/2024/12/msg00010.html
Closes: #1092090
|
| | |
| |
| |
| |
| | |
There were some references to APT::StringView that don't make much
sense anymore.
|
| | |
| |
| |
| | |
I typoed that.
|
| | |
| |
| |
| |
| |
| | |
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#
|
| |\ \
| | |
| | |
| | |
| | | |
test: Check "${METHODSDIR}/sqv" not "/usr/bin/sqv"
See merge request apt-team/apt!424
|
| |/ /
| |
| |
| |
| | |
This is the correct check to find out whether we have built
with sqv support.
|
| |\ \
| | |
| | |
| | |
| | | |
http: seccomp: Allow reading directories
See merge request apt-team/apt!421
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This is needed by OpenSSL.
Closes: #1091351
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
sqv: Avoid propagating errors between files
See merge request apt-team/apt!422
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We inadvertently did not discard pending errors when the
fallback to Dir::Etc::trusted succeeded, do so.
Also add some quick safety checks to make sure we enter the
verification in a good state, and that if somehow errors are
pending after a verification we return false.
Closes: #1091679
|