| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the solver handles cases where a Breaks b (<< 1) and
if we install that a, upgrades b. However, where b Depends a (= 1),
b was removed again.
This addresses the problem by iterating over installed reverse
dependencies of upgrades and upgrading them so that both cases
work roughly similarly.
LP: #1974196
|
| |
|
|
|
|
|
|
| |
Pass some package names to upgrade to see that that works
Gbp-Dch: ignore
|
|\
| |
| |
| |
| | |
Fix readme typos
See merge request apt-team/apt!244
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Switch from "security.d.o" to "deb.d.o" (matching bullseye release notes)
See merge request apt-team/apt!246
|
| |/
| |
| |
| | |
Also, this adds "SUITE-updates", which helps show off one of the smaller benefits of deb822-style sources.list (less duplication).
|
|\ \
| |/
|/|
| |
| | |
Rewrite phased updates using a keep-back approach
See merge request apt-team/apt!245
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a package is already pinned to a negative value, we should not
override this with a positive 1. This causes packages to be installable
that were pinned to -1, which is not intended.
For this, implement phasing as a ceiling of 1 for the pin instead
of a fixed 1 value. An alternative would have been to fix it to
NEVER_PIN, but that would mean entirely NEW packages would not be
installable while phasing which is not the intention either.
LP: #1978125
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a lot closer to the original implementation in update-manager,
but still has a couple of differences that might cause bugs:
- When checking whether a version is a security update, we only
check versions in between and not any later version. This happens
mostly because we do not know the suite, so we just check if there
is any version between the installed version and our target that
is a security update
- We only keep already installed packages, as we run before the
resolver. update-manager first runs the resolver, and then marks
for keep all packages that were upgraded or newly installed that
are phasing (afaict).
This approach has a significant caveat that if you have version 1
installed from a release pocket, version 2 is in security, and version
3 is phasing in updates, that it installs version 3 rather than 2
from security as the policy based implementation does.
It also means that apt install does not respect phasing and would
always install version 3 in such a scenario.
LP: #1979244
|
|\ \
| | |
| | |
| | |
| | | |
Fix integer underflow in flExtension
See merge request apt-team/apt!240
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this patch, the expression `Res - File.length()` that was
used as the length underflowed. It was very unlikely to cause any
problem given the saturating behavior of the std::string
constructor that's used.
Replacing `Res - File.length()` with `File.length() - Res` would
have worked, but omitting the last argument altogether invokes an
std::string constructor which does the right thing.
|
|/
|
|
| |
Closes: #1011315
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
/dev might not be populated for example in unshare chroots, so just
using a temporary file it is until triehash supports non-file input.
Regression-Of: f6438ea9e726a1c13ce8d90ac78cc272346ab0f8
Gbp-Dch: Ignore
|
|
|
|
|
|
|
|
|
|
| |
Who does arch:any builds, right?
Ignoring for changelog as this would just confuse readers as the
effected version was never released.
Regression-of: cd92098caa64b7fd30cdc6b5d56bf7e9e17a449e
Gbp-Dch: Ignore
|
|\
| |
| |
| |
| | |
Support building with no/less docs and use it more in CI
See merge request apt-team/apt!238
|
| |
| |
| |
| |
| |
| |
| | |
The rest of our documentation files is in apt-docs, but this one is
general and small enough to be in the default install so users have an
easier time finding information like how to reach us and some debug
advice.
|
| |
| |
| |
| |
| |
| |
| | |
Some of our headers use APT_COMPILING_APT trickery to avoid exposing too
broadly details we don't want external clients to know and make use of.
The flip-side is that this can lead to different compilation units
seeing different definitions if they aren't all using the same config.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use 'stty sane' to combat against stepped output and co caused by
(especially) failed tests, but it does so many things that it
occasionally fails to reset some bits in the parallel interaction we
have with it which fails the tests without a real problem in apt…
Ideally we would be better at stitching the output together, but for the
time being lets ignore these failures instead to stabilize the tests.
|
| |
| |
| |
| |
| | |
The documentation will not realistically vary between architectures so
building it twice is just wasting time and resources.
|
| |
| |
| |
| |
| | |
The checks mostly deal with verifying the syntax of the documentation
files and the po4a translations which have no tests otherwise.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Our public interface doesn't use zlib for quite a while now so lets drop
the last remnants as hopefully nobody depends on us bringing it in…
Unlike our own private lib for transitive provision of unistd.h.
References: 680b916ce7203a40ebd0a3882b9a71ca77278a67
|
| |
| |
| |
| |
| |
| | |
Building the library just so we can build the helpers against it is not
only wasteful but as we are supposed to test the system we can use that
as an additional simple smoke test before the real testing starts.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
autopkgtest says:
Tests may not modify the source tree (and may not have write access to it).
We don't really modify the source of course, but we created our build/
directory in the tree, which seems to work just fine (for now), but lets
be nice.
|
| |
| |
| |
| |
| |
| | |
Reorganising the control file allows this simple test to run first and
be marked as superficial which makes no practical difference, but is
more correct.
|
| |
| |
| |
| |
| |
| |
| |
| | |
As the name suggests the command was introduced for the travis CI which
used to be based on a fixed old(er) ubuntu release. The service is no
more (at least not like it was) and nowadays the command runs in
unstable or equivalent environments, so can depend a bit more on apt
features we have implemented years ago instead of duck tapping.
|
| |
| |
| |
| |
| |
| | |
The documentation generated by doxygen is currently not reproducible,
but as fixing this seems hard we can at least provide a way to check
more automatically if the rest of src:apt is reproducible or not.
|
| |
| |
| |
| |
| |
| | |
Differentiating between different types of documentation we build helps
in better expressing what needs to be done for our arch:any and arch:all
packages currently as well.
|
| |
| |
| |
| |
| |
| |
| | |
References: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names
Closes: #1009797
[@donkult: reworded commit message slightly & changed variable name]
|
|/
|
|
|
|
|
|
|
|
|
|
| |
CMake by default sets the RPATH property on executables that link to
shared libraries in the same project with an absolute path, which
triggers BuildId differences.
References: https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
https://gitlab.kitware.com/cmake/cmake/-/issues/18413
Closes: #1009796
[@donkult: reworded commit message slightly and have flag passed first]
|
|\
| |
| |
| |
| | |
Do not accept arguments for apt-cache dotty, xvcg
See merge request apt-team/apt!237
|
| |
| |
| |
| |
| |
| |
| | |
These commands do not actually interpret the same
arguments as depends, or any own ones for that matter.
Gbp-Dch: full
|
|\ \
| | |
| | |
| | |
| | | |
Fix mirror method dequeuing incorrect items
See merge request apt-team/apt!236
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the mirror method handles a URI Acquire from apt for a mirror list
it already has, it calls the `RedirectItem` function directly. This
function assumes that the item being redirected is at the head of the
queue, and as such calls `Dequeue` to remove it from the queue. This
resulted in incorrect items being removed from the queue when this
branch is taken and the queue was already non-empty, as the item to be
handled in this case is actually the last item in the queue.
This changes `RedirectItem` to properly remove the item passed to it
instead of calling Dequeue.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Consistently dealing with fields via pkgTagSection::Key
See merge request apt-team/apt!233
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We abstract hashes a fair bit to be able to add new ones eventually,
which lead us to building the field names on the fly. We can do better
through by keeping a central place for these names, too, which even
helps in reducing code as we don't need the MD5 → Files dance anymore.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The speed critical paths were converted earlier, but the remaining
could benefit a tiny bit from this as well especially as we have the
facility now available and can therefore brush up the code in various
places in the process as well.
Also takes the time to add the hidden Exists method advertised in
the headers, but previously not implemented.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
FindS has a APT::StringView based API nowadays, so we can avoid these
explicit calls also allowing us to avoid the std::string in input or
output entirely or at least move it a few branches down.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It was introduced in the first commit for EDSP, but beside this
reference, never appears in documentation and code. Seems like an
earlier name of what APT-ID ended up to be and as such should be
more than safely being able to retire now.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The dependency relation fields old names were deprecated in 1995
as the new ones were introduced. That seems barely long enough now
as a transition period.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
dpkg-dev stopped recognizing it in 2007 (1.14.7) while building packages.
The rename itself happened in 1995 (0.93.72).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The previous regime of the file was to sort it on insert, but that
changes the values in the generated enum, which is fine as long as we
only use it in libapt itself, but breaks on other users.
The header was always intended to be private to apt itself, so we just
document this here now and lay the ground work to have the file in the
future only appended to, so that it remains sufficiently ABI stable that
we can use it outside the library in our apt tools.
We also remove some fields apt is unlikely to need or only uses in
certain cases outside of any (speed) critical path to have enough room
to add more fields soon as currently we are limited to 128 fields max
and it would be sad if we use up that allowance entirely already.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The hack is 7 years by now, so in an attempt to make that slightly
cleaner lets move this to proper variables that can be assigned via
an extra-environment file sources by the framework rather than relying
on my user name and locate in public.
Gbp-Dch: Ignore
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It happens to the best, so it might happen for us, too, one day.
Better to catch it directly instead.
Gbp-Dch: Ignore
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Avoid use of deprecated std::iterator (twice)
See merge request apt-team/apt!232
|
| | | |
| | | |
| | | |
| | | | |
Closes: #1008036
|
| | | |
| | | |
| | | |
| | | | |
Closes: #1010030
|
| |_|/
|/| |
| | |
| | | |
Closes: #1010029
|