Re: [Tails-dev] [PATCH 1/2] wiki: fix link to vagrant page

[intrigeri]

Arnaud:
> Signed-off-by: Arnaud 
> ---
>  wiki/src/contribute/build/vagrant-setup.mdwn | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

applied, thanks!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Debian 9: Build fails consistently, name resolution fails sooner or later

[intrigeri]

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 change the Debian mirror used for
> provisioning the VM. But when it comes to build the Tails iso, I have no
> choice but to download the packages from the Tails mirror, right ? Same
> goes for TorBrowser ?

Exactly.

> Right now I'm working on tweaking the build system, and adding retries
> here and there, so that the build keeps going and doesn't give up so
> easily. I think that `apt-cacher-ng` should help me to mitigate the
> problem, but up to now I destroyed the VM too often to take advantage of
> it ;)

Sounds great!

Cheers !
-- 
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Wiki patches, fix dead links

[Arnaud]

Good to know, thanks for sharing the info. I'll be careful to check the
Redmine next time.

Cheers


On 03/11/2017 02:22 AM, Cody Brownstein wrote:
> Thank you for the patches.
>
> The broken link to the Debian Live Manual is bug #12261 on Redmine.
>
> https://labs.riseup.net/code/issues/12261
>
> The link proposed in the patch is to a manual "for a much more
> up-to-date version of live-build than [is used for Tails]," (quoting
> anonym).
>
> (I learned this also.)
>
>
> On 03/10/2017 07:35 AM, Arnaud wrote:
>> Dear Tails,
>>
>> here comes wiki patches. BTW, what is the prefered way to contribute
>> trivial wiki patches like these ones ?
>>
>> Cheers,
>> Arnaud
>>
>> ___
>> Tails-dev mailing list
>> Tails-dev@boum.org
>> https://mailman.boum.org/listinfo/tails-dev
>> To unsubscribe from this list, send an empty email to
>> tails-dev-unsubscr...@boum.org.
>

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Wiki patches, fix dead links

[Cody Brownstein]

Thank you for the patches.

The broken link to the Debian Live Manual is bug #12261 on Redmine.

https://labs.riseup.net/code/issues/12261

The link proposed in the patch is to a manual "for a much more 
up-to-date version of live-build than [is used for Tails]," (quoting 
anonym).


(I learned this also.)


On 03/10/2017 07:35 AM, Arnaud wrote:

Dear Tails,

here comes wiki patches. BTW, what is the prefered way to contribute trivial 
wiki patches like these ones ?

Cheers,
Arnaud

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


--
Cody Brownstein
Liquidity, LLC

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Wiki patches, fix dead links

[u]

Hi Arnaud,

> here comes wiki patches. 

Thank you. I did not review this, I just wanted to answer your question:

> BTW, what is the prefered way to contribute trivial wiki patches like these 
> ones ?

I think the preferred way is to create a Git branch and publish it
somewhere and then issue a merge request on this list like you just did
with the patches.

Cheers!
u.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] [PATCH 1/2] wiki: fix link to vagrant page

[Arnaud]

Signed-off-by: Arnaud 
---
 wiki/src/contribute/build/vagrant-setup.mdwn | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/wiki/src/contribute/build/vagrant-setup.mdwn 
b/wiki/src/contribute/build/vagrant-setup.mdwn
index c13c82f5b9..26b57d0478 100644
--- a/wiki/src/contribute/build/vagrant-setup.mdwn
+++ b/wiki/src/contribute/build/vagrant-setup.mdwn
@@ -16,7 +16,7 @@ Vagrant support files are located in the `vagrant` directory 
at the root of the
 
 This directory contains:
 
- * `Vagrantfile`: [configuration file for 
Vagrant](http://vagrantup.com/docs/vagrantfile.html],
+ * `Vagrantfile`: [configuration file for 
Vagrant](http://vagrantup.com/docs/vagrantfile/),
  * `provision/setup-tails-builder`: idempotent provisioning script that is
run inside the virtual machine upon boot,
  * `provision/assets/build-tails`: build script to be run inside the
-- 
2.11.0

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Debian 9: Build fails consistently, name resolution fails sooner or later

[Arnaud]

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, and enough storage (I didn't find
where that one is defined btw).

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.

So yep, I'm living in Vietnam. Overall, the network is not that bad
here, however they have a problem with the underwater cable AAG (Asia
America Gateway). Basically, from time to time the AAG stops working,
and the AAG is the main cable that connects Vietnam to the rest of the
world. What happens then is a bit unclear to me, to say the least.

Well, from a user point of view, what happens is very clear. The web
becomes a bit unreliable. Sometimes, websites are very slow to load, or
become completely unavailable for a few minutes. Amazingly, google
searches are still fast (more on that later). I've seen `apt-get update`
on my machine starting very fast, then slowing down and down, then
stalled. So I opened my `sources.list`, got rid of the
`httpredir.debian.org` url, replaced by `debian.xtdv.net` (the only
Vietnamese Debian mirror that I know) to ensure my traffic remains in
Vietnam, and now it works like a charm.

From a technical point of view, what happens is quite unclear. I played
a bit with `nmap --traceroute --script traceroute-geolocation`, and this
is a great tool ! I can see that requests to
time-based.snapshots.deb.tails.boum.org go a long way through Europe.
Requests to www.vagrantup.com go through Japan, which seems a bit more
direct. Amazingly, requests to google go directly from Vietnam to the
States. Which explains why they are still fast when everything else is
slow, and which makes me wonder if google has private undersea cables.

Anyway, I'm no expert, and I'm not sure how to interpret these results.
I have no idea how it will look like when I run the same traceroute
tomorrow. So let's get back to Tails.

The build process involves downloading a lot of data. Most of it from
Tails server, and I think the problem here is just that the connectivity
in Vietnam right now is way too bad to handle that. Somehow it always
fails sooner or later, it timeouts or something.

From my understanding, I can change the Debian mirror used for
provisioning the VM. But when it comes to build the Tails iso, I have no
choice but to download the packages from the Tails mirror, right ? Same
goes for TorBrowser ?

Right now I'm working on tweaking the build system, and adding retries
here and there, so that the build keeps going and doesn't give up so
easily. I think that `apt-cacher-ng` should help me to mitigate the
problem, but up to now I destroyed the VM too often to take advantage of
it ;)

I'll keep trying and let you know how it goes.

Cheers !



If you were interested in all this conversation (a bit off-topic), you
might find the following links interesting:

http://www.submarinecablemap.com

https://www.citypassguide.com/en/travel/ho-chi-minh-city/daily/news/neverending-story-vietnam-and-the-undersea-internet-cable-ruptures





___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Maintaining I2P

[Alexandre Trottier]

Hello,

I'm interested in maintaining I2P for future releases of tails.
I'm profficient at python and bash, and do Sys Admin work as a job so I
feel like this is something that I could do.

I have never had to maintain a package for a distribution before so I'm not
sure where to start.

If anyone could provide some directions (white papers, pdfs, web sites,
etc...) or describe the overall process it would be greatly appreciated.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Debian 9: Build fails consistently, name resolution fails sooner or later

[anonym]

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, but
>> it was also a name resolution failure.
> 
> I too experienced build failures during
> `config/chroot_local-hooks/10-tbb`. It turned out to be caused by
> insufficient memory, of which I had 8 GB RAM (some took by the gnome
> session and system services) plus 8 GB swap. I could build successfully
> after increasing swap to 16 GB.

Interesting! We try to make sure that RAM builds can start only if enough RAM 
is available, but I guess there could be edge cases when close to the minimal 
amount.

Arnaud, how much RAM does your host system have, and which TAILS_BUILD_OPTIONS 
do you use? Also, please try adding `noram` to TAILS_BUILD_OPTIONS (but first 
make sure the VM is shut down, e.b. `rake vm:halt`).

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Debian 9: Build fails consistently, name resolution fails sooner or later

[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, but
> it was also a name resolution failure.

I too experienced build failures during
`config/chroot_local-hooks/10-tbb`. It turned out to be caused by
insufficient memory, of which I had 8 GB RAM (some took by the gnome
session and system services) plus 8 GB swap. I could build successfully
after increasing swap to 16 GB.

Hope this helps.

Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Presentation slides for Tails

[intrigeri]

ghostla...@autistici.org:
> There we have an alarming amount of materials. Making a request for zipped 
> archive
> "download all" link somewhere on that page? Folder structure within the 
> archive would
> be great.

I've added a link to the Git repository on
https://tails.boum.org/contribute/how/promote/material/
in the hope it helps people downloading the whole thing.

Cheers,
-- 
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.