You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ian has reported in a comment on the 16.0rc1 blog post that TKLDev is consistently failing it's initial setup step. It appears that verification of the bootstrap fails, which halts the tkldev-setup script, leaving the TKLDev setup incomplete. It appears to be because we're not preloading the relevant key. Here is a manual re-run:
root@tkldev ~# tkldev-setup
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 [tkldev-setup]: verifying bootstrap-buster-amd64
gpg: key 85C25E95A16EB94D: "Turnkey Linux Release Key <release@turnkeylinux.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
gpg: Signature made Sun Mar 8 10:37:48 2020 UTC
gpg: using RSA key F190A48B54DC56B2C7F24DCBAC5EB00493E5BC1C
gpg: Can't check signature: No public key
The text was updated successfully, but these errors were encountered:
Ian has reported in a comment on the 16.0rc1 blog post that TKLDev is consistently failing it's initial setup step. It appears that verification of the bootstrap fails, which halts the
tkldev-setup
script, leaving the TKLDev setup incomplete. It appears to be because we're not preloading the relevant key. Here is a manual re-run:The text was updated successfully, but these errors were encountered: