Hi,
groente will be the RM for Tails 6.4.
The current plan is:
- Monday, June 17: build images, start testing
- Tuesday, June 18: releasing
@testers, please let the RM know how much time you'll have for manual QA
from Monday 17:00 to Tuesday 11:00 (Europe/Berlin)!
Cheers!
On 19/04/2024 04.02, Dillon Arlo via Tails-dev wrote:
Hi goats,
Hey!
Note that this is not a support forum, but for Tails development.
However, I will respond any way in hopes of you aiding us on this front.
If what I propose below doesn't work, please use our normal support
channels:
On 13/04/2024 13.55, NoisyCoil via Tails-dev wrote:
It looks like fixing uBlock is quite trivial, actually, so I did it
myself. When an upstream patch becomes available I will revert my
changes and apply that instead.
Why not submit your changes in a merge request to upstream? :)
On 29/03/2024 20.53, NoisyCoil via Tails-dev wrote:
en passing, to whoever caused the 6.1 retagging fuzz, I lost a full day
of testing work because of that, I hate you. Kidding <3
Actually this happens every single release, where there is a ~1 hour
window where you can fetch this
On 27/03/2024 12.18, groente via Tails-dev wrote:
Hi,
Anonym will be the RM for Tails 6.2
That is me! :)
The current plan is:
- Monday, April 22nd: build images, start testing
- Tuesday, April 23rd: releasing
@testers, please let the RM know how much time you'll have for manual QA
from
Hi,
We have no yet decided who will be the RM for Tails 6.1.
The current plan is:
- Monday, 2024-03-25: build images, start testing
- Tuesday, 2024-03-26: releasing
@testers, please let the RM know how much time you'll have for manual QA
from Monday 17:00 to Tuesday 11:00 (Europe/Berlin)!
On 30/01/2024 12.28, boyska wrote:
Hi,
We still don't know who will be the RM for Tails 6.0
I will be the RM for Tails 6.0.
The current plan is:
- Monday, February 26: build images, start testing
- Tuesday, February 27: releasing
@testers, please let the RM know how much time you'll have
:
On Feb 1, 2024, at 5:25 AM, anonym wrote:
But, as already shown above, Tails allows you to customize it
extensively through the persistence feature. The Additional Software
persistence feature [3] allows you to keep any package from Debian
installed and up-to-date, so just install python3
Hi,
First of all, very impressive work! Damn!
On 21/01/2024 23.04, NoisyCoil via Tails-dev wrote:
In principle, making a universal arm64 image could be possible, but
asides from the firmware (storing different firmware for different
platforms on the same image may be feasible), the software
On 01/02/2024 04.46, Patrick wrote:
Python3-pip should be added back next release
It never was installed in any Tails release.
and with a global config to torify it by default.
You can make any single file (like `~/.config/pip/pip.conf`) persistent
with the Dotfiles persistence feature. [0]
On 07/07/2023 22.36, kb0...@juno.com wrote:
Greetings;
I have my Tails installed on a write protected 8gb Kanguru USB 3.0 flash
drive,
because it has a physical write protect switch.
I write protect it after installing and after any updates, physically
protecting Tails.
I have
On 20/06/2023 19.19, richard wrote:
Hi Tails devs,
So the legacy tor daemon recently got two new features in alpha you
should be aware of, proof-of-work and conflux circuits:
Thanks for the heads-up! This is very valuable!
- proof-of-work: Onion service providers will be able to opt-in to a
Hi,
Tails 4.26 is scheduled for January 11. We haven't decided who is gonna be the
release manager yet.
Dear manual testers, please tell tails...@boum.org how much manual testing you
can do on:
- January 10, later afternoon CET
- January 11, morning CET
Cheers!
Please ignore this thread where I mistakenly wrote 4.25 when I meant 4.26.
*tired brain*
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
Hi,
Tails 4.25 is scheduled for January 11. We haven't decided who is gonna be the
release manager yet.
Dear manual testers, please tell tails...@boum.org how much manual testing you
can do on:
- January 10, later afternoon CET
- January 11, morning CET
Cheers!
Hey!
Tails 4.25 is scheduled for release on 2021-12-07. I will be the release
manager.
Dear manual testers, please tell tails...@boum.org how much manual testing you
can do on:
- December 6, later afternoon CET
- December 7, morning CET
Cheers!
boyska:
Hi,
Tails 4.24 is scheduled for November 2.
Tails 4.24 is postponed to Friday, November 5. (Reason: Tor Browser 11 was
postponed until then.)
I will be the release manager!
Dear manual testers, please tell tails...@boum.org how much manual testing you
can do on:
- November 4,
anonym:
Hi,
Tails 4.23 is scheduled for October 5.
We haven't decided who is gonna be the release manager yet.
FWIW, I'll be the RM for this bugfix release. I'll start preparing it on the
morning (CEST) of 2021-10-04.
___
Tails-dev mailing list
Hi,
Tails 4.23 is scheduled for October 5.
We haven't decided who is gonna be the release manager yet.
Dear manual testers, please tell tails...@boum.org how much manual
testing you can do on:
- October 4, later afternoon CEST
- October 5, morning CEST
Cheers!
anonym:
Matthew Finkel:
Hello!
We are happy to announce the first Tor Browser 10.5.6 release candidate
for wider testing. Packages can be found at:
https://people.torproject.org/~sysrqb/builds/10.5.6-build2/
We lack a signature for sha256sums-unsigned-build.txt, please upload!
Never mind
Matthew Finkel:
Hello!
We are happy to announce the first Tor Browser 10.5.6 release candidate
for wider testing. Packages can be found at:
https://people.torproject.org/~sysrqb/builds/10.5.6-build2/
We lack a signature for sha256sums-unsigned-build.txt, please upload!
Cheers!
Hans:
Yeah, yeah, sigh, it's me again
Now I am running into a new issue, but I believe, something external happened.
For learning I removed all the downloaded things completely. Then I deleted
also ~/.vagrant.d/ in my home and started from the beginning with a new git
clone and a new,
Hans:
Am Dienstag, 20. Juli 2021, 13:49:47 CEST schrieb anonym:
In your previous email I see that you did some changes inside the tails
folder without committing them to Git. Tails will only include changes that
are in Git, and will refuse to build when you have uncommitted changes
Hans:
Additionally the deb-package, I put below ~/chroot_local-packages/ is not going
to be
installed (maybe, because XFCE is not installed, as
kali-undercover.deb needs got XFCE dependencies).
The chroot_local-packages feature has frequently been broken, but I suspect
there is another
from boyska and anonym, who just finished the 4.20 release process!
BLAZE IT!
[0] Presumably with intrigeri as mentor since I'm on vacation! :)
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe
Romper Stomper via Tails-dev:
Is it true that the “tails” ports are controlled by the NSA?
I'm not sure what you mean with "ports". However, NSA doesn't control anything
related to Tails to our knowledge, and we do what we can to defend against it, e.g.:
Hi,
As you might have noticed, 4.19~beta1 (for the Tor Launcher replacement) that
was planned for release yesterday is not out yet. The explanation is:
* I was supposed to prepare it, but I've been sick this week and haven't been
able to put in the needed hours
* We found some last-minute
intrigeri:
Hi,
A few months ago, GitLab Inc. open-sourced the "Reviewer" feature for
Merge Requests.
This allows keeping track _independently_ of:
- Who's responsible for bringing the MR to completion: the Assignee.
- Who's responsible for reviewing the MR: the Reviewer.
I must say
Hi!
Tails 4.17 is scheduled for March 23. The current plan is that
intrigeri is the RM.
tails-manual-test...@boum.org, please let tails...@boum.org know
whether you can do manual testing on March 22 (mid/late afternoon
UTC) or March 23 (morning UTC).
Cheers!
intrigeri:
Tails 4.16 is scheduled for February 23.
I hope anonym will be the RM.
I will be! :)
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email
Hey,
Due to CVE-2021-3156 for sudo [0] we are preparing an imminent emergency
release. The plan is to release Tails 4.15.1 tomorrow afternoon/evening (CET).
Please don't touch the stable tails.git branch until Tails 4.15.1 is publicly
released!
Cheers!
[0]
Justin McAfee:
I believe there's a certain expectation by the OP that window sizes will
be correlated with browser fingerprinting.
Indeed. Probably because this used to be an issue in Tor Browser, which it warned about
if you maximized the window. But this was solved in Tor Browser 9.0 (and
Hi,
Tails 4.13 is scheduled for December 15, and intrigeri is the Release Manager.
Dear manual testers, please let tails...@boum.org know if you can do manual
testing on December 14 (evening in Europe) and/or December 15 (morning in
Europe). Thanks in advance!
Cheers!
proc...@riseup.net:
On 10/29/20 3:18 PM, anonym wrote:
proc...@riseup.net:
On a related note, with restrict-stream-events set to true, I was still able to
access all stream events when testing with netcat in the workstation VM.
Initially it worked as intended and didn't pass this info
proc...@riseup.net:
Re-sending this in a human readable form:
Thanks!
A couple of months ago I was looking at locking down the amount of info leaked
to Tor Browser in case it is compromised - if/when stream events access is
enabled. my thought was to have the cake and eat it too.
I guess
Hi,
The Tails 4.12 release is scheduled on 2020-10-20, mark you calendars!
intrigeri has the honor the be the RM this time.
Manual testers, intrigeri will let you know the exact time for testing, but by
default it should be the day of the release and the day before, so the 19th and
20th of
anonym:
> So, here's the schedule I propose:
>
> # Tails 4.11~rc1
>
> I'd like the release candidate to include the latest possible Tor Browser 10
> alpha, so I'm trying to coordinate with the Tor Browser developers. My guess
> is that it will latest be on September 11, bu
Hi,
I will be the release manager for Tails 4.11, a major release (IMHO, see
below), scheduled to be available for users on 2020-09-22. Since it is a major
release, we'll have a release candidate too this time.
First, let me explain why I think we need a major release. There are two main
emma peel:
> intrigeri:
>> Hi,
>>
>> Cyril Brulebois (2020-07-29):
>>> Maybe we should make sure downloading over bittorrent finishes, and
>>> not only starts?
>>
>> This would make the manual testing session start a bit later (with "a
>> bit" being more or less long depending on the RM's Internet
Hi,
As far as I know there has been no discussion about who will be the RM for
Tails 4.9, so I'll apply our default rule that it will be kibi. Tails 4.9 is
scheduled to be released on 2020-07-28.
This will be a bugfix release.
Manual testers, please report whether you are available for
ding who to @mention, please mention @anonym and I'll
try to help!
2. Is this person already the assignee of the ticket you are posting to? If so
they will be notified any way, so we don't necessarily have to spam them
further by @mentioning them. But please err on the side of over-using @mention
Hi!
Today I rebased a development branch on stable and proceeded to absentmindedly
typed "stable" again when force-pushing:
git push -f origin stable
I.e. I force-pushed an old state of stable
(cf9e208256acc3db931c51cd4df1066452c856c9). Oops! :S
Looking at the last job for stable on
See e.g. https://gitlab.tails.boum.org/tails/tails/-/issues/17367
The attachment links in the Attachment section work fine. However, the links in
the comments where they were added have bad URLs:
https://redmine.tails.boum.org/code/attachments/download/2547/GNOME+Settings+Selection.png
It
intrigeri:
> While Redmine is down, if you need to view a Redmine issue, until the
> migration to GitLab is completed, you can now replace
> https://redmine.tails.boum.org/ with
> https://public-redmine-archive.tails.boum.org/ in the URL and access
> our fancy new static archive of Redmine
Iain Learmonth:
> Hi,
>
> On 20/03/2020 15:30, sajolida wrote:
>>> In Tails' threat model it is assumed that adversaries monitor the default
>>> bridges provided by the Tor Browser, and that our users want to avoid
>>> detection of that, so we are not interested in adding the default bridges
David Fifield:
> On Fri, Mar 20, 2020 at 11:51:41AM +0100, anonym wrote:
>> tl;dr: if Tails makes it too easy to use Meek bridges, could it overload the
>> current set of Meek bridges?
>
> The default meek bridge is already overloaded, unfortunately.
Ack. Tails will then *
Hi,
tl;dr: if Tails makes it too easy to use Meek bridges, could it overload the
current set of Meek bridges?
First some background: during startup Tails can be told to start Tor Launcher
so users can e.g. configure any bridges they want. So far we have not provided
any pre-configured
Hi, lists!
kibi (Cc:ed) will be the release manager for Tails 4.4, scheduled to be
released on 2020-03-10 (Mozilla seems to still agree :)). kibi, please give us
details about the release schedule, freeze, deadlines, etc if needed!
Manual testers, please report whether you are available for
Cyril Brulebois:
> Hi folks,
>
> I'd like to offer my apologies for my tendency to be, or at least appear
> to be, negative on the tails-dev XMPP channel when I'm preparing a new
> Tails release. I tend to be easily frustrated when I cannot do anything
> else than waiting for some cron job to get
Hi, Tails contributors!
As release managers, one of the things we produce is the changelog (i.e.
debian/changelog; we are *not* talking about the release notes). We have the
following questions for you, potential users of this file:
- Do you read the changelog at all?
- If so, what do you
intrigeri:
> If you're fine with this proposal, you may stop reading here.
I like this proposal! And with my RM hat on I even love it because I hate the
Fix committed → Resolved dance for new releases. :)
___
Tails-dev mailing list
Tails-dev@boum.org
intrigeri:
> Hi,
>
> intrigeri:
>> So I propose that we drop the "QA Check" field and instead, introduce
>> a "Needs Validation" status.
>
> This proposal from March 24 was implemented on June 2.
>
> Any feedback about how this change impacted your work so far?
100% optimization, 0% loss of
[Whoops, dropped tails-dev in my first attempt to answer.]
Georg Koppen:
> Tails - News:
>> This release is an emergency release to fix a critical security vulnerability
>> in _Tor Browser_.
>>
>> It also fixes [other security
>>
Elmar Stellnberger:
> My security infrastructure has suffered a significant setback since
> you have decided to separate usb and cd images. I need a read only
> image that can be booted from a read only usb stick or in my case
> from a read-only sdcard used with an sdcard reader that supports
>
intrigeri:
> So I propose that we drop the "QA Check" field and instead, introduce
> a "Needs Validation" status.
Sounds much simpler, awesome! +1
> Given we now have "mentions" (@nickname) on our Redmine, for the
> majority of cases, when the requested info can presumably be provided
> cheaply
intrigeri:
> Hi,
>
> scratch all that. With the updates Georg nicely shared, we can now
> tell that 3.13 will be a regular bugfix release and there won't be any
> 3.13~rc1. It's not 100% clear yet who will be the release manager
> but kibi agreed to be the fallback option.
>
> I expect the
alienpup:
> anonym wrote:
>> anonym:
>>> Testers, please let me know if you are available on:
>>>
>>> * 2019-01-19, to test Tails 3.12~rc1.
>>
>> Testers, how bad would it be for you if I tell you on the 18th that I
>> will need anot
anonym:
> Testers, please let me know if you are available on:
>
> * 2019-01-19, to test Tails 3.12~rc1.
Testers, how bad would it be for you if I tell you on the 18th that I will need
another day to prepare the release, so testing will happen on 2019-01-20 (and
maybe evening/nigh
Hi,
I'll be the release manager for Tails 3.12, which is a major release scheduled
for 2019-01-29. Here is the release schedule:
* 2019-01-18:
- Feature Freeze: All feature branches targeting Tails 3.12 should
be merged into the `devel` branch by noon, CET.
- Build and upload Tails
ambifarius:
> Hi anonym
>
> Thanks for your tip.
>
> I am still unable to build the Tails ISO 3.6.2 despite following your
> suggestion.
>
> Below are some of my questions based on the error message (please see
> attachment to this email):
>
> 1. Lines 150
ambifarius:
> Hi,
>
> I have problems building an ISO using the current stable release, 3.6.2
>
> rake build was aborted due to command error. Please refer to the attachment
> for details.
You tried to build from our 'master' branch, which we recommend against. Please
read the "Git branch
Hi, tails-dev@, tails-ux@ and tails-l10n@ lists!
You were excluded from u's proposal (only sent to tails-project@) to move
today's contributor's meeting to 16:00 CEST; below you'll see that she thinks
her proposal wasn't done on time, while others think it was and has passed, so
there's quite
Hi,
A patch for a "potentially exploitable crash" [0] in Firefox was made public by
mistake, resulting in Firefox 52.7.3esr and Tor Browser 7.5.3, so we need yet
another emergency release, Tails 3.6.2, which I'll be the RM for. This also
gives us the opportunity to sneak in a few other
Loic Dachary:
> Journalist using SecureDrop decrypt and read documents in an airgap Tails. I
> wonder which tools are available to search the documents stored in their
> persistence.
What about GNOME Files' built-in search functionality [1]? It works well enough
for me (although I can imagine
Hi,
I'll be the release manager for Tails 3.5, which is a minor/bugfix release
scheduled on 2018-01-23. The list of tickets targeting Tails 3.5 can be found
here:
https://labs.riseup.net/code/projects/tails/issues?query_id=276
Below you'll find the preliminary release schedule:
*
Fidel Ramos:
> Hello everyone. This is my first message to this mailing list. I'm a Tails
> user, but I haven't contributed code before, just donations.
Welcome, Fidel! I hope you won't be dissuaded by my negative answer...
> As you may know Bitcoin Cash is a fork of Bitcoin that has been
>
Uzair Farooq:
> Hey,
>
>> How long does it take to get a successful result of the verification
>> extension on your machine?
>
> It took half an hour for us. We haven't processed such large SHA files
> previously so I wasn't aware that it could take this long. Again, the
> problem here is that
sajolida:
> Uzair Farooq:
>> I've pushed two repositories:
>>
>> Extension: https://github.com/usman-subhani/verification-extension
>
> anonym: Can you check this one?
Sure!
The lack of atomic Git history makes it hard to wrap my head around it, but
luckily it's shor
Hi,
I'll be the release manager for Tails 3.3, which is a minor/bugfix release
scheduled on 2017-11-14. The list of tickets targeting Tails 3.3 can be found
here:
https://labs.riseup.net/code/projects/tails/issues?query_id=252
There are currently 170 open tickets listed. Go get 'em!
anonym:
> * 2017-09-26:
> - Finish testing Tails 3.2 by the afternoon, CEST.
> - Release Tails 3.2 during late CEST.
Tails 3.2 is ready to be released, but we'll follow the Tor Browser and Firefox
plan to delay the release until tomorrow.
Details: https://mailman.boum.org/piperm
Georg Koppen:
> intrigeri:
>> Hi,
>>
>> Georg Koppen:
>>> anonym:
>>>> Georg Koppen:
>>>>> Just to inform you about things we learned a couple of minutes ago: the
>>>>> Firefox release is due on Thursday.
the quoted parts below!
Cheers!
anonym:
> Georg Koppen:
>> Hi,
>>
>> Just to inform you about things we learned a couple of minutes ago: the
>> Firefox release is due on Thursday. It got postponed by two days mainly
>> to give 57 beta more publicity.
>>
Georg Koppen:
> Hi,
>
> Just to inform you about things we learned a couple of minutes ago: the
> Firefox release is due on Thursday. It got postponed by two days mainly
> to give 57 beta more publicity.
>
> We'll follow and release Tor Browser on Thursday as well.
Got it! It makes sense for
anonym:
> Besides, with what key would Tails be encrypted with? Our *public* key?
Here I meant: "Our *secret* key, so it can be decrypted with the *public* key?"
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listi
Anonymous:
> Have the developers considered the idea of releasing the
> Tails ISO as a GPG encrypted archive? This would create
> another verification method with distribution as users would
> need to decrypt the archive via a specific method in order
> to utilize the ISO and further verify it
anonym:
> anonym:
>> * 2017-09-14:
>>- Feature Freeze: All feature branches targeting Tails 3.2 should
>> be merged into the `devel` branch by noon, CEST. I'm open to make
>> exceptions if you can be online and responsive during that
>> afternoon
anonym:
> * 2017-09-14:
>- Feature Freeze: All feature branches targeting Tails 3.2 should
> be merged into the `devel` branch by noon, CEST. I'm open to make
> exceptions if you can be online and responsive during that
> afternoon, but ask me first!
>
anonym:
> ### ... and the checksums differ (i.e. reproduction failed).
> [...]
> sudo apt -o APT::Install-Suggests="true" \
> -o APT::Install-Recommends="true" \
> install diffoscope -t stretch-backports
It was reported to us th
anonym:
> git checkout 3.2~alpha1
Oops! That should be:
git checkout 3.2-alpha1
In other words, the "~" (tilde) should be a "-" (dash).
Sorry for the inconvenience!
Cheers!
signature.asc
Description: OpenPGP digital signature
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Tails and Tor contributors,
dear Reproducible Builds community,
We have sent out a first call [1] for testing to build Tails 3.1 reproducibly
and we have received some build reports. Thank you very much for your help! We
have since then tried
Andres Pavez:
> Hi,
> I have failed trying to reproduce Tails 3.1. I got a iso with a different
> hash.
> Then, I was able to successfully reproduce the failed iso again with
> the same hash.
>
> Attached you will find the info, I hope helps to improve the
> reproduction of Tails.
Thanks! Make
intrigeri:
> Hi,
>
> anonym:
>> * 2017-10-02:
>> - All branches targeting Tails 3.2 *must* be merged into the
>> `testing` branch by noon, CEST.
>> - The upcoming Tor Browser is hopefully out so we can import it.
>
> Ouch, I think this release sc
For the correct release schedule, please see "[Updated] Release schedule for
Tails 3.2", or:
https://mailman.boum.org/pipermail/tails-dev/2017-September/011642.html
Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
Hi,
[This is a repost of <19736ec9-e3b1-87f3-5752-eaeaac33a...@riseup.net> with the
correct dates. Please ignore the previous plan which incorrectly put the Tails
3.2 release on 2017-10-03!]
I'll be the release manager for Tails 3.2, which is a major release scheduled
on 2017-09-26. The list
anonym:
> intrigeri:
>> * it integrates nicely in a GNOME desktop (e.g. in terms of HIG ⇒
>>consistent UI & UX).
I did a quick and dirty test:
git clone https://github.com/Whonix/anon-connection-wizard
git clone https://github.com/Whonix/python-guime
iry:
> anonym:
>> All this looks promising, so to answer your question whether we're
>> interested: yes! :)
>
> Hi anonym! That sounds awesome!
>
>> I haven't looked at this in detail yet (from what I saw so far I
>> think some people will be sad over it usin
intrigeri:
> anonym:
>> (from what I saw so far I think some people will be sad over it
>> using Qt instead of GTK)
>
> As long as:
>
> * it's Qt5 (let's please stop adding apps that only work with the
>obsolete Qt4; we already ship Qt5 and the cor
Hi,
I'll be the release manager for Tails 3.2, which is a major release scheduled
on 2017-10-03. The list of tickets targeting Tails 3.2 can be found here:
https://labs.riseup.net/code/projects/tails/issues?query_id=198
Whoops, there are 182 of them right now! :S I suppose (hope!) there is
Patrice Mannoni:
> I highly recommend against this.
Ack. But what are we supposed to do with a recommendation lacking any sort of
argumentation/motivation? Please share your thoughts!
> And hope it isn't implemented over the short-term.
Tor Launcher (even the new one) would at best be a
iry:
> Hi Tails developers!
>
> Several months ago, anonym and I had a discussion about the future of
> anon-connection-wizard on the @tor-dev[0], where he said:
>
>> [snip]
Thanks for picking up this again!
> Now, though there are still a lot of improvements can be
Thanks for participating!
So the problem in your ISO image is that /etc/hostname gets all executable bits
set, which shouldn't happen. I've filed this as:
https://labs.riseup.net/code/issues/13623
nock, it'd be interesting to see if you can reproduce this issue again. So, can
you please retry
e managers
> cabal anymore.
>
> So, what should we do about it? I'll make the call as the 3.0 release
> manager if no consensus emerges, but I first need some input from
> a few people (at least anonym, Ulrike, and sajolida) to make up my
> mind, so please read on :)
>
> I s
___
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.
[Sorry if this is a ~repost -- my MUA crashed while sending the email.]
anonym:
> During mine and intrigeri's upcoming Stretch sprint we plan to build and
> upload Tails 3.0~rc1 on 2017-05-19 and release it on 2017-05-20. Testers,
> please let me and intrigeri know:
>
> * if yo
anonym:
> Hi,
>
> During mine and intrigeri's upcoming Stretch sprint we plan to build and
> upload Tails 3.0~rc1 on 2017-05-19 and release it on 2017-05-20. Testers,
> please let me and intrigeri know:
>
> * if you are available on 2017-05-19, late CEST
>
> * if y
anonym:
> Hi,
>
> During mine and intrigeri's upcoming Stretch sprint we plan to build and
> upload Tails 3.0~rc1 on 2017-05-19 and release it on 2017-05-20. Testers,
> please let me and intrigeri know:
>
> * if you are available on 2017-05-19, late CEST
>
> * if y
intrigeri:
> anonym:
>> This change will require some coordination with our infra's sysadmins,
>> though, so it might take a while for it to be applied.
>
> … unless "defaultcomp" remains unofficially supported for a little
> while, with a mere warning displa
Arnaud:
> Dear Tails,
>
> this is just a detail I'd like to discuss.
>
> When I did my first Tails build a while ago, I didn't specify any
> SquashFS compression setting. So I expected the compression to be the
> default. And amazingly, there's a setting called 'defaultcomp', which
> correspond
Arnaud:
> Hi,
>
>> In order to get Tails builds reproducible, we had to refactor the way we
>> use vagrant in our build system [1]. Under the hood, a lot of our build
>> scripts have changed, but for most use cases the transition should be
>> transparent.
>
> I have made some very minor cosmetic
Vasiliy Kaygorodov:
> On Wed, May 10, 2017 at 6:20 PM, anonym <ano...@riseup.net> wrote:
>>
>>
>> Might I instead suggest that you add vmdebootstrap to your PATH, i.e.:
>>
>> export PATH="${PATH}:${HOME}/ve/tails/bin"
>>
>> so y
1 - 100 of 889 matches
Mail list logo
