02:23 <mitchellh> hippiehacker: VAGRANT_LOG=debug

02:27 <chrislerum> ah, another non-sleeper

02:30 <mitchellh> I'm sleeping soon :)

05:20 <bigon> mitchellh: hi, sdog just told me that you were pkging vagrant for debian?

05:20 <bigon> because I'm working on this too, it's almost in the archive http://git.bigon.be/?p=user/bigon/vagrant.git;a=summary

07:28 <ironmunk> has anyone else had issues with Vagrant 0.9.3 + VB 4.1.8

07:28 <ironmunk> I can't seem to get the vagrant up command to complete

07:28 <ironmunk> even after I update the vbox additios

07:29 <Dieterbe> \yeah i had some like that

07:29 <ironmunk> i've tried a few boxes from vagrantbox.es

07:29 <Dieterbe> and then when you pgrep you see 3 virtualbox processes running VM's

07:29 <Dieterbe> (well 3 in my case, but i mean "one or more")

07:30 <ironmunk> the machine boots fine from what I can see

07:30 <ironmunk> but can't vagrant ssh into it etc

10:45 <* miketheman> yawns

10:45 <chrislerum> what do you typically do if you download a box, vagrant up it, and see errors and you determine it's because something in the packaged box is out-of-date? 1) go looking for another box? 2) um, ssh in, manually updating things, repackage and use that new box from then on?

10:46 <chrislerum> other options?

10:47 <cburyta> i think repackaging is really the best way to do it. you may need to take a look at the files that were packaged (via —vagrantfile or —inclue) though, to make sure you repack it the same as it was packaged.

10:47 <cburyta> though it may be something you could resolve with a quick shell provision line in the working Vagrantfile?

10:49 <chrislerum> cburyta: ah, i like that last option. seems a simple sudo gem update --system is what was needed for my current issue - i could put something like that in the config block?

10:50 <chrislerum> cool, found the right page at vagrantup.com. thanks

10:53 <cburyta> sweet

11:09 <miketheman> liking the green color output of the chef provisioner.

11:10 <cburyta> i'll second that, it's awesome

11:10 <chrislerum> well ja, as long as it stays green we're all happy

11:15 <chrislerum> guys, what happens when it's deploy time? i know i'm developing locally in a virtual machine on my machine, but do you, say, run your website in production 'inside' a virtual machine on your remote server?

11:16 <chrislerum> you almost have to don't you, to make all this useful? otherwise you'd have to work to get the remote environment matching the box image you devved on(?)

11:20 <cburyta> i think the idea is to use the provision tools to document your process, so you can use the same scripts (chef / puppet or even shell) to update your production env

11:20 <KarlHungus> hrm. since i've updated to 0.9.x vagrant is unable to manage the network on my freebsd boxes

11:20 <KarlHungus> "The distro of your VM couldn't be detected or doesn't support networking features." yada yada yada

11:21 <KarlHungus> has freebsd VM support been dropped? i've updated the config.vm.system directives to config.vm.guest, but to no avail

11:22 <chrislerum> cburyta: ah ok, that makes sense, trying to wrap my head around the big pic, star systems slipping through my fingers

11:29 <cburyta> chrislerum: personally, i had a bit of a hard time wrapping my head around puppet and vagrant… so i backed off and focused on provisioning with shell scripts. it made it easier for me to focus on the vagrant stuff

12:15 <mattk> hey! anyone have tips on getting vagrant up and running on a Win7 64bit env?

12:18 <ryancoleman> Hello. Does anyone know if I can have veewee pass folders from my host to the guest being built for use in the post install script?

12:19 <cburyta> it *may* already do that… the guest /vagrant folder might be the directory your in… don't quote me on that as it's been a few weeks since I played around with veewee.

12:26 <ryancoleman> cburyta: It didn't seem to do that but if you think it might, maybe I should play more with doing a reboot after the guest additions are installed. Thanks!

12:27 <mattk> any win7 ideas?

12:28 <chrislerum> mattk: you've looked at the main vagrant site?

12:29 <chrislerum> mattk: i don't do windows, but latest vagrant version had talk of 'finally we have windows compatability'

12:39 <jslatts> anyone ever had any issues with chef recognizing that a file differs from a template and refusing to overwrite it?

12:46 <kenperkins> mitchellh: thanks again fro that pointer yesterday

13:23 <KarlHungus> ok. i'm stumped. anyone have a working freebsd guest with 0.9.x?

13:23 <KarlHungus> i'd love to see your Vagrantfile.

13:27 <mgolisch> KarlHungus: what doenst work?

13:29 <KarlHungus> mgolisch: networking

13:30 <miketheman> KarlHungus: once you get it working, let me know, too. :)

13:31 <KarlHungus> haha. ok. =) it appears that i need to adjust the guest file to support the configure_networking_yadayadayada method instead of what its doing.

13:31 <KarlHungus> i'll figure it out

13:43 <KarlHungus> mitchellh: why'd you break my freebsd guests with 0.9.x? ;)

13:56 <miketheman> mitchellh: thx

13:59 <mitchellh> KarlHungus: What broke? :(

14:03 <KarlHungus> networking

14:03 <KarlHungus> it appears that i need to implement configure_networks in the freebsd guest definition

14:04 <mitchellh> ah yes, yes yes

14:04 <KarlHungus> i should have a pull request ready shortly

14:04 <mitchellh> thanks :)

15:23 <KarlHungus> mitchellh: it seems there a few things that need updating for the freebsd guest. would you prefer that i create feature branches for each and issue multiple pull requests, or lump them all into one branch and put each fix in its own commit with a single pull req?

15:32 <mitchellh> KarlHungus: Just lump them all and we can fix them if we need to, I won't mind in this case

15:32 <KarlHungus> ok. networking is done, on to shared folders

16:26 <frem> I'm having trouble running 'gem install vagrant' on windows. the compile fails. http://hastebin.com/sukaroxete.txt

16:27 <frem> looks like it's during libffi compilation.

16:30 <frem> ah, it's a known issue with the latest ffi gem. using an earlier gem works: gem install ffi --version='1.0.9'

18:44 <mitchellh> frem: Jesus, I hate that the FFI gem pushes broken gem installs.

18:44 <mitchellh> but yeah, 1.0.9

20:32 <jmorton> evening!

20:33 <jmorton> i've installed couchdb on my box but port forwarding doesn't seem to be working for 5984, could I be missing something?

21:25 <cmsimike> yes

21:25 <cmsimike> paste config

21:26 <cmsimike> pastebin