Has anyone been able to successful setup the Vagrant box recently? I've
been beating my head against a wall for a while for a while now. I can't
seem to resolve LinuxGuestAdditions related problems with the latest
versions of VirtualBox (5.1.26) and Vagrant (1.9.8). Initially the shared
folders wouldn't mount, which appears to be a known VirtualBox bug that I
have been able to fix by using the vbguest plugin ("vagrant plugin install
vagrant-vbguest"). This allows the 'vagrant up' or provision process to
continue but eventually fails with an unmet package dependency issue:
<snip ...>
==> default: Running provisioner: shell...
default: Running:
C:/Users/brians/AppData/Local/Temp/vagrant-shell20170825-13220-1j44pm0.sh
==> default: Ign:1 http://mirrors.gigenet.com/debian stable InRelease
==> default: Hit:2 http://security.debian.org stable/updates InRelease
==> default: Hit:3 http://mirrors.gigenet.com/debian stable Release
==> default: Hit:5 http://debian.inode.at/debian jessie-backports InRelease
==> default: Reading package lists...
==> default: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: linux-headers-3.16.0-4-amd64 is already the newest version
(3.16.43-2+deb8u3).
==> default: 0 upgraded, 0 newly installed, 0 to remove and 282 not
upgraded.
==> default: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: Some packages could not be installed. This may mean that you
have
==> default: requested an impossible situation or if you are using the
unstable
==> default: distribution that some required packages have not yet been
created
==> default: or been moved out of Incoming.
==> default: The following information may help to resolve the situation:
==> default: The following packages have unmet dependencies:
==> default: virtualbox-guest-x11 : Depends: xorg-video-abi-18 but it is
not installable
==> default: E
==> default: :
==> default: Unable to correct problems, you have held broken packages.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
If anyone has had success, could you please share which versions of
VirtualBox and Vagrant you used? I did attempt using VirtualBox 5.1.14 at
one point but no joy.
Thanks very much.
Brian
On Tuesday, April 26, 2016 at 11:22:03 AM UTC-4, Alexander Rössler wrote:
>
> I have put some effort in making the making the Machinekit Vagrant box
> as install-able as possible. It would be great if you could try it out
> and share your experience. Especially regarding the documentation.
>
> https://github.com/strahlex/machinekit-vagrant
>
> Making a basic Machinekit + QtQuickVcp documentation will probably be my
> summer project.
>
> --
> Alexander
>
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
