You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "suggestion" for using VirtualBox 4.x (rather than 5.x) seems really outdated. Although there is a 4.3.40 package that was put out there just a couple weeks ago, the last previous 4.x release was almost 2 years ago with many 5.x releases since then.
I already have several VMs happily running in v5.2. I'd prefer to avoid the need to scrap those, uninstall VirtualBox, and install what seems reasonable to assume is a "less modern" version just so I can occasionally test a package that behaves for me on other VMs but fails automated testing. At the same time, I am stuck with packages that can't be approved because they fail.
While I am (just barely) astute enough to install and use VirtualBox, I am not well versed on it. I really don't know how the changes from 4 to 5 may have impacted things. What are the implications of using the Chocolatey-test-environment with v5, and what are the chances that the test environment can be updated to work with VirtualBox 5.x?
Thanks.
The text was updated successfully, but these errors were encountered:
I never saw the, "Virtualbox 4.3.28+ (5.x may have issues, so try to stay in 4.3.x series)" from chocolatey-test-environment :-( I've always used a 5.x Virtualbox on macOS and linux.
I have not run into any problems using Virtualbox 5.x. My fork of the chocolatey-test-environment uses WindowsServer2016 (from Stefan-Schere fork of packer-windows) works great.
Using all of the above I could pack draftsight and install it without any problems.
The "suggestion" for using VirtualBox 4.x (rather than 5.x) seems really outdated. Although there is a 4.3.40 package that was put out there just a couple weeks ago, the last previous 4.x release was almost 2 years ago with many 5.x releases since then.
I already have several VMs happily running in v5.2. I'd prefer to avoid the need to scrap those, uninstall VirtualBox, and install what seems reasonable to assume is a "less modern" version just so I can occasionally test a package that behaves for me on other VMs but fails automated testing. At the same time, I am stuck with packages that can't be approved because they fail.
While I am (just barely) astute enough to install and use VirtualBox, I am not well versed on it. I really don't know how the changes from 4 to 5 may have impacted things. What are the implications of using the Chocolatey-test-environment with v5, and what are the chances that the test environment can be updated to work with VirtualBox 5.x?
Thanks.
The text was updated successfully, but these errors were encountered: