18:01:37 <GeKo> #startmeeting tor-browser
18:01:37 <MeetBot> Meeting started Mon Aug  1 18:01:37 2016 UTC.  The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:37 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
18:01:43 <GeKo> hi everybody!
18:01:48 <boklm> hi
18:01:56 <GeKo> we are probably not many today and i am basically not here as well :)
18:02:06 <GeKo> so we'll see how it goes
18:02:19 <GeKo> last week i've been on vacation
18:02:37 <GeKo> and started struggling with the release on the weekend today
18:03:15 <GeKo> i feel this struggle is continuing at least until tomorrow and then i hope i'll have another couple of days off
18:03:30 <GeKo> i plan to be back as usual monday next week
18:03:40 <GeKo> that's it for the status update from me
18:03:51 <arthuredelstein> hi everyone
18:03:57 <GeKo> o/
18:06:11 <arthuredelstein> sorry, I'm still writing my update...
18:06:24 * boklm can go next
18:06:29 <boklm> This past week I worked on #19410 and #19737, and helped build the new releases
18:06:37 <boklm> This week I'm planning to publish the new releases, work on #16551 and on adding tests for #8725
18:06:50 <boklm> That's it for me
18:09:37 <mikeperry> GeKo: ugh, Mozilla tagging releases afterwords is bad form.. plus we stopped getting release emails.. I'm sorry I dropped that. I didn't expect them to do that - I assumed the release was actually delayed :/
18:10:15 * arthuredelstein is ready to go now
18:10:16 <GeKo> yeah, and it wasn't :( the candidate build is from July 26
18:10:50 <mikeperry> maybe they can add us to some email listbot about candidate builds and (hopefully) their commits?
18:11:10 <GeKo> might be a good idea. i'll ask them
18:12:13 <arthuredelstein> This week I was mostly on vacation, but for the past couple days I worked on three patches: uplifting for the font whitelist patch (bugzil.la/1121643) and our system colors patch, and #19741.
18:12:38 <arthuredelstein> The last ticket turned out to be really mysterious and I still haven't tracked it down.
18:13:24 <GeKo> but it is reproducible, right?
18:13:26 <arthuredelstein> Also, while looking at the system colors patch I noticed that we're still leaking the user's system display settings on Windows. For example, the background color of a normally white web page
18:13:32 <GeKo> (i have not tested it yet)
18:13:42 <arthuredelstein> GeKo: Yes, it's reproducible. Just doesn't make sense to me yet.
18:13:51 <GeKo> ok
18:14:35 <arthuredelstein> I'll be posting a ticket about system colors on Windows.
18:14:50 <arthuredelstein> I plan to continue working on those this week.
18:14:53 <arthuredelstein> That's all for me.
18:15:31 <GeKo> okay, thanks.
18:15:54 <GeKo> who else is here? i know mcs/brade are away.
18:17:03 <sukhe> I can go next :)
18:17:13 <GeKo> hey! cool, sure :)
18:17:49 <sukhe> we have ported the Tor Browser updater patches to Tor Messenger and I am happy to report that the updater is working
18:18:06 <GeKo> wow, that's good news! congrats
18:18:07 <arthuredelstein> cool!
18:18:21 <sukhe> the MAR generation is kinda manual but that's not a big concern for now
18:18:47 <sukhe> there is just one small issue and that is that the updater in Browser can't seem to find the dynamic libraries on OS X and Linux (Windows is fine)
18:19:07 <sukhe> I thought this would be covered by #4234, #13379 and #18900 (nsUpdateDriver.cpp) but I am clearly missing something here
18:19:39 <sukhe> for example, the error on Linux is:
18:19:41 <sukhe> /tmp/tor-messenger/Browser/updates/0/updater: error while loading shared libraries: libmozsqlite3.so: cannot open shared object file: No such file or directory
18:19:52 <sukhe> (almost similar for OS X)
18:20:18 <sukhe> both of these go away by setting LD_LIBRARY_PATH and DYLD_LIBRARY_PATH to . so I was wondering what is a proper way of fixing this?
18:21:13 <sukhe> (we can end the meeting for now and discuss this later)
18:21:55 <GeKo> i guess we'd need mcs/brade here. i don't know what's wrong without looking closer
18:22:23 <sukhe> ok thanks, I will email them
18:22:51 <sukhe> what is left before testing is signing the MAR files but I don't see any major blockers there
18:22:57 <sukhe> that's it from me and the TM team :0
18:22:58 <sukhe> er, :)
18:23:17 <GeKo> do you plan to bake your own signing keys into the tor messenger?=
18:23:39 <sukhe> GeKo: for signing the MAR files, yes
18:23:46 <GeKo> okay.
18:23:52 <sukhe> I thought it would be good to have redundancy. do you think that's a good idea?
18:24:31 <GeKo> i was mainly asking what to expect with respect to our signing machine
18:24:43 <sukhe> in future, ideally, we would also like to sign the binaries on Windows and OS X but I haven't thought much about that yet
18:24:50 <GeKo> whether you want to use that setup as well
18:25:10 <GeKo> well, as i said boklm and i can sign the windows binaries for you already
18:25:44 <sukhe> ok that's great. OS X as well?
18:25:47 <GeKo> and os x should be doable too
18:25:50 <GeKo> yes
18:25:53 <sukhe> nice, thanks
18:26:06 <GeKo> i am about to hook boklm here up as well
18:26:19 <GeKo> we should be ready shortly (i hope)
18:26:48 <sukhe> great. we plan to release in two months or so with the secure updater, so I think that should fit with our timeline as well
18:27:11 <GeKo> sounds good. let us know if there is anything you need
18:27:26 <sukhe> thanks
18:28:31 <GeKo> not sure if mikeperry wants to give an update
18:28:44 <GeKo> meanwhile i have one item to discuss
18:29:10 <GeKo> i hope the signing goes well tomorrow (there is still hope)
18:29:26 <GeKo> boklm: i wonder what to do about the alpha and the osx diff?
18:29:48 <GeKo> should we reapply libfaketime stuff and rebuild?
18:30:18 <GeKo> or should we say: we found a machine that got different results for osx due to timestamping things and we are invetsigating?
18:30:37 <boklm> I am not sure it is due to timestamping, or something else
18:30:38 <GeKo> and ship the stuff you got? (and which i matched on the lxc machine)?
18:31:01 <boklm> so I am not sure reapplying libfaketime stuff would fix it
18:31:34 <GeKo> i see. so, given the tight timeline it might be okay for the alpha that we point the issue out but go with the stuff we have
18:32:24 <boklm> yes, I think we can open a ticket to investigate that, and point to that ticket
18:32:50 <GeKo> okay.
18:37:37 <GeKo> do we have anything else?
18:39:02 <GeKo> thanks everbody then *baf*
18:39:05 <GeKo> #endmeeting