You are here
Carlos Mora - Mon, 2019/02/04 - 11:26
Hi,
apt update output:
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:4 http://deb.debian.org/debian stretch Release
Err:3 https://dl.yarnpkg.com/debian stable InRelease
The following signatures couldn't be verified because the public
key is not available: NO_PUBKEY 23E7166788B63E1E
<more lines>
W: An error occurred during the signature verification. The repository is not updated
and the previous index files will be used.
GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures
couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following
signatures couldn't be verified because the public key is not available: NO_PUBKEY
23E7166788B63E1E
An attempt to get the pubkey from yarnpkg didn't help
wget https://dl.yarnpkg.com/debian/pubkey.gpg apt-key add pubkey.gpg
After that, the new key appears in apt-key-list, but the key is still missing.
Did someone got this solved?
KR
Forum:
We lock down third party repos
We lock down third party repos as per best practice. To update the key, try this:
FWIW this has occurred because the yarn key is rotated annually, and the old one expired 1st Jan 2019.
Hi Jeremy,
Hi Jeremy,
Sorry, I did as sugested, but still the same result.
root@GitLab-Server ~/scratchdir# apt-key --keyring /usr/share/keyrings/yarn.gpg list /usr/share/keyrings/yarn.gpg ---------------------------- pub rsa4096 2016-10-05 [SC] 72EC F46A 56B4 AD39 C907 BBB7 1646 B01B 86E5 0310 uid [ unknown] Yarn Packaging <yarn@dan.cx> sub rsa4096 2016-10-05 [E] sub rsa4096 2019-01-02 [S] [expires: 2020-02-02] sub rsa4096 2019-01-11 [S] [expires: 2020-02-02]the key seems to be there but still
-----
last minute update. Success!!!
the name of the keyring is yarn-repository.gpg, so the command to update it should be:
I found out looking into /etc/apt/sources/list.d/yarn.list
Thanks!
Oops, apologies on the misdirection. My bad!
Yes you are absolutely correct! Apologies on that and glad to hear that you worked it out.
FWIW there is a TurnKey convention for 3rd party apt repos, of consistently naming the sources.list file, the preferences file and the gpg key all the same (with the relevant file extension). Generally, this is a descriptive name which should make it relatively obvious what it is or who it's supplied by. Whilst "yarn-repository.gpg" is descriptive, it doesn't match the name of the sources.list file, nor the preferences file, so it appears that the convention is sort of broken in the GitLab appliance! In retrospect I probably should have double checked rather than relying on memory...
FWIW, I've been working on updating the Canvas appliance (which also installs Yarn) and that does comply with the convention, hence the gpg key file is named /usr/share/keyrings/yarn.gpg.
Also it's worth noting that we're currently in the process of a major overhaul of the GitLab appliance. The current one installs from source, but we've decided to change the install to be use the Omnibus package. It's proving a little more complex than I'd hoped, so is still not ready, but there is progress. You can check out the outline plan, discussion and progress here. I hope to release that ASAP, but no hard ETA currently.
Still No Go!
What version of TurnKey are you running?
What version of TurnKey are you running? If you're not sure, please give the output of the following:
Also please give the output of the following commands:
~ » turnkey-version
Looks like you aren't using TurnKey!
As you aren't using TurnKey, it's likely that apt isn't looking for your Yarn key in /usr/share/keyrings. It's likely in the default keyring (/etc/apt/trusted.gpg).
That leaves you with 2 choices. You can just continue to use the default keyring file (which is likely what its already pre-configured). Or alternatively, you can update your sources.list entry to use the new keyring file that you have already created (as per best practice).
To update the yarn key in the default keyring, re-run the command but this time, omit the the --keyring location. I.e.:
Alternatively, you can reconfigure the relevant sources.list entry to use the new (separate) keyring file you've already created. To do that, you'll need to update the relevant apt repo line in the relevant sources.list (I assume it's /etc/apt/sources.list.d/yarn.list?!). This is what the relevant line should look like:
That fixed it. Thank you!
Add new comment