[Tails-dev] ASP offline issue: advice needed

Hi, A bug was found in Additional Software Packages (ASP) that make the install fail if APT lists are updated outside ASP and they reference new version of ASP installed packages. This is likely to happen every new Tails release. This is now solved when the user is connecting to the network after

[Tails-dev] RFC: Additional Software Packages plan

Hi, As you might already know, we are working on a user interface for Additional Software Packages: https://tails.boum.org/doc/advanced_topics/additional_software/ We summed up our findings in the blueprint at: https://tails.boum.org/blueprint/additional_software_packages/gui/ If you'r

Re: [Tails-dev] *Modified* release schedule for 2018, take 3

Hi, intrigeri: > So I'll update our calendar, Redmine etc. right away :) > It's OK for me te have Additional Software Packages improvements ready for 2018-08-28. Cheers ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/ta

Re: [Tails-dev] Replacing Florence with GNOME's own on-screen keyboard?

Hi, intrigeri: > We have issues with Florence design, implementation, and its poor > integration into GNOME; it's not getting any better over time. One > option we have is to simply drop it and instead rely on GNOME's own > on-screen keyboard. I've starting looking at GNOME OSK at GUADEC, and u

Re: [Tails-dev] Tails Greeter Accessability

est it out. Hopefully there will be some testing ISO available this summer. I'll stay you tuned and your testing would be much appreciated. Cheers, Alan ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To un

Re: [Tails-dev] Tails Greeter Accessability

hat. > If this gets implemented at some point, I’d be happy to test it out. Hopefully there will be some testing ISO available this summer. I'll stay you tuned and your testing would be much appreciated. Cheers, Alan ___ Tails-dev mailing l

Re: [Tails-dev] Onion Circuits upstream maintenance

intrigeri: > I agree that Tails' Redmine feels like the right place to handle > this. > Me too, and thanks Sascha for your patch ! > Now I'll let Alan comment on this, and more importantly perhaps on > the "who" question. > I'm happy to partcicpate t

Re: [Tails-dev] Help! JavaScript / GNOME Shell extension problem || removing topIcons

Hi, intrigeri: > one the remaining issues that make me a bit sad about the current > state of Tails/Jessie (scheduled to be released in two weeks) is: > > https://labs.riseup.net/code/issues/10576 > > Anyone at ease with JavaScript and/or the GNOME Shell extensions > system, who has time to gi

Re: [Tails-dev] Windows 10 theme for Tails/Jessie

Hi, On Tue, 27 Oct 2015 15:59:38 -0400 Christian Medel wrote: > I got it to work shortly, and this is the result : Congrats! If you need changes in the extension to change the position/color of some thinks that you can't change in a theme, feel free to ask me (no promise, but I'll try) Cheers

Re: [Tails-dev] Windows 10 theme for Tails/Jessie

Hi, Christian Medel wrote: > I guess I just booted in a normal Cinnamon session altogether. I don't think that it's a good idea to ship cinnamon on Tails. It's a *fork* of GNOME and would make the user experience under the camouflage too different than under the standard GNOME I think. > The ba

[Tails-dev] Greeter revamp: prototype time?

Hi, [please answer to tails...@boum.org] As you might now, we are working on revamping the greeter interface since more than one year. We came to a proposal, which is summarized in this blueprint: https://tails.boum.org/blueprint/greeter_revamp_UI/design_rationale_phase1/ I think it's mature en

Re: [Tails-dev] Tor Monitor build fails

Hi, Sascha Steinbiss wrote: > I can build everything perfectly directly after cloning: > > [vagrant@debian-8:~] $ git clone https://github.com/satta/tor-monitor.git > Cloning into 'tor-monitor'... > remote: Counting objects: 153, done. > remote: Compressing objects: 100% (74/74), done. > remote:

[Tails-dev] Reminder: help porting Windows camouflage to GNOME 3.14

Hi everybody! Long story short: we send a call for participation on porting "Windows camouflage" to GNOME 3.14. We got not serious answer. If nobody volunteers to do the job, next Tails major version will *not* include camouflage mode. Find below the full call. Cheers * * * Call for particip

[Tails-dev] Tor Monitor: don't show duplicate streams with the same destination in the same circuit

Hi, sajolida wrote: > Done in #10183. > After checking how this could be done, I'm really unsure. I currently display the stream Tor has. Deduplicating streams would mean to create another list of streams, which would not ma to Tor streams. Then, how should we update the status of the stream gro

[Tails-dev] Tor Monitor: don't show duplicate streams with the same destination in the same circuit

Hi, sajolida wrote: > Alan: > > intrigeri wrote: > >> sajolida wrote (27 Aug 2015 16:48:14 GMT) : > >>> C. Duplicate information > >> > >>> In the list of circuits I sometimes see duplicated lines. > >> > >> Technical nitpi

Re: [Tails-dev] Testing Tor Monitor

Hi, intrigeri wrote: > sajolida wrote (27 Aug 2015 16:48:14 GMT) : > > C. Duplicate information > > > In the list of circuits I sometimes see duplicated lines. > > Technical nitpicking: these are streams, not circuits :) > > > For example when connecting to heavy websites like YouTube. > > See

Re: [Tails-dev] [Review] Adding laptops which don't shutdown properly

Hi, sajolida wrote: > > But I was wondering how relevant it is to add computers there, as that > > list might never ends, wrt. to UEFI hardware? > > I think it's fine. In the current state of Tails, it is impossible for an hardware boot in UEFI mode to shutdown properly. Perhaps saying this lik

Re: [Tails-dev] Package Tor Monitor

Hi, bertagaz wrote: > Reading http://www.glatzor.de/projects/python-distutils-extra/, it seems > you can configure distutils-extra to disable the build_l18n target with > such a setup.cfg. Not sure that it's the one responsible of your problem > though. > No, because it will not build the .mo fi

Re: [Tails-dev] Tor Monitor build fails

Hi, u wrote: > Alan: > > I just tried to build the package and failed: > > > > $ git-buildpackage --git-debian-branch=debian > > gbp:error: Couldn't checkout "tor-monitor_0.1.orig.tar.gz": Execution > > failed: [Errno 2] No such file

[Tails-dev] Tor Monitor build fails

Hi, Sascha Steinbiss wrote: > Long story short, there’s a first version of a tor-monitor package in: > https://github.com/satta/tor-monitor > I just tried to build the package and failed: $ git-buildpackage --git-debian-branch=debian dh clean --with python3 --buildsystem=pybuild

Re: [Tails-dev] Package Tor Monitor

Hi, Sascha Steinbiss wrote: > You are definitely more familiar with the internals of the Python distutils > steps. > I am happy with any solution you propose as long as ‘setup.py build’ does not > generate a new POT file on each build (hence updating the timestamp) > but reuses a version that is

Re: [Tails-dev] Package Tor Monitor

Hi, Clement Hermann wrote: > Le 19/08/2015 23:42, Sascha Steinbiss a écrit : > Hi Sascha, welcome ! > > Long story short, there’s a first version of a tor-monitor package in: > > https://github.com/satta/tor-monitor > > First, thanks a lot! > I just I a look at it, and I was wondering : the pot

[Tails-dev] Testing with openqa?

Hi, At GUADEC I talked with SuSE people about testing. They use something called OpenQA[1] that looks like a software that does basically what our automated test suite does[2]: test installers, live isos and applications integrations by "clicking" on UI images in VMs. They are trying to convince o

Re: [Tails-dev] Package Tor Monitor

Hi, intrigeri wrote: > Alan wrote (17 Aug 2015 23:42:12 GMT) : > > Would someone knowledgeable please package: > > https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 > > Some more bits of info that might help people raise their hand: > [...] > Please

Re: [Tails-dev] Package Tor Monitor

Hi, sajolida wrote: > Alan: > > Would someone knowledgeable please package: > > https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 > > I don't have the skills to package this but I would be happy to test it > in Tails or elsewhere. How can I do that? C

[Tails-dev] Package Tor Monitor

Hi, Would someone knowledgeable please package: https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 Thanks by advance ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an

Re: [Tails-dev] [Tails-ux] Tails 1.5 - USB boot from Macbook Polycarbonate A1342 Late 2009

Hi, I'm forwarding you this feedback on 32-bits UEFI received on tails-ux: On Tue, 11 Aug 2015 20:34:20 +0200 "aka pseudonym" wrote: > USB boot from Macbook Polycarbonate A1342 Late 2009 now works with Tails 1.5. > (It sort of sometimes did with 1.4.1 and never with 1.4.) Well done adding >

[Tails-dev] OpenHelp documentation conference in September

Hi, I learned at GUADEC that there will be an open source documentation conference in September that may be very interesting for the people working on documentation. It is called OpenHelp and is from Sept 26 to Sept 30: http://conf.openhelp.cc Cheers __

Re: [Tails-dev] Heads up: changed ways to track review'n'merge requests

Hi! On Mon, 13 Jul 2015 09:51:38 +0200 intrigeri wrote: > in the "[Tails-dev] Getting rid of review'n'merge email on this list" > thread, we've decided to stop requiring review'n'merge email on this > list. Alternate ways to track such requests have been found and set > up, and are documented the

Re: [Tails-dev] [review'n'merge:1.5] feature/9381-ship-amd64-syslinux

> So, to clarify: now that u. has validated that this branch reaches its > goal, it still needs to be reviewed and merged for 1.5. Any taker? > Merged, thanks! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To u

Re: [Tails-dev] RFC: persistent Tor state

Hi, > anonym and I have made great progress on this front, and we would like > feedback from you folks regarding the state of our current reasoning > and preferred design: > > https://labs.riseup.net/code/issues/5462 > https://tails.boum.org/blueprint/persistent_Tor_state/ > I've read throug

Re: [Tails-dev] Getting rid of review'n'merge email on this list

Hi, intrigeri wrote: > A) Decide that the Atom feed is good enough and document it, with its >aforementioned limitation (so that people can adjust their config). >I volunteer to do that if we decide to go this way. > > B) Decide that it's not good enough, and then look into a push >n

Re: [Tails-dev] Fwd: Python 2, Python 3, Stretch & Buster

Hi! On Thu, 16 Apr 2015 20:44:07 +0200 intrigeri wrote: > The largest bits of our Python stuff is being ported to Python 3 > already, but it looks like it's time to stop writing new Python > 2 code, for good. Anyone wanting to refresh our blueprint about > remaining Python 2 stu

Re: [Tails-dev] underlay for UX or blueprints

Hi, intrigeri wrote: > Perhaps we should instead have: > > * An entirely different ikiwiki at https://blueprints.tails.b.o/. > I believe it would fulfill the needs you described, without the most > important drawbacks identified above. Also, it may allow us to fully > disable the web inter

Re: [Tails-dev] How to replace the green onion

Hi, On Sun, 15 Mar 2015 18:15:22 +0100 intrigeri wrote: > >> Do you want me to file whatever tickets are needed about it? > >> > > I'd appreciate it. > > I've updated #9002 to reflect what I believe is the consensus we've > reached, and I've assigned it to you. Thanks!

Re: [Tails-dev] How to replace the green onion [was: What do we miss to replace Vidalia]

Hi, On Sun, 15 Mar 2015 23:29:55 +0100 intrigeri wrote: > sajolida wrote (15 Mar 2015 19:46:47 GMT) : > >> I'm personally undecided wrt. which one of these two is the best. > > > Neither am I :) > > Then I'm all for "those who do the work decide"

Re: [Tails-dev] State of TAILS accessibility with Orca

Hi, sajolida wrote: > Hadi Rezaee: > > except the fact that i cannot start orca in the greeter > > Yeah, unfortunately that's a known issue: > https://labs.riseup.net/code/issues/7500 > What do you think about the proposed solution (from the above ticket): Easy solution: Add gnome-sta

Re: [Tails-dev] How to replace the green onion

Hi, intrigeri wrote: > Alan wrote (06 Mar 2015 21:04:46 GMT) : > > intrigeri wrote: > >> Now, in the first iteration, the information we want to convey to that > >> Shell extension is exactly one bit ("Tor is ready", and possibly "Tor > >> is d

Re: [Tails-dev] How to replace the green onion

Hi, sajolida wrote: > Regarding whether the onion turns red when Tor is not usable anymore > (for whatever reason that we still need to specify). This I can't tell > either. > To avoid regressions, let's just implement a very simple 1 bit extension (Tor/no Tor). > If you think that you need mor

Re: [Tails-dev] How to replace the green onion [was: What do we miss to replace Vidalia]

Hi, sajolida wrote: > intrigeri: > > Alan wrote (06 Mar 2015 21:12:43 GMT) : > >> sajolida wrote: > >>> I hereby propose to have the list of circuits accessible directly from > >>> the green onion as it is the case now in Vidalia. But I'm not s

Re: [Tails-dev] How to replace the green onion [was: What do we miss to replace Vidalia]

Hi, sajolida wrote: > Following-up on the ideas of: > > - Keeping the green onion as a permanent visual feedback on the desktop. > - Not breaking too much of what people have been used to unless we > have a good (UX) reason to do so (keeping what works in Vidalia). > - Integrating Tor Monitor

Re: [Tails-dev] How to replace the green onion

Hi, intrigeri wrote: > Alan wrote (22 Feb 2015 01:48:28 GMT) : > > intrigeri wrote: > >> Alan wrote (20 Feb 2015 19:43:10 GMT) : > >> > I'm not opposed to exposing a DBus interface in a future version of > >> > TorMonitor to provi

Re: [Tails-dev] review and merge feature/6999-compress-png

Hi, intrigeri wrote: > > Of course, this only make sense if we get a compression rate that is > > worth doing all that stuff... so maybe we should investigate c) before > > deciding on this and seem how the result affects the final ISO size. > > Exactly. I bet a couple doc branch reviews that th

[Tails-dev] Macbook Air EFI fixed

There is supposedly a bug with booting Tails on Macbook Air or Macbook Pro due to an EFI issue. According to your support channel, you recommend a program to install the Tails ISO on a USB drive. The recommended program does create a Tails/USB drive but it wont boot on a Macbook. The soluti

Re: [Tails-dev] Tails contributors meeting: Tuesday March 03

Hi, sajolida wrote: > We're not doing general plans and availability during monthly meetings > anymore since they are public. We only do short discussions on tickets > as listed on the blueprint. I don't know if we should revive that old > tradition... > I saw "Availability and plans for the nex

Re: [Tails-dev] How to replace the green onion [was: What do we miss to replace Vidalia]

Hi, Some precisions on my last email below. Alan wrote: > intrigeri wrote: > > I can imagine that we have a totally separate backend that monitors > > Tor's connectivity status > > Please note that I'm not aware of such a concept of "connectivity > stat

Re: [Tails-dev] Tails contributors meeting: Tuesday March 03

cement for vidalia[4] in tails/jessie. This is discussed on tails-dev[5] [1]: https://labs.riseup.net/code/issues/5464 [2]: https://mailman.boum.org/pipermail/tails-ux/ [3]: http://git.tails.boum.org/alan/tor-monitor [4]: https://labs.riseup.net/code/issues/6841 [5]: https://mailman.boum.org/pipermail/

Re: [Tails-dev] Git branches to delete: review needed

Hi, intrigeri wrote: > Alan wrote (22 Feb 2015 02:10:26 GMT) : > > * feature/edit-additional-software-conffile: this branch adds a > > subcommand to tails-additionnal software to ease creation/edition of > > its configuration. I don't remember why it never got me

Re: [Tails-dev] Git branches to delete: review needed

Hi, intrigeri wrote: > Please have a look and shout if there's something in there that we > should keep. > Looks good to me. > Also, if you're Alan, anonym, bertagaz or sajolida, look for your name > on that blueprint: there are a few branches I need your opinion about

Re: [Tails-dev] What do we miss to replace Vidalia

Hi! intrigeri wrote: > Would be good if this filtering idea was written down in a ticket > somewhere, though. Need a Tor Monitor "Affected Tool" value > in Redmine? > Would you please file this ticket? Cheers ___ Tails-dev mailing list Tails-dev@boum.

[Tails-dev] How to replace the green onion [was: What do we miss to replace Vidalia]

Hi! intrigeri wrote: > Alan wrote (20 Feb 2015 19:43:10 GMT) : > > On Thu, 19 Feb 2015 14:23:03 + > > sajolida wrote: > >> intrigeri: > >> > sajolida wrote (18 Feb 2015 11:32:17 GMT) : > >> >> intrigeri: > > [About the green onion] &

Re: [Tails-dev] [RFC] UX for ISO verification + Tails Installer + full upgrades [was: ISO verification automation proposals]

Hi, > - The rewording and graphics are to be taken care off by tchou and me. > Maybe we'll have to learn a bit of Python GTK... > Please note that Tails Installer is Python QT, not Gtk. Cheers ___ Tails-dev mailing list Tails-dev@boum.org https://mai

Re: [Tails-dev] Automated builds specification

is > >> build *after being locally merged into branch B*, or not. > >> Given that's what we're really interested in, and given > >> "Scenario 1 : reviewer" is clearer (answer is: yes), I guess the > >> answer is yes here too, bu

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

Hi! > I've tried it, and it looks great, congrats! > Thanks! > A few UI remarks: > > * I like it very much :) > > * I'm not sure about the subtitle in the title bar, that reads > "Display Tor circuits and streams": maybe drop "Display"? Anyway, > I'll let sajolida nitpick on such things :)

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

Tor Monitor gets notifications about > whatever streams and circuits Tor creates etc. But if Tor Monitor is > started after Tor has already opened streams and circuits, then it > needs to send a GETINFO (or whatever) command to get the list of > already existing cir

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

Hi, intrigeri wrote: > Alan wrote (15 Feb 2015 00:42:34 GMT) : > > intrigeri wrote: > >> I'd love to understand why this would be more useful than some > >> existing GNOME network monitor that we don't have to maintain, and so > >> far I fail to

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

Hi again, On Thu, 19 Feb 2015 14:23:03 + sajolida wrote: > intrigeri: > > sajolida wrote (18 Feb 2015 11:32:17 GMT) : > >> intrigeri: > >>> Alan wrote (12 Feb 2015 15:32:15 GMT) : > >>>>>> - Ability to close a circuit manually. > &g

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

Hi, intrigeri wrote: > >> > - Bandwidth Graph. > >> > >> Advanced feature IMO, already present in arm. If we care much about > >> getting this info graphically, then I think some GNOME system monitor > >> would be a better tool to satisfy the need (it would be a suitable > >> replacement in th

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

intrigeri wrote: > Alan wrote (09 Feb 2015 20:57:52 GMT) : > > Do we miss something else to replace Vidalia ? > > It would make sense to look at the Vidalia bugs we've suffering from > for years, to ensure we can drop our workarounds. E.g. the fact > Vidalia doesn&#x

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

Hi, intrigeri wrote: > sajolida wrote (11 Feb 2015 15:12:02 GMT) : > > $ python tormonitor.py > > [Errno 13] Permission denied > > Traceback (most recent call last): > > File "tormonitor.py", line 346, in > > app = TorMonitorApplication() > > File "tormonitor.py", line 316, in __init__ >

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

Hi, sajolida wrote: > I cloned your repo, installed python-stem, tried to run setup.py and > tormonitor.py and got errors for both. > > How can I test this from Tails? > > $ python setup.py > File "setup.py", line 10 > requires=['stem','gi'] >^ > SyntaxError: invalid syntax >

[Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

sues/6841 [2]: https://labs.riseup.net/code/issues/6842 [3]: http://git.tails.boum.org/alan/tor-monitor/ ___ 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:1.3] bugfix/8756-repair-local-packages

On Wed, 21 Jan 2015 18:32:39 +0100 intrigeri wrote: > this fixes a bug identified by Alan on > https://labs.riseup.net/code/issues/8724#note-12 > I'm giving up on this, which remains to be tested. See https://labs.riseup.net/code/issu

Re: [Tails-dev] Getting rid of Vidalia [Was: What to do about I2P in Tails?]

Hi, On Sat, 02 Aug 2014 17:33:33 +0200 intrigeri wrote: > Jacob Appelbaum wrote (27 Jul 2014 14:24:53 GMT) : > > Vidalia is unmaintained but it isn't currently a security problem. > > Long term, we need a different solution for sustainability, of course. > > Yes. Once Tor#8641 is implemented [1]

Re: [Tails-dev] Hybrid ISOs: need to reconsider the plan (#8510)

Hi, On Mon, 26 Jan 2015 12:38:07 +0100 intrigeri wrote: > Alan wrote (18 Jan 2015 13:40:37 GMT) : > > I'll do that within the week to all computers I have access to. > > Any regression detected? > No, but all the computers with a working DVD reader w

Re: [Tails-dev] [review'n'merge:1.3] feature/8719-mount-output-in-bug-reports

Hi, On Sun, 18 Jan 2015 12:17:23 +0100 intrigeri wrote: > this branch includes the output of mount(8) in WhisperBack bug > reports, for various reasons mentioned on the ticket. > > Please review'n'merge into devel for 1.3, thanks. > Merged, thanks! _

Re: [Tails-dev] Greeter mockups

Hi, On Tue, 03 Feb 2015 21:19:22 +0100 intrigeri wrote: > FYI I'm told the blueprint is now out-of-date comparing to the current > state of discussion and mockups. > Thanks for pointing this out. > See e.g. > https://labs.riseup.net/code/attachments/download/651/greeter1.png > > => likely thos

Re: [Tails-dev] [review'n'merge:1.3] bugfix/7450-too_easy_to_exit (on openpgp applet repository)

Hi, On Wed, 26 Nov 2014 23:19:43 +0100 Clement Hermann wrote: > I fixed #7450 in my Tails OpenPGP Applet repository, in the > bugfix/7450-too_easy_to_exit branch. It should apply cleanly on the > version currently in Tails : > https://git-tails.immerda.ch/nodens/openpgp-applet/commit/?h=bugfix/74

[Tails-dev] [review'n'merge:jessie] feature/7756-reintroduce-whisperback

Hi, Please review feature/7756-reintroduce-whisperback, which should fix #7756 - Reintroduce WhisperBack in Jessie ISOs (https://labs.riseup.net/code/issues/7756). More info on the ticket. Cheers ___ Tails-dev mailing list Tails-dev@boum.org https://ma

Re: [Tails-dev] [review'n'merge:1.3] feature/6992-whisperback-email-address

On Fri, 16 Jan 2015 20:19:45 +0100 intrigeri wrote: > please review'n'merge into devel for 1.3. > Details are in the commit message and on the ticket. > Merged thanks! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails

[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/l

Re: [Tails-dev] Hybrid ISOs: need to reconsider the plan (#8510)

Hi, > I prefer option C: #8524 won't tell us much anyway, it's merely here > to evaluate the size of the subset of Tails users who will have risks > of regressions a) they boot Tails from DVD; and b) their BIOS is buggy > enough to not boot properly from a DVD burnt from a ISO image. > It won't ac

Re: [Tails-dev] [review'n'merge:1.2.2] bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices

Hi! > > I reviewed the new patch but had a few concerns with it. Please > > have a look at https://labs.riseup.net/code/issues/6538 > > Ok I have made the required changes. > > Thanks! I'm not sure to have time to take care of that in the next few days thought. If someone else feels like it, do

Re: [Tails-dev] [review'n'merge:1.2.1] bugfix/7678-Tails-Installer-crashes-on-upgrade

Hi! On Wed, 7 Jan 2015 18:58:22 +0100 kurono wrote: > > > > -toplevels = config['liveos_toplevel_files'] - > > for f in toplevels: +for f in > > config['liveos_toplevel_files']: > > > > Ok the new version is in > http://git.tails.boum.org/kurono/liveusb-creator/ the branch i

Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell

Hi! On Sat, 03 Jan 2015 17:17:08 + sajolida wrote: > [...] Then I also think that it is important to request them > to send regular updates on their progress. Because if we have 5-10 > answers and they all start exploring the basics in parallel, then it's > important to be able to identify qu

Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell

Hi, On Thu, 01 Jan 2015 13:06:04 + sajolida wrote: > Alan: > > % Call for participation : port windows camouflage to GNOME 3.14 > > I added this to a branch. See the current version of the call here: > > http://git.tails.boum.org/tails/tree/wiki/src/news/windows_cam

Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell

Hi, On Wed, 31 Dec 2014 10:57:00 -0500 Daniel Kahn Gillmor wrote: > On 12/28/2014 07:03 PM, Alan wrote: > > > Please find below a blog post proposal. > > Thanks for this, Alan. I would be happy to see it published. A > couple native-english-speaker suggestions belo

Re: [Tails-dev] error

Hi, This is the public mailing list for Tails development. I forwarded your email to the public support list tails-supp...@boum.org. Cheers On Wed, 31 Dec 2014 17:24:55 +0100 oraj wrote: > Dear Sir > Yours new wersion of Tails 1.2.2 probably has an error.I tried create > iso on usb when this i

Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell

Hi, Please find below a blog post proposal. Cheers --- % Call for participation : port windows camouflage to GNOME 3.14 You are into GNOME development and want to participate to Tails? You improve your GTK and/or GNOME Shell theming skills and want to support users needing privacy and stealth?

[Tails-dev] quto; qted testing [was: feature/6880-torsocks-2, aka. drop Polipo and install torsocks 2.0]

Hi, intrigeri: > Alan wrote (25 Dec 2014 16:39:02 GMT) : > > I only did manual test of the modified applications > > and random other internet applications as I still don't have a > > reliable automated testing setup. If someone wants to run the > > automated

Re: [Tails-dev] fix-committed issues [was: Git/Redmine integration: fixing a regression with new goodies?]

> > * "fix-committed: #" will flag # as "Fix committed" > > > >This keyword MAY be used in the commit message when merging > >a branch with --no-ff. It MUST not be used anywhere else. If the > >reviewer+merger chooses not to use it, then they MUST manually > > flag the ticket

[Tails-dev] fix-committed issues [was: Git/Redmine integration: fixing a regression with new goodies?]

Hi, > * "fix-committed: #" will flag # as "Fix committed" > >This keyword MAY be used in the commit message when merging >a branch with --no-ff. It MUST not be used anywhere else. If the >reviewer+merger chooses not to use it, then they MUST manually flag >the ticket as "

Re: [Tails-dev] [review'n'merge:1.3] feature/6880-torsocks-2, aka. drop Polipo and install torsocks 2.0

Hi, > Alan wrote (23 Dec 2014 16:45:22 GMT) : > > I checked the diff and tested wget, APT, Totem and GnuPG that all > > work fine under experimental. Tickets and design doc liiks fine too. > > Cool, thanks for the review! > > Please test the branch once merged in

Re: [Tails-dev] [review'n'merge:1.3] bugfix/8470-clean-up-apt-pinning

> this branch removes obsolete APT pinning config for XUL extensions > we're now taking from the Tor Browser tarball, instead of from Debian. > Merged thanks! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To un

Re: [Tails-dev] Build failed in Jenkins: build_Tails_ISO_experimental #1457

These are the result of review and merges that built fine on my machine. I don't understand where is the problem... On Tue, 23 Dec 2014 10:15:18 -0800 (PST) tails-sysadm...@boum.org wrote: > See > > > Changes: > > [a

Re: [Tails-dev] [review'n'merge:1.2.1] bugfix/7678-Tails-Installer-crashes-on-upgrade

Hi, > Ticket: https://labs.riseup.net/code/issues/7678 > > I don't have yet a liveusb-creator repo yet, (If I remember correctly > already sent the requirement). So I am attaching the patch. > Thanks for the patch which I imported into liveusb-creator repository in the feature branch. I confirm

Re: [Tails-dev] [review'n'merge:1.2.2] bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices

Hi, > Ok done, I attached a new patch. > I reviewed the new patch but had a few concerns with it. Please have a look at https://labs.riseup.net/code/issues/6538 Thanks for your contribution! Cheers ___ Tails-dev mailing list Tails-dev@boum.org https:/

Re: [Tails-dev] [review'n'merge:1.3] feature/6880-torsocks-2, aka. drop Polipo and install torsocks 2.0

Hi, I checked the diff and tested wget, APT, Totem and GnuPG that all work fine under experimental. Tickets and design doc liiks fine too. The only issue blocking the merge are useless unset lines in wget wrapper: /usr/local/bin/wget includes unset http_proxy unset HTTP_PROXY

Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell

Hi, > >> > * let's specify how Tails/Jessie's Windows Camouflage should > >> > look like, and put the implementation ideas and pointers we have > >> > into a blueprint > > > I can do a blueprint specifying the must and extras. > > Awesome! > Please review https://tails.boum.org/blueprint/upda

Re: [Tails-dev] Meeting: our Tails/Jessie progress and plans

Hi, > intrigeri wrote (17 Dec 2014 17:07:26 GMT) : > > I say let's do that, cover what we can, and if it doesn't fit or if > > we need Alan and he's not here, then we can still schedule another > > meeting. Let's keep this thing rolling! > I&#x

Re: [Tails-dev] Release schedule for Tails 1.2.2

Hi, > Me and intrigeri are going to work together on the final image > building, starting early (CET) on 2015-01-13, and if we're efficient, > we may even try to release 1.2.2 on the same day. This may depend on > testers being "on call" late (CET) that day. > > So, testers, please let me know if

Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell

sajolida wrote: > intrigeri: > > Alan wrote (02 Dec 2014 14:24:35 GMT) : > >> Do we still want to provide Windows Camouflage? How much energy do > >> we want to put in it and who wants to participate? > > > > My current position is: > > > >

Re: [Tails-dev] Git/Redmine integration: fixing a regression with new goodies?

Hi, > * "will-fix: #" will flag # as "In Progress" > > * "fix-committed: #" will flag # as "Fix committed" > > It seems to work, see e.g. https://labs.riseup.net/code/issues/8359. > > So, if you folks are happy enough with that, I can encode this into > [[contribute/*]] (merge

[Tails-dev] Windows camouflage for Jessie/GNOME shell

Hi, Let's start thinking about Windows camouflage for Tails Jessie/GNOME shell (https://labs.riseup.net/code/issues/8064) Do we still want to provide Windows Camouflage? How much energy do we want to put in it and who wants to participate? If we want to keep shipping a windows camouflage for Tai

[Tails-dev] GNOME safety list report

Hi, Here is a quick summary of what happened on GNOME saftey list. There were very low traffic. * There was a thread about proposals for OPW, including : - "a metadata scrubber GUI, based on the tools from mat.boum.org." - disabling USB ports when screen is locked * There was an announce tha

Re: [Tails-dev] Meeting: our Tails/Jessie progress and plans

Hi, > > I think it's time to meet, talk and adjust our plans. I hereby > > propose a dedicated meeting at 4pm CET on December 18, 19 or 20. > > I do not expect to make it any of these dates. What about December 15, > 16, or 17? Worst case, if your proposed dates are the only ones that > work for

Re: [Tails-dev] Release schedule for Tails 1.2.1

Hi, > Mozilla broke TBB's deterministic build setup with ESR 33.3.0, and > while we may have linux32 builds of TBB 4.0.2 ready later today, > they'll be without QA. Therefore I think we should delay Tails 1.2.1 > with one day, so we test and release on 2014-12-03. Any objections to > this new plan

Re: [Tails-dev] Release schedule for Tails 1.2.1

Hi, > Who's available for testing the final 1.2.1 image on 2013-12-02? Me. > In case there's a delay, who's available the day after, on 2013-12-03? > No sorry. Cheers ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tai

[Tails-dev] setxkbmap under tails [was: Please test l10n status of Tails/Jessie]

Hi, On Wed, 08 Oct 2014 11:04:41 +0200 intrigeri wrote: > > "setxkbmap de" does not work. no error, but it simply stays in > > english. > > Both `setxkbmap us' and `setxkbmap de' seem to work here. The layout > indicator in GNOME's top panel isn't updated, but the active > layout is. > Using se

Re: [Tails-dev] On keeping Tails running with the laptop lid shut

Hi, > sajol...@pimienta.org wrote (06 Oct 2014 22:57:12 GMT) : > > exit-1 wrote: > >> gsettings set org.gnome.settings-daemon.plugins.power > >> lid-close-ac-action nothing > > Does this blank the screen to prevent overheating? No. This is lid-close-ac-action=blank which is current Tails default

  1   2   3   4   5   6   >