apt, branch 1.5_alpha2 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.5_alpha2 2017-06-29T15:52:42Z Upload 1.5~alpha2 to experimental 2017-06-29T15:52:42Z Julian Andres Klode jak@debian.org 2017-06-29T15:52:42Z urn:sha1:24f801bb0d45911cf195a56c49f6968f98442697 Build-Depend on debhelper (>= 10) to shut up lintian 2017-06-29T15:52:04Z Julian Andres Klode jak@debian.org 2017-06-29T15:52:04Z urn:sha1:55db48d5a968591e79ec87f6e49570e6ffcd2fc7 Bump Standards-Version (and wrap-and-sort a bit) 2017-06-29T15:50:05Z Julian Andres Klode jak@debian.org 2017-06-29T15:49:19Z urn:sha1:47e66f653665fde8c7f31ba545580f8c6e4add91 http: Only use system CA store if CaInfo is not set 2017-06-29T14:12:40Z Julian Andres Klode jak@debian.org 2017-06-29T13:30:12Z urn:sha1:58a1a72988e9280343821243217c1fc7d5ddea46 It turns out that curl only sets the system trust store if the CaInfo option is not set, so let's do the same here. Demote gnupg to Suggests 2017-06-29T10:59:16Z Julian Andres Klode jak@debian.org 2017-06-29T10:59:16Z urn:sha1:22ee196fb90997f9265dd9344054cb4f43f2046e stretch was the migration release for gpg->gpgv basically, so let's demote it now. Have apt Recommend ca-certificates 2017-06-29T10:54:33Z Julian Andres Klode jak@debian.org 2017-06-29T10:49:40Z urn:sha1:617e315a7ed3b02320243f3a7eb7f295bb56b509 The http method needs ca-certificates for TLS support, so enable it. Improve error message if system CA store is empty 2017-06-29T10:54:30Z Julian Andres Klode jak@debian.org 2017-06-29T10:47:55Z urn:sha1:5e9c1b36764109ab13232188892730c326fb41e8 Tell the user to install ca-certificates. Closes: #866377 fix a "critical" typo in old changelog entry 2017-06-29T09:23:33Z Robert Luberda robert@debian.org 2017-06-29T09:23:33Z urn:sha1:ec0ebf784d15821786334a4781d0b58b0b163363 This typo exposes a bug in apt-listchanges that prevents commands like `apt-listchanges --show-all apt_*.deb' from showing the changelog. The bug will be fixed in next upload of apt-listchanges, but I think it would be nice have the typo fixed as well. Closes: 866358 use port from SRV record instead of initial port 2017-06-28T23:23:59Z David Kalnischkies david@kalnischkies.de 2017-06-28T20:56:27Z urn:sha1:9bdc09016f9570389451dd619d7e878bfeaa91df An SRV record includes a portnumber to use with the host given, but apt was ignoring the portnumber and instead used either the port given by the user for the initial host or the default port for the service. In practice the service usually runs on another host on the default port, so it tends to work as intended and even if not and apt can't get a connection there it will gracefully fallback to contacting the initial host with the right port, so its a user invisible bug most of the time. support tor+https being handled by http 2017-06-28T20:26:56Z David Kalnischkies david@kalnischkies.de 2017-06-28T20:20:22Z urn:sha1:579f8f1008eceecd3da9ac53923c6a8d08244cb7 The apt-transport-tor package operates via simple symlinks which can result in 'http' being called as 'tor+https', so it must pick up the right configuration pieces and trigger https support also in plus names.