Last modified: 2014-07-18 20:57:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69899, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67899 - Guest Additions 4.1.18 won't install on Trusty
Guest Additions 4.1.18 won't install on Trusty
Status: RESOLVED WONTFIX
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Ori Livneh
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-11 23:05 UTC by Matthew Flaschen
Modified: 2014-07-18 20:57 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Error log from failed build of vboxguest (4.44 KB, text/x-log)
2014-07-11 23:05 UTC, Matthew Flaschen
Details

Description Matthew Flaschen 2014-07-11 23:05:28 UTC
Created attachment 15916 [details]
Error log from failed build of vboxguest

It is able to download VBoxGuestAdditions_4.1.18.iso, but there seems to be a low-level error preventing the kernel module from building.  Log attached.

4.1.18 is the version used by my host OS, Debian (https://packages.debian.org/wheezy/virtualbox).
Comment 1 Bryan Davis 2014-07-11 23:34:14 UTC
VirtualBox 4.1.18 was released Jun 20th 2012, so it's not surprising that the guest additions code that goes along with it has compilation issues on an OS that was released nearly two years later.

The new problem that has been introduced here is that setup.sh is now installing the Vagrant-VBGuest plugin which is trying to force updating your guest os extensions on each `vagrant up`.

One workaround would be to add:

    Vagrant.configure("2") do |config|
      config.vbguest.auto_update = false
    end

to a local Vagrantfile-extra.rb file in your ~/.vagrant.d/Vagrantfile. This should disable the auto-update feature of the plugin for you. You could alternately put that snippet in a Vagrantfile-extra.rb in the MediaWiki-Vagrant checkout directory.
Comment 2 Matthew Flaschen 2014-07-18 20:57:24 UTC
I worked around it by upgrading VirtualBox on the host.  Bolding marking as WONTFIX per your comments; feel free to reopen if you think it is worth fixing.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links