Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.1.1 2015-11-27T14:40:47Z 2015-11-27T14:40:47Z David Kalnischkies david@kalnischkies.de 2015-11-27T14:40:47Z urn:sha1:5dd00edbcf702cac1ea22392796c65881a8ef6f9 Git-Dch: Ignore 2015-11-27T13:02:49Z David Kalnischkies david@kalnischkies.de 2015-11-27T13:02:49Z urn:sha1:28f24d3dad1844af316337d565ba2ebc11c8ce97 Closes: #806422 2015-11-27T11:29:22Z Michael Vogt mvo@ubuntu.com 2015-11-27T11:29:22Z urn:sha1:ef39c148105cf30aea822022a5f41a120897cc65 If it does not exist disabled priv dropping as there is nothing we can drop to. This will unblock people with special chroots or systems that deleted the "_apt" user. Closes: #806406 2015-11-27T11:10:57Z Michael Vogt mvo@ubuntu.com 2015-11-27T11:07:48Z urn:sha1:a416a90b631a430306df6ed3fa1d4f3a1bdc7949 This fixes a regression caussed by commit 95278287f4e1eeaf5d96749d6fc9bfc53fb400d0 that moved the error detection of RunFds() later into the loop. However this broke detecting issues like dead acquire methods. Instead of relying on the global error state (which is bad) we now pass a boolean value back from RunFds() and break on false. Closes: #806406 2015-11-25T14:20:10Z David Kalnischkies david@kalnischkies.de 2015-11-22T14:09:50Z urn:sha1:add81166f8ecb194ab5cf881200ab9d890abea6c The manpages were fixed by Justin B Rye, lets deal with the rest now. Git-Dch: Ignore 2015-11-25T14:20:10Z Justin B Rye justin.byam.rye@gmail.com 2015-11-22T09:14:12Z urn:sha1:839603418384565a53d9aca7b23dbd7742e3ea77 Git-Dch: Ignore 2015-11-21T17:04:29Z Justin B Rye justin.byam.rye@gmail.com 2015-11-21T16:50:06Z urn:sha1:d04e44ac8177fc5b70ae0189bb5e437c2502f910 Reference mail: https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html 2015-11-21T12:47:19Z David Kalnischkies david@kalnischkies.de 2015-11-21T12:47:19Z urn:sha1:abd6af5a1ce2c20a5742c5c3182dfadce10367ca In 8d041b4f we made apt figure out based on the last Release file it has if it should request a file or not given that the hashes changed or not. So if we have a last Release file and do a request, do not sent a Last-Modified header as we expect a change so much that a non-change would indeed be an error. The Last-Modified header is therefore at best ignored by the server, so sending it is just wasted effort. In the worst case as time is a fragile thing the server decides against sending us an update with the idea that we already have the latest content, which we know for a fact that we haven't. Given that we sent less information to the server our request is on its own also less identifiable as coming from a returning or new user. The disadvantage is that if we end up getting an old index file after getting a new Release file from another mirror the old mirror will not be able to tell us 'Hit', but instead sends us the complete file we discard, but both lets us end up with the same error class in the end, so the difference isn't big in practice. 2015-11-20T08:46:18Z David Kalnischkies david@kalnischkies.de 2015-11-20T08:46:18Z urn:sha1:89497574da3dd40076d955efc936b54e76a8c59c Reported-By: codespell Git-Dch: Ignore 2015-11-19T23:54:07Z David Kalnischkies david@kalnischkies.de 2015-11-19T23:54:07Z urn:sha1:6789e01e9370b3b7f65d52138c5657eaa712b4d1 Out of memory and similar circumstanzas could cause MMap::Map to fail and especially the mmap/malloc calls in it. With some additional checking we can avoid segfaults and similar in such situations – at least in theory as if this is a real out of memory everything we do to handle the error could just as well run into a memory problem as well… But at least in theory (if MMap::Map is made to fail always) we can deal with it so good that a user actually never sees a failure (as the cache it tries to load with it fails and is discarded, so that DynamicMMap takes over and a new one is build) instead of segfaulting. Closes: 803417