<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/libapt, branch 1.1_exp14</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.1_exp14</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.1_exp14'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2015-09-14T13:22:18Z</updated>
<entry>
<title>srv test: do 100 pulls twice and compare list</title>
<updated>2015-09-14T13:22:18Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-11T23:23:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9bfb1136abfd58e48545304507dedceb2fe87a36'/>
<id>urn:sha1:9bfb1136abfd58e48545304507dedceb2fe87a36</id>
<content type='text'>
The previous implementation was still a bit unstable in terms of failing
at times. Lets try if we have more luck with this one.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>use clock() as source for SRV randomness</title>
<updated>2015-09-01T17:01:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-01T16:32:22Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=76abe9a5aad69eb7e67295588c6825cdae0341af'/>
<id>urn:sha1:76abe9a5aad69eb7e67295588c6825cdae0341af</id>
<content type='text'>
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).
</content>
</entry>
<entry>
<title>use unusable-for-security hashes for integrity checks</title>
<updated>2015-09-01T12:19:44Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-01T11:58:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=63d609985eb7eefa5f2332bfe4fab96f017760a1'/>
<id>urn:sha1:63d609985eb7eefa5f2332bfe4fab96f017760a1</id>
<content type='text'>
We want to declare some hashes as not enough for security, so that a
user will need --allow-unauthenticated or similar to get data secured
only by those hashes, but we can still us these hashes for integrity
checks if we got them.
</content>
</entry>
<entry>
<title>Add test for using ExtractTar on compressed files</title>
<updated>2015-08-27T11:45:57Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2014-03-16T13:48:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=992a1e83eb3fa4a7e6a19288e7c0af7c5d2b25c0'/>
<id>urn:sha1:992a1e83eb3fa4a7e6a19288e7c0af7c5d2b25c0</id>
<content type='text'>
Git-Dch: ignore
</content>
</entry>
<entry>
<title>Add basic (non weight adjusted) shuffling for SrvRecords selection</title>
<updated>2015-08-20T09:41:51Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@debian.org</email>
</author>
<published>2015-08-20T08:40:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c29dbdffcb6f67812f823f1f844b87320cf6b437'/>
<id>urn:sha1:c29dbdffcb6f67812f823f1f844b87320cf6b437</id>
<content type='text'>
Also add "Debug::Acquire::SrvRecs" debug option and the option
"Acquire::EnableSrvRecods" to allow disabling this lookup.
</content>
</entry>
<entry>
<title>add c++11 override marker to overridden methods</title>
<updated>2015-08-10T15:27:17Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-07-08T22:35:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3b3028467ceccca0b73a8f53051c0fa4de313111'/>
<id>urn:sha1:3b3028467ceccca0b73a8f53051c0fa4de313111</id>
<content type='text'>
C++11 adds the 'override' specifier to mark that a method is overriding
a base class method and error out if not. We hide it in the APT_OVERRIDE
macro to ensure that we keep compiling in pre-c++11 standards.

Reported-By: clang-modernize -add-override -override-macros
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>bring back deb822 sources.list entries as .sources</title>
<updated>2015-08-10T15:25:26Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-06-21T21:12:24Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=81460e32961bb0b9922bf8a1a27d87705d8c3e51'/>
<id>urn:sha1:81460e32961bb0b9922bf8a1a27d87705d8c3e51</id>
<content type='text'>
Having two different formats in the same file is very dirty and causes
external tools to fail hard trying to parse them. It is probably not a
good idea for them to parse them in the first place, but they do and we
shouldn't break them if there is a better way.

So we solve this issue for now by giving our deb822 format a new
filename extension ".sources" which unsupporting applications are likely
to ignore an can begin gradually moving forward rather than waiting for
the unknown applications to catch up.

Currently and for the forseeable future apt is going to support both
with the same feature set as documented in the manpage, with the
longtime plan of adopting the 'new' format as default, but that is a
long way to go and might get going more from having an easier time
setting options than from us pushing it explicitely.
</content>
</entry>
<entry>
<title>fix memory leaks reported by -fsanitize</title>
<updated>2015-08-10T15:25:25Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-06-18T15:33:15Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3d8232bf97ce11818fb07813a71136484ea1a44a'/>
<id>urn:sha1:3d8232bf97ce11818fb07813a71136484ea1a44a</id>
<content type='text'>
Various small leaks here and there. Nothing particularily big, but still
good to fix. Found by the sanitizers while running our testcases.

Reported-By: gcc -fsanitize
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>some CXXFLAGS housekeeping</title>
<updated>2015-08-10T15:25:25Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-06-17T20:15:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c3392a9fccc04129816057b1184c651171034376'/>
<id>urn:sha1:c3392a9fccc04129816057b1184c651171034376</id>
<content type='text'>
More warnings are always better.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>fileutl_test.cc: Check for /etc/passwd instead of /bin/sh</title>
<updated>2015-08-10T09:43:23Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2015-08-10T09:42:34Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=20cf708a62df5e4aa45a506819db425c6cc975fe'/>
<id>urn:sha1:20cf708a62df5e4aa45a506819db425c6cc975fe</id>
<content type='text'>
This fixes the tests on systems where usrmerge is installed.

Gbp-dch: ignore
</content>
</entry>
</feed>
