Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.3_pre1 2016-07-05T18:44:45Z 2016-07-05T18:44:45Z David Kalnischkies david@kalnischkies.de 2016-07-05T13:44:53Z urn:sha1:1b50bba6571661d1ddc1db808bd618bd0de3cae4 If other logs can't be written this is a warning to, so for consistency sake translate the errors to warnings. 2016-07-05T18:44:45Z David Kalnischkies david@kalnischkies.de 2016-07-05T13:40:23Z urn:sha1:5958c7497eea24d55ff305764f058ba1ae836200 Unlikely to happen in practice and I wonder more how I could miss these in earlier reviews, but okay, lets fix it for consistency now. 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-29T10:17:41Z David Kalnischkies david@kalnischkies.de 2016-06-29T07:16:53Z urn:sha1:8e99b22c31eb47d0422e9a69e83dc99bb315ded8 Julian noticed on IRC that I fall victim to a lovely false friend by calling referring to a 'planer' all the time even through these are machines to e.g. remove splinters from woodwork ("make stuff plane"). The term I meant is written in german in this way (= with a single n) but in english there are two, aka: 'planner'. As that is unreleased code switching all instances without any transitional provisions. Also the reason why its skipped in changelog. Thanks: Julian Andres Klode Gbp-Dch: Ignore 2016-06-27T09:57:13Z David Kalnischkies david@kalnischkies.de 2016-06-26T11:20:19Z urn:sha1:b4f91d4d150a0d9bcc77563abbc03d28da2ff4e3 In 385d9f2f23057bc5808b5e013e77ba16d1c94da4 I implemented the storage of scenario files based on enabling this by default for EIPP, but I implemented it first optionally for EDSP to have it independent. The reasons mentioned in the earlier commit (debugging and bugreports) obviously apply here, especially as EIPP solutions aren't user approved, nearly impossible to verify before starting the execution and at the time of error the scenario has changed already, so that reproducing the issue becomes hard(er). 2016-06-27T09:57:13Z David Kalnischkies david@kalnischkies.de 2016-06-25T17:53:58Z urn:sha1:262fdd8b5882dcd23f3b4cb266132ad3c326f83a Freeing 'Install' for future use as an interface for "dpkg --install", which is currently not used by any existent planer, so the implementation of it itself will be delayed until then. 2016-06-27T09:57:12Z David Kalnischkies david@kalnischkies.de 2016-06-06T15:58:00Z urn:sha1:8d1cb6da6e21302c654da3f09de3975af7e4a11f A rather special need option, but the internal planer supports this and we have a testcase for it & sometimes it is hit (as a bug through). The option itself mostly serves as a reminder for implementors that they should be careful with removes and especially temporary removes if they perform any. 2016-06-27T09:57:12Z David Kalnischkies david@kalnischkies.de 2016-06-06T13:04:42Z urn:sha1:a21aca106ce93e8a2841d4a2c7a8432f9dfc7b6d APT has 3 modes: no immediate configuration, all packages are configured immediately and its default mode of configuring essentials and pseudo-essentials immediately only. While this seems like a job of different planers at first, it might be handy to have it as an option, too, in case a planer (like apts internal one) supports different modes where the introduction of individual planers would be counter intuitive. 2016-06-27T09:57:12Z David Kalnischkies david@kalnischkies.de 2016-06-03T12:40:06Z urn:sha1:14bed2c0108a99d68f453ff61273d5ae59a5c3f0 The generation of the EIPP request was a bit to strict not generation what would actually be needed to be part of the scenario. 2016-06-27T09:57:12Z David Kalnischkies david@kalnischkies.de 2016-06-03T11:09:13Z urn:sha1:4cdc3bf0e24a74b0af45e1cbabfcaebd9d0c3318 For the order there is no inherent difference between delete or purge, so we don't tell the planer about this and instead decide in apt if a package should be purged or not which also allows us to not tell the planer about rc-only purges as we can trivially do this on our on as there is no need to plan such purges.