Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.4_rc2 2016-11-24T23:15:13Z 2016-11-24T23:15:13Z David Kalnischkies david@kalnischkies.de 2016-11-24T11:14:39Z urn:sha1:e1ae0531bfad0fce8590c26d1e38825df22d812a 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 2016-11-09T18:33:33Z David Kalnischkies david@kalnischkies.de 2016-11-09T18:15:01Z urn:sha1:34b491e735ad47c4805e63f3b83a659b8d10262b We can't cleanup the environment like e.g. sudo would do as you usually want the environment to "leak" into these helpers, but some variables like HOME should really not have still the value of the root user – it could confuse the helpers (USER) and HOME isn't accessible anyhow. Closes: 842877 2016-09-11T15:44:17Z Julian Andres Klode jak@debian.org 2016-09-11T11:58:40Z urn:sha1:bccb344412a0e97afdf0aaaf41a31124c84f6eaa We need to ignore messages from gcov. All those messages start with profiling: and are printed using vfprintf(), so the only thing we can do is add a library overriding those functions and linking apt-pkg to it. 2016-08-26T13:49:10Z Julian Andres Klode jak@debian.org 2016-08-23T11:15:15Z urn:sha1:24a59c62efafbdb8387b2d3c5616b04b9fd21306 Several modules use std::array without including the array header. Bad modules. Some modules use STDOUT_FILENO and friends, or close() without including unistd.h, where they are defined. One module also uses WIFEXITED() without including sys/wait.h. Finally, environ is not specified to be defined in unistd.h. We are required to define it ourselves according to POSIX, so let's do that. 2016-08-16T16:49:37Z David Kalnischkies david@kalnischkies.de 2016-08-11T16:24:35Z urn:sha1:d94b1d80d8326334d17f6a43061368e783b8e0aa If the server told us in a previous request that it isn't supporting Ranges with bytes via an Accept-Ranges header missing bytes, we don't try to formulate requests using Ranges. 2016-08-13T06:49:35Z David Kalnischkies david@kalnischkies.de 2016-08-12T20:13:09Z urn:sha1:148c049150cc39f2e40894c1684dc2aefea1117e It seems completely pointless from a server-POV to sent empty header fields, so most of them don't do it (simply proven by this limitation existing since day one) – but it is technically allowed by the RFC as the surounding whitespaces are optional and Github seems to like sending "X-Geo-Block-List:\r\n" since recently (bug reports in other http clients indicate July) at least sometimes as the reporter claims to have seen it on https only even through it can happen with both. Closes: 834048 2016-08-10T14:17:19Z Julian Andres Klode jak@debian.org 2016-08-09T15:40:01Z urn:sha1:c85c4bed0a4b32ee2dcbd86ea819e39f3d8beb84 Bye, bye, old friend. 2016-08-06T20:36:02Z Julian Andres Klode jak@debian.org 2016-08-06T19:32:36Z urn:sha1:dfd863ea50c0fcf9b9ac4dfb5ae0e64c529bd767 This early support seems a bit hacky, but it's a hard switch: The integration tests do not understand the old build system anymore afterwards. I don't really like that. 2016-07-02T10:01:17Z David Kalnischkies david@kalnischkies.de 2016-07-02T09:28:42Z urn:sha1:0b45b6e5de1ba4224ced67a9952e009d0f4139a0 All apt versions support numeric as well as 3-character timezones just fine and its actually hard to write code which doesn't "accidently" accepts it. So why change? Documenting the Date/Valid-Until fields in the Release file is easy to do in terms of referencing the datetime format used e.g. in the Debian changelogs (policy §4.4). This format specifies only the numeric timezones through, not the nowadays obsolete 3-character ones, so in the interest of least surprise we should use the same format even through it carries a small risk of regression in other clients (which encounter repositories created with apt-ftparchive). In case it is really regressing in practice, the hidden option -o APT::FTPArchive::Release::NumericTimezone=0 can be used to go back to good old UTC as timezone. The EDSP and EIPP protocols use this 'new' format, the text interface used to communicate with the acquire methods does not for compatibility reasons even if none of our methods would be effected and I doubt any other would (in these instances the timezone is 'GMT' as that is what HTTP/1.1 requires). Note that this is only true for apt talking to methods, (libapt-based) methods talking to apt will respond with the 'new' format. It is therefore strongly adviced to support both also in method input. 2016-06-10T08:49:34Z David Kalnischkies david@kalnischkies.de 2016-06-09T19:06:48Z urn:sha1:6f35be91c9e86e463bca7df6eadf05412c7b732c Seen first in #826783, but as this buglog also shows leaked uncompressed files as well we don't close it just yet.