W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packagecloud.io/github/git-lfs/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B05F25D762E3157 W: Failed to fetch https://packagecloud.io/github/git-lfs/ubuntu/dists/xenial/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B05F25D762E3157 W: Some index files failed to download. They have been ignored, or old ones used instead.
Then "sudo apt-get update" failed: public key is not available: NO_PUBKEY 6B05F25D762E3157 in ubuntu xenial
I’ve started getting the same thing in the last couple days. It happens on
sudo apt update on the xenial workers.
As a temporary workaround you can do
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 762E3157.
To fix, I think travis will need to update its xenial image which is including the git-lfs repo.
Thanks for the report, I was going to do about the same as we are also affected.
We will do the workaround by adding the keyserver
This is still broken, but the workaround works!
Thanks for the report. Could you tell me how you identified the key ID?
The key shows in the logs.
You mean 6B05F25D762E3157?
Yep. See the last 8 characters.
Workers using trusty are also affected on some builds, see:
Is there any official status on this? Looks like it hasn’t been fixed yet.
Travis used do be amazing, but since a couple of years ago it started to went south,… and it seems only to accelerate in that direction.
I’ve raised a support request relating to this as I don’t think the workaround is viable when using:
addons: apt: packages: - somepackage
If you know otherwise I’m happy to be wrong.
Working on a fix…
Where does that workaround go in the .travis.yml?
Edit: Figured this out. Anybody else trying to use this workaround, add this section to .travis.yml:
before_install: - sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 762E3157
Also, this is pretty gross, and I hope they fix the xenial environment soon, given that it’s now the default environment for linux…
ISTM the real workaround is to use a newer Ubuntu image that does not suffer from this issue. Add to your
Xenial is already the default Ubuntu image. It’s been that way for a month or so.
worked for mw