Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vagrant.pkg cannot be verified on Catalina for upgrade #11158

Closed
timcoote opened this issue Oct 26, 2019 · 3 comments
Closed

vagrant.pkg cannot be verified on Catalina for upgrade #11158

timcoote opened this issue Oct 26, 2019 · 3 comments

Comments

@timcoote
Copy link

Tip: Before submitting your issue, don't hesitate to remove the above introductory text, possible empty sections (e.g. References), and this tip.

Vagrant version

Run vagrant -v to show the version. If you are not running the latest version
of Vagrant, please upgrade before submitting an issue.

Host operating system

This is the operating system that you run locally.
macOS 10.15 (19A583)

Expected behaviour

Following the instructions in vagrant 2.2.5 to upgrade, download the dmg.
Open downloaded package vagrant_2.2.6_x86_64.dmg
Double click on 'vagrant.pkg'
there should be an interaction to upgrade from the previous version of vagrant

Actual behavior

Double click on vagrant.pkg, get error message:
'“vagrant.pkg” can’t be opened because Apple cannot check it for malicious software."
"This software needs to be updated. Contact the developer for more information."
"This item is on the disk image “vagrant_2.2.6_x86_64.dmg”. Chrome downloaded this disk image today at 11:25 from releases.hashicorp.com."

Steps to reproduce

  1. Download package from https://www.vagrantup.com/downloads.html
  2. launch downloaded file
  3. double click on updater 'vagrant.pkg'

References

Are there any other GitHub issues (open or closed) that should be linked here?
For example:

@timcoote
Copy link
Author

Probably a dupe of #11127

@briancain
Copy link
Member

Hi @timcoote - Thanks for opening an issue! You're right, this is a duplicate of that issue. I'll go ahead and close this one.

@ghost
Copy link

ghost commented Jan 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants