| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| |
| | |
Build with and fix warnings of gcc-13
See merge request apt-team/apt!280
|
| | |
| |
| |
| |
| | |
Reported-By: gcc-13 -Wunused-result
Gbp-Dch: Ignore
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The matchers are usually called via its base class, but if we would call
them via the derivate class we would not be able to call the not
explicitly "imported" overloads, which would be strange.
Reported-By: gcc-13 -Woverloaded-virtual
Gbp-Dch: Ignore
|
| | |
| |
| |
| |
| | |
Reported-By: clang-tidy [cppcoreguidelines-explicit-virtual-functions]
Gbp-Dch: Ignore
|
| | |
| |
| |
| |
| |
| |
| | |
In gcc-13 internal includes were reduced exposing our laziness.
Reported-By: gcc-13
Gbp-Dch: Ignore
|
| | |
| |
| |
| |
| | |
Reported-By: gcc -Wsign-compare
Gbp-Dch: Ignore
|
| | |
| |
| |
| |
| | |
Reported-By: gcc -Wunused-parameter
Gbp-Dch: Ignore
|
| |/
|
|
|
|
|
|
| |
The code isn't using any of the member types this template provides,
so we can just drop it from the code without any practical effect.
Reported-By: gcc -Wdeprecated-declarations
Gbp-Dch: Ignore
|
| |
|
|
| |
Closes: #1029280
|
| |\
| |
| |
| |
| | |
Document --allow-insecure-repositories
See merge request apt-team/apt!277
|
| |/
|
|
|
| |
since --no-allow-insecure-repositories is the default.
Signed-off-by: MichaIng <micha@dietpi.com>
|
| | |
|
| |\
| |
| |
| |
| | |
make ?installed pattern match installed version only when narrowed
See merge request apt-team/apt!275
|
| | |
| |
| |
| | |
They have been since 1.9.9, lol
|
| |/
|
|
|
|
|
|
| |
This is the correct behavior, but it was overlooked when aptitude
patterns where ported. I remember wondering about this, but I checked
the aptitude code and saw a check that CurrentVer != 0 or something
and then apparently did not notice another implementation for version
matching.
|
| |\
| |
| |
| |
| | |
Do not document path to be repeatable in apt-ftparchive cmds
See merge request apt-team/apt!267
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The manpage for apt-ftparchive {packages,sources} claims that the
path argument can be repeated, but that logically conflicts with having
two optional arguments after that and isn't implemented in code either,
so we just adapt the documentation to reality here.
So, since when is this documentation wrong? The manpage is currently
written in xml (since 2004), but the sgml before that had the same
mistake included all the way back to a time in which time itself is not
stable (the commit is dated in git 2004, but the commit message
says 2001 while including a d/changelog stanza dated 2000) in
my favorite commit "Join with aliencode" which brought in a whole lot
of stuff adding also (quoting said d/changelog entry) "apt-ftparchive
the all dancing all singing FTP archive maintenance program".
In other words: It was documented this way for more than 22 years.
Reported-By: Michael Tokarev on IRC
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Changes in the entities do not lead to a rebuild of the manpages
otherwise. We also try to have each lingua have its own (translated)
entities as dependencies rather than all as the old code order
would have suggested.
Gbp-Dch: Ignore
|
| |\ \
| | |
| | |
| | |
| | | |
Add 'tasks' section to default APT::Never-MarkAuto-Sections list
See merge request apt-team/apt!273
|
| |/ /
| |
| |
| |
| |
| | |
Task packages need to be handled just like metapackages so that users
don't accidentally autoremove half of their system after removing one
of task's dependencies.
|
| | |
| |
| |
| | |
Closes: #1023456, #1025843
|
| |\ \
| | |
| | |
| | |
| | | |
Typo fix
See merge request apt-team/apt!270
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
improve `--help` text for cmdline `apt autoremove`
See merge request apt-team/apt!271
|
| |/ / |
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Actually delete temporary apt-key.*.asc helper files
See merge request apt-team/apt!266
|
| | |
| |
| |
| |
| |
| |
| | |
During development there was an if (0) there for debugging purposes
that unfortunately stayed in and caused files to accumulate.
LP: #1995247
|
| |\ \
| | |
| | |
| | |
| | | |
po/zh_CN.po: Update translation for apt/2.5.3
See merge request apt-team/apt!264
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
Documentation for autopurge command
See merge request apt-team/apt!263
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
since base-passwd 3.6.1 the _apt user is in the default /etc/passwd, so we can...
See merge request apt-team/apt!260
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
- so do not call adduser if the _apt user already exists
- make adduser dependency optional if base-passwd >= 3.6.1
- do not call adduser if $DPKG_ROOT is non-empty as adduser doesn't
support working on a custom root directory
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Allow apt to run if no dpkg/status file exists
See merge request apt-team/apt!257
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Not having a dpkg/status file used to be a hard error which from a
boostrap perspective is suspect as in the beginning, there is no
status so you would need to touch it into existence.
We make a difference between factual non-existence and inaccessibility
to catch mistakes in which the file is not readable for some reason,
the testcase test-bug-254770-segfault-if-cache-not-buildable is an
example of this.
Note that apt has already figured out at this point that this is a
Debian-like system which should have a dpkg/status file. This change
does not effect the auto-detection and is not supposed to.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We needed a fake dpkg in our status file for dpkg --assert-multi-arch to
work in the past, but recent dpkg versions do not require this anymore,
so we can remove this somewhat surprising hackery in favour of better
hidden hackery we only use if we work with an older dpkg (e.g. on
current Debian stable).
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Failing to properly create the status file class should be reported back
to the caller so it can proceed accordingly instead of proceeding into
more failures.
This gives us:
E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory)
E: The package lists or status file could not be parsed or opened.
instead of:
E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory)
E: Could not open file - open (2: No such file or directory)
E: Problem opening
E: The package lists or status file could not be parsed or opened.
and valgrind reporting actions on uninitialised values.
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
phased update improvements
See merge request apt-team/apt!262
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
By marking them at the end, we might make other decisions that
depend on the new phased updates, confusing the solver. Run the
marking at the start too.
The EDSP test file from Jeremy was modified to include Machine-ID
and Phased-Update-Percentage fields and then filtered to mostly
exclude packages irrelevant to the test case by running
grep-dctrl \( -FRequest "EDSP 0.5" -o -FInstalled yes \
-oFPhased-Update-Percentage 10 \) \
-a --not -FArchitecture i386
LP: #1990586
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When iterating over I's dependencies (which are called Pkg), we
accidentally checked if I was Protected() instead of Pkg when deciding
whether Pkg can be kept back.
LP: #1990684
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add Machine-ID to the first stanza, and copy Phased-Update-Percentage
to package stanzas.
This will be tested at a later state by the EDSP test case for
bug 1990586.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Respect users pkg order on `apt install` for resolving
See merge request apt-team/apt!256
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The command line is evaluated in two steps: First all packages given
are marked for install and as a second step the resolver is started on
all of them in turn to get their dependencies installed.
This is done so a user can provide a non-default choice on the command
line and have it respected regardless of where on the command line it
appears.
On the other hand, the order in which dependencies are resolved can
matter, so instead of using a "random" order, we now do this in the
order given on the command line, so if you e.g. have a meta package
pulling in non-default choices and mention it first the choices are
respected predictably instead of depending on first appearance of the
package name while creating the binary cache.
I might have "broken" this more than a decade ago while introducing the
reworked command line parsing for Multi-Arch, which also brought in the
split into the two steps mentioned above which was the far more
impactful 'respect user choice' change. This one should hardly matter in
practice, but as the tests show, order can have surprising side effects.
|
| | | |/
| |/|
| | |
| | |
| | | |
Reported-By: gcc
Gbp-Dch: Ignore
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
apt-pkg/contrib/fileutl.h Explicitly include sys/stat.h
See merge request apt-team/apt!255
|
| | |/ /
| | |
| | |
| | | |
This fixes compatibility with musl C library.
|