[Tails-dev] Typo fix for /doc/about/warning/index.en.html

2014-11-24 Thread Matt Kraai
Hi, doc/about/warning/index.en.html contains a typo: Rogues should be Rogue. Here's a patch to correct it: diff --git a/wiki/src/doc/about/warning.mdwn b/wiki/src/doc/about/warning.mdwn index 54b97f6..2c7fdc3 100644 --- a/wiki/src/doc/about/warning.mdwn +++ b/wiki/src/doc/about/warning.mdwn @@

Re: [Tails-dev] Typo fix for /doc/about/warning/index.en.html

2014-11-24 Thread intrigeri
Matt Kraai wrote (24 Nov 2014 13:43:16 GMT) : doc/about/warning/index.en.html contains a typo: Rogues should be Rogue. Here's a patch to correct it: Thanks, applied! ___ Tails-dev mailing list Tails-dev@boum.org

[Tails-dev] [review'n'merge:1.2.1] test/8161-more-robust-pidgin-connected

2014-11-24 Thread intrigeri
Hi, the proposed branch makes the Pidgin tests a bit more reliable. The only change outside the test suite is that it installs xdotool, which is now needed in the test suite (and I suspect we'll want to use it in a few other similar cases). Cheers, -- intrigeri

Re: [Tails-dev] [review'n'merge: 1.2.1] feature/8028-remove-unsafe-browser-test-menu-workaround

2014-11-24 Thread anonym
On 23/11/14 19:23, intrigeri wrote: Hi, anonym wrote (21 Nov 2014 14:22:58 GMT) : Please review'n'merge into stable and devel. I've already merged it into feature/jessie since the old workaround didn't work there due to (I think) GUI unresponsiveness, but this branch works reliably.

Re: [Tails-dev] keeping up with transports

2014-11-24 Thread sajolida
intrigeri: sajolida wrote (22 Nov 2014 11:55:50 GMT) : I started a ticket for that: https://labs.riseup.net/code/issues/8287 Thanks! So what is required for the inclusion of a new pluggable transports? * Having it in Debian ... stable or ${stable_codename}-backports. Anything

[Tails-dev] Jessie images outside of feature/jessie

2014-11-24 Thread Kill Your TV
I'm trying to build a Jessie image (to try my hand at https://labs.riseup.net/code/issues/8262) as I normally do for the standard Wheezy images. For example, I branched off of feature/jessie: git checkout -b kytv/tests I commited my changes which only touch files under features/. I then

[Tails-dev] Building with Vagrant (doc update)

2014-11-24 Thread Kill Your TV
The versions of Vagrant which are currently in Debian are not suitable for building Tails using Vagrant. The version in Wheezy is too old and the version in Jessie/Sid is too new. The build page advises to install Vagrant from Jessie but this cannot work. A working Vagrant can be installed from

Re: [Tails-dev] vpwned

2014-11-24 Thread Kill Your TV
On Mon, 3 Nov 2014 19:13:50 + (UTC) anonym ano...@riseup.net wrote: 02/11/14 00:48, intrigeri wrote: So, let's start listing usecases. Mine are: * downloading from / uploading to a FTP server * printing a document on a network printer * going through whatever steps a

Re: [Tails-dev] [review'n'merge: 1.2.1] feature/8028-remove-unsafe-browser-test-menu-workaround

2014-11-24 Thread intrigeri
anonym wrote (24 Nov 2014 16:56:38 GMT) : Done, earlier today. Thanks for taking the ticket! Merged, thanks. Cheers! -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list,

Re: [Tails-dev] keeping up with transports

2014-11-24 Thread intrigeri
Hi, sajolida wrote (24 Nov 2014 17:24:57 GMT) : In an intent to make all this digestible for the user documentation maybe we can try to summarize that. (I'm trying to find a way to have this fit in the main doc here not in the FAQ.) I'm not convinced that this information can possibly be

Re: [Tails-dev] Jessie images outside of feature/jessie

2014-11-24 Thread intrigeri
Kill Your TV wrote (25 Nov 2014 01:58:44 GMT) : I discovered that working images can be built from the branch feature/jessie, Right, due to https://tails.boum.org/contribute/APT_repository/. but how do others build jessie images from /outside/ of the main feature/jessie branch? I don't