apt/apt-pkg, branch 1.1.5

pkgcache: Make hash arch-independent using fixed size integer

2015-12-14T15:16:56Z

This helps writing test cases. Also adapt the test case that expected 64-bit. Nothing changes performance wise, the distribution of the hash values remains intact.

tagfile: Hardcode error message for out of range integer values

2015-12-14T12:58:46Z

This makes the test suite work on 32 bit-long platforms. Gbp-Dch: ignore

non-existing directories don't need to be cleaned

2015-12-14T02:21:20Z

Trying to clean up directories which do not exist seems rather silly if you think about it, so let apt think about it and stop it. Depends a bit on the caller if this is fixing anything for them as they might try to acquire a lock or doing other clever things as apt does. Closes: 807477

support regex and co in 'apt-cache policy $pkg' again

2015-12-14T01:38:34Z

Regression of 1e064088bf7b3e29cd36d30760fb3e4143a1a49a (1.1~exp4) which moved code around and renamed methods heavily ending up calling the wrong method matching packagenames only instead of calling the full array. Most commands work with versions, so this managed to fly under the radar for quite a while. Closes: 807870

show a more descriptive error for weak Release files

2015-12-14T01:26:23Z

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

parse .diff/Index hashes in reverse order

2015-12-13T17:53:08Z

Reversing the parsing order ensures that we parse weaker hashes (like SHA1) before we touch newer/stronger hashes (like SHA256) as the weaker ones will usually be there for a longer time already with data already present, which we would discard if we start with the strong one first. The discarding is visible in the debug logs: File X wasn't in the list for the first parsed hash! (history) File X wasn't in the list for the first parsed hash! (patches) which if file X is part of the patch-path means apt will not find a path and fallback to acquire the whole file instead needlessly. If file X isn't part of the patch-path that is no problem, so that effects only the update-call which updates with patches coming from before and after the addition of a new hash.

fix typos and docs in GlobalError documentation

2015-12-13T16:46:49Z

Reported-By: Manuel A. Fernandez Montecelo Git-Dch: Ignore

mmap: Define _DEFAULT_SOURCE instead of _BSD_SOURCE

2015-12-11T14:02:24Z

Fixes a warning reported by gcc. Gbp-Dch: ignore

Bump cache minor version to 2 to trigger rebuilds

2015-12-11T13:48:21Z

With the package names now normalized to lower case, the caches of affected systems need to be rebuild. Adjust the minor version to trigger such a rebuild. Gbp-Dch: ignore

Convert package names from Packages files to lower case

2015-12-11T13:48:21Z

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