[Tails-dev] Tails contributors meeting: Wednesday December 03
The next Tails contributors meeting is scheduled for: Wednesday 03 December #tails-dev on irc.oftc.net 9pm in Paris 8pm in London 3pm in New-York 12am in San Francisco Every one interested in contributing to Tails is welcome. Feel free to propose and prepare discussion topics. Either: - Raise them in this thread so that others can ask details and prepare the discussion too. - Update the blueprint of the agenda: https://tails.boum.org/blueprint/monthly_meeting/ - Make sure that the discussion tickets that you want to treat during the meeting are well detailed on Redmine. If you want to get involved but don't know yet how, please introduce yourself during the meeting, and be sure to tell us what you are interested in. The meeting might not be the most adequate time and place to properly introduce newcomers to the development process, but at least it should be a fine place to know each others, and schedule a better suited event. ___ 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] Release schedule for Tails 1.2.1
On 18/11/14 11:11, anonym wrote: > So here is the new tentative release schedule for Tails 1.2.1: > > 2014-12-01 TBB 4.x based on Firefox 31.3.0esr is *hopefully* out >Tag 1.2.1 in Git >Build and upload 1.2.1 ISO and IUKs > 2014-12-02 Test (early CEST) and release (late CEST) Tails 1.2.1 > > Who's available for testing the final 1.2.1 image on 2013-12-02? In case > there's a delay, who's available the day after, on 2013-12-03? 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? Cheers! ___ 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/7951-refactor-chroot-browsers
On 01/12/14 06:24, intrigeri wrote: > anonym wrote (30 Nov 2014 20:42:04 GMT) : >> On 31/10/14 16:02, intrigeri wrote: >>> Ooops, I forgot this one. Obviously the test fails, so I think I've >>> fixed it in e44f97c. >>> >>> No big deal, but it makes me question how much trust I can put, as >>> a reviewer, into "I've tested it (both manually and automatically) >>> very thoroughly" => how much change did happen on this branch *after* >>> you tested it thoroughly? > >> I have no good explanation for this. The test suite ran well for me but >> I may have focused more on the Unsafe Browser. > > Fair enough. > >> Any way, let's interpret that quote lightly, and in any case the >> merger should test the stuff to their satisfaction on their own, >> right? :) > > In theory, yes. In practice, given how resources-consuming the > automated test suite is, and the fact we currently have no way to > externalize its running, frankly I'm not keen to run again features > that the branch developer tells me they've run successfully: here, > I basically can't build an ISO while running the test suite without > harming the reliability of the latter, so it's partly blocking me from > working on anything else. (TODO++ upgrade that Mac thing lying here > and set it up to run the test suite :) > > What I try to do when reviewing is to run all the *other* features, to > catch unintended breakage at a distance. So, for the time being, > indeed I tend to rely on "I've run $FEATURES successfully". Can we > agree that this implicitly means "on the exact commit that I'm > proposing to be merged" in the future? Ok, I'll be careful with such statements from now on then. For the record, an image built from this branch at commit d35dbc7 passes all the features that directly use any of the chroot browsers: * features/firewall_leaks.feature * features/i2p.feature * features/unsafe_browser.feature Cheers! ___ 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] Building with Vagrant (doc update)
On 01/12/14 08:09, intrigeri wrote: > anonym wrote (30 Nov 2014 21:19:35 GMT) : >>> A working Vagrant can be installed from snapshot.d.o. Perhaps the >>> attached patch against master would be a decent way to address this >>> problem until either Tails' vagrant setup is updated (or replaced?). > >> Thanks! I applied it, [...] > > I'm concerned that we're suggesting people to install .deb's > downloaded over plain HTTP, on the system they're using to develop > Tails, without even a warning that it might be dangerous. What about: * pin the specific versions of vagrant and ruby-net-ssh * add http://snapshot.debian.org/archive/debian/20141010T042049Z as a Debian source * apt-get -o Acquire::Check-Valid-Until=false update * apt-get install vagrant ruby-net-ssh * remove http://snapshot.debian.org/... source * apt-get update ? Cheers! ___ 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] Building with Vagrant (doc update)
On 01/12/14 12:24, anonym wrote: > On 01/12/14 08:09, intrigeri wrote: >> anonym wrote (30 Nov 2014 21:19:35 GMT) : A working Vagrant can be installed from snapshot.d.o. Perhaps the attached patch against master would be a decent way to address this problem until either Tails' vagrant setup is updated (or replaced?). >> >>> Thanks! I applied it, [...] >> >> I'm concerned that we're suggesting people to install .deb's >> downloaded over plain HTTP, on the system they're using to develop >> Tails, without even a warning that it might be dangerous. > > What about: > > * pin the specific versions of vagrant and ruby-net-ssh > * add http://snapshot.debian.org/archive/debian/20141010T042049Z as a > Debian source > * apt-get -o Acquire::Check-Valid-Until=false update > * apt-get install vagrant ruby-net-ssh > * remove http://snapshot.debian.org/... source > * apt-get update I think this is better than the current unauthenticated workaround, so I pushed new instructions live. I also pushed some other improvements: 8fa1910 Suggest a safe workaround for installing Vagrant. 57a948c Quote code more consistently. bf53809 Remove workaround instructions for #6514. 8378e4b Update Vagrant memory usage figures. I dared doing this because I think the old instructions were downright confusing in some cases (e.g. the left-over workaround for #6514), and hard to follow (no code to copy-paste). My changes may still need improvements, though, so please have a look! Cheers! ___ 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.
[Tails-dev] [review'n'merge: 1.2.2] bugfix/7644-remove-mounted-image-from-vagrant-build-box
Hi, I've uploaded a new Vagrant basebox which fixes the tiny issue described in #7644. It's just a hacked version of the old basebox -- see the message in commit 2a0ca9e for details. One result is that the version reported inside the VM, e.g. in the hostname, stays the same as the old buildbox, and that's why I haven't updated `VIRTUAL_MACHINE_HOSTNAME` in `vagrant/lib/tails_build_settings.rb`. To test, checkout this branch and simply run `rake build` and the new basebox should be downloaded. Well, if you already have built Tails from the Git tree used, you must first rename/remove `vagrant/.vagrant` so your old setup isn't used. Any takers? KillYourTV? Cheers! ___ 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] Building with Vagrant (doc update)
hi, anonym wrote (01 Dec 2014 12:35:46 GMT) : > I think this is better than the current unauthenticated workaround, so I > pushed new instructions live. I also pushed some other improvements: Great! I think you messed up the
[Tails-dev] [review'n'merge:1.2.2] liveusb-creator:bugfix/8353-update-status-when-device-appears
Hi, I've had this usability issue on my personal todo list for (at least) months, along with a tentative patch. Now properly tested (by live-patching the code in a running Tails 1.2), so here we go => candidate for 1.2.2. I've described the steps to reproduce on the ticket. Given that new .deb's will be built within 48 hours for Tails 1.2.1, I didn't bother uploading one that would be superseded in two days. But once someone reviews+tests this, and merges it into liveusb-creator:master, then I'm happy to build the corresponding .deb, upload it to the stable APT suite, and run the corresponding automated tests on it. Cheers, -- intrigeri ___ 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.
[Tails-dev] Meeting: our Tails/Jessie progress and plans
Hi, so, we wanted to have that meeting in the 2nd half of September, and then we failed. Anyway, since then, we've made good progress, and things are starting to look quite good! 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. Alan, anonym? Anyone else interested? Cheers, -- intrigeri ___ 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.
