<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-apt-patterns, branch 2.7.11</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.7.11</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.7.11'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2023-01-13T11:27:55Z</updated>
<entry>
<title>make ?installed pattern match installed version only when narrowed</title>
<updated>2023-01-13T11:27:55Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2023-01-13T11:23:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=73f7408f6d164e595fb2e3a3df856a8f8168fcb9'/>
<id>urn:sha1:73f7408f6d164e595fb2e3a3df856a8f8168fcb9</id>
<content type='text'>
This is the correct behavior, but it was overlooked when aptitude
patterns where ported. I remember wondering about this, but I checked
the aptitude code and saw a check that CurrentVer != 0 or something
and then apparently did not notice another implementation for version
matching.
</content>
</entry>
<entry>
<title>Avoid dealing with a fake dpkg stanza in the tests</title>
<updated>2022-09-02T14:55:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2022-08-31T19:49:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3498fbedafbf30e5c91deeaefa6a60d1e387593a'/>
<id>urn:sha1:3498fbedafbf30e5c91deeaefa6a60d1e387593a</id>
<content type='text'>
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).
</content>
</entry>
<entry>
<title>add pattern to select packages by codename (closes: #1002646)</title>
<updated>2021-12-26T21:04:21Z</updated>
<author>
<name>Johannes Schauer Marin Rodrigues</name>
<email>josch@mister-muffin.de</email>
</author>
<published>2021-12-26T15:29:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ed282548bc4b8f96ac531c9f73b42d968eadea98'/>
<id>urn:sha1:ed282548bc4b8f96ac531c9f73b42d968eadea98</id>
<content type='text'>
</content>
</entry>
<entry>
<title>add pattern to select packages by priority (closes: #989558)</title>
<updated>2021-10-04T21:39:04Z</updated>
<author>
<name>Johannes Schauer Marin Rodrigues</name>
<email>josch@mister-muffin.de</email>
</author>
<published>2021-09-07T18:30:21Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=cdfae5a9624e7283d372fce261efd018841d21cb'/>
<id>urn:sha1:cdfae5a9624e7283d372fce261efd018841d21cb</id>
<content type='text'>
</content>
</entry>
<entry>
<title>apt list: Fix behavior of regex vs fnmatch vs wildcards</title>
<updated>2020-05-04T11:08:33Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-05-04T11:08:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c4f85bcb8bee1b5e647c7e629f616cffc7d12bbc'/>
<id>urn:sha1:c4f85bcb8bee1b5e647c7e629f616cffc7d12bbc</id>
<content type='text'>
Previously (and still in cacheset), patterns where only allowed to
start with ? or ~, which ignores the fact that a pattern might just
as well start with a negation, such a !~nfoo.

Also, we ignored the --regex flag if it looked like this, which
was somewhat bad.

Let's change this all:

* If --regex is given, arguments are always interpreted as regex
* If it is a valid package wildcard (name or * characters), then
  it will be interpreted as a wildcard - this set of characters is
  free from meaningful overlap with patterns.
* Otherwise, the argument is interpreted as a pattern.

For a future version, we need to adapt parsing for cacheset and
list to use a common parser, to avoid differences in their
interpretation. Likely, this code will go into the pattern parser,
such that it generates a pattern given a valid fnmatch argument
for example.
</content>
</entry>
<entry>
<title>Reinstate * wildcards</title>
<updated>2020-05-04T10:48:56Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-05-04T10:23:50Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=75f59b16312523ab3deb995c48e8c8ae07586c23'/>
<id>urn:sha1:75f59b16312523ab3deb995c48e8c8ae07586c23</id>
<content type='text'>
Reinstate * wildcards as they are safe to use, but do not allow any
other special characters such as ? or [].

Notably, ? would overlap with patterns, and [] might overlap with
future pattern extensions (alternative bracketing style), it's also
hard to explain.

Closes: #953531
LP: #1872200
</content>
</entry>
<entry>
<title>Don't crash pattern matching sections if pkg has no section</title>
<updated>2020-03-10T09:57:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2020-03-10T09:46:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=429effb963fba7529b8ff57d6b0474916d4fed69'/>
<id>urn:sha1:429effb963fba7529b8ff57d6b0474916d4fed69</id>
<content type='text'>
Packages from third-party sources do not always follow the established
patterns of more properly maintained archives. In that case it was a
driver package for a scanner&amp;printer device which has only a minimum of
info attached, but also minimal non-installed packages do not include
sections, so we really shouldn't assume their availability.
</content>
</entry>
<entry>
<title>apt(8): Disable regular expressions and fnmatch</title>
<updated>2020-01-15T21:19:17Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-15T21:01:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=21cb4a9e513ccb6f376fbcaf67957c4851cbbe32'/>
<id>urn:sha1:21cb4a9e513ccb6f376fbcaf67957c4851cbbe32</id>
<content type='text'>
This is the first step. Next step will be to add warnings to
apt-get and then remove support there as well.
</content>
</entry>
<entry>
<title>patterns: Add ?section</title>
<updated>2019-11-26T11:01:42Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-11-26T11:01:42Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a93b4443c18ee211691f7b336b161fea7d1df699'/>
<id>urn:sha1:a93b4443c18ee211691f7b336b161fea7d1df699</id>
<content type='text'>
</content>
</entry>
<entry>
<title>patterns: Add ?all-versions</title>
<updated>2019-11-26T10:56:28Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-11-26T10:56:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=96f795bce665a1907b885bd2d57d6ab22b0a4199'/>
<id>urn:sha1:96f795bce665a1907b885bd2d57d6ab22b0a4199</id>
<content type='text'>
</content>
</entry>
</feed>
