| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
Closes: #1116322
|
| |
|
|
| |
Closes: #1115367
|
| |
|
|
| |
Closes: #1115366
|
| |
|
|
| |
Closes: #1110853
|
| |\
| |
| |
| |
| | |
ExecFork: Simplify closing and make it safe
See merge request apt-team/apt!525
|
| | |
| |
| |
| |
| | |
Rather than just setting the flags to 0 or FD_CLOEXEC, read
the current value and append or remove as needed.
|
| |/
|
|
|
|
|
|
|
| |
Implement a wrapper around FD_CLOEXEC and use it in place of
the raw fcntl(). This wrapper _Exit()s the child if the operation
failed.
Restructure the close_range() handling to simply mark all fds for
closing first and then "reopen" the ones we should keep.
|
| | |
|
| |\
| |
| |
| |
| | |
ExecFork: Use close_range() if available
See merge request apt-team/apt!524
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Use close_range() if we have it in preference to iterating
over /proc/self/fd and falling back to closing all possible
fds.
This builds sets of ranges to close that take into account
the APT::Keep-Fds vector, and a test case is provided to
ensure correctness of the splitting logic.
Preference is given to close_range() over /proc as in the
optimal case, this results in a single system call!
|
| |\
| |
| |
| |
| | |
Let APT::Get::Mark-Auto satisfy APT::Get::Build-Dep-Automatic
See merge request apt-team/apt!514
|
| |/
|
|
|
|
|
|
| |
This allows:
apt build-dep --mark-auto apt
Closes: #973260
|
| |\
| |
| |
| |
| | |
Fix history command error when no ID was given
See merge request apt-team/apt!520
|
| |/ |
|
| |\
| |
| |
| |
| | |
fix compiling with musl
See merge request apt-team/apt!508
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In case apt is compiled against musl-libc, then compilation fails with the
following error:
cmdline/apt-internal-solver.cc:122:20: error: 'basename' was not declared in this scope; did you mean 'rename'?
| 122 | if (strcmp(basename(argv[0]), "solver3") == 0)
| | ^~~~~~~~
| | rename
To fix it, include libgen header where musl can find this function also.
Once this is fixed, compilation fails once again with musl-libc, because
the basename function takes *char argument instead of const *char:
this is because the musl implementation cuts off the trailing slashes
of the path, in case the argument is a folder path.
To account for this, instead of passing argv[0] directly, create a non-const
string copy of it, and pass that to base.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
| |
We don't quite know why a stuck queue cannot get unstuck here,
and it's possible that this is causing the queue to stall, but
shrug.
Closes: #1111554
|
| | |
|
| |\
| |
| |
| |
| | |
Add history undo, redo, and rollback features
See merge request apt-team/apt!518
|
| |/ |
|
| |
|
|
|
|
| |
When testing as installed, we inadvertently do not replace
the command-line with dummy in the "apt history-list"
command.
|
| | |
|
| | |
|
| |
|
|
| |
For some reason I have them in my log file.
|
| |
|
|
|
| |
This will particularly be useful in the next commit; just
strip the path form the commandline.
|
| |\
| |
| |
| |
| | |
History Command and Parsing
See merge request apt-team/apt!516
|
| |/ |
|
| |
|
|
|
|
|
|
|
| |
autopkgtest run on stable can have an uname like "6.12.41+deb13-amd64".
The +deb13 being relatively new in the package name. The code doing the
autoremoval has no problem with it and its a legal package name, but
the test that wants to check if the right regexes are generated does not
escape the + correctly (aka at all) so it isn't finding the regex it is
looking for failing the test.
|
| |
|
|
|
|
|
|
| |
Tests usually print the command they run, but it can be overridden with
a chosen message to make clearer what is actually tested. To debug
failures it can be useful to know the command run through especially if
its a partly generated command depending on the test environment
(like in the kernel autoremove test).
|
| | |
|
| |\
| |
| |
| |
| | |
edsp: Bug fixes for architecture reading and dumping solver errors
See merge request apt-team/apt!483
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We skipped the Architecture: line because when the outer
loop got to it, the inner loop started and read the next
line after it.
Get rid of the nested loop instead, and first run a loop
to find the request line, and then a second loop to parse
the request flags.
An alternative would be to use a combined loop that
supports non-compliant protocol implementations, but
that's harder to read and we don't expect there to be
any especially on the request side.
|
| |/
|
|
| |
We need to actually use the architecture values we set
|
| |\
| |
| |
| |
| | |
Fix indentation compiler warning with clang
See merge request apt-team/apt!498
|
| |/
|
|
|
|
| |
This commit fixes the following compiler warning.
cacheiterators.h:423:54: warning: misleading indentation;
statement is not part of the previous 'if' [-Wmisleading-indentation]
|
| |\
| |
| |
| |
| | |
debListParser: Cache `essential` and `myArch` more
See merge request apt-team/apt!503
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Lookup these variables in the constructor once, rather than
once per package.
This requires a bit of care as debListParser::UsePackage()
defaults to "all" for essential when unset, hence we simply
change its == "all" comparisons to == "all" || .empty().#
This removes any per-paragraph configuration lookups
from the file parser.
Also parse myArch from ParseProvides down to ParseDepends()
as that call ended up causing it to query APT::Architecture
*again* since the function we call is static.
Together, the removed config lookups safe about 2.3% of
cache generation runtime.
|
| |\
| |
| |
| |
| | |
Update Simplified Chinese translation
See merge request apt-team/apt!504
|
| |/ |
|
| |
|
|
| |
Closes: #1111875
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Lots of people have pinned an older version that is no longer
installable, or more common yesterday, we saw a lot of people
who seemingly manually installed a newer version of a deb than
in the repositories, causing the package to be considered obsolete,
which does not make much sense.
Oops: 4c39d922-410f-11f0-bbf9-fa163ec44ecd
Oops: a64054f6-4140-11f0-bbfd-fa163ec44ecd
Oops: a32196c1-661d-11f0-a97c-fa163ec8ca8c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of inadvertently sorting dependency targets against
the first alternative in an or group, sort them against the
current alternative as we should.
Otherwise we ended up sorting
gnome-shell | notification-daemon
With
Package: notification-daemon
Package: awesome
Provides: notification-daemon
into
gnome-shell | awesome | notification-daemon
<-we sorted this part wrongly->
This fixes a minor difference in test-release-candidate-switching
in one case, but not the other where the difference was actually
caused by the loss of install argument ordering information in
the new solver, so just flip the arguments so both solvers produce
the same outcome.
|
| |
|
|
| |
Closes: #1111124
|
| |
|
|
|
| |
xmllint 2.14 reports that filename cannot be used inside of
arg, breaking the CI. Remove the filename element.
|
| |\
| |
| |
| |
| | |
completion: apt why/why-not
See merge request apt-team/apt!505
|
| |/ |
|
| | |
|
| | |
|