| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In "Restore ?garbage by calling MarkAndSweep before parsing" I
made install code run MarkAndSweep before parsing arguments such
that the "?garbage" pattern works correctly.
This caused test suite breakage because packages now ended up
with marked flags in the debug output. Hence add "m" to the output
we assert where necessary.
In a nicer world we might want to just do MarkAndSweep if we actually
have a ?garbage pattern to evaluate but that is a bit unpredictable
in terms of performance expectations and because a "read-only" construct
modifies the depcache, so let's go with the more expected option for now
Regression-of: b6f362e8013b03efce54e7381e0e22fac1fa1539
|
| |\
| |
| |
| |
| | |
Fix incorrect time unit comment for PulseInterval
See merge request apt-team/apt!304
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Update fr.po (add a missing dot)
See merge request apt-team/apt!306
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This ensures that things work correctly.
LP: #1995790
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We used GTEST_ROOT, which becomes an issue with 3.27 as that variable
would influence find_package behaviour by providing PREFIXES –
introduced with potentially mixed-cased name in 3.12.
CMake Warning (dev) at test/libapt/CMakeLists.txt:8 (find_package):
Policy CMP0144 is not set: find_package uses upper-case <PACKAGENAME>_ROOT
variables. Run "cmake --help-policy CMP0144" for policy details. Use the
cmake_policy command to set the policy and suppress this warning.
CMake variable GTEST_ROOT is set to:
/usr/src/googletest/googletest
For compatibility, find_package is ignoring the variable, but code in a
.cmake module might still use it.
As using this new feature isn't what we wanted at all, we just use a
different variable name to avoid the warning and potential future
problems if we would keep using this name.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
CMake Deprecation Warning at CMakeLists.txt:6 (cmake_minimum_required):
Compatibility with CMake < 3.5 will be removed from a future version of
CMake.
Update the VERSION argument <min> value or use a ...<max> suffix to tell
CMake that the project does not need compatibility with older versions.
Picking 3.13 here is a semi-random choice to avoid raising the requirement
too much needlessly while also hopefully avoiding needing to raise it
soon again based on the referenced mail.
While we are at it, lets also fix the other spewed warning:
CMake Warning (dev) at CMakeLists.txt:5 (project):
cmake_minimum_required() should be called prior to this top-level project()
call. Please see the cmake-commands(7) manual for usage documentation of
both commands.
References: https://lists.debian.org/msgid-search/20230617162957.6pklb6632zf4nijc@mail.gaussglocke.de
|
| | | |
| | |
| | |
| | | |
Closes: #1055178
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This unbreaks mmdebstrap scenarios if you mirror Debian or use
a distro where apt did not get overridden to required.
Reported-By: josch on IRC, following discovery by helmut
Gbp-Dch: full
|
| | | |
| | |
| | |
| | | |
Thanks: jwilk for suggestion
|
| | | |
| | |
| | |
| | | |
This reverts commit 668451def296afeb0c358a7d80ff39dc546defab.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This avoids the rabbit hole of md5 on FIPS systems, and repositories
have moved to including the value as well.
Also stop validating the field, this can be an arbitrary string
as far as we are concerned.
|
| | | |
| | |
| | |
| | | |
Translation template reordering carnage :D
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Downgrade unmerged-usr from error to two warnings
See merge request apt-team/apt!307
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
One warning will be issued before the Y/n prompt, the other will
be issued at the end after package installs have been attempted
or if there were other failures, such that the last line you see
is warnings about unmerged-usr
I do not anticipate this to be the final version either, but
there we go.
Closes: #1052058
|
| | | |
| | |
| | |
| | | |
Closes: #1051731
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Closes: #1049427
|
| | | |
| | |
| | |
| | | |
Closes: #1051723
|
| | | |
| | |
| | |
| | | |
Closes: #1051720
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Closes: #1051642
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As of bookworm, merged-usr is mandatory, and people got caught
in the crosshairs of the dpkg fsys-unmessusr debacle and inadvertently
reverted back to an unmerged configuration and continue to remain
on an unsupported system unknowingly.
Help them by erroring out when they are installing packages on /,
they are not in a chroot, and a usrmerge package is available.
|
| |/ / |
|
| | |
| |
| |
| |
| | |
It seems the ubuntu:lunar image has a user with UID 1000 already
which was not the case in previous versions.
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Try to compare SHA256 to determine same version
See merge request apt-team/apt!305
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we know both SHA256, and they're different, the packages are. This
approach stores the SHA256 only at runtime, avoiding the overhead of
storing it on-disk, because when we update repositories we update all
of them anyhow.
Note that pkgCacheGenerator is hidden, so we can just modify its
ABI, hooray.
Closes: #931175
LP: #2029268
|
| | |
| |
| |
| |
| |
| |
| | |
While we are at it fix the mislabeling as (5) in some places and
unfuzzy the translations.
Reported-By: Enrico Zini on IRC
|
| | |
| |
| |
| | |
Closes: #1040644
|
| | |
| |
| |
| |
| |
| |
| |
| | |
@DonKult: Dropped the explicit %-position change from the referenced
bug through as that will require code (and string) changes to work
correctly.
References: https://bugs.debian.org/1034378
|
| | |
| |
| |
| | |
Closes: #1033909
|
| | |
| |
| |
| | |
Closes: #1033904
|
| |\ \
| |/
|/|
| |
| | |
Add "apt-patterns" reference to "apt list" description in apt(8)
See merge request apt-team/apt!303
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Fix snapshot crashes
See merge request apt-team/apt!301
|
| |/
|
|
|
| |
We did not handle multiple components properly, add a contrib
component to the test case.
|
| |\
| |
| |
| |
| | |
Do not fail on systems running in FIPSmode.
See merge request apt-team/apt!295
|
| | |
| |
| |
| |
| | |
Initialize using gcrypt's GCRYCTL_NO_FIPS_MODE, available since
gcrypt version 1.10.0, otherwise apt aborts on FIPS enabled systems.
|
| |\ \
| | |
| | |
| | |
| | | |
dist-upgrade: Revert phased updates using keeps only
See merge request apt-team/apt!299
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes an issue where phased updates gain new dependencies
and cause them to be installed despite themselves not being
installed.
In the cause of investigation, it turned out that we also need
to evaluate the candidate version at those early stage rather
than the install version (which is only valid *after* MarkInstall).
This does not fully resolve the problem: If an update pulls in
a phased update, depends are still being installed. Resolving
this while ensuring that phased updates cannot uninstall packages
requires us to do a minimization of changes by trying to keep
back each new install removal and then seeing if any dependency
is being broken by it. This is more complex and will happen
later.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the bug, mutter was kept back due to phasing and the new gnome-shell
depended on that, and was therefore kept back as well, however,
gnome-shell-common was not broken, and apt decided to continue upgrading
it by removing gnome-shell and the ubuntu desktop meta packages.
This is potentially a regression of LP#1990586 where we added keep
back calls to the start of the dist-upgrade to ensure that we do not
mark stuff for upgrade in the first place that depends on phasing
updates, however it was generally allowed by the resolver to also
do those removals.
To fix this, we need to resolve the update normally and then use
ResolveByKeepInternal to keep back any changes broken by held back
packages.
However, doing so breaks test-bug-591882-conkeror because ResolveByKeep
keeps back packages for broken Recommends as well, which is not
something we generally want to do in a dist-upgrade after we already
decided to upgrade it.
To circumvent that issue, extend the pkgProblemResolver to allow
a package to be policy broken, and mark all packages that already
were already going to be policy broken to be allowed to be that,
such that we don't try to undo their installs.
LP: #2025462
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
update: Add notice about missing Signed-By in deb822 sources
See merge request apt-team/apt!298
|
| | |/
| |
| |
| |
| |
| |
| | |
We want to gently steer users towards having Signed-By for each
source such that we can retire a shared keyring across sources
which improves resilience against configuration issues and
incompetent malicious actors.
|
| |/ |
|