Tails

#3 Updated by intrigeri 2014-11-26 07:34:05

> 1.6.x does not work with the current build system

May you please be a little bit more specific? (error messages)

#5 Updated by kytv 2015-01-09 14:40:02

Sorry for not seeing this earlier.

It’s the problem you mentioned in https://mailman.boum.org/pipermail/tails-dev/2014-July/006258.html with Vagrant no longer allowing being imported as a library. I’ll get Vagrant setup again so I can get the error for documentation purposes.

#6 Updated by _adamb 2015-07-13 08:31:28

kytv wrote:
> Sorry for not seeing this earlier.
>
> It’s the problem you mentioned in https://mailman.boum.org/pipermail/tails-dev/2014-July/006258.html with Vagrant no longer allowing being imported as a library. I’ll get Vagrant setup again so I can get the error for documentation purposes.

Vagrant (as of 1.7.3) does still allow being imported as a library. The problem appears to be ruby load paths from invocation of rake (ie the rake gem is not correctly aware of where the vagrant gem library should be found).

I have version above working in a still-testing-state.

Please note the patch at https://mailman.boum.org/pipermail/tails-dev/2015-July/009270.html currently works for the upstream Vagrant vagrant 1.7.3 package (DEB/RPM).

The native jessie vagrant 1.6.5+dfsg1-2 from Debian repo appears to be re-packaged as a gem consequently with completely different file path structure, but if the Rakefile for building Tails does not work under the native jessie gem, then a variant of the patch to include vagrant.rb etc. should fix the issue.

#7 Updated by hybridwipe 2015-08-26 21:48:34

_adamb wrote:
> kytv wrote:
> > Sorry for not seeing this earlier.
> >
> > It’s the problem you mentioned in https://mailman.boum.org/pipermail/tails-dev/2014-July/006258.html with Vagrant no longer allowing being imported as a library. I’ll get Vagrant setup again so I can get the error for documentation purposes.
>
> Vagrant (as of 1.7.3) does still allow being imported as a library. The problem appears to be ruby load paths from invocation of rake (ie the rake gem is not correctly aware of where the vagrant gem library should be found).
>
> I have version above working in a still-testing-state.
>
> Please note the patch at https://mailman.boum.org/pipermail/tails-dev/2015-July/009270.html currently works for the upstream Vagrant vagrant 1.7.3 package (DEB/RPM).

I tried this patch and vagrant 1.7.4 (what’s in unstable currently), and it fails:
rake aborted!
NameError: uninitialized constant Bundler
/home/austin/src/tails/Rakefile:24:in `<top (required)>’
(See full trace by running task with —trace)

#8 Updated by intrigeri 2015-09-01 04:39:47

> I tried this patch and vagrant 1.7.4 (what’s in unstable currently), and it fails:

Thanks. I wasn’t too hopeful given that patch felt very specific to how the upstream .deb is structured.