apt/apt-pkg/pkgcachegen.cc, branch 1.1.exp11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.exp112015-08-27T09:27:44Zignore AllowMem parameter in cache generation2015-08-27T09:27:44ZDavid Kalnischkiesdavid@kalnischkies.de2015-08-22T09:56:38Zurn:sha1:c4171975018eca191426dc1466b61a967e08921f
The parameter name suggests that it should forbid the building of the
entire cache in memory, but this isn't how it was previously and as
AllowMem is false by default it actually prevents previous usecases from
working like being root and configuring apt to build no caches at all.
This should be fixed at some point to actually work, but that is hard to
pull off as it means switching the default and some callers (including
apt itself) actually did call it explicitly with false in certain
cases for no apparent reason (at least now where it is common to have
enough memory to throw at every problem and even if not is a slow apt
usally better than an apt erroring out).
Closes: 796459
Fix more instances of missing remapping handling2015-08-27T09:05:28ZJulian Andres Klodejak@debian.org2015-08-26T21:55:13Zurn:sha1:a6deb7a0ea70e945dfd750d1bdc1b783b187873e
After fixing Bug#796999, we noticed that there were
some more instances of iterators which had no associated
Dynamic object, causing them to not be updated when
the cache was remapped.
This happened in two places: In NewPackage() and in
NewProvidesAllArch().
Gbp-Dch: ignore
pkgcachegen: Account for remapping when parsing depends from NewPackage2015-08-27T09:05:12ZJulian Andres Klodejak@debian.org2015-08-26T21:26:54Zurn:sha1:05c001c8dbcf327a77f1e4183900cad9b321d3f9
In both the Ver and Dep variables, we need to account for remapping,
as otherwise we would still reference the old bug.
Reproduction environment:
* An i386 system with amd64 foreign architecture
* A sources.list with
deb http://snapshot.debian.org/archive/debian/20150826T102846Z/ unstable main
deb http://snapshot.debian.org/archive/debian/20150826T102846Z/ experimental main
Thanks: Jakub Wilk for the bug report and the backtraces
Closes: #796999
Cleanup includes after running iwyu2015-08-17T10:01:45ZMichael Vogtmvo@debian.org2015-08-17T10:01:45Zurn:sha1:88a8975f156e452d9f3ebe76822b236e8962ebbaDeprecate SPtrArray<T> and convert everyone to unique_ptr<T[]>2015-08-13T09:31:00ZJulian Andres Klodejak@debian.org2015-08-13T09:28:32Zurn:sha1:98cc7fd2c1d397623960baf69ae3cec04a87a23e
More standardization
Mark SPtr as deprecated, and convert users to std::unique_ptr2015-08-13T09:30:59ZJulian Andres Klodejak@debian.org2015-08-13T08:49:31Zurn:sha1:6c413b188618b9fcb5368b60971dfa5d45b3cd74
Switch to std::unique_ptr, as this is safer than SPtr.
Drop C++11 elements from headers2015-08-11T11:59:15ZJulian Andres Klodejak@debian.org2015-08-11T09:49:21Zurn:sha1:350d30d24fee9a1aa5fedc7a30e7416999653417drop obsolete explicit :none handling in pkgCacheGen2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-20T11:34:25Zurn:sha1:cc480836c739e36dc0c741fa333248c0a8150ec7
We archieve the same without the special handling now, so drop this code.
Makes supporting this abdomination a little longer bearable as well.
Git-Dch: Ignore
eliminate dead file-provides code in cache generation2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-20T08:33:07Zurn:sha1:1d3eea5caf65aacd7f112d14030a0499f32b9c75
The code was never active in production, it just sits there collecting
dust and given that it is never tested probably doesn't even work
anymore the way it was supposed to be (whatever that was exactly in the
first place). So just remove it before I have to "fix" it again next
time.
Git-Dch: Ignore
elimate duplicated code in pkgIndexFile subclasses2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-20T08:17:29Zurn:sha1:c9443c01208377f0cba9706412ea3a98ad97b56d
Trade deduplication of code for a bunch of new virtuals, so it is
actually visible how the different indexes behave cleaning up the
interface at large in the process.
Git-Dch: Ignore