On 01/11/13 21:33, intrigeri wrote:
Alan wrote (01 Nov 2013 17:33:04 GMT) :
However, if nobody feels skilled to do it, I could commit to search
for a good fix of to propose the current patch as a bugfix branch.
The proposed fix seems way better than the current situation to me.
I'd rather
On 02/11/13 16:43, intrigeri wrote:
Tails refuses to boot from devices that expose themselves as
non-removable. Historically, all USB sticks said they were removable,
even if this is not correct according to the specification (removable
is rather for devices that can be fed with removable
On 02/11/13 17:32, intrigeri wrote:
sajol...@pimienta.org wrote (02 Nov 2013 16:06:02 GMT) :
Some users reported difficulties to connect to OFTC using Pidgin on
Tails 0.21. I managed to reproduce that bug. If I start pidgin from the
command line with the debug option,
First, make sure you
On 03/11/13 15:49, intrigeri wrote:
sajol...@pimienta.org wrote (30 Oct 2013 13:43:08 GMT) :
Actually, there are links to documentation that was renamed in
liveusb-creator too
Now, have a look at commit 0fea5a9 in liveusb-creator.
Reviewed, not tested (I assumed you've done this already),
sajol...@pimienta.org wrote (06 Nov 2013 11:35:12 GMT) :
Reviewed, not tested (I assumed you've done this already), merged into
master.
Actually, the link is updated all-right in the UI, and the link is
correct. Buy clicking on the link doesn't do anything. It was not doing
anything in Tails
On 31/10/13 21:23, Kevin C. Krinke wrote:
General thoughts? Concerns? Addition TODO suggestions? Anyone?
I tried it in Tails 0.21, and it's great. First I thought we would do a
quick and dirty applet but this one is a real clone of the original one.
I love it. Whatever I'll say here is
On 05/11/13 18:53, Kevin C. Krinke wrote:
With the Tails Clock project nearing completion (only testing,
translations and bugfixes left) I'm wondering what my next task /
project should be and so I'm opening this up to all to help decide.
Some ideas off the top of my head...
* Redmine
On 06/11/13 13:43, intrigeri wrote:
sajol...@pimienta.org wrote (06 Nov 2013 11:35:12 GMT) :
Reviewed, not tested (I assumed you've done this already), merged into
master.
Actually, the link is updated all-right in the UI, and the link is
correct. Buy clicking on the link doesn't do
Hi,
Kevin C. Krinke wrote (05 Nov 2013 17:45:51 GMT) :
Just tested on Tails 0.22 (feature_wheezy-0.22-20131105T1143Z-30e8c3c).
Note that there are two packages in addition to python-tz that are
required. To install Tails Clock on 0.22, perform the following:
JFTR, 0.22 won't be based on
Hi Kevin,
Kevin C. Krinke wrote (05 Nov 2013 17:53:32 GMT) :
With the Tails Clock project nearing completion (only testing,
translations and bugfixes left) I'm wondering what my next task /
project should be and so I'm opening this up to all to help decide.
Some ideas off the top of my
On 2013-11-06 8:03 AM, sajol...@pimienta.org wrote:
On 31/10/13 21:23, Kevin C. Krinke wrote:
General thoughts? Concerns? Addition TODO suggestions? Anyone?
I tried it in Tails 0.21, and it's great. First I thought we would do a
quick and dirty applet but this one is a real clone of the
Hola!
On 2013-11-06 8:42 AM, intrigeri wrote:
JFTR, 0.22 won't be based on Wheezy: these images have 0.22 in their
name only to indicated that the feature/wheezy branch is currently
based on the code that will be called 0.22 in December. The nightly
builds based on the devel branch are much
Great idea. This could become a holding pen for a bunch of tickets that
then become easy-to-collect requirements if there are new pools of funding
for development available.
On Tue, Nov 5, 2013 at 6:56 AM, intrigeri intrig...@boum.org wrote:
Hi,
when discussing with Zack a few days ago, I
Dear Friends
I'd like to know how I could unsuscribe from your mailing list.
Thanks a lot
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
intrigeri wrote:
This stuff (+ 2 minor polish commits of mine) can be tested in:
[...]/tails-i386-feature_wheezy-0.22-20131105T0917Z-30e8c3c.iso
Ok.
I wonder if we really want to start the ibus daemon and applet unless
logged in with a locale that needs one of these input methods, so I've
Hi,
intrigeri wrote (12 Oct 2013 15:47:58 GMT) :
Then, I hereby propose we make newly created system partitions 2.5GB,
Implemented in feature/bigger-system-partition, candidate for 0.22.
No change in Git, only a feature branch (same name) in
liveusb-creator, and a snapshot .deb in
winterfa...@riseup.net wrote (06 Nov 2013 16:26:12 GMT) :
Bug #5624 seems to indicate we want to start the IBus daemon always, since
it must be started at login time to be fully usable (environment variables
must be set up). See mentions of restart X in that bug report, and final
dot under
Hi,
Kevin C. Krinke wrote (06 Nov 2013 15:15:04 GMT) :
On 2013-11-06 8:42 AM, intrigeri wrote:
* .config/tailsclock/settings reads:
# DO NOT EDIT - This file is overwritten automatically. #
May I ask why? Isn't manual configuration supported?
When / why would manual configuration be
winterfa...@riseup.net wrote (06 Nov 2013 18:00:57 GMT) :
intrigeri wrote:
I'm convinced, marking the ticket as resolved. Thanks for clarifying.
Would you happily add a sub-sub-[...]-section to contribute/design,
that points to the relevant added script, and documents this?
I would see it in
On 2013-11-06 12:47 PM, intrigeri wrote:
Whenever a configuration option is changed in the prefs dialog, the
entire file is re-written. #LazyProgramming
Should I do something different there?
I suggest loading the config file when the prefs dialog is open.
Monitoring changes of the config
Hi,
I was taking a look of this bug tails-greeter: reset passphrase on failure
https://labs.riseup.net/code/issues/5904, but I think it is already solved in
the greeter, or there is something missing?
Cheers,
Andres
___
tails-dev mailing list
Andres Gomez Ramirez wrote (06 Nov 2013 20:12:58 GMT) :
I was taking a look of this bug tails-greeter: reset passphrase on failure
https://labs.riseup.net/code/issues/5904, but I think it is already solved in
the
greeter, or there is something missing?
You're totally right: I can't reproduce
Hi,
A draft preliminary plan could be:
1. Have Tails Installer write down the UUID in boot loader config on
initial install
2. Have Tails Installer preserve the UUID in boot loader config on
upgrade
3. Have Tails Updater (IUK) preserve the UUID in boot loader config
on
23 matches
Mail list logo
