apt/debian, branch 1.6_beta1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.6_beta12018-02-26T12:15:26ZRelease 1.6~beta12018-02-26T12:15:26ZJulian Andres Klodejulian.klode@canonical.com2018-02-26T12:15:26Zurn:sha1:5206249ea92fccf9e812a2d373cbd2f16c623059apt.conf.autoremove: Add linux-cloud-tools to list2018-02-23T14:37:53ZJulian Andres Klodejulian.klode@canonical.com2018-02-23T14:37:53Zurn:sha1:923ba67464960940a19b24a341e896a9338161fb
LP: #1698159
Merge branch 'pu/not-valid-before' into 'master'2018-02-19T15:06:06ZJulian Andres Klodejak@debian.org2018-02-19T15:06:06Zurn:sha1:928ecff984be22632c27a69e072741e74491292c
Check that Date of Release file is not in the future
See merge request apt-team/apt!3Check that Date of Release file is not in the future2018-02-19T15:05:01ZJulian Andres Klodejulian.klode@canonical.com2018-01-29T15:15:41Zurn:sha1:9e5899cac1a6367e3769af52a724821880e538f6
By restricting the Date field to be in the past, an attacker cannot
just create a repository from the future that would be accepted as
a valid update for a repository.
This check can be disabled by Acquire::Check-Date set to false. This
will also disable Check-Valid-Until and any future date related checking,
if any - the option means: "my computers date cannot be trusted."
Modify the tests to allow repositories to be up to 10 hours in the
future, so we can keep using hours there to simulate time changes.
tests: install aptitude for test-method-mirror2018-02-19T14:57:43ZDavid Kalnischkiesdavid@kalnischkies.de2018-02-07T00:45:03Zurn:sha1:13c85c9cec9e071e90ea190a74cbaabe7c51024c
This is an optional dependency for the test, but the skipping of the
test is very noisy and checking that an unchanged aptitude isn't
downright exploding with our libapt isn't a bad idea either.
Gbp-Dch: Ignore
Release 1.6~alpha72018-01-18T14:47:08ZJulian Andres Klodejulian.klode@canonical.com2018-01-18T14:47:08Zurn:sha1:70e68ed87d8ecd011df80f00c6b8ff6316e2b413Point people to salsa.d.o instead of anonscm.d.o for git2018-01-18T14:39:22ZJulian Andres Klodejulian.klode@canonical.com2018-01-18T14:36:51Zurn:sha1:0f16676cd73cfd3858039d4e4e337513e7466725Drop obsolete Suggests on python-apt2018-01-18T13:46:07ZJulian Andres Klodejulian.klode@canonical.com2018-01-18T13:43:42Zurn:sha1:8aae95a7f87a50d1eeb3c4720556a117ec1f59d9
This has not been used for a while. It was added for apt-mark
in 7b4159cf2a4b7de10622c7e4e29247067358a3ab, but apt-mark has
been rewritten in C++ quite some time ago.
Closes: #887607
apt-compat.cron.daily: Correctly handle undetermined power status2018-01-10T07:33:41ZJulian Andres Klodejak@debian.org2018-01-10T07:30:25Zurn:sha1:ca2fcc639c7363a04998f650b96573d806b32dd2
If on_ac_power exits with 255 the script would fail at this point
because set -e was set, but it should continue, as 255 means the
power status could not be determined.
LP: #1742378
Release 1.6~alpha62018-01-03T22:35:18ZJulian Andres Klodejak@debian.org2018-01-03T22:35:18Zurn:sha1:a283107760379b869b9b730e03b9d2d4aac4e736