I'm very confused about this bug. Having read this, and 846892 and 844724 I still don't know what the correct gpg magic rune to use is.
Currently emdebian-archive-keyring.gpg is created with:
gpg --no-permission-warning -q --homedir . --no-default-keyring \
--keyring ./emdebian-archive-keyring.gpg --import 1804772E.txt
If I understand right that makes a .gpg file in the "binary OpenPGP
format" keyring that apt-key understands in stable, but makes a
'keybox' format keyring (that apt-key doesn't understand) in unstable. Right?
Is there a gpg rune to check what format is in use?
Do I have to give apt-key a key or a keyring? Does it matter?
the key 1804772E.txt is in the form "PGP public key block Public-Key
(old)" according to file. Maybe it doesn't actually need transforming at all?
I can put it into a keyring as above and then export from that keyring to a key
with
gpg2 --export --keyring ./emdebian-archive-keyring.gpg --no-default-keyring >
emdebian-archive-keyring.asc
but so far as I understand things that creates a key, not a
keyring. And it's two steps, rather than one.
The SUPPORTED KEYRING FILES section says:
Binary keyring files intended to be used with any apt version should therefore
always be created with --export
but so far as I can see --export doesn't create a keyring, it just
creates a key. and AIUI apt-key wants a keyring (.gpg), not a key.
I am clearly confused about how this is supposed to work.
All I really want to know is 'what is the rune to get 1804772E.txt
into the right format to to go in /etc/apt/trusted.gpg.d', and 'what
should it be called?'
I guess I can work this out by trial and error, but it would be good
to be sure I was doing the right thing.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: Digital signature
