Vvv: GPG error: public key not available for package cloud.io

[hphioolen]

Expected Behavior

Vagrant up should work

Current Behavior

Vagrant up fails on error:
GPG error: https://packagecloud.io trusty InRelease: The following signatures couldn't be verified because the public key is not available:

Possible Solution

Steps to Reproduce (for bugs)

started on a fresh install on MacOS 10.13.6
\ V\ V\ V / Varying Vagrant Vagrants
_/_/_/ v2.4.0-git::master

Platform: darwin13.4.0 shell:/bin/bash
Vagrant: 2.2.2
VirtualBox: 6.0.0r127566

https://gist.github.com/hphioolen/1bcb2a55f2e03f37856c5a4522b9a427

Context

Your Environment

• VVV version: 2.4.0
• VVV Git Branch:
  master
• Vagrant version: 2.2.2
• VM Provider name: Virtualbox
• VM Provider version: 6.0.0
• Operating System and version: MacOS 10.13.6

[tomjn]

This looks to be related to #1700,

[tomjn]

eurgh https://twitter.com/packagecloudio/status/1082362236369162240

[tomjn]

can you test https://github.com/Varying-Vagrant-Vagrants/VVV/pull/1702 ? It should resolve the issue, but I want to be sure, then I can make an emergency release

[hphioolen]

It seems that this is the issue, I'm jest not sure how to fix it.
I'm guessing this should solve it:

For APT repositories: Use apt-key to import the repository’s new GPG key. Be sure to substitute the user and repository in this example before running it: curl -L https://packagecloud.io/user/repository/gpgkey | apt-key add -. You will need to be root to run this command.

But what are user and repository in this? And should I run this on my local machine or on the vagrant box?

[tomjn]

Try the pull request I opened, it replaces the keys as needed

On Wed, 9 Jan 2019 at 09:38, hphioolen [e-mail] wrote:

It seems that this is the issue, I'm jest not sure how to fix it.
I'm guessing this should solve it:

For APT repositories: Use apt-key to import the repository’s new GPG key.
Be sure to substitute the user and repository in this example before
running it: curl -L https://packagecloud.io/user/repository/gpgkey |
apt-key add -. You will need to be root to run this command.

But what are user and repository in this? And should I run this on my
local machine or on the vagrant box?

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1701#issuecomment-452632492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADl52osRgAoKMJ5bERRCrd3Cr6cBdl8ks5vBbikgaJpZM4Z2cia
.

[hphioolen]

Hi Thanks. I've tried to vagrant up twice with the 'develop' branche. Once with the original box and once on a fresh install. in both cases I get exactly the same GPG error.
I also tried this today on another Mac. dame results

[tomjn]

@hphioolen I just merged the pull request with a fix, can you confirm the fix fixes it? It's in the develop branch now

[georgewalish]

@tomjn I had this same issue and your fix in the develop branch worked. Thank You!

[hphioolen]

Works thanks!

[enkrates]

What is the timeline for this fix to make it into master? I'm still seeing the bug there and I'm weighing switching to develop to get the fix.

[tomjn]

there aren't many differences between master and develop at the moment, mostly bug fixes. I'm hoping to do a release before the end of the week but I'm ill at the moment so I don't have a lot of energy to get stuff done

[enkrates]

Thanks for all the work you do on this project and please don't rush on my account. I'll happily wait for you to find the time to merge. 😄

[tomjn]

Specifically I want to test and verify that #1704 doesn't cause any issues for people so I can merge it, and I want someone to double check https://github.com/Varying-Vagrant-Vagrants/VVV/pull/1705

[tomjn]

Marking this as closed as it's fixed in develop with iminent release in #1714

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.