apt/test/integration/test-apt-cache-remapping, branch 2.7.11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.7.112022-09-02T14:55:45ZAllow apt to run if no dpkg/status file exists2022-09-02T14:55:45ZDavid Kalnischkiesdavid@kalnischkies.de2022-09-01T13:14:52Zurn:sha1:f52c1ce9b31befb71016a20759b96b4946034fcb
Not having a dpkg/status file used to be a hard error which from a
boostrap perspective is suspect as in the beginning, there is no
status so you would need to touch it into existence.
We make a difference between factual non-existence and inaccessibility
to catch mistakes in which the file is not readable for some reason,
the testcase test-bug-254770-segfault-if-cache-not-buildable is an
example of this.
Note that apt has already figured out at this point that this is a
Debian-like system which should have a dpkg/status file. This change
does not effect the auto-detection and is not supposed to.
do not remap current files if nullptrs in cache generation2017-12-24T09:31:29ZDavid Kalnischkiesdavid@kalnischkies.de2017-12-24T09:31:29Zurn:sha1:5ba048a475cfd728906875327ddceed4614a1c9d
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