apt/test/libapt, branch 1.3

CMake: test/libapt: Use a prebuilt GTest library if available

2016-09-02T12:34:37Z

If a non-existing source directory is specified, try finding the system gtest library. Debian derived distributions are a bit strange because they only ship the source code and not the library...

tests: silence -Wmissing-declarations

2016-09-01T14:13:32Z

Gbp-Dch: Ignore Reported-By: gcc -Wmissing-declarations

tests: don't do boundless string compares with data()

2016-08-12T09:56:21Z

Git-Dch: Ignore

ensure a good clock() value for usage and tests

2016-08-12T09:12:10Z

We use clock() as a very cheap way of getting a "random" value, but the manpage warns that this could return -1, so we should be dealing with this. Additionally, e.g. on hurd-i386 the value increases only slowly – to slow for our fast running tests for randomness hence producing the same range in both samples, so we introduce a simple busy-wait loop (as clock is counting processor time used by the program) in the test which delays the second sample just enough making our randomness a bit more predictable.

don't perform int
2016-08-12T09:12:04Z
Comparing floating numbers is always fun and in this instance a 9 < 9.0 is "somehow" true on hurd-i386 letting the tests fail by reporting that too much progress achieved. A bit mysterious, but with some rework we can use code which avoids dealing with the floats in this way entirely and make our testcases happy.

allow user@host (aka: no password) in URI parsing

2016-08-10T21:20:15Z

If the URI had no password the username was ignored

Get rid of the old buildsystem

2016-08-10T14:17:19Z

Bye, bye, old friend.

CMake: Add unit tests

2016-08-10T14:11:43Z

Add support for our GTest based unit tests. By default, CMake will look in /usr/src/gtest for the external GTest project, but this can be overriden by defining GTEST_ROOT when invoking cmake. Gbp-Dch: ignore

ensure Cnf::FindFile doesn't return files below /dev/null

2016-07-19T16:05:13Z

Very unlikely, but if the parent is /dev/null, the child empty and the grandchild a value we returned /dev/null/value which doesn't exist, so hardly a problem, but for best operability we should be consistent in our work and return /dev/null always.

don't do atomic overrides with failed files

2016-06-29T12:46:34Z

We deploy atomic renames for some files, but these renames also happen if something about the file failed which isn't really the point of the exercise… Closes: 828908