| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This is pure syntactic sugar - ?narrow does not exist in the
abstract syntax.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
README.md: fix dead anonscm link
See merge request apt-team/apt!78
|
| |
| |
| |
| | |
https://anonscm.debian.org/git/apt/apt.git/tree/doc/style.txt is not available
anymore.
|
|\ \
| |/
|/|
| |
| | |
Search in all available description translations
See merge request apt-team/apt!79
|
|/
|
|
|
|
|
|
|
|
|
|
| |
When multiple translations of package descriptions are available,
perform search in all of them. It allows using search patterns in
any of the configured languages.
Previously, only the first available translation was searched. As
the result, patterns in e.g. English never matched packages which
had their descriptions translated into local language.
Closes: #490000
|
|
|
|
|
|
|
| |
We recently made info an alias for show, but we did not change the
command-line parser to work around it.
LP: #1843812
|
| |
|
|
|
|
|
|
| |
GTest 1.9 uses a variable defined in the parent directory, thus
failing to configure. Configure the project in the parent directory
instead.
|
|
|
|
|
|
|
|
|
|
| |
Using --force-depends causes dpkg to continue removing packages
a package depends upon even if that package fails to be removed,
because dpkg turns off all sanity checks. So we gotta tell dpkg
to stop immediately if there's an error removing stuff.
Closes: #935910
LP: #1844634
|
|
|
|
|
| |
This should probably make those functions thread-safe, which
might be useful for some external users.
|
|
|
|
|
|
|
|
| |
Commit 1d9e29c9e2a5591b42a99a721b901fc003ed9149 added support
for suffixes to to intervals, but did not adjust the code to
actually support them by replacing -eq with =.
LP: #1840995
|
| |
|
|
|
|
|
|
| |
In C++, this warns about not returning in a function not returning
void, which is undefined behavior and causes weird crashes. Make it
an error.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Package patterns
See merge request apt-team/apt!74
|
| |
| |
| |
| |
| | |
Only disallow ,() and on the start of a word also ~ and ?. Make
sure to include \0 as disallowed.
|
| | |
|
| |
| |
| |
| | |
This matches any package that does not have versions.
|
| |
| |
| |
| |
| |
| | |
The ?exact-name pattern matches the name exactly, there is
no substring matching going on, or any regular expression
or fnmatch magic.
|
| |
| |
| |
| |
| |
| | |
This matches all packages where at least one of the versions
is marked essential; or well, whenver apt considers a package
essential.
|
| |
| |
| |
| |
| | |
This matches all packages that have broken dependencies in the
installed version or the version selected for install.
|
| |
| |
| |
| |
| |
| | |
These two are mutually exclusive states of installed-ness. And
?installed package is fully unpacked and configured; a ?config-files
package only has config files left.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These match packages that have no version in a repository, or
where an upgrade is available. Notably,
?and(?obsolete,?upgradable) == ?false
because an upgradable package is by definition not obsolete.
|
| |
| |
| |
| |
| |
| | |
These patterns allow you to identify automatically installed
packages, as well as automatically installed packages that are
no longer reachable from the manually installed ones.
|
| |
| |
| |
| |
| |
| |
| | |
This implements the basic logic patterns:
?and ?false ?not ?or ?true
and the basic package patterns:
?architecture ?name ?x-name-fnmatch
|
| |
| |
| |
| |
| | |
This adds a transformation from parse tree into a CacheFilter and
connects it with cachesets and the apt list command.
|
| |
| |
| |
| |
| | |
This does not describe much yet, as there's not much to talk
about.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce a parser for patterns that generates a parse tree. The
language understood by the parser is:
pattern = '?'TERM
| '?'TERM '(' pattern (',' pattern)* ','? ')'
| WORD
| QUOTED-WORD
TERM = [0-9a-zA-Z-]
WORD = [0-9a-ZA-Z-.*^$\[\]_\\]
QUOTED_WORD = "..." # you know what I mean
This language is context free, which is a massive simplification
from aptitude's language, where ?foo(bar) could have two different
meanings depending on whether ?foo takes an argument or not.
|
|\
| |
| |
| |
| | |
Fix segfault in pkgAcquire::Enqueue() with Acquire::Queue-Mode=access
See merge request apt-team/apt!73
|
| |
| |
| |
| |
| |
| | |
Unfortunately for us, apt update with Acquire::Queue-Mode=access
does not always crash on a real system, so run the whole thing
in valgrind.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In commit 79b1a8298, QueueName() was changed, amongst other things,
to exit early when the queue mode was single access, as single
access does not need any fancy queue name. The exit became too
early though, as Config was not initialized anymore, but the
caller was relying on it.
Fix QueueName() to always initialize Config and in Enqueue()
initialize Config with a nullptr, so if this regresses it's
guaranteed to fail harder. Also add a test case - this is
very simple, but the first and only test case for access
queue mode.
Regression-Of: 79b1a82983e737e74359bc306d9edb357c5bdd46
LP: #1839714
|
| |
|
|\
| |
| |
| |
| | |
Improve locking messaging - pid and name, "do not remove lock file"
See merge request apt-team/apt!68
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We want to tell users which process is holding the lock so they
can easily understand what's going on, and we want to advise
users not to remove the lock file, because ugh, that's bad.
Re-initalize the flock structure, in case it got mangled by
previous fcntl call.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Also in old changelogs, but nothing really user visible
like error messages or alike so barely noteworthy.
Reported-By: codespell
Gbp-Dch: Ignore
|
| |
| |
| |
| | |
Reported-By: cppcheck
|
| |
| |
| |
| |
| |
| |
| |
| | |
The error messages say only which package it was trying to provide, but
not which package & version tried it which can be misleading as to which
package (version) is the offender.
References: #930256
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Work like applying patches via rred can be performed by many concurrent
rred processes, but we can't just spawn new ones forever: We limit us to
the number of CPUs which can drive them and reuse existing ones if they
have nothing to do at the moment.
The problem arises if we have reached the limit of queues and all of
them are busy which is more likely to happen on "slow" machines with few
CPUs. In this case we opted for random distribution, but that can result
in many big files (e.g. Contents) being added to one queue while the
others get none or only small files.
Ideally we would ask the methods how much they still have to do, but
they only know that for the current item, not for all items in the
queue, so we use the filesize of the expected result.
|
|\ \
| |/
|/|
| |
| | |
Change a pronoun in the readme from `he` to `they`
See merge request apt-team/apt!69
|
|/
|
|
|
|
|
|
| |
Using gender neutral language in your documentation is a inclusion win!
Here's some documents describing more context here:
- https://en.wikipedia.org/wiki/Singular_they#Trend_toward_gender-neutral_language
- https://open.buffer.com/inclusive-language-tech
- https://www.grammarly.com/blog/use-the-singular-they/
|
| |
|
| |
|