Merge lp:~utlemming/livecd-rootfs/v380 into lp:livecd-rootfs
| Status: | Merged |
|---|---|
| Merged at revision: | 1318 |
| Proposed branch: | lp:~utlemming/livecd-rootfs/v380 |
| Merge into: | lp:livecd-rootfs |
| Diff against target: |
29 lines (+12/-0) 2 files modified
debian/changelog (+7/-0) live-build/ubuntu-cpc/hooks/042-vagrant.binary (+5/-0) |
| To merge this branch: | bzr merge lp:~utlemming/livecd-rootfs/v380 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Dimitri John Ledkov | 2016-02-22 | Approve on 2016-02-22 | |
|
Review via email:
|
|||
Description of the Change
Fix for Vagrant Images (LP: #1546108).
| Kevin W Monroe (kwmonroe) wrote : | # |
I don't think this will work, at least not on OSX with vagrant-1.8.1. Attempting to 'vagrant up <foo>' based on this box results in:
-----
There are errors in the configuration of this machine. Please fix
the following errors and try again:
Vagrant:
* Unknown configuration section 'customize'.
-----
I altered your patch to 042-vagrant.binary like this:
http://
And it worked for me. Just my $0.02.
| Kevin W Monroe (kwmonroe) wrote : | # |
I should have explained my changes a bit better.. I think 'customize' is a provider-specific thing, so config.customize won't work. The only refs I can find to customize from vagrantup.com are from the "VBOXMANAGE CUSTOMIZATIONS" section here [0], which call '.customize' on a config.vm.provider object.
The other change I made was to add a File.join(Dir.pwd, foo) instead of the bare 'console.log'. Without that, I was getting:
-----
RawFile#0 failed to create the raw output file console.log (VERR_ACCESS_
-----
So I included an explicit path (pwd) so the console log was created in the same dir as my Vagrantfile. I also named the console.log with a xenial prefix in case you have multiple boxes that you want to define console.logs for.
[0] - https:/

¯\_(ツ)_/¯