05/06/14 22:11, intrigeri wrote:
Likely we want this into 1.0.1. Anyone up to add the LTS repo to APT
sources, with proper pinning? (I would suggest picking only selected
packages from there, since it's a free-for-all archive, so stuff may
not have seen the same amount of QA than regular
Hi,
Branch: feature/squeeze-lts-updates
Ticket: None
Please merge this branch into stable before the 1.0.1 freeze on Sunday,
2014-06-08.
The purpose of this branch is to install openssl and GnuTLS security
updates from Squeeze LTS. Hence the only difference compared to a
current stable build
06/06/14 14:35, intrigeri wrote:
anonym wrote (06 Jun 2014 12:21:11 GMT) :
Branch: feature/squeeze-lts-updates
I'll take it. Please file a ticket so I don't forget.
Done, assigned to you: https://labs.riseup.net/code/issues/7374
I'll also replace http.debian.net with the ftp.us.debian.org
Hi,
I have just removed Tor 0.2.4.21-1+tails1~d60.squeeze+1 [1] packages
from the stable APT suite, so the 0.2.4.22 ones will installed from now
on and, hence, be in Tails 1.0.1. (For the record I did the same for
devel in time for the 1.1~beta1 freeze; see my last comment on #7342.)
I have run
29/05/14 19:09, Alan wrote:
I've looked at all these tickets, closed/updated them as necessary,
and created a few new ones. These tickets describe my vision of what
the theme should look like in 1.1:
#7316: Fix system tray icon size in camouflage mode
I worked on this several hours. There
28/05/14 10:44, intrigeri wrote:
Hi,
intrigeri wrote (11 May 2014 19:45:19 GMT) :
tl;dr:
* If you are maintaining your Tails build VM manually, please
upgrade your Tails build VM to Wheezy, and install our custom
live-build package as documented on
everything to anonym but I think they would welcome help!
I've looked at all these tickets, closed/updated them as necessary, and
created a few new ones. These tickets describe my vision of what the
theme should look like in 1.1:
#7316: Fix system tray icon size in camouflage mode
#7325: Fix application
Hi,
As was decided during the last few days, Tails 1.1 will be postponed
[1]. Ignore the old release schedule for Tails 1.1 [2]!
Just to be clear, Tails 1.0.1 will be a point-release of 1.0 that's
still based on Debian Squeeze, and all the different 1.1 releases will
be based on Debian Wheezy.
27/05/14 09:08, intrigeri wrote:
anonym wrote (26 May 2014 18:14:27 GMT) :
I pinged the ticket and now Mike Perry seems to want to revert those
prefs [1] although the follow-ups makes it look like it's not decided yet.
... so it seems unclear what we should do for RC1.
My take
13/05/14 22:12, intrigeri wrote:
anonym wrote (13 May 2014 15:53:17 GMT) :
My suggestion would be that we don't use the emergency shitdown, and
simply sends a `halt`, which we did before, and which was much more
reliable. I know you want us to the same ways we except our users to
use, and I
13/05/14 22:48, intrigeri wrote:
anonym wrote (13 May 2014 15:54:22 GMT) :
Regarding the removal of test suite steps that look at notifications:
[...]
2. These steps were also useful to... actually test that we're
displaying these notifications. In the context of the test suite
27/05/14 20:03, intrigeri wrote:
Alan wrote (27 May 2014 17:36:04 GMT) :
- gnome-theme-windows8 (@git.tails.boum.org)
- gnome-panel-applet-window-picker (@git.tails.boum.org).
I'm happy to review the packaging once it's Lintian-clean (with
lintian --info --display-info --pedantic run on the
27/05/14 18:29, intrigeri wrote:
Hi,
anonym wrote (09 May 2014 10:38:41 GMT) :
I'll be release manager for the Tails 1.1 release. Here's the
preliminary release schedule:
2014-05-28 Feature freeze.
Tag 1.1-rc1 in Git.
Build and upload 1.1-rc1 ISO/IUKs
26/05/14 13:30, intrigeri wrote:
Alan wrote (12 Apr 2014 10:47:24 GMT) :
Created https://labs.riseup.net/code/issues/7013 for it,
with hopefully all the needed information.
Anonym, please assign me a subtask of this if you want and notify me by
personal email.
anonym, alan: how's
26/05/14 14:31, intrigeri wrote:
anonym wrote (26 May 2014 12:24:44 GMT) :
Any way, I guess not removing python2.6 any more is a mistake?
Nice catch! Yes, this does look like a mistake. I can safely remove it
from a runnig Tails/devel. I'll drop it directly in devel, if you
don't mind
26/05/14 15:14, intrigeri wrote:
Hi,
anonym wrote (20 May 2014 11:42:18 GMT) :
Luckily I found a proper fix, now ready for review in
bugfix/7065-keyboard-localization. It's in both Tails' and the Greeter's
Git, and a new Greeter snapshot has been uploaded to the feature
branch's APT suite
26/05/14 15:23, intrigeri wrote:
Hi,
anonym wrote (26 May 2014 12:38:40 GMT) :
In other words, a s/usewithtor/torsocks/ is all that's needed, right?
That would be my guess too, but I did not test it.
Given your two responses to this pull request, should I take it that you
reviewed
26/05/14 11:40, intrigeri wrote:
Hi,
anonym wrote (18 May 2014 22:33:47 GMT) :
This branch imports Tor Launcher 0.2.5.4 (from 0.2.5.3) + a few fixes
from master (see commit message). With this package, our delta against
upstream has only decreased since upstream has fixed several things we
26/05/14 11:07, intrigeri wrote:
Hi,
merged, thanks. Congrats!
Thanks!
Other (non-blocking) comments:
The entry in debian/changelog for 1.6.9.0 seems to lack everything
that can be found in the 1.6.7.0 and 1.6.8.0 upstream changelog
sections, that hence don't appear anywhere in
26/05/14 11:19, intrigeri wrote:
Hi,
intrigeri wrote (12 May 2014 14:45:05 GMT) :
I'll let you follow-up with the Tor ticket, and nag the TBB team
if needed.
I'm curious (and would like our browser in 1.1~rc1 to be as close as
possible to the one we'll ship in the final 1.1): any news on
think it's now ready for a final review and merge. I assigned the
ticket back to anonym as this should go pretty fast.
Merged!
Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from
26/05/14 14:57, intrigeri wrote:
Hi,
bugfix/7279-Florence-font workarounds #7279. Please merge for 1.1.
Assigned to anonym.
Reported to Debian as https://bugs.debian.org/749326.
I can confirm the bug and the fix. Merged!
Cheers!
___
Tails-dev
, and
the known workarounds, in doc/7280-VirtualBox-vs-syslinux-6.
Please review'n'merge for 1.1. Assigned to anonym.
Merged. And thanks for adding it to the 1.1~rc1 announcement! :)
Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
https
26/05/14 01:06, Alan wrote:
Hi,
This looks like a mix of Windows 8 and 8.1:
* the color theme is like the default in 8
* the background image is the default from 8
* the start button is only present in 8.1
Some screencasts of 8.0 seemd to have it. Perhaps is it an option?
I think there
interesting years ahead of us! :S
Please review'n'merge for 1.1. Assigned to anonym.
Works like charm. Merged!
Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send
14/05/14 15:57, anonym wrote:
09/05/14 17:36, intrigeri wrote:
However, even if I'd prefer a solution without a static sleep, I prefer
shipping this in 1.1 compared to our other options.
Luckily I found a proper fix, now ready for review in
bugfix/7065-keyboard-localization. It's in both Tails
19/05/14 00:57, sajol...@pimienta.org wrote:
anonym:
16/05/14 09:52, sajol...@pimienta.org wrote:
Anyway, I'm absolutely not sure I'll be able to fix that before the
freeze. I'd rather concentrate on the documentation upgrades. So if any
VirtualBox user want to have a look...
I haven't done
19/05/14 14:36, sajol...@pimienta.org wrote:
anonym:
Reading this, I get the impression that *all* guest features are broken,
but at least Shared folders work (but not auto-mounting since
`VBoxService` is broken). This exception may be worth mentioning, but I
won't block on it...
Ah shit
19/05/14 16:51, sajol...@pimienta.org wrote:
GNOME Orca was broken in Tails 1.1, this branch fixes it.
Ticket: #7251 - ORCA screen reader fails to start
Branch: bugfix/7251-orca → devel
Merged!
Cheers!
___
Tails-dev mailing list
14/05/14 00:35, intrigeri wrote:
Hi,
please review'n'merge
bugfix/looser-memory-requirements-for-upgrades-check into devel,
for Tails 1.1. As explained on the ticket, this allows us to avoid
bumping the hardware requirements, and to avoid having to implement
#5502 right now.
Tested in a 1
24/04/14 23:43, Andres Gomez Ramirez wrote:
Hello,
Attached I send a patch for Bug #5673 - Wheezy: way too small fonts in Tails
Installer
https://labs.riseup.net/code/issues/5673.
Looks good! Merged and a new liveusb-creator package has been built an
uploaded to devel and experimental.
Hi,
Branch:feature/torbutton-1.6.9.0
APT suite: feature-torbutton-1.6.9.0
Ticket:https://labs.riseup.net/code/issues/7097
This branch imports Torbutton 1.6.9.0 and (by necessity) fixes #7097.
Note that bot a Git and APT level merge are needed.
Normally I suppose intrigeri would take
Hi,
Branch: feature/tor-launcher-0.2.5.4
Ticket: None
This branch imports Tor Launcher 0.2.5.4 (from 0.2.5.3) + a few fixes
from master (see commit message). With this package, our delta against
upstream has only decreased since upstream has fixed several things we
patched in our Tor Launcher.
16/05/14 09:52, sajol...@pimienta.org wrote:
Anyway, I'm absolutely not sure I'll be able to fix that before the
freeze. I'd rather concentrate on the documentation upgrades. So if any
VirtualBox user want to have a look...
I haven't done a code review yet, but it looks very promising to me
11/05/14 11:55, intrigeri wrote:
Hi,
I have uploaded shared-mime-info 1.2-1~bpo70+1.tails1 to the APT suite
corresponding to this branch, since 1.3 won't make its way into Debian
sid-testing-wheezy-backports in time for Tails 1.1 (see
Debian #743942). This package cherry-picks the commit we
15/05/14 06:23, John Olsen wrote:
Gentlemen:
I regard myself as a power windows user and program in pascal, php,
basic, a couple variations of assembly and write MySQL stored
procedures. Yet, I have been unable to navigate through to the point
where I have an operating USB stick. Why?
14/05/14 01:57, intrigeri wrote:
Hi,
xulrunner is being phased out. Iceweasel 30 betas in Debian don't ship
it anymore. We use it to run tor-launcher. We have to migrate away
from it before we move to Firefox 31 ESR.
Details: https://labs.riseup.net/code/issues/7236
Sorry for the bad
07/03/14 16:20, Alan wrote:
Hi,
Alan wrote (07 Mar 2014 13:51:02 GMT) :
* HACKING has not been updated to document that one should run
the test suite before releasing (fixed in c31f5a5)
This was kind of intended, as it is far from complete and the
refactoring it is supposed to test
15/05/14 02:28, Nick Mathewson wrote:
On Wed, May 14, 2014 at 4:55 PM, anonym ano...@riseup.net wrote:
14/05/14 21:46, Nick Mathewson wrote:
Hi, all!
We're going to be releasing Tor 0.2.4.22 soon. I have a candidate
source bundle at [...]
Unless there's a lot of unexpected problems, am I
15/05/14 20:35, sajol...@pimienta.org wrote:
I've been working on fixing the build of the VirtualBox guest modules in
Tails 1.1.
ticket: 5972
branch: bugfix/fix_virtualbox_dkms_build
Summary:
- Good news: The build is fixed, way less hackish, and that was easy.
- Bad news: The
14/05/14 11:00, Andres Gomez Ramirez wrote:
But the patch is compound of two parts: one for obligatory password
and other that checks for admin password matching. I think this last
part could be keep.
Sorry, but I don't get it. I've looked as best I can on the patch, and
the only other thing
09/05/14 17:36, intrigeri wrote:
Hi,
bugfix/7065-keyboard-localization fixes issue #7065 for me.
Assigned to the RM (anonym) for review.
The solution I've found to this problem is partly implemented in the
greeter, and partly in the main Git repo, so it'll require two Git
merges + an APT
14/05/14 15:57, anonym wrote:
However, even if I'd prefer a solution without a static sleep, I prefer
shipping this in 1.1 compared to our other options.
Well, something also should be done so we don't get ['us', 'us'] when
'us' is the selected layout, which my current (simplistic) patch does
04/04/14 14:47, Alan wrote:
Please review and merge into tails-greeter:master
tails-greeter:bugfix/6959-persistent_printers.
I believe it fixes https://labs.riseup.net/code/issues/6959 Persistence
of printer broken in Tails 0.23
Please also merge bugfix/6959-persistent_printers-wheezy
09/05/14 17:36, intrigeri wrote:
bugfix/7065-keyboard-localization fixes issue #7065 for me.
While testing this branch I noticed that Alt+Shift doesn't switch layout
any more. Apparently GNOME nowadays expects grp\tgrp:alt_shift_toggle so
that should be fixed in tails-greeter.
However, we
14/05/14 21:46, Nick Mathewson wrote:
Hi, all!
We're going to be releasing Tor 0.2.4.22 soon. I have a candidate
source bundle at [...]
Unless there's a lot of unexpected problems, am I right to assume that
there's a good probability for 0.2.4.22 to be released before 8th of
June (the day
15/05/14 00:59, Kill Your TV wrote:
On Sun, 11 May 2014 09:20:59 + (UTC)
intrigeri intrig...@boum.org wrote:
Hi Kill Your TV,
I'm wondering what version of I2P you want to see in Tails 1.1. In the
devel branch, we're currently installing 0.9.12-1~deb7u+1 from your
APT repo.
If you
13/05/14 13:58, intrigeri wrote:
anonym wrote (13 May 2014 11:23:56 GMT) :
As the RM, I agree with all this. [...] I trust you'll deal with the
rest in time for the release.
Thanks a lot.
I'd like to start merging now (for the super-quick resolution), but I
have issues building liveusb
13/05/14 15:17, intrigeri wrote:
anonym wrote (13 May 2014 12:42:35 GMT) :
and --git-no-pristine-tar doesn't help (and
../liveusb-creator_3.11.6.orig.tar.gz exists)
FTR, we don't use pristine-tar for this package.
I just did what the building instructions said one should do when
11/05/14 13:50, intrigeri wrote:
Hi,
intrigeri wrote (10 May 2014 15:22:54 GMT) :
Test suite run in progress, I'll inspect results and
report back later (likely tomorrow).
Here we go!
I think my first failure may be a blocker, as it's a regression.
For the others, I don't know.
So,
09/05/14 12:38, anonym wrote:
The dates in June are pretty much set in stone as far as I'm concerned,
but the freeze and RC dates may be moved a couple days (so this time the
release schedule is indeed very preliminary) since I have other
commitments that may collide. More precisely, the May
10/05/14 14:08, intrigeri wrote:
anonym wrote (09 May 2014 14:24:40 GMT) :
Because of all this I've finally concluded that I would prefer to keep
on maintaining our sikuli/rjb adapter for the time being, and possibly
return to this upstreaming process if Rukuli shows promise to at least
stay
30/03/14 19:22, Andres Gomez Ramirez wrote:
Hi,
Do you think you could rebase your patch on top of the wheezy branch
of the greeter, and test it in an (experimental) Wheezy-based ISO?
You can download such an ISO on
http://nightly.tails.boum.org/build_Tails_ISO_feature-wheezy/
yes,
Hi,
I'll be release manager for the Tails 1.1 release. Here's the
preliminary release schedule:
2014-05-28 Feature freeze.
Tag 1.1-rc1 in Git.
Build and upload 1.1-rc1 ISO/IUKs.
2014-05-29 Test 1.1-rc1.
2014-05-30 Officially release 1.1-rc1.
01/05/14 12:20, intrigeri wrote:
hi,
anonym: our experimental APT suite has e.g. an oldish tails-perl5lib
compared to the devel and stable ones. I suspect something went wrong
with this part of the release process.
Woah, I had completely missed this email. I've now (AFAICT) fixed the
state
, a few commits every month).
[1] https://github.com/chaslemley/sikuli_ruby
[2] https://github.com/andreanastacio/Rukuli
anonym, bertagaz: want to have a(nother) look, and decide if you
prefer to do the upstreaming work now, or to commit to maintain our
own sikuli/rjb adapter on the long
Hi,
Branch:feature/torbrowser-24.5.0esr-1+tails1
APT suite: feature-torbrowser-24.5.0esr-1-tails1
Ticket:No
Please review and merge (both Git and APT suite wise) into devel. I'ts
already been merged into experimental.
I've run features/torified_browsing.feature in the automated test
merged it myself, as 3.13 has indeed disappeared from sid, and
all the builds we care about are broken. I'm leaving the ticket as
ready for QA, so that anonym can review it when he's back.
Looks good. My short tests didn't detect any immediate regressions on
two bare metal systems, and in KVM
06/05/14 18:46, intrigeri wrote:
hi,
a core developer added some VirtualBox/UEFI compatibility notes in
commit 349ebfe82. Thanks!
That was me.
The thing is, these reports are about an ISO built from a commit
I made on May 3rd; and, I only uploaded on the very same day a version
of
07/05/14 18:35, intrigeri wrote:
anonym wrote (07 May 2014 16:00:14 GMT) :
However, I don't think that's relevant as I was testing *DVD* boot from
the image I built.
Ah, OK. I've added this (very important) info to the test reports page.
This was what I though the known issue was about
01/05/14 13:14, intrigeri wrote:
anonym wrote (02 Apr 2014 14:37:19 GMT) :
Test suite
==
* Adapt test suite for Wheezy
https://labs.riseup.net/code/issues/6559
I've started already, and will try to complete this ASAP, to help
evaluate how much stuff is still broken
Hi,
Please review and merge the branch bugfix/7166-vagrant-memory-checks
into the devel branch, which fixes #7166 [1]. I've optimistically
assigned the ticket to Kill Your TV since s/he did the previous testing.
This time, a successful test means that you can build Tails in RAM like
this, which
26/04/14 11:54, intrigeri wrote:
Hi,
anonym wrote (24 Apr 2014 17:53:16 GMT) :
For the code review it may be useful to have a look at the (rather
trivial) backporting work I did, which can be found in our 'tor' Git
repo. The backporting to 0.2.4.21 can be found in isolation
Hi,
Please review and merge into devel:
Tails Git branch: bugfix/vagrant-ram-bump-for-wheezy
This branch simply bumps the Vagrant builder's RAM by 512 MiB (from 6.5
GiB to 7 GiB), which is necessary to complete builds due to Wheezy's
increased size on disk.
Note that in order to have these
25/04/14 11:46, sajol...@pimienta.org wrote:
Sorry for the short delay, but here is the branch that integrates the
logo in the most critical places:
- SVG source for the logo in different forms
- website
- splash screen
Branch: feature/logo
Tickets:
- #7088: Integrate the new
25/04/14 14:52, anonym wrote:
25/04/14 11:46, sajol...@pimienta.org wrote:
Sorry for the short delay, but here is the branch that integrates the
logo in the most critical places:
- SVG source for the logo in different forms
- website
- splash screen
Branch: feature/logo
Tickets
13/04/14 12:54, intrigeri wrote:
Hi,
feature/6608-OpenPGP-signature-verification-in-Nautilus completes the
steps to have seahorse-nautilus fully replace seahorse-plugins
in Wheezy. It therefore will solve #6608, #5516 and #7039.
Please review'n'merge in devel for Tails 1.1.
I tested it,
11/04/14 14:27, intrigeri wrote:
Hi,
bugfix/use-Wheezy-repo-for-debian-mozilla fixes #7063: we were still
using the squeeze-backports APT suite from mozilla.debian.net.
Candidate for 1.1, assigned to anonym for review, but again, if
someone else is faster, I guess he won't mind.
Luckily
Hi,
Please review and merge into 'stable':
Tails Git branch: feature/tor-0.2.4.21-1+tails1_d60.squeeze+1
APT suite:feature-tor-0.2.4.21-1-tails1-d60.squeeze-1
No code was changed in Tails' Git repo, so only an APT suite merge is
needed. This will simply install Tor 0.2.4.21 with the
21/04/14 12:27, Nusenu wrote:
Hi,
the code to blacklist heartbleed affected tor directory authority keys
has been merged about a week ago [1].
Do you have an ETA on when you are going to release it (tor and TBB
packages)?
As the release manager for the Tails 1.0 release I'm also
23/04/14 16:51, Nick Mathewson wrote:
On Wed, Apr 23, 2014 at 10:28 AM, anonym ano...@riseup.net wrote:
21/04/14 12:27, Nusenu wrote:
Hi,
the code to blacklist heartbleed affected tor directory authority keys
has been merged about a week ago [1].
Do you have an ETA on when you are going
of this feature would not
be a blocker.
For what it's worth, to me the feature parity with Incognito goal has
felt very arbitrary for years. Each feature should be evaluated in
itself, IMHO, and I think we've done a good job at that, including with
this one.
anonym: unless there are objections
15/04/14 12:43, intrigeri wrote:
anonym wrote (14 Apr 2014 15:33:33 GMT) :
Please review and merge feature/tor-launcher-0.2.5.3 into stable (for
the 1.0 release) and devel branches.
It seems that you forgot to push your changes to our Tor Launcher
repo, so I can't review this branch yet
08/04/14 22:49, intrigeri wrote:
Hi,
anonym wrote (08 Apr 2014 20:18:23 GMT) :
I'll be release manager for the Tails 1.0 release. Here's the
preliminary release schedule:
Thanks a lot!
Which Tails core people are available for testing on 2014-04-17 and
2014-04-28?
I can dedicate
11/04/14 19:20, Kill Your TV wrote:
Tails devs,
Please review and merge the following change for the upcoming Tails 1.0
git://repo.or.cz/tails/kytv.git bugfix/i2p_incoming
It's a small but important change, setting I2P to disable inbound
connections. Inbound connections are already
Hi,
Please review and merge feature/tor-launcher-0.2.5.3 into stable (for
the 1.0 release) and devel branches.
It bases the bundled Tor Launcher on version 0.2.5.3 (from 0.2.5.0)
which brings several upstream fixes and new translations. It also
contains the following new not-yet-upstreamed
Hi,
Please review and merge doc/bridge-mode-design into master for the Tails
1.0 release.
The branch simply adds a design document for of the bridge mode
feature, or Tor network configuration as I ended up calling it.
Cheers!
___
Tails-dev mailing
04/04/14 16:38, intrigeri wrote:
Hi,
please review'n'merge
bugfix/7022-use-stable-APT-suite-when-building-from-stable-branch into
stable, so that our builds from the stable branch use the right APT
suite. Candidate for 1.0 (otherwise the build from stable is broken,
anyway, so it's not as
09/04/14 20:24, intrigeri wrote:
Hi,
David Goulet wrote (09 Apr 2014 17:51:22 GMT) :
Here is my analysis of CVE-2014-2568 and CVE-2014-0131 in terms of
security severity for Tails.
Thanks a lot!
My temporary conclusion is: not worth taking the risk of introducing
regressions with a
Hi,
I'll be release manager for the Tails 1.0 release. Here's the
preliminary release schedule:
2014-04-16 Feature freeze.
Tag 1.0-rc1 in Git.
Build and upload 1.0-rc1 ISO and IUK.
2014-04-17 Test 1.0-rc1.
2014-04-18 Officially release 1.0-rc1.
20/03/14 11:24, intrigeri wrote:
Code
* NetworkManager does not auto-connect when MAC spoofing is enabled
https://labs.riseup.net/code/issues/6911
@anonym: do you want to take care of it?
For the record, this one has been fixed.
* Unusable documentation window
20/03/14 12:07, intrigeri wrote:
Hi,
(stealing the RM hat for a short while, by initiating this discussion.
anonym, I'll let you take care of bringing this to a conclusion.)
if we don't do anything special, then we'll release Tails 1.0 with the
same kernel (3.12) as 0.23. Given 1.0
like it), let's *not* do it for e.g. the Tails Greeter Git
repo, only for the Tails Git repo. Otherwise there will be complications
for the work on the 1.0 release.
I've got two additional questions, mainly for anonym (with his RM
hat):
* do you think you can take care, in a timely manner
Hi,
When generating the upgrade-description files for 0.23 I issued the
following command:
VERSION=0.23
PREVIOUS_VERSION=0.22.1
NEXT_VERSION=1.0
MAJOR_RELEASE=1
( cd $IUK_CHECKOUT \
./bin/tails-iuk-generate-upgrade-description-files \
Hi,
Ticket: https://labs.riseup.net/code/issues/6885
Branch: bugfix/6885-tor-launcher-localisation
This fixes the bug which broke Tor Launcher in all non-English locales.
See ticket for details.
Please review and merge!
Cheers!
___
Tails-dev mailing
14/03/14 12:02, intrigeri wrote:
Hi,
as expected, Linux 3.13.5-1 has migrated to testing, which breaks most
of our builds, and prevents me from doing the reviewing job I've
been assigned.
Dear RM, what's your ETA for proposing a fix?
Sorry, I have them downloaded and ready. It slipped my
14/03/14 15:07, anonym wrote:
14/03/14 12:02, intrigeri wrote:
Hi,
as expected, Linux 3.13.5-1 has migrated to testing, which breaks most
of our builds, and prevents me from doing the reviewing job I've
been assigned.
Dear RM, what's your ETA for proposing a fix?
Sorry, I have them
08/03/14 12:47, winterfa...@riseup.net wrote:
Commit aba712d6156 in Tails main repo devel branch can't be right.
It is checking out tails-iuk_completed for perl5lib.
It seems the IUK translation actually was errorneously commited to
perl5lib repo too.
Thanks for notifying us! Yeah, this was
20/02/14 17:04, anonym wrote:
13/02/14 01:22, anonym wrote:
I'll be release manager for the Tails 0.23 release. Here's the
preliminary release schedule:
Here's an updated release schedule for Tails 0.23:
2014-03-05 Feature freeze.
Tag 0.23-rc1 in Git
05/03/14 20:10, intrigeri wrote:
Hi,
preamble: I'd like to see this in Tails 0.23, since this will be the
first release when most users see incremental upgrades in action, and
it would be good for them if the IUK download time was a bit shorter.
I'm now running most of our automated test
03/03/14 14:23, intrigeri wrote:
Hi,
I've had a look at the rewritten branch, at commit 7d0ea0b.
rootALL = (tor-launcher)NOPASSWD: /usr/bin/tor-launcher
What is this useful for? root can already run any command as any user
without password, no?
Woops, indeed. Removed.
amnesia
28/02/14 14:08, intrigeri wrote:
Hi,
I've had a look at the branch, and here's a first set of comments
and questions. I'll test an ISO later.
First, congrats, this generally looks very good!
anonym wrote (27 Feb 2014 05:35:18 GMT) :
It also removes Vidalia.
Why? Last time we
04/03/14 21:25, anonym wrote:
In the long run we probably want to convince upstream that this is
a valid use case and have the description changed/complemented.
Agreed. I think a ticket about it should be created in the Tor
Launcher's Trac.
I have this on my personal TODO.
Done: https
28/02/14 15:02, intrigeri wrote:
Hi,
intrigeri wrote (28 Feb 2014 13:08:57 GMT) :
I'll test an ISO later.
The Tor Launcher says The Tor Browser will open after a Tor network
connection is established, which is untrue. Perhaps this string could
be parameterized by whatever environment
28/02/14 14:27, intrigeri wrote:
Hi,
intrigeri wrote (28 Feb 2014 13:08:57 GMT) :
I've had a look at the branch, and here's a first set of comments
and questions. I'll test an ISO later.
Also, I'd love to see the test suite updated accordingly, so that we
can check that no too obvious
04/03/14 19:06, intrigeri wrote:
Hi,
bugfix/6592-fix-races-with-check-for-upgrades fixes #6592 for me.
Candidate for 0.23, so that we suffer less when running the test suite
in a few days.
It was a bit difficult to follow the commits back and forth so I instead
reviewd the diff against
02/03/14 10:39, intrigeri wrote:
Hi,
Matsa wrote (01 Mar 2014 21:18:04 GMT) :
We are looking forward to translate it in french, could the RM tell us
when we can start, the deadline and, above all, the place to find the
strings to translate the UI?
There's still potential for changes, so
01/03/14 19:58, intrigeri wrote:
Hi,
anonym wrote (28 Feb 2014 14:44:00 GMT) :
28/12/13 23:50, intrigeri wrote:
For whatever reason, the TailsToaster (i.e. `@domain_name`) domain isn't
present for me (also checked with `virsh list`), [...]
Fixed by commit 0caac4a2, thanks.
Ah
28/02/14 13:56, winterfa...@riseup.net wrote:
+TOR_CONTROL_PASSWD='passwd'
Why do we set this?
Iceweasel (as amnesia) does not have access to the authentication
cookie, and shouldn't. If Torbutton cannot read the authentication cookie,
it refuses to talk to the control port, even when
27/02/14 17:17, Andreas Kuckartz wrote:
Any ideas?
In case you are using vagrant = 1.2, I'm aware of this issue. If you
use an older vagrant than that it's new to me. Which version are you using?
While I have an unpublished fix that seems to work, I want to take a
closer look before pushing it
501 - 600 of 890 matches
Mail list logo
