Fedora 27/28 and CentOS vagrant boxes updated - Chrome 68

[Tirloni, Giovanni]

Well, I don't really like to inflict more pain than necessary with Vagrant boxes (or do I? :P) but Chrome 68 just got released and it seems important to test against it. Sorry!

You're not required to update to this latest version (20180725) as infusion's Vagrantfile will update Chrome/Firefox but it means you're opting for a 2.3GB download versus updating Chrome (~50MB) every time you run `vagrant destroy/up`. It might be better depending on your CPU/bandwidth scenario and specific dev workflow.

v20180725 is the same as v20180723 with two extra days of package updates and Chrome 68. Tested with Infusion and Universal [0][1].

0 - https://buildkite.com/fluid-project/infusion/builds/342
1 - https://ci.gpii.net/job/universal-tests/991

Cheers,
Giovanni

On 07/23/2018 06:23 PM, Tirloni, Giovanni wrote:
> Hello,
> 
> Version '20180723' of these boxes have been released to address an issue in mouse integration and newest versions of VirtualBox and the Linux kernel.
> 
> 🏆 Huge thanks to Joseph for reporting this issue and working together to find a fix 🏆
> 
> If you're running old versions of VirtualBox, it's recommended to update to version 5.2.16. This is what CI is running too.
> 
> Boxes have been built/tested with:
> 
>      * VirtualBox 5.2.16
>      * vagrant 2.1.2
>      * Docker 18.06 (new)
> 
> You can update them by running these commands:
> 
>      $ vagrant box update --box inclusivedesign/centos7
>      $ vagrant box update --box inclusivedesign/fedora27
>      $ vagrant box update --box inclusivedesign/fedora28
> 
> You projects will need to be destroyed and recreated, please make backups if needed (vagrant destroy; vagrant up).
> 
> To verify that all your boxes are up to date:
> 
>      $ vagrant box outdated --global
> 
> To remove old versions automatically:
> 
>      $ vagrant box prune
> 
> Any help in testing Fedora 28 would be appreciated as Fedora 27 will go out of support soon.
> 
> Cheers,
> Giovanni
> 
>