<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-private, branch 2.1.7</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.1.7</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.1.7'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2020-05-18T20:22:24Z</updated>
<entry>
<title>private-search: Only use V.TranslatedDescription() if good</title>
<updated>2020-05-18T20:22:24Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-05-13T22:06:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e61886cacbc5411ea027e3a3d1d5c31793ed2b71'/>
<id>urn:sha1:e61886cacbc5411ea027e3a3d1d5c31793ed2b71</id>
<content type='text'>
When we could not find a translated description, we were
pushing V.TranslatedDescription() to the vector, but that
one might not have been good either.

Add the check so we don't crash later when trying to access
it.

LP: #1877987
</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>apt(8): Wait for frontend and cache lock</title>
<updated>2020-02-26T19:36:52Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-26T19:31:03Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=93e1565796b61eb44bec39f50e09a34cbe090178'/>
<id>urn:sha1:93e1565796b61eb44bec39f50e09a34cbe090178</id>
<content type='text'>
This is a rework of !6 with additional stuff for the frontend
lock, so we can lock the frontend lock and then keep looping
over dpkg lock.
</content>
</entry>
<entry>
<title>Make map_pointer&lt;T&gt; typesafe</title>
<updated>2020-02-24T17:29:07Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-24T16:46:10Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4fad7262291a8af1415fb9a3693678bd9610f0d6'/>
<id>urn:sha1:4fad7262291a8af1415fb9a3693678bd9610f0d6</id>
<content type='text'>
Instead of just using uint32_t, which would allow you to
assign e.g. a map_pointer&lt;Version&gt; to a map_pointer&lt;Package&gt;,
use our own smarter struct that has strict type checking.

We allow creating a map_pointer from a nullptr, and we allow
comparing map_pointer to nullptr, which also deals with comparisons
against 0 which are often used, as 0 will be implictly converted
to nullptr.
</content>
</entry>
<entry>
<title>Replace map_pointer_t with map_pointer&lt;T&gt;</title>
<updated>2020-02-24T16:08:34Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-24T16:08:34Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c3587c0d9de852eca11d9bbc004095d54115eda4'/>
<id>urn:sha1:c3587c0d9de852eca11d9bbc004095d54115eda4</id>
<content type='text'>
This is a first step to a type safe cache, adding typing
information everywhere. Next, we'll replace map_pointer&lt;T&gt;
implementation with a type safe one.
</content>
</entry>
<entry>
<title>Remove code tagged APT_PKG_590, add some missing includes</title>
<updated>2020-02-18T11:48:38Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-02-18T11:48:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e8016805b87bead8eb3dff0d0559c5d9590b721b'/>
<id>urn:sha1:e8016805b87bead8eb3dff0d0559c5d9590b721b</id>
<content type='text'>
Remove all code scheduled to be removed after 5.90, and fix
files to include files they previously got from hashes.h
including more headers.
</content>
</entry>
<entry>
<title>Implement short patterns (patterns starting with ~)</title>
<updated>2020-02-03T11:55:54Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-20T13:14:49Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=fd43b1694f1382a3a47f5dc546ebe3d39fcd6e7d'/>
<id>urn:sha1:fd43b1694f1382a3a47f5dc546ebe3d39fcd6e7d</id>
<content type='text'>
Also make pattern detector in cacheset and private's list accept
such patterns. We probably should just try to parse and see if it
is a (start of a) pattern.
</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>Convert users of {MD5,SHA1,SHA256,SHA512}Summation to use Hashes</title>
<updated>2020-01-14T12:10:36Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-07T19:36:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=79de3008ebfc6b4a5dd32e9de1d19788da0b885d'/>
<id>urn:sha1:79de3008ebfc6b4a5dd32e9de1d19788da0b885d</id>
<content type='text'>
This makes use of the a function GetHashString() that returns
the specific hash string. We also need to implement another overload
of Add() for signed chars with sizes, so the existing users do not
require reinterpret_cast everywhere.
</content>
</entry>
<entry>
<title>satisfy: Fix segmentation fault when called with empty argument</title>
<updated>2019-12-06T12:48:07Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-12-06T12:46:58Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=05d1549fb65b00137b22159761462626d11bfe73'/>
<id>urn:sha1:05d1549fb65b00137b22159761462626d11bfe73</id>
<content type='text'>
apt satisfy "" caused a segmentation fault because we were iterating
over the characters, checking if the next character was the end of
the string; when it could also be the current character.

Instead, check whether the next character is before the end of
the string, rather than identical to the end.
</content>
</entry>
</feed>
