Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.1.6 2015-12-24T16:14:15Z 2015-12-24T16:14:15Z Julian Andres Klode jak@debian.org 2015-12-24T16:14:15Z urn:sha1:65ac6aad5f707849a127202f808d087d1fcaddc9 Gbp-Dch: ignore 2015-12-24T16:03:21Z Julian Andres Klode jak@debian.org 2015-12-24T16:03:21Z urn:sha1:3ac050d1ccfa33dbed236a565511fd3fe84b8465 2015-12-23T18:42:53Z David Kalnischkies david@kalnischkies.de 2015-12-23T18:42:53Z urn:sha1:117551478551958d62d9555c595f2990805137c0 And as we are at it lets fix the 'style' issue I introduced with the filefd changes as well. Reported-By: gcc -fsanitize's & cppcheck Git-Dch: Ignore 2015-12-23T16:48:16Z David Kalnischkies david@kalnischkies.de 2015-12-23T16:48:16Z urn:sha1:8d968cc2d1e11da81f3bab878c1a413a97ca27ed We try to acquired the locks, but we didn't stop if we failed to get it… Closes: 808561 2015-12-23T16:16:13Z David Kalnischkies david@kalnischkies.de 2015-12-23T16:16:13Z urn:sha1:b3db9d81325769fb9d9c6518f9d917f90328bef1 We don't need the buffer that often - only for ReadLine - as it is only occasionally used, so it is actually more efficient to allocate it if needed instead of statically by default. It also allows the caller to influence the buffer size instead of hardcoding it. Git-Dch: Ignore 2015-12-23T15:42:12Z David Kalnischkies david@kalnischkies.de 2015-12-23T15:42:12Z urn:sha1:f63123c385738b059cd854b694a0f62558fb8cbe The default implementation of ReadLine was very naive by just reading each character one-by-one. That is kinda okay for libraries implementing compression as they have internal buffers (but still not great), but while working with files directly or via a pipe as there is no buffer there so all those reads are in fact system calls. This commit introduces an internal buffer in the FileFd implementation which is only used by ReadLine. The more low-level Read and all other actions remain unbuffered – they just changed to deal with potential "left-overs" in the buffer correctly. Closes: 808579 2015-12-22T15:35:06Z David Kalnischkies david@kalnischkies.de 2015-12-22T15:32:56Z urn:sha1:7a68effcb904b4424b54a30e448b6f2560cd1078 If we use the library to compress xz, still try to understand and pick up the arguments we would have used to call xz to figure out which level the user wants us to use instead of defaulting to level 6 (which is the default level of xz). 2015-12-22T14:56:47Z David Kalnischkies david@kalnischkies.de 2015-12-22T14:56:47Z urn:sha1:885a1ffd27e621d7cd2452b39e2053e2f1044253 dpkg switched from CRC32 to CRC64 in 777915108d9d36d022dc4fc4151a615fc95e5032 with the message: | This is the default CRC used by the xz command-line tool, align with | it and switch from CRC32 to CRC64. It should provide slightly better | detection against damaged data, at a negligible speed difference. 2015-12-22T14:46:13Z David Kalnischkies david@kalnischkies.de 2015-12-22T14:46:13Z urn:sha1:fa89055f13726dcc07f9fe14b5f1e8a7af210d61 This isn't implementing any new features, it is "just" moving code around from FileFd methods which decided on each call how to handle the request by including all logic for all possible compressor backends in the method body to a model in which backend-specifics are implemented in a FileFdPrivate subclass. This avoids a big chunk of #ifdef's and should make it a tiny bit more obvious which backend uses which code. The execution of the idea is slightly uglified by the need to preserve ABI and API which causes liberal befriending. Git-Dch: Ignore 2015-12-19T22:04:34Z David Kalnischkies david@kalnischkies.de 2015-12-18T12:17:11Z urn:sha1:785cb6fc843f4751ff9c57dcdf375ad061e83f36 The output changes slightly between different versions, which we already dealt with in the main testcase for apt-key, but there are two more which do not test both versions explicitly and so still had gpg1 output to check against as this is the default at the moment. Git-Dch: Ignore