Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.3_pre2 2016-07-08T12:34:37Z 2016-07-08T12:34:37Z Julian Andres Klode jak@debian.org 2016-07-08T12:33:44Z urn:sha1:b8c465aa89406d6bba17e8ecf04710eae2c71d08 Yes, we might still add new features to 1.3 or break some more stuff. Stay tuned! 2016-07-07T18:39:03Z Julian Andres Klode jak@debian.org 2016-07-07T18:38:00Z urn:sha1:4bdf29d39c401ac479f6486469328fa648f9feab 2016-07-07T18:20:44Z Julian Andres Klode jak@debian.org 2016-07-07T18:20:44Z urn:sha1:ec51fe3ff619835a0e2e672112f42ad3293ee760 Now post-build script should no longer complain... Gbp-Dch: ignore 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-07-01T22:03:20Z David Kalnischkies david@kalnischkies.de 2016-07-01T21:44:37Z urn:sha1:f4dcab0504a68595d9e95c953ce66f46f9ad30aa Debian isn't using 'update' anymore for years and the command is in direct conflict with our goal of not requiring gnupg anymore, so it is high time to officially declare this command as deprecated. 2016-07-01T20:00:52Z David Kalnischkies david@kalnischkies.de 2016-07-01T20:00:52Z urn:sha1:08fcf9628806af202e555bd02b3611e4e9a3d757 apt-key needs gnupg for most of its operations, but depending on it isn't very efficient as apt-key is hardly used by users – and scripts shouldn't use it to begin with as it is just a silly wrapper. To draw more attention on the fact that e.g. 'apt-key add' should not be used in favor of "just" dropping a keyring file into the trusted.gpg.d directory this commit implements the display of warnings. 2016-07-01T14:40:36Z David Kalnischkies david@kalnischkies.de 2016-07-01T14:40:36Z urn:sha1:a5f9b45e4a67246f7af2c6fc62de9c531cd314a4 There is no real point in having two commands which roughly do the same thing, especially if the difference is just in the display of the fingerprint and hence security sensitive information. Closes: 829232 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-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.