Then "sudo apt-get update" failed: public key is not available: NO_PUBKEY 6B05F25D762E3157 in ubuntu xenial


#1
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.

#2

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.


#3

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


#4

This is still broken, but the workaround works!


#5

Thanks for the report. Could you tell me how you identified the key ID?


#6

The key shows in the logs.


#7

You mean 6B05F25D762E3157?


#8

Yep. See the last 8 characters.


#9

Workers using trusty are also affected on some builds, see:
https://travis-ci.org/Gallopsled/pwntools/jobs/482058694#L555
Is there any official status on this? Looks like it hasn’t been fixed yet.


#10

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.


#11

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.


#12

Working on a fix…