apt/test, branch 1.9.4Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.9.42019-09-19T09:11:18ZFix use of GTest to adjust for GTest 1.92019-09-19T09:11:18ZJulian Andres Klodejulian.klode@canonical.com2019-09-19T09:02:44Zurn:sha1:25006573002971500d1501331716e9ca348f815f
GTest 1.9 uses a variable defined in the parent directory, thus
failing to configure. Configure the project in the parent directory
instead.
Pass --abort-after=1 to dpkg when using --force-depends2019-09-19T08:37:55ZJulian Andres Klodejulian.klode@canonical.com2019-09-19T08:16:26Zurn:sha1:8a54113d450140bd6b158cb05473cacca859a54d
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
Add ?virtual pattern2019-08-15T18:21:34ZJulian Andres Klodejulian.klode@canonical.com2019-08-15T11:40:31Zurn:sha1:c94b507b92b3d833761f3e416d4d5bba709bf87f
This matches any package that does not have versions.
Add the ?exact-name pattern2019-08-15T18:21:34ZJulian Andres Klodejulian.klode@canonical.com2019-08-15T11:36:04Zurn:sha1:af674d82d5cd36e22223ec49675d32adad07e0a9
The ?exact-name pattern matches the name exactly, there is
no substring matching going on, or any regular expression
or fnmatch magic.
Add ?essential pattern2019-08-15T18:21:34ZJulian Andres Klodejulian.klode@canonical.com2019-08-15T11:35:01Zurn:sha1:08762e0e4e2923360339eeb4d8ed26a00d7f1de5
This matches all packages where at least one of the versions
is marked essential; or well, whenver apt considers a package
essential.
Add ?broken pattern2019-08-15T18:21:34ZJulian Andres Klodejulian.klode@canonical.com2019-08-15T11:32:54Zurn:sha1:9282c9094ab3e77cebe90e97b2f9a5fc21463e2f
This matches all packages that have broken dependencies in the
installed version or the version selected for install.
Add ?config-files and ?installed patterns2019-08-15T18:21:34ZJulian Andres Klodejulian.klode@canonical.com2019-08-15T11:31:30Zurn:sha1:a3e9ab661b2d670f7d0da53a5f56c52af0763c5b
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.
Add ?obsolete and ?upgradable patterns2019-08-15T18:21:34ZJulian Andres Klodejulian.klode@canonical.com2019-08-15T11:23:55Zurn:sha1:89790c11799c4144e37a6a1f0dbe0f6fff89ea89
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.
Add ?automatic and ?garbage patterns2019-08-15T18:21:34ZJulian Andres Klodejulian.klode@canonical.com2019-08-15T11:12:43Zurn:sha1:083e72a5939d33dc1fd7596aa441a9982332f776
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.
Add patterns for the existing CacheFilter::Matcher classes2019-08-15T18:21:34ZJulian Andres Klodejulian.klode@canonical.com2019-08-15T10:50:22Zurn:sha1:c64a85dd7524546864603b955f601bf64c9a4bcf
This implements the basic logic patterns:
?and ?false ?not ?or ?true
and the basic package patterns:
?architecture ?name ?x-name-fnmatch