apt/cmdline, branch 1.2.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.2.12016-01-08T14:40:01Zsupport '-' and no parameter for stdin in apt-helper cat-file2016-01-08T14:40:01ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-07T23:35:39Zurn:sha1:abec2980ef1ff051be14c26097a76b6429b3b7bc
This way it works more similar to the compressor binaries, which we
can relief in this way from their job in the test framework avoiding the
need of adding e.g. liblz4-tool to the test dependencies.
keep compressed indexes in a low-cost format2016-01-08T14:40:01ZDavid Kalnischkiesdavid@kalnischkies.de2016-01-07T19:32:09Zurn:sha1:0179cfa83cf0042235eda41db7f35c420781c63e
Downloading and storing are two different operations were different
compression types can be preferred. For downloading we provide the
choice via Acquire::CompressionTypes::Order as there is a choice to
be made between download size and speed – and limited by whats available
in the repository.
Storage on the other hand has all compressions currently supported by
apt available and to reduce runtime of tools accessing these files the
compression type should be a low-cost format in terms of decompression.
apt traditionally stores its indexes uncompressed on disk, but has
options to keep them compressed. Now that apt downloads additional files
we also deal with files which simply can't be stored uncompressed as
they are just too big (like Contents for apt-file). Traditionally they
are downloaded in a low-cost format (gz) as repositories do not provide
other formats, but there might be even lower-cost formats and for
download we could introduce higher-cost in the repositories.
Downloading an entire index potentially requires recompression to
another format, so an update takes potentially longer – but big files
are usually updated via pdiffs which has to de- and re-compress anyhow
and does it on the fly anyhow, so there is no extra time needed and in
general it seems to be benefitial to invest the time in update to save
time later on file access.
apt-helper: cat-file: Add -C/--compress option2016-01-07T14:51:00ZJulian Andres Klodejak@debian.org2016-01-07T14:51:00Zurn:sha1:df46a87ab6b67019277884f7ae990af26080280d
This allows passing compressing the output. The compressor must
be a compressor name, extension, or an extension without the
leading dot.
apt-cache: stats: Show a table utilization as percentage2016-01-03T16:42:17ZJulian Andres Klodejak@debian.org2016-01-03T16:39:39Zurn:sha1:38a5b1ceeeca6ff530a2816a39bcd10d14c85d33
Gbp-Dch: ignore
apt-cache: stats: Average is over used, not all, buckets2016-01-03T16:34:50ZJulian Andres Klodejak@debian.org2016-01-03T16:34:50Zurn:sha1:6d7fc45ed4e22163bba6478c7523f4509d200c58
It does not make sense to consider empty buckets in the
average, as they do not affect the lookup performance.
apt-helper: Use CopyFile() for concatenating the files2015-12-28T10:41:04ZJulian Andres Klodejak@debian.org2015-12-28T10:41:04Zurn:sha1:ff2717e8c6a7633bbd38be95b2d30615802b6679
There's no point in keeping using yet another read-then-write
loop.
Gbp-Dch: ignore
apt-helper: Check that we can open stdout2015-12-26T22:27:15ZJulian Andres Klodejak@debian.org2015-12-26T22:26:55Zurn:sha1:cb7fce24492ff6e0b7df0f33e2ac47970b4281dd
Gbp-Dch: ignore
apt-helper: Add a cat-file command for concatening files2015-12-26T20:48:14ZJulian Andres Klodejak@debian.org2015-12-26T20:45:32Zurn:sha1:2658e1c5487d0bb9c6223cf149a48f47e8d10b4d
This can automatically handle compressed files and is useful
for stuff like apt-file.
avoid triggering gpg2 migration in apt-key2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-18T11:35:43Zurn:sha1:803491dc568d2994745c3c4359f68053f7261658
The presents (even of an empty) secring.gpg is indication enough for
gpg2 to tigger the migration code which not only produces a bunch of
output on each apt-key call, but also takes a while to complete as an
agent needs to be started and all that.
We workaround the first part by forcing the migration to happen always
in a call we forced into silence, but that leaves us with an agent to
start all the time – with a bit of reordering we can make it so that we
do not explicitly create the secring, but let gpg create it if needed,
which prevents the migration from being triggered and we have at least a
bit less of a need for an agent. Changes - even to public only keyrings
- still require one, but such actions are infrequent in comparison to
verification calls, so that should be a net improvement.
avoid evaluating shell in paths used in apt-key2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-17T16:41:11Zurn:sha1:bc8f83a5afd858206efe518c31bbb1ac948a39a3
apt-key creates internally a script (since ~1.1) which it will call to
avoid dealing with an array of different options in the code itself, but
while writing this script it wraps the values in "", which will cause
the shell to evaluate its content upon execution.
To make 'use' of this either set a absolute gpg command or TMPDIR to
something as interesting as:
"/tmp/This is fü\$\$ing cràzy, \$(man man | head -n1 | cut -d' ' -f1)\$!"
If such paths can be encountered in reality is a different question…