<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-apt-cache-remapping, branch 2.2.1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.2.1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.2.1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2017-12-24T09:31:29Z</updated>
<entry>
<title>do not remap current files if nullptrs in cache generation</title>
<updated>2017-12-24T09:31:29Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-12-24T09:31:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5ba048a475cfd728906875327ddceed4614a1c9d'/>
<id>urn:sha1:5ba048a475cfd728906875327ddceed4614a1c9d</id>
<content type='text'>
If the cache needs to grow to make room to insert volatile files like
deb files into the cache we were remapping null-pointers making them
non-null-pointers in the process causing trouble later on.

Only the current Releasefile pointer can currently legally be a
nullpointer as volatile files have no release file they belong to, but
for safety the pointer to the current Packages file is equally guarded.

The option APT::Cache-Start can be used to workaround this problem.

Reported-By: Mattia Rizzolo on IRC
</content>
</entry>
</feed>
