apt.git - Saurik's version of apt managed for tvOS/ARM64

Age	Commit message (Collapse)	Author
2014-09-27	use only one --keyring in gpg interactions	David Kalnischkies
	We were down to at most two keyrings before, but gnupg upstream plans dropping support for multiple keyrings in the longrun, so with a single keyring we hope to be future proof – and 'apt-key adv' isn't a problem anymore as every change to the keys is merged back, so we have now the same behavior as before, but support an unlimited amount of trusted.gpg.d keyrings.
2014-09-27	add --secret-keyring option for apt-key	David Kalnischkies
	For some advanced usecases it might be handy to specify the secret keyring to be used (e.g. as it is used in the testcases), but specifying it via a normal option for gnupg might not be available forever: http://lists.gnupg.org/pipermail/gnupg-users/2013-August/047180.html Git-Dch: Ignore
2014-09-27	allow to specify fingerprints in 'apt-key del'	David Kalnischkies

2014-09-27	add a test for apt-key export{,all}	David Kalnischkies
	Git-Dch: Ignore
2014-09-27	respect --keyring also in merged keyring commands	David Kalnischkies
	Git-Dch: Ignore
2014-09-27	support gnupg2 as drop-in replacement for gnupg	David Kalnischkies
	If both are available APT will still prefer gpg over gpg2 as it is a bit more lightweight, but it shouldn't be a problem to use one or the other (at least at the moment, who knows what will happen in the future).
2014-09-27	delay gnupg setup in apt-key until it is needed	David Kalnischkies
	'apt-key help' and incorrect usage do not need a functioning gnupg setup, as well as we shouldn't try to setup gnupg before we actually test if it is available (and print a message if it is not).
2014-09-27	merge fragment keyrings in apt-key to avoid hitting gpg limits	David Kalnischkies
	gnupg has a hardlimit of 40 (at the moment) keyrings per invocation, which can be exceeded with (many) repositories. That is rather misfortune as the longrun goal was to drop gnupg dependency at some point in the future, but this can now be considered missed and dropped. It also means that 'apt-key adv' commands might not have the behaviour one would expect it to have as it mainly operates on a big temporary keyring, so commands modifying keys will break. Doing this was never a good idea anyway through, so lets just hope nothing break too badly. Closes: 733028
2014-09-27	refactor key removal code to reuse it in next step	David Kalnischkies
	Git-Dch: Ignore
2014-09-27	set a primary-keyring only if we have access to it	David Kalnischkies

2014-09-27	support (multiple) arguments properly in apt-key	David Kalnischkies

2014-09-27	only create new trusted.gpg if directory is writeable	David Kalnischkies

2014-09-27	all errors should be printed to stderr	David Kalnischkies
	Git-Dch: Ignore
2014-09-27	add a (hidden) --quiet option for apt-key	David Kalnischkies

2014-09-27	remove leftover debug output from multikey softlink	David Kalnischkies
	Git-Dch: Ignore
2014-02-22	Fix typos in documentation (codespell)	Michael Vogt

2014-01-16	use gpg --homedir instead of explicit file placement	David Kalnischkies
	Avoids that gpg gets the idea it could use files from the user which weren't overridden specifically like secret keyring and trustdb as before.
2013-12-19	fix apt-key net-update test to use the buildin webserver	Michael Vogt

2013-12-13	make apt-key net-update actually testable	Michael Vogt

2013-12-01	generate apt-key script with vendor info about keys	David Kalnischkies
	The apt-key script uses quiet a few keyring files for operation which are specific to the distribution it is build on and is hence one of the most patched parts – even if it is not that often used anymore now that a fragment directory for trusted.gpg exists.