apt/apt-pkg/contrib/srvrec.cc, branch 2.7.2

srvrec: Keep support for older resolver

2021-03-20T19:33:34Z

Some C libraries e.g. musl do not implement the new res_n* APIs therefore keep the old implementation as fallback and check __RES version macro to determine the API level Signed-off-by: Khem Raj Cc: Julian Andres Klode

Reorder config check before result looping for SRV parsing debug

2020-07-02T16:57:11Z

It isn't needed to iterate over all results if we will be doing nothing anyhow as it isn't that common to have that debug option enabled.

srvrec: Use re-entrant resolver functions

2019-08-22T11:11:00Z

This should probably make those functions thread-safe, which might be useful for some external users.

don't try SRV requests based on IP addresses

2018-05-11T12:35:30Z

IP addresses are by definition not a domain so in the best case the requests will just fail; we can do better than that on our own.

Reformat and sort all includes with clang-format

2017-07-12T11:57:51Z

This makes it easier to see which headers includes what. The changes were done by running git grep -l '#\s*include' \ | grep -E '.(cc|h)$' \ | xargs sed -i -E 's/(^\s*)#(\s*)include/\1#\2 include/' To modify all include lines by adding a space, and then running ./git-clang-format.sh.

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.

srvrec: Do not expose C++11 tuple use in header

2015-10-30T13:44:52Z

This makes non-C++11 reverse deps wishing to use it FTBFS.

GetSrvRecords: Make thread-safe

2015-10-30T13:20:09Z

Gbp-Dch: ignore

avoid triggering the c++11 erase api change on travis

2015-09-02T10:35:22Z

Git-Dch: Ignore

use clock() as source for SRV randomness

2015-09-01T17:01:45Z

Initializing a random number generator with the time since epoch could be good enough, but reaches its limits in test code as the 100 iterations might very well happen in the same second and hence the seed number is always the same… clock() has a way lower resolution so it changes more often and not unimportant: If many users start the update at the same time it isn't to unlikely the SRV record will be ordered in the same second choosing the same for them all, but it seems less likely that the exact same clock() time has passed for them. And if I have to touch this, lets change a few other things as well to make me and/or compilers a bit happier (clang complained about the usage of a GNU extension in the testcase for example).