asheesh changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Channel glossary: "i,i" means "I have no point, I just want to say". b == thumbs up. | Public logs at https://botbot.me/freenode/sandstorm/ & http://logbot.g0v.tw/channel/sandstorm/today
gemlog has joined #sandstorm
<gemlog> So happy with oasis these past months. Kept moving and didn't have to keep configuring routers of others...
<gemlog> Thots on http://www.redmine.org/ as a sandstorm app/grain?
<gemlog> It's quite slick. Just re-googled this irc to mention it, that's all.
gemlog has left #sandstorm ["Konversation terminated!"]
hannes2 has joined #sandstorm
hannes3 has quit [Ping timeout: 240 seconds]
frankier has joined #sandstorm
synchroner has joined #sandstorm
synchroner has quit [Client Quit]
synchrone has joined #sandstorm
synchrone has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
synchrone has joined #sandstorm
synchrone has quit [Client Quit]
synchrone has joined #sandstorm
synchrone has quit [Client Quit]
decipherstatic has quit [Quit: Leaving]
jemc has joined #sandstorm
<xet7_> Is Redmine available for sandstorm?
<mrdomino> hurf. okay so on reflection i still don't quite understand why i had such a hell of a time getting the sandstorm raw api example to compile
<mrdomino> (incidentally rawapi works now, but when i do spk dev on ssjekyll, i get a segfault on page load for some reason -- haven't tried to trace it yet)
<mrdomino> i am now looking at building this sucker. it seems like Makefiles are common practice for the published examples. ekam would be great but it's really slow if i have to restart it to say change a flag or something. i'm still eyeing bazel.
Zertrin has quit [Remote host closed the connection]
Zertrin_ has joined #sandstorm
xet7 has quit [Quit: Leaving]
xet7_ has quit [Ping timeout: 250 seconds]
xet7 has joined #sandstorm
sydney_untangle has quit [Quit: brb]
sydney_untangle has joined #sandstorm
frankier has quit [Remote host closed the connection]
Lionel_Debroux_ has quit [Ping timeout: 276 seconds]
xet7_ has joined #sandstorm
icebrain has quit [Quit: WeeChat 1.2]
Lionel_Debroux_ has joined #sandstorm
evernite- has quit [Quit: ZNC 1.6.1 - http://znc.in]
Telesight has joined #sandstorm
rafaelmartins has quit [Read error: Connection reset by peer]
rafaelmartins has joined #sandstorm
<JonTheNiceGuy[m]> It also has a cat... :)
<kentonv> zarvox: hmm, that text is wrong (our code isn't setuid), but I did have a discussion with them some time back where basically I told them that I didn't feel like it made sense for us to switch to bubblewrap at that time
Telesight has quit [Quit: Leaving.]
jemc has quit [Ping timeout: 276 seconds]
jemc has joined #sandstorm
<TC01> so, I destroyed and attempted to remake my vagrant VM, and got the following exciting output from vagrant-spk: https://paste.fedoraproject.org/404059/70611418/
<TC01> the "bad file descriptor" lines keep getting printed (I'm not actually sure how to stop this short of killing a bunch of qemu/vagrant processes)
<TC01> I'm using Fedora 24 with vagrant-spk in libvirt mode as per https://github.com/sandstorm-io/vagrant-spk/blob/master/HOWTO-libvirt.md, and it _was_ working fine
<mrshu> TC01: I never managed vagrant-spk to work on fedora to be honest
<TC01> mrshu: I mean, I had it working last week :(
<TC01> it's possible a package update broke something, but I can't help but notice sandstorm 174 seems to have been released between now and then
<TC01> (and what seems to fail is the sandstorm install script)
* TC01 is uncertain what to do to debug this though
<zarvox> Looks like a recent change to install.sh breaks installation under vagrant-spk cc asheesh
<zarvox> TC01: you can likely use an older install.sh and use that instead, lemme figure out what all that entails
<TC01> zarvox: great, thanks :)
<zarvox> TC01: so, you can download install.sh as of sandstorm-173 at https://raw.githubusercontent.com/sandstorm-io/sandstorm/fcd75e5286e61342f952ee41a3f278619e3a2db3/install.sh , drop that in your ~/.sandstorm/caches/, and temporarily comment out line 14 of the global-setup.sh script
<zarvox> then, vagrant-spk vm destroy && vagrant-spk vm up
<TC01> zarvox: neat, thanks. that seems to work successfully, so I'd guess it was the issue :)