Arnaud:
>
>
> On 04/04/2017 12:45 PM, anonym wrote:
>> I don't know what you mean with "Tor download" -- the build system itself
>> doesn't run or use tor.
>
> I was talking about the tor browser that is downloaded in
> `config/chroot_local-hooks/10-tbb`, through a series of `curl` commands.
>
On 04/04/2017 12:45 PM, anonym wrote:
> I don't know what you mean with "Tor download" -- the build system itself
> doesn't run or use tor.
I was talking about the tor browser that is downloaded in
`config/chroot_local-hooks/10-tbb`, through a series of `curl` commands.
This part takes forever
Arnaud:
> On 04/04/2017 11:49 AM, anonym wrote:
>>> So at the moment, I'm still in this situation where build fails, and I
>>> retry and retry until at some point it succeeds. I didn't have much time
>>> to work on that yet. I'll come back to you when I workaround this issue,
>>> one way or
On 04/04/2017 11:49 AM, anonym wrote:
>> So at the moment, I'm still in this situation where build fails, and I
>> retry and retry until at some point it succeeds. I didn't have much time
>> to work on that yet. I'll come back to you when I workaround this issue,
>> one way or another.
> A
Arnaud:
> While these patches don't hurt, I can tell you now that they solve
> nothing. And I don't want to be responsible for cluttering the build
> system with useless stuff like that ;)
Thanks! :)
> So at the moment, I'm still in this situation where build fails, and I
> retry and retry until
Hi intrigeri, thanks for the feedback.
On 04/04/2017 08:42 AM, intrigeri wrote:
>
> This seems to have fallen through the cracks. TBH we're not very good
> at tracking patches sent over email, so in the future, I recommend
> filing Redmine tickets, assigned to the current release manager
>
Hi Arnaud,
Arnaud:
> On 03/11/2017 08:41 PM, anonym wrote:
>> Arnaud:
>>> --- a/vagrant/provision/setup-tails-builder
>>> +++ b/vagrant/provision/setup-tails-builder
>> [...]
>>> +# Configure apt to retry
>>> +echo 'APT::Acquire::Retries "20";' > /etc/apt/apt.conf.d/99retries
>> This will only
On 03/11/2017 08:41 PM, anonym wrote:
> Arnaud:
>> --- a/vagrant/provision/setup-tails-builder
>> +++ b/vagrant/provision/setup-tails-builder
> [...]
>> +# Configure apt to retry
>> +echo 'APT::Acquire::Retries "20";' > /etc/apt/apt.conf.d/99retries
> This will only affect provisioning, not any
Hi,
>> +# Configure apt to retry +echo 'APT::Acquire::Retries "20";' >
>> /etc/apt/apt.conf.d/99retries
> This will only affect provisioning, not any usage of APT during the
> build, right? Or will it propagate into the chroot somehow?
I'm not sure about that, actually I don't fully understand
Arnaud:
> --- a/vagrant/provision/setup-tails-builder
> +++ b/vagrant/provision/setup-tails-builder
[...]
> +# Configure apt to retry
> +echo 'APT::Acquire::Retries "20";' > /etc/apt/apt.conf.d/99retries
This will only affect provisioning, not any usage of APT during the build,
right? Or will it
Arnaud:
> I managed to build Tails, finally ! So let me share here the little
> patch I ended up with, in case it can help someone. This patch deals
> with the transient network problems I experienced.
Thanks, applied!
___
Tails-dev mailing list
Hi !
I managed to build Tails, finally ! So let me share here the little
patch I ended up with, in case it can help someone. This patch deals
with the transient network problems I experienced.
Additionally, I increased the RAM of the VM to 1024M, just to be on the
safe side. I've experienced an
Hi,
Arnaud:
> thanks for your support !
:)
> However, after a lot of investigation (mostly in the wrong direction),
> I'm pretty sure to know what's wrong. It's not Tails, it's not the VM,
> it's not my config. It seems to be the network here in Vietnam.
OK :(
> From my understanding, I can
Hi all,
thanks for your support !
I updated to Tails 3.0-beta2, destroyed the VM, started again, failed
again !
My build config is very 'vanilla', I didn't touch anything. So it means
that the build happens within the VM, with apt-cacher-ng enabled. The VM
has the default settings: 512M of RAM,
segfault:
> Arnaud:
>> The failure doesn't always happen at the same point of the build. At
>> first, I thought it was related to `apt`, but I also experienced in
>> failure on a `curl` command (when downloading Tor Browser, in
>> `config/chroot_local-hooks/10-tbb`). I don't have the log anymore,
Arnaud:
> The failure doesn't always happen at the same point of the build. At
> first, I thought it was related to `apt`, but I also experienced in
> failure on a `curl` command (when downloading Tor Browser, in
> `config/chroot_local-hooks/10-tbb`). I don't have the log anymore, but
> it was
Hi Arnaud,
Arnaud:
> I've been trying to build a Tails image an didn't succeed yet. My
> machine is running Debian 9.
> As for Tails, I checked out the tag '3.0-beta1', and that's what I'm
> trying to build at the moment.
> So far, the build always fails sooner or later because of network
>
Dear Tails,
first, let me quickly introduce myself, I'm Arnaud, part of the
SilentKeys team. Please refer to this mail to remember about SilentKeys
(it was quite a while ago):
https://mailman.boum.org/pipermail/tails-project/2016-April/000488.html
I've been trying to build a Tails image an
18 matches
Mail list logo
