Correct process for upgrading Vagrant from 1.7.2 to 1.8.1 on a CentOS 7.2 box, to support VirtualBox 5.0.x?

47 views
Skip to first unread message

David Karr

unread,
May 6, 2016, 7:08:08 PM5/6/16
to Vagrant
On my CentOS 7.2 box, I have Vagrant 1.7.2 by default, but I've installed VirtualBox 5.0.x, which apparently 1.7.2 doesn't support. I can install 1.8.1 by RPM. By implication, that appears to support VirtualBox 5.0.x. Can I just install the rpm file, or do I have to do something else first, or is there a more correct way to do this?

Alvaro Miranda Aguilera

unread,
May 6, 2016, 11:46:13 PM5/6/16
to vagra...@googlegroups.com
Hello

You can always upgrade both, and I am not aware of such limitation of minimum versions.

If the latest packages are not available as part of the distribution, you can just grab the rpms from :



Alvaro.

On Sat, May 7, 2016 at 11:08 AM, David Karr <davidmic...@gmail.com> wrote:
On my CentOS 7.2 box, I have Vagrant 1.7.2 by default, but I've installed VirtualBox 5.0.x, which apparently 1.7.2 doesn't support. I can install 1.8.1 by RPM. By implication, that appears to support VirtualBox 5.0.x. Can I just install the rpm file, or do I have to do something else first, or is there a more correct way to do this?

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1f73190f-4a88-4f75-bd29-77ca27a7f85a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

David Karr

unread,
May 9, 2016, 6:18:17 PM5/9/16
to Vagrant


On Friday, May 6, 2016 at 8:46:13 PM UTC-7, Alvaro Miranda Aguilera wrote:
Hello

You can always upgrade both, and I am not aware of such limitation of minimum versions.

If the latest packages are not available as part of the distribution, you can just grab the rpms from :



I finally got back to this.  As I said, I have 1.7.2 installed, most likely from yum or out of the box from the image.  I downloaded the 1.8.1 RPM.  I then ran "rpm -i <path to rpm file>".  This reported numerous errors like the following:

    file /opt/vagrant/bin/vagrant from install of vagrant-1:1.8.1-1.x86_64 conflicts with file from package vagrant-1:1.7.2-1.x86_64
    file /opt/vagrant/embedded/gems/bin/vagrant from install of vagrant-1:1.8.1-1.x86_64 conflicts with file from package vagrant-1:1.7.2-1.x86_64


 So, what do I do about this?

Alvaro Miranda Aguilera

unread,
May 9, 2016, 7:04:44 PM5/9/16
to vagra...@googlegroups.com
Hello,

In rpm based OS you can't have 2 packages that are the same (the only exception is the kernel), so the command need to be different.

you can rpm -Uvh <vagrant_rpm> to upgrade the package.

Or you can:

rpm -e vagrant
rpm -ivh <vagrant_rpm>

or

yum localinstall <vagrant_rpm>

Alvaro.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f49042db-ffec-48e9-a099-30f17d906d44%40googlegroups.com.

David M. Karr

unread,
May 9, 2016, 7:29:00 PM5/9/16
to vagra...@googlegroups.com
On 05/09/2016 04:04 PM, Alvaro Miranda Aguilera wrote:
Hello,

In rpm based OS you can't have 2 packages that are the same (the only exception is the kernel), so the command need to be different.

you can rpm -Uvh <vagrant_rpm> to upgrade the package.

Or you can:

rpm -e vagrant
rpm -ivh <vagrant_rpm>

or

yum localinstall <vagrant_rpm>

I like that last alternative.  That worked fine.  Thanks.

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/dE_yIeb51Rc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewxWAU6PQgwSEhPOTV5ZQMaLRwN3erL4yzDYy2q5OyxEw%40mail.gmail.com.

David Karr

unread,
May 10, 2016, 12:21:38 PM5/10/16
to Vagrant
On Monday, May 9, 2016 at 4:04:44 PM UTC-7, Alvaro Miranda Aguilera wrote:
Hello,

In rpm based OS you can't have 2 packages that are the same (the only exception is the kernel), so the command need to be different.

you can rpm -Uvh <vagrant_rpm> to upgrade the package.

Or you can:

rpm -e vagrant
rpm -ivh <vagrant_rpm>

or

yum localinstall <vagrant_rpm>

By the way, I noticed that "localinstall" is just a synonym for "install", and "localinstall" is just kept around for "legacy reasons".
 
Reply all
Reply to author
Forward
0 new messages