Enthusiastic about sequoia's gpg layer, whoohoo!

My first try wasn't as exciting though:

anarcat@angela:~/s/t/account-keyring> gpg-sq --locate-keys user@torproject.org
gpg:   error: Error parsing option auto-key-locate in /home/anarcat/.gnupg/gpg.conf
gpg: because: Unknown --auto-key-locate mode "local wkd dane cert pka ldap keyserver".
gpg: because: This is not a keyserver url either: relative URL without a base
anarcat@angela:~/s/t/account-keyring[1]>

Boom. Am I doing something wrong? Perhaps sq should just ignore the
auto-key-locate setting and DTRT?

If i comment out that line, it fails on a different setting:

anarcat@angela:~/s/t/account-keyring> gpg-sq --locate-keys user@torproject.org
gpg:   error: Trust model Tofu not implemented
anarcat@angela:~/s/t/account-keyring[1]>

And then, *finally* it fails with this:

anarcat@angela:~/s/t/account-keyring[1]> gpg-sq --locate-keys user@torproject.org
gpg: The command --locate-keys is not yet implemented in the Sequoia
gpg: Chameleon.  To help us prioritize our work, please file a bug at
gpg:   https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues

IMHO, it should have failed there *first* before making me modify two
bits of my gpg.conf... but I guess that's a matter of opinion.

Note that the missing --locate-keys support is already filed upstream:

https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues/112

So I'm not sure if this bug report should just be tracking that
upstream issue, or we also want to discuss the bits where i need to
basically ditch half of my gpg.conf to use chameleon, but I figured I
would file it all here in one shot and open that discussion. :)

I'm happy to close that and split that up if that's better for you.

Thanks for your hard work in packaging sequoia, you all rock! :)