18:58:48 #startmeeting Tor Browser meeting 22 February 20201 18:58:48 Meeting started Mon Feb 22 18:58:48 2021 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:58:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:58:59 Hello! 18:59:01 err. year = 2021 18:59:07 hi! 18:59:11 hello! 18:59:16 Pad: https://pad.riseup.net/p/tor-tbb-keep 18:59:38 o/ 18:59:39 I'd like to welcome back pospeselr ! *cough* 18:59:42 o/ 18:59:51 oh hey fancy meeting you folks here 18:59:54 hi! 18:59:56 p/ 18:59:59 Welcome back pospeselr! 19:00:01 o/ 19:00:03 actually 19:00:17 and a special hi! to boklm too from me :) 19:00:23 :) 19:00:24 :) 19:00:31 hi everyone 19:00:58 o/ 19:02:17 Jeremy_Rand_Talos: I hope you're warmer this week than last week 19:02:44 wb pospeselr! 19:02:48 sysrqb, yes, heating just came back this morning. :) 19:02:58 :) 19:03:23 that's good news, at least 19:03:40 indeed, thanks :) 19:06:29 alrighty. 19:07:18 This is release week. 10.0.12 and 10.5a11 should be published ~tomorrow 19:07:48 10.0.12 is signed and ready to go. Signing 10.5a11 is in progress 19:09:08 We may have an emergency release later this week or next week, when we have a patch for fixing the recent issues on Arch/Fedora/OpenSuse/etc. 19:09:17 that will be a Linux-only release 19:10:07 a firefox issue? 19:10:15 Please upadte your boards, if needed: https://gitlab.torproject.org/groups/tpo/applications/-/boards 19:10:25 boklm: no, this is only affecting Tor Browser 10.0 19:10:41 it seems related to a change within glibc 2.33 19:10:58 ok 19:11:06 https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40328 19:11:33 sysrqb: it then seems we should disentangle all the bugs you duped over tho that one 19:11:45 but I duped tor-browser#40350 and tor-browser#40335 into that ticket 19:11:50 because not all users had a newer glibc i think 19:11:58 GeKo: i thought they did 19:12:23 but the tab crash seems related to freetype 19:12:28 while arch didn't update its freeetype versoin 19:12:45 yep 19:13:33 i suspect they are all related to an incompatibility in the sandbox 19:14:24 but I am planning on debugging tor-browser#40328 and then finding if the fix for that also fixes the crashes on the other distros 19:14:45 and then reopen one of the duped tickets if it doesn't solve the issue 19:15:43 sounds good. 19:16:11 i can re-open one of the freetype-specific crash issues for collecting more info there 19:16:26 but i think we have enough data for identifying the problem 19:17:59 acat did you successfully deply the android instrumented test last week? 19:18:09 *deploy 19:18:30 no, i think we'll need a machine that is kvm capable 19:18:36 hrm 19:18:41 nested kvm. 19:18:56 okay 19:19:10 the latest arm-based images are for android 25 19:19:22 and i couldn't make my scripts work with those 19:19:46 yeah, using an arm-bsaed emulator would be sadness 19:19:59 so i just made a MR with the scripts that work in my local setup, and i hope it's easy to make them work in a kvm-capable machine 19:20:12 okay 19:20:18 thanks 19:21:14 that's tor-browser-bundle-testsuite!14 19:21:22 yes 19:21:48 acat: hey, regarding tests. did you move the test suite run away from your user? 19:22:18 to a role account, so we can debug and run things in a group? 19:22:54 GeKo: i will do next, i was planning to update the repo to use the latest scripts in that MR in the machine 19:22:59 with the tb-tester user 19:23:37 just before you are leaving would be fine :) 19:24:18 sure 19:25:17 acat: did you try running a x86 emulator on the machine, even without kvm support? 19:25:26 (maybe that fails, i don't remember) 19:25:37 yes, it fails 19:25:40 okay 19:25:58 i did not try to run an old x86 image actually, that might work 19:26:27 but i think it will probably be still too slow 19:26:38 yeah 19:26:49 should I be added to the tb-tester ldap group? 19:26:59 boklm: yeah, I can add you 19:27:06 (or, request you be added) 19:27:09 thanks 19:28:52 This week we re-start the process of rebasing onto Mozilla beta 19:29:03 I'll open the usual tracking tickets for that 19:29:43 boklm: GeKo usually works on moving tor-browser-build onto the newer toolchain 19:29:55 but we're hoping you can start taking on that responsibility 19:30:05 ok 19:30:38 i can help you with that explaining where to look and what worked so far 19:30:46 i think he'll be happy to help you with the tricks he's learned 19:30:49 and where we still have open issues in the process 19:30:57 yeah 19:31:23 what all is being upgraded? 19:31:31 "Everything" 19:31:44 is the rebase for both desktop and android? 19:31:58 oh fun 19:32:16 pospeselr: it varies with every version, but it could be any part of the toolchain that mozilla update 19:32:32 boklm: the priority is getting android builds 19:32:41 boklm: the toolchain update is mostly for android 19:32:53 but i have a branch for linux, too 19:33:01 ^ 19:33:10 which i keep updated for the time in the future where we are at the point to actually merge it 19:33:12 I hope we don't hit any blockers for moving Linux 19:33:28 and, more importantly, to have something for the test suite to run 19:33:29 got it 19:34:50 I'll open new issues for this works and assign them 19:35:01 so android nightly builds are based on beta, and desktop still on esr but we plan to move them to beta too at some point? 19:35:17 yes, that's correct 19:35:30 hopefully that happens before we need to transition to the next esr, too 19:35:53 but I still like the idea of having a single stable tor-browser git brnach, and a single alpa 19:36:00 *alpha 19:36:19 and not maintaining four branches on two very different versions of firefox 19:36:31 (increasingly different) 19:38:09 okay, GeKo, i think you added the discussion topic on moving the nightly builds? 19:38:50 yes 19:39:00 i think we should start moving the nightly builds over 19:39:08 at the begin of this cycle 19:39:12 if there are no blockers left 19:39:14 wfm 19:39:29 which i think we don't have? 19:39:34 is that right, boklm? 19:39:43 yes, I think everything is ready 19:39:47 great 19:39:54 i saw boklm's nightly build had some issue with building win64 yesterday (?), while the new serer did not 19:40:03 maybe that was a temporary issue 19:40:18 but seeing the new server succeed was nice 19:40:22 so one thing to consider is that we likely need the old build system and the new one in parallel for the time being 19:40:27 yes, it looked like a temporary issue but I did not investigate much 19:40:41 boklm: no problem considering we have the new one 19:40:43 :) 19:40:47 i am not sure if everyone who is building releases has the resources for that 19:41:04 we have the sunet machine which can still do stable builds 19:41:19 but won't do nightlies and alphas based on the new system 19:41:40 and we have the tpo machine(s) which can only do the new thing 19:41:52 so that could be one pair for release building 19:42:02 i am not sure what else we have 19:42:55 ah, i see. yes 19:43:23 boklm said he could begin building again, too 19:43:26 * boklm has a local machine that can do both the new and old system 19:43:30 we *could* think trying to use the new system for stable, too, at some point 19:43:48 but i'd like to have at least some alpha cycles first 19:44:02 in theory, boklm and I could build stable, if needed 19:44:05 i guess ideally we just use the new one for 10.5 onward for desktop 19:44:15 yep 19:44:17 well, i can build, too 19:44:25 but i only have access to the tpo machines 19:44:38 and sunet? 19:44:42 that is my dev machine i had can't do full builds anymore 19:44:43 does the stable still need wheezy? 19:44:51 yes sunet 19:44:57 and the new tpo ones 19:45:07 boklm: yes 19:45:14 for centos 6 19:45:29 ah, I think the new system doesn't work with wheezy 19:45:34 yep 19:45:49 we'd need sacrifice centos 6 here, too 19:45:52 (with wheezy containers) 19:46:05 which would be a bit shitty in the midst of a series 19:46:21 in particular as we said 10.5 will be the first one without centos 6 support 19:46:23 that would be a large change for a stable series 19:46:32 yeah 19:46:34 so i would definitely prefer waiting until 10.5 stable 19:47:19 okay 19:47:35 so, i'll review the remaining patches for the switch and merge them this week 19:47:44 and then send an announcement mail to tbb-dev 19:47:48 and we are done :) 19:47:51 sounds good? 19:47:54 sounds good 19:47:58 sounds good to me 19:48:08 great 19:49:09 really good work on getting this working 19:49:15 congrats aboklm and GeKo 19:49:16 sysrqb: i might be able to do the alpha publishing and hopefully merge the publishing instructions, too 19:49:24 err, boklm 19:49:30 yeah, it's been boklm's baby 19:49:31 thanks 19:49:33 nice work! 19:50:12 GeKo: sure, sounds good to me 19:50:14 thanks 19:50:19 sysrqb: so, if you give me signed bundles i can plan to pick that up 19:50:25 cool 19:51:55 Jeremy_Rand_Talos: did you have any documentation about what changes you needed to make for working on cirrus CI? 19:53:29 sysrqb, most of it is pretty non-invasive. Added a few lines to the container start/finish commands in rbm.conf to support saving/restoring container filesystems, and added a few lines to some toolchain build scripts to support resuming from a halfway completed build 19:53:53 neat 19:54:11 sysrqb, I will try to write up more detailed docs, this literally first worked Sunday morning 19:54:25 ok, no worries or rush 19:54:30 i was just curious 19:54:33 congrats on getting it working 19:55:07 > 22 February 20201 19:55:11 weird, fix the topic 19:55:19 sysrqb, thanks :) Note that Namecoin doesn't use Rust, so I didn't patch the Rust build script, but the same thing I did for clang should work in Rust 19:55:26 Jeremy_Rand_Talos: is that without using CRIU? 19:55:36 boklm, right, it's not using CRIU 19:56:33 boklm, it's a really dumb implementation of checkpoints that abuses the fact that you can send SIGINT to GNU Make, run make again, and it'll resume where it left off 19:57:08 * sysrqb TIL 19:57:20 Lastly, huge thanks to acat for all of their work in tor browser 19:57:51 thanks, it was a pleasure :) 19:57:52 I have we see you around here after this week 19:57:58 *I hope 19:58:06 +1 19:58:10 +1 19:58:12 +2 19:58:12 +1 19:58:46 sure, i hope i can somehow keep contributing :) 19:59:42 Good luck with your next position :) 19:59:54 thanks! 20:00:02 okay, I think that wraps up this weekly meeting 20:00:04 thanks everyon! 20:00:07 +e 20:00:10 #endmeeting