Hi,
Kill Your TV wrote (29 Jul 2014 02:12:19 GMT) :
As a quick workaround I installed privoxy in the VM and the build
succeeded, but I don't see why it was only failing intermittently
prior to installing privoxy.
To debug this further, I would need a *full* build log, and to know
what you
On Wed, 30 Jul 2014 09:52:47 + (UTC)
intrigeri intrig...@boum.org wrote:
Hi,
Kill Your TV wrote (29 Jul 2014 02:12:19 GMT) :
As a quick workaround I installed privoxy in the VM and the build
succeeded, but I don't see why it was only failing intermittently
prior to installing
Hi,
[No need to Cc me, I do read this list.]
Kill Your TV wrote (30 Jul 2014 15:18:13 GMT) :
Everything else was configured
according to https://tails.boum.org/contribute/build/#index2h1 . What's
stated on this page--at this point in time--is exactly what's needed to
make a tails image
Hi,
I had another look at this problem. And now, to be honest, what I find
weird is not that it doesn't work for some people. Rather, it's that
it does work for me :~/
May you please retry after applying the (untested) attached patch,
or something inspired by it?
Cheers,
--
intrigeri
diff
On Wed, 30 Jul 2014 20:13:02 + (UTC)
intrigeri intrig...@boum.org wrote:
Hi,
I had another look at this problem. And now, to be honest, what I find
weird is not that it doesn't work for some people. Rather, it's that
it does work for me :~/
It continued to worked for me until I
I was getting this error during builds with Vagrant. I've manually set
up a Wheezy VM and I'm still seeing it.
Some in #tails-dev have suggested that this build failure can be solved
by changing any instance of dpkg-dev to libdpkg-perl but that's just
wrong. The output looks like the following:
