apt/apt-pkg/deb, branch 1.1.6Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.62015-12-14T01:26:23Zshow a more descriptive error for weak Release files2015-12-14T01:26:23ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-14T01:18:25Zurn:sha1:bd4a8f51649ee37291c6e07310104a94f4f5fbed
If we can't work with the hashes we parsed from the Release file we
display now an error message if the Release file includes only weak
hashes instead of downloading the indexes and failing to verify them
with "Hash Sum mismatch" even through the hashes didn't mismatch (they
were just weak).
If for some (unlikely) reason we have got weak hashes only for
individual targets we will show a warning to this effect (again, befor
downloading and failing the index itself).
Closes: 806459
Convert package names from Packages files to lower case2015-12-11T13:48:21ZJulian Andres Klodejak@debian.org2015-12-11T13:27:56Zurn:sha1:fffa3b57b4f2334dff3b9bef5401521307e1a721
dpkg does that when reading package files, so we should do
the same. This only deals with parsing names from binary
package paragraphs, it does not look at source package names
and/or the list of binaries in a dsc file.
Closes: #807012
Avoid overflow when summing up file sizes2015-12-07T13:44:15ZJulian Andres Klodejak@debian.org2015-12-07T13:42:25Zurn:sha1:5a97834817dd43b7833881f38f512a9f2fdac8a9
We need to pass 0llu instead of 0 as the init value, otherwise
std::accumulate will calculate with ints.
Reported-by: Raphaël Hertzog
require explicit paths to dsc/control as we do for deb files2015-12-01T13:26:05ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-01T13:09:23Zurn:sha1:f359b7e8c03884cd9f097d4b3ff8b8b8be8053ba
Otherwise a user is subject to unexpected content-injection depending on
which directory she happens to start apt in. This also cleans up the code
requiring less implementation details in build-dep which is always good.
Technically, this is an ABI break as we override virtual methods, but
that they weren't overridden was a mistake resulting in pure classes,
which shouldn't be pure, so they were unusable – and as they are new in
1.1 nobody is using them yet (and hopefully ever as they are borderline
implementation details).
Closes: 806693
add messages to our deprecation warnings in libapt2015-11-27T14:40:47ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-27T14:40:47Zurn:sha1:5dd00edbcf702cac1ea22392796c65881a8ef6f9
Git-Dch: Ignore
review of new/changed translatable program strings2015-11-21T17:04:29ZJustin B Ryejustin.byam.rye@gmail.com2015-11-21T16:50:06Zurn:sha1:d04e44ac8177fc5b70ae0189bb5e437c2502f910
Reference mail:
https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
apply various suggestions made by cppcheck2015-11-05T11:21:33ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-04T20:08:55Zurn:sha1:258b9e512c4001e806c5c0966acecd3d742ec6e9
Reported-By: cppcheck
Git-Dch: Ignore
do not use read() returned value unconditionally2015-11-05T11:21:33ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-04T17:01:35Zurn:sha1:9fb4e6510faaa9c84b88d4cb567bf3deebf8e0b7
A slightly unlikely bug, but lets fix it while slightly reworking this
whole function to be slightly saner to look at, even if still not good.
Git-Dch: Ignore
wrap 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
ignore newlines in dpkg-deb control output for installing debs2015-11-04T17:42:28ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-30T22:16:01Zurn:sha1:2f91076de326a0dee067659381a9c4cf745f0efe
Leading or trailing newlines can be confusing for our parser as it
expects two newlines to start/stop a new stanza. To solve this the lines
we wanna add are printed first, ignore any leading newlines and then add
the stanza as provided by dpkg-deb with or without trailing newlines as
the parser will look at the first stanza only anyway and removing
trailing newlines is considerably harder to do.
Closes: 802553