| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| |
| | |
extracttar: Move large buffer to heap for valgrind
See merge request apt-team/apt!378
|
| | |
| |
| |
| |
| |
| |
| | |
valgrind has some trouble on ppc64el with the large buffer, and
also on armhf where it seems to not understand the resulting
stack clash protector, so let's move it to the heap using simple
STL std::array in a std::unique_ptr.
|
| |\ \
| | |
| | |
| | |
| | | |
Minor localisation fixes
See merge request apt-team/apt!374
|
| | | |
| | |
| | |
| | | |
Closes: #967973
|
| | | |
| | |
| | |
| | | |
Closes: #1050616
|
| | | |
| | |
| | |
| | | |
Closes: #959854
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Ignore pending input before confirmation prompts
See merge request apt-team/apt!375
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In the unlikely case input is not a terminal (but not in some way
assumed with command line flags) we should print the string we act on
after the prompt so that people can see what is happening rather
than having the prompt "mysteriously" hidden on terminals or
prepended to the first line of the download progress in logs.
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Pressing ENTER for too long lets it end up in the input buffer which the
confirmation prompt happily picks up and accepts as confirmation for
deleting potentially half your system or doing other silly things.
Ironically, this confirmation will also be silent in terms of output as
it is likely erased by future progress reporting.
Closes: #1082956
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
fix: `apt list --upgradable` with `--target-release`
See merge request apt-team/apt!376
|
| | | |/
| |/| |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
apt-patterns(7): add recommends
See merge request apt-team/apt!377
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This checks for the previous boundaries for path sizes; but
we also added a check for many files in a directory, limited
to 4096.
Sadly the directory check did not fail with the old code either,
it's hard to actually get it to fail correctly.
|
| | |
| |
| |
| |
| |
| | |
Add support for testing apt-ftparchive, set valgrind to quiet such
that we can check program output, and pass --error-exitcode=7 to get
an (should be unused) magic error code if it detects errors.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Wstored directory entries as a binary tree, but we did not balance it,
leading to exponential complexity on insertion and potentially
exponential levels of stack recursion in DoPrint(), causing overflows.
Simply use an std::set storing pairs of (path, package) instead,
this is very simple, and handles aspects such as ordering or the
same package appearing multiple times correctly.
Iteration becomes a bit tricky: After seeing (file1, pkg1) when
we see (file1, pkg2) we need to append pkg2 to the current line;
once we see (file2, anything), we need write out the line and
start a new one.
For memory optimization, we use a new class StringInBlock to handle
the block-managed C strings generated by Mystrdup() in a type-safe
manner. This ensures proper lifetime of objects and no accidental
conversions to std::string. This saves a significant amount of
space (a pair of std::string is 64-byte large; a pair of pointers
is 16 byte large, a 48 byte saving per entry); reproducing the Contents
file of Ubuntu 24.10, using straight-forward std::string resulted in
GB of memory usage, whereas the C-style string only uses 1.35 GB.
As a side effect of the patch we also remove arbitrary 1024-byte
buffer sizes. There also is a change in output: The package names
are now sorted alphabetically, instead of being in visit order.
LP: #2083697
|
| |/
|
|
|
|
|
|
|
| |
Add a safety check to ensure that the block were are allocating
actually fits the string we want to write. If it doesn't, abort
the program.
While we are here, bump the buffer size from 40 KiB to 4 MiB,
because why bother with smaller buffers.
|
| |
|
|
| |
Closes: #1080210
|
| |\
| |
| |
| |
| | |
Implement 'Pin: source-version <foo>'
See merge request apt-team/apt!372
|
| | |
| |
| |
| | |
As wondered about by Paride some minutes ago.
|
| |\ \
| |/
|/|
| |
| | |
Fix compilation error with clang/libc++ 18
See merge request apt-team/apt!371
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Do not return error if `Signed-By` value in source list is empty
See merge request apt-team/apt!364
|
| | |
| |
| |
| | |
Signed-off-by: Aristo Chen <aristo.chen@canonical.com>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Basically this boils down to checking that the priority of the
source candidate candidate is higher or equal than the priority
of the package's candidate that is being under consideration.
It stands to reason if we maybe we should actually calculate a
source candidate version; this will look similar but may perhaps
perform slightly different.
|
| |\ \
| | |
| | |
| | |
| | | |
Update Catalan translation
See merge request apt-team/apt!369
|
| | | | |
|
| |/ / |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Only revoke weak RSA keys now, add 'next' and 'future' levels
See merge request apt-team/apt!365
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Algorithms not in the next level give a warning, algorithms
in not in the future level introduce an audit message for
the --audit flag.
next: >=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512
future: >=rsa3072,ed25519,ed448
LP: #2073126
|
| | | |
| | |
| | |
| | | |
This checks whether a public key algorithm is asserted.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
|/|
| |
| | |
More code but nicer to read
|
| | |
| |
| |
| | |
Closes: #1075975
|
| | |
| |
| |
| | |
Closes: #1075875
|
| | |
| |
| |
| | |
Closes: #1075874
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The option is supported by the command (as this is done by a bit more
low level code), but the command line parsing did not expect them to
be used for the apt show & list command, so that it would report error.
As such, a workaround for this issue is to use:
-o APT::Snapshot=BANANA
instead of e.g.
-S BANANA
Closes: #1075819
|
| |\ \
| |/
|/|
| |
| | |
Show installed version (not candidate version) while removing a package
See merge request apt-team/apt!362
|
| |/
|
|
|
| |
Showing a package version which was never installed in removals is
confusing.
|
| | |
|
| |\
| |
| |
| |
| | |
Fixes for the Obsolete handling
See merge request apt-team/apt!361
|
| | |
| |
| |
| | |
Run clang-format
|
| | |
| |
| |
| |
| | |
If we are not upgraded, we should continue to keep the installed
package installed if possible.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
This makes more sense, as all package versions are obsolete that
are not the candidate, usually.
Pay special attention to no-strict-pinning: If we don't have
strict pinning, a package without a candidate version may still
be non-obsolete if the latest version is not obsolete.
Likewise, in no-strict-pinning any later source version that exists
will cause the package to be considered obsolete, rather than just
candidates.
|