[Tails-dev] Please review doc/7143-virtualization
I've been silently working for a while on fixing our oldest hole in the roof: Adapt documentation from Incognito! So please review doc/7143-virtualization. Consider this as an initial version, and please comment on it. There are still probably quite a lot of things to adjust. -- sajolida ___ 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] [review'n'merge:1.3] bugfix/8699-only-create-timestamps-in-Jenkins
Hi,
since the .{src,bin}pkgs stuff was merged, our build system is leaving
.{start,end}.timestamp files around, which are useless in most cases.
anonym has complained about it, so here's a branch that only generates
these files when building from Jenkins.
This means that we can't trivially generate .{src,bin}pkgs files
outside of Jenkins anymore. If someone is lacking this feature some
day, tell me and I'll revisit.
Candidate for 1.3.
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] Removing mutt and msmtp (or making them usable by default)
intrigeri: sycamoreone wrote (18 Jan 2015 20:25:29 GMT) : We should either just remove the packages or make them usable by default (like configuring the Tor SOCKS proxy) and then also make sure that there are no leaks in the mail headers, quotations, etc. Fully agreed. Same here so I created #8727. Feel free to assign it to you sycamoreone, that should be an easy one. -- sajolida ___ 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] OnionMail sysop list fwd: New statistics script.
Messaggio originale Oggetto:New statistics script. Data: Mon, 19 Jan 2015 15:55:58 GMT, Mon, 19 Jan 2015 15:47:56 GMT Mittente: sysop@louhlbgyupgktsw7.onion Rispondi-a: sysop.list@ridotnp5m5lp22gw.onion A: sysop.list@ridotnp5m5lp22gw.onion https://github.com/onionmail/onm-stat We call for the participation of managers of server onionmail sysop read usage statistics and let us know how many users are using OnionMail. After a year of working on this project we want to understand how many users use OnionMail. Is availiable on github a php-cli script that get the statistics of partial use. OnionMail Ptoject. ___ 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] OnionMail sysop list fwd: New statistics script.
Hi, please remove tails-dev@boum.org from your mailing-list; I've complained a few times already about off-topic email you're sending to us. I'd rather not have to block your email address from posting on tails-dev@boum.org, as I still have hopes that you send on-topic email here some day. Still, if we go on receiving all that spam from you, I'll probably just do that. 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.
[Tails-dev] [review'n'merge:jessie] whisperback:feature/python3
Hi, Please review whisperback:feature/python3, which should fix #7755 - Migrate WhisperBack to Python 3 (https://labs.riseup.net/code/issues/7755). More info on the ticket. 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.
[Tails-dev] RFC: Use homogenous Debian mirrors at build time (#8726)
Hi, we're currently hard-coding very little about the Debian mirrors we use at build time in our Git tree. Historically, this was meant to allow people to choose their preferred mirror (e.g. local mirror) and to cope with squid-deb-proxy's lack of flexibility. Nowadays, most of us use apt-cacher-ng, that can rewrite such URLs on the fly if needed (generally a bad idea, see below, but oh well), so probably we don't need this flexibility anymore. Besides, this level of flexibility has just hit us hard, by introducing a bug (#8715) that has taken many hours to three of us to debug. More generally, our stuff will be more consistent, easier to reproduce, and our QA process will be more reliable if we all use the same mirrors at build time as the one we configure in the ISO. So, I want to: 1. hard-code in auto/config all mirrors that shall be used at build time 2. update vagrant/provision/setup-tails-builder so that it doesn't configure LB_*MIRROR*, and deconfigures them if present 3. update wiki/src/contribute/build.mdwn so that it doesn't advise to set $LB*MIRROR* 4. update tails::builder so that it doesn't configure LB_*MIRROR*, and deconfigures them if present (Steps 1-3 are implemented already in feature/8726-use-homogenous-Debian-mirrors-at-build-time.) Thoughts? Use cases I've not thought of? 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] [review'n'merge] doc/know_issues
intrigeri: +This problem might be corrected in Tails 1.1 and newer when UEFI boot is used: +please report your test results back to us. I think that when UEFI boot is used doesn't make it clear enough what actual action a user has to take. In another, similar part of the known issues page, we write: Legacy support needs to be enabled in order to start Tails. To enable legacy boot support, enable 'Launch CSM' under boot (menu). I think that it's a good enough inspiration source to improve your proposed working. Do you want to try it? I will try to find something better. But I think the most important point here is to point users in the right direction. If the page just says UEFI boot that is something I can put into a search engine, maybe together with the brand and model number of my computer. -- sycamoreone ___ 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] Automated builds specification
Hi, On Sun, Jan 18, 2015 at 08:07:46PM +, sajolida wrote: bertagaz: 0. We might also want a mechanism for devs to pro-actively state they want to keep their branches being build even if the last commit was older than the last release. IIRC If I understand correctly, adding a dummy commit would bring back my branch in the set of branches that are automatically built. So maybe we don't need a dedicated mechanism handle those rare cases. That's the idea, having a timestamp file that would be use for this dummy commit. But it comes for free, sure. :) bert. ___ 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] Resolving the DNS Round Robin limit for mirrors
Thomas White: Not sure if anyone knows of this, but the following might be a good solution to scale the current mirror system and is used by a number of other open source projects. http://mirrorbrain.org Thanks for your input, We already considered using mirrorbrain and it is already mentioned on our blueprint for a new mirror infrastructure: https://tails.boum.org/blueprint/HTTP_mirror_pool Our current plan is to write a very minimal custom PHP script. The downside of mirrorbrain here is that it's quite big (probably too big for what we want to do) and it's not in Debian, not really authenticated, audited, etc. Still, if we want to further improve our custom script in the future, for example to include load balancing or geolocation, we might end up reinventing partly the wheel when more complex tools such as mirrorbrain already exist. Anyway, I don't feel like I'm the right person to best argue or decide on this. -- sajolida ___ 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.
