apt/test/libapt, branch 1.4_beta1

optional write aptwebserver log to client specific files

2016-11-24T23:15:13Z

The test test-handle-redirect-as-used-mirror-change serves multiple clients at the same time, so the order of the output is undefined and once in a while the two clients will intermix their lines causing the grep we perform on it later to fail making our tests fail. Solved by introducing client-specific logfiles which we all grep and sort the result to have the results more stable. Git-Dch: Ignore

follow the googletest merge in build-depends

2016-11-24T23:15:13Z

Do not read stderr from proxy autodetection scripts

2016-10-04T17:30:30Z

This fixes a regression introduced in commit 8f858d560e3b7b475c623c4e242d1edce246025a don't leak FD in AutoProxyDetect command return parsing which accidentally made the proxy autodetection code also read the scripts output on stderr, not only on stdout when it switched the code from popen() to Popen(). Reported-By: Tim Small

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.