anonym:
> In case you are using vagrant >= 1.2, I'm aware of this issue. If you
> use an older vagrant than that it's new to me. Which version are you using?
I am on Debian unstable. vagrant package 1.4.3-1.
> While I have an unpublished fix that seems to work, I want to take a
> closer look before pushing it (cause I think there are a few other,
> related inconsistencies in the Rakefile). Until then you can work around
> it by only issuing the `rake build` when the vagrant VM is halted. So
> run `rake vm:halt` now and from then on you always build like this:
>
> rake build; rake vm:halt
>
> to make sure that you don't leave the VM running afterwards.
Build process is running now, thanks!
It also explains why I was able to build Tails *once* a few hours before
the problem occurred (in fact that was my first successful Tails build
ever). I did not consider the possibility that a VM might still be
running after that and creating problems.
Cheers,
Andreas
