<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg, branch 1.9.8</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.9.8</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.9.8'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2020-01-27T12:23:53Z</updated>
<entry>
<title>NewGroup: Create GrpIterator after allocation (fix segfault)</title>
<updated>2020-01-27T12:23:53Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-27T12:23:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=cafebee579f6a9399fbfcc86e2c89a479aee465e'/>
<id>urn:sha1:cafebee579f6a9399fbfcc86e2c89a479aee465e</id>
<content type='text'>
NewGroup created a GrpIterator and then called WriteStringInMap()
which might remap the cache, causing the iterator to go invalid.

Avoid this simply by creating the iterator later on.
</content>
</entry>
<entry>
<title>mmap: Do not look for empty pool unless we need to</title>
<updated>2020-01-17T16:19:56Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-17T16:19:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8dc1d3c4662e9009ed56483fd4254ee1154b6e23'/>
<id>urn:sha1:8dc1d3c4662e9009ed56483fd4254ee1154b6e23</id>
<content type='text'>
Given that we have a maximum of 12 pools, and much more
items to insert, it does not make sense to have two branches
in the hot path.

Move the search for an empty pool into the unlikely case
that no matching pool has been created yet - a condition
that is guaranteed to only happens up to 12 times.
</content>
</entry>
<entry>
<title>pkgcache.cc: Mix PACKAGE_VERSION into the cache hash</title>
<updated>2020-01-16T17:21:20Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-16T17:19:34Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=25353dc6646e5b9fff55059a5c85183589cf472d'/>
<id>urn:sha1:25353dc6646e5b9fff55059a5c85183589cf472d</id>
<content type='text'>
This ensures that caches build with one version can't be
opened with another, which makes sense. It's a temporary
approach until we can replace major:minor fields with
a version string.

For example, this would have prevented 1.9.7 from using
broken caches from 1.9.6.
</content>
</entry>
<entry>
<title>NewProvidesAllArch: Check if group is empty before using it</title>
<updated>2020-01-16T10:10:47Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-16T09:53:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ea4b7921b7e3eadb42be1deab5f343dbba8f29df'/>
<id>urn:sha1:ea4b7921b7e3eadb42be1deab5f343dbba8f29df</id>
<content type='text'>
APT 1.9.6 introduced empty groups by making use of groups to
deduplicate package names. This is not normally a problem, but
here we assumed that every group has at least one package.

This caused a problem because automake was providing automake-1.16
while having the source package automake-1.16. So we found the
automake-1.16 group, iterated over its empty package list, trying
to store the provides (which hence never happened).

LP: #1859952
</content>
</entry>
<entry>
<title>Merge branch 'pu/apt-regex-cli' into 'master'</title>
<updated>2020-01-15T22:02:32Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2020-01-15T22:02:32Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=087c97b7959acb1f9417b0b02be58709666476dc'/>
<id>urn:sha1:087c97b7959acb1f9417b0b02be58709666476dc</id>
<content type='text'>
apt(8): Disable regular expressions and fnmatch

See merge request apt-team/apt!95</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>netrc: Add warning when ignoring entries for unencrypted protocols</title>
<updated>2020-01-15T21:07:25Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-12-04T12:58:38Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a9916c3faa2b8c6fa288599efec65868d050b0ef'/>
<id>urn:sha1:a9916c3faa2b8c6fa288599efec65868d050b0ef</id>
<content type='text'>
Commit 93f33052de84e9aeaf19c92291d043dad2665bbd restricted auth.conf
entries to only apply to https by default, but this was silent - there
was no information why http sources with auth.conf entries suddenly
started failing. Add such information, and extend test case to cover
it.
</content>
</entry>
<entry>
<title>Remove includes of (md5|sha1|sha2).h headers</title>
<updated>2020-01-14T12:10:36Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-07T20:21:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8c1a37e12790a23f3b132899485e011f9134b483'/>
<id>urn:sha1:8c1a37e12790a23f3b132899485e011f9134b483</id>
<content type='text'>
Remove it everywhere, except where it is still needed.
</content>
</entry>
<entry>
<title>Deprecate the Summation classes and mark them for removal</title>
<updated>2020-01-14T12:10:36Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-01-07T20:05:27Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5872a2e7dd308e49a063a20da1beb40a32d1e9b2'/>
<id>urn:sha1:5872a2e7dd308e49a063a20da1beb40a32d1e9b2</id>
<content type='text'>
</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>
</feed>
