apt/apt-pkg/edsp, branch 1.2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.22015-11-04T17:42:28Zwrap every unlink call to check for != /dev/null2015-11-04T17:42:28ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-02T17:49:52Zurn:sha1:ce1f3a2c616b86da657c1c796efa5f4d18c30c39
Unlinking /dev/null is bad, we shouldn't do that. Also, we should print
at least a warning if we tried to unlink a file but didn't manage to
pull it of (ignoring the case were the file is /dev/null or doesn't
exist in the first place).
This got triggered by a relatively unlikely to cause problem in
pkgAcquire::Worker::PrepareFiles which would while temporary
uncompressed files (which are set to keep compressed) figure out that to
files are the same and prepare for sharing by deleting them. Bad move.
That also shows why not printing a warning is a bad idea as this hide
the error for in non-root test runs.
Git-Dch: Ignore
sanify API to get 'the' candidate version2015-11-04T17:04:05ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-30T15:34:25Zurn:sha1:294a80209a0c6ea617a14fb2ae650d4fd329eab5
This was discussed a while ago on #debian-apt and now that I see myself
making this mistake lets bite the bullet and fix it in the easy way out
version: Using a new name which fits with a similar named setter and
deprecate the old method instead of 'hostily' changing API.
Closes: #803471
use a less generic special trigger filename for stdin2015-09-14T13:22:18ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-10T16:46:05Zurn:sha1:7f58427b9584686f80cd5eccfdd02c1ace75518a
Git-Dch: Ignore
implement autobit and pinning in EDSP solver 'apt'2015-09-14T13:22:18ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-08T20:14:11Zurn:sha1:188a6fcf4f13df1fd362a0aff27a23493ddd1ec5
The parser creates a preferences as well as an extended states file
based on the EDSP scenario file, which isn't the most efficient way of
dealing with this as thes text files have to be parsed again by another
layer of the code, but it needs the least changes and works good enough
for now. The 'apt' solver is in the end just a test solver like dump.
Cleanup includes after running iwyu2015-08-17T10:01:45ZMichael Vogtmvo@debian.org2015-08-17T10:01:45Zurn:sha1:88a8975f156e452d9f3ebe76822b236e8962ebbaAnnotate more methods with APT_OVERRIDE2015-08-11T13:58:42ZJulian Andres Klodejak@debian.org2015-08-11T13:58:03Zurn:sha1:6d7122b5356c0b4d8f51aafdfc1c232392fca695
Gbp-Dch: ignore
Reported-By: g++ -Wsuggest-override
Thanks: g++ -Wsuggest-override
parse packages from all architectures into the cache2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-20T10:32:46Zurn:sha1:7f8c0eed6983db7b8959f1498fc8bc80c98d719e
Now that we can dynamically create dependencies and provides as needed
rather than requiring to know with which architectures we will deal
before running we can allow the listparser to parse all records rather
than skipping records of "unknown" architectures.
This can e.g. happen if a user has foreign architecture packages in his
status file without dpkg knowing about this architecture (or apt
configured in this way).
A sideeffect is that now arch:all packages are (correctly) recorded as
available from any Packages file, not just from the native one – which
has its downsides for the resolver as mixed-arch source packages can
appear in different architectures at different times, but that is the
problem of the resolver and dealing with it in the parser is at best a
hack (and also depends on a helpful repository).
Another sideeffect is that his allows :none packages to appear in
Packages files again as we don't do any kind of checks now, but given
that they aren't really supported (anymore) by anyone we can live with
that.
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
add volatile sources support in libapt-pkg2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-18T16:03:54Zurn:sha1:5465192b9aeb1ccea778950ccf2d1b7b32f2cd91
Sources are usually defined in sources.list (and co) and are pretty
stable, but once in a while a frontend might want to add an additional
"source" like a local .deb file to install this package (No support for
'real' sources being added this way as this is a multistep process).
We had a hack in place to allow apt-get and apt to pull this of for a
short while now, but other frontends are either left in the cold by this
and/or the code for it looks dirty with FIXMEs plastering it and has on
top of this also some problems (like including these 'volatile' sources
in the srcpkgcache.bin file).
So the biggest part in this commit is actually the rewrite of the cache
generation as it is now potentially a three step process. The biggest
problem with adding support now through is that this makes a bunch of
previously mostly unusable by externs and therefore hidden classes
public, so a bit of further tuneing on this now public API is in order…
add c++11 override marker to overridden methods2015-08-10T15:27:17ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-08T22:35:40Zurn:sha1:3b3028467ceccca0b73a8f53051c0fa4de313111
C++11 adds the 'override' specifier to mark that a method is overriding
a base class method and error out if not. We hide it in the APT_OVERRIDE
macro to ensure that we keep compiling in pre-c++11 standards.
Reported-By: clang-modernize -add-override -override-macros
Git-Dch: Ignore