You are here
Adam - Fri, 2022/01/14 - 18:55
Heyo.
I am also having the same issue mentioned in the comment on this thread. When running
tkldev-setup
I get the following error:
INFO [tkldev-setup]: Downloading bootstrap-buster-amd64 File 'bootstrap-buster-amd64.tar.gz' already there; not retrieving. File 'bootstrap-buster-amd64.tar.gz.hash' already there; not retrieving. INFO [signature-verify]: Verifying GPG signature gpg: Signature made Sun Mar 8 10:37:48 2020 UTC gpg: using RSA key F190A48B54DC56B2C7F24DCBAC5EB00493E5BC1C gpg: Can't check signature: No public key FATAL [signature-verify]: /turnkey/fab/bootstraps/bootstrap-buster-amd64.tar.gz.hash GPG verification failed
Which looks to be the same error reported in this github issue.
Any ideas on anything try / troubleshooting steps.
Forum:
Hi Adam, looks like you found a bug!
Initially I thought that was a bit weird!? As your posted output notes, it uses the "signature-verify" script to confirm that the files are appropriately signed (signature-verify comes from buildtasks).
It should check for the key, and if not found locally, download it, either via Ubuntu key server or fall back to downloading from the website.
However, the v16.x key wasn't actually available via the website URL! I have just fixed that (and for v17.x too), so it should work now...
Please re-run and let me know how you go.
If it does work ok, then hopefully other issues you may hit should be covered by that thread you link to. Please do not hesitate to post if you hit other issues and/or need more detail/assistance.
FWIW once you have it all set up and working, you should be fine. But until then, as we're currently in the process of transitioning to v17.0, there is a risk that new changes I push may break the initial setup of v16.x TKLDev.
I still get the same error as
I still get the same error as Adam with 16.1. It looks like the public key was successfully downloaded, though:
That's the wrong key. You need the Buster one!
That's the key for the upcoming v17.0 release (based on Debian Bullseye)! You need the one for Buster (the basis of v16.x).
I suspect that you got that one because we're in the process of transitioning and the 'master' branch of Buldtasks now has the Bullseye key. You need to check out the 16.x branch. I.e.:
16.x failure, 17.0rc1 success
Thanks, I saw you had switched common and cdroots to 16.x in the linked thread but missed that buildtasks also needs it. I did run into a different error when building an appliance (below) after updating the branches:
However, I can build successfully on 17.0rc1, so I'll use that and stop pestering you for support. Thanks for the quick responses and all the work you put into this!
Add new comment