| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|\
| |
| |
| |
| | |
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.
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
typecast time_t and suseconds_t from std::chrono
See merge request apt-team/apt!259
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This ensures that it compiles when clang compiler is passing
-DFORTIFY_SOURCES=2
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
This fixes build on some architectures like mips
progress.cc:125:31: error: non-constant-expression cannot be narrowed from type 'std::chrono::duration<long long>::rep' (aka 'long long') to '__time_t' (aka 'long') in initializer list [-Wc++11-narrowing]
struct timeval NowTime = { Now_sec.count(), Now_usec.count() };
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
| |
| |
| | |
See merge request apt-team/apt!252
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A temporary filename is used as a workaround for bugs/missing features
in other software dealing with /dev/stdin, but nobody said I have to use
the exact same filename….
However in-tree builds are not generally recommended.
References:
https://salsa.debian.org/debian/sbuild/-/commit/aa4a4326d09969e809f336e1b75cbd7342a77529
https://salsa.debian.org/ci-team/autopkgtest/-/commit/fb0561efc41a117963fa3e31802db6b2664c7aa5
Regression-Of: 701a501fb1c84296d2003c0092e4308742079591
Reported-By: Lance Fredrickson <lancethepants@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Support for envvar NO_COLOR was added in 2.3.11, but with our own
options we can also be a tiny bit more sensible in not overriding
an explicit choice to disable colors.
References: 400a6895566b67d70bcde43dc8a1cc1c7121f87d
|
|\ \
| |/
|/|
| |
| | |
doc: Explain that apt-get download ensures package authenticity
See merge request apt-team/apt!251
|
|/
|
|
|
|
|
|
|
|
|
| |
The documentation currently does not specify whether `apt-get download`
verifies the authenticity of downloaded packages or not. The underlying
code does verify the authenticity of packages as usual and would fail if
the package signature is invalid. Therefore it makes sense to make this
guarantee explicit in the documentation, because without it
security-conscious users will likely want to recheck the signatures or
checksums manually which is not necessary in this case and just wastes
time.
|
| |
|
|\
| |
| |
| |
| | |
Upgrade all binaries in a source package
See merge request apt-team/apt!247
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
First mark them for upgrade without autoInst, so we don't call
their "mark other binaries loop"; then call them again with it.
Without this change, each binary package would upgrade the next
one in the list, recursively.
|
|/
|
|
|
|
|
|
|
| |
Schedule all other binaries in the source package for upgrade if
the candidate version belongs to the same source version as the
package we are upgrading.
This will significantly reduce the risk of partial upgrades and
should make life a lot easier.
|
|\
| |
| |
| |
| | |
Mark broken reverse depends for upgrade
See merge request apt-team/apt!248
|
| | |
|
| |
| |
| |
| |
| |
| | |
Because the auto installer now also marks other binaries in the
package for upgrade, we do need to run it or we don't mark those
for upgrade.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
|/|
| |
| | |
apt-pkg: (re)export pkgTagSection::Key to fix FTBFS in python-apt
See merge request apt-team/apt!249
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With apt 2.5.1 python-apt fails to build with:
```
...
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.10 -c python/acquire-item.cc -o build/temp.linux-x86_64-3.10/python/acquire-item.o -std=c++11 -Wno-write-strings -DAPT_8_CLEANER_HEADERS -DAPT_9_CLEANER_HEADERS -DAPT_10_CLEANER_HEADERS -DPY_SSIZE_T_CLEAN
In file included from python/python-apt.h:30,
from python/apt_pkgmodule.h:211,
from python/acquire-item.cc:25:
/usr/include/apt-pkg/deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not been declared
48 | bool ParseDepends(pkgCache::VerIterator &Ver, pkgTagSection::Key Key,
| ^~~
```
This commit adds a small fix by (re)exporting `pkgTagSection::Key`.
|
| |
|
|
|
|
|
|
| |
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).
|