All times are UTC.
00:02:38 --> gerard-majax has joined #instantbird 00:08:46 --> Alex1 has joined #instantbird 00:09:15 <-- gerard-majax has quit (Ping timeout: 121 seconds) 00:36:19 --> freaktechnik_ has joined #instantbird 00:37:50 <-- freaktechnik has quit (Ping timeout: 121 seconds) 00:37:50 * freaktechnik_ is now known as freaktechnik 00:52:47 <-- aleth has quit (Quit: :tiuQ) 00:54:53 --> clokep has joined #instantbird 00:54:53 * ChanServ sets mode +o clokep 00:57:37 <-- chrisccoulson has quit (Connection closed) 01:02:03 --> clokep_ has joined #instantbird 01:02:03 * ChanServ sets mode +o clokep_ 01:05:02 <-- clokep has quit (Ping timeout: 121 seconds) 01:05:02 * clokep_ is now known as clokep 01:17:37 <-- Bollebib has quit (Connection closed) 02:00:51 <-- clokep has quit (Ping timeout: 121 seconds) 03:59:11 <instant-buildbot> build #1563 of linux-nightly-default is complete: Failure [4failed compile] Build details are at http://buildbot.instantbird.org/builders/linux-nightly-default/builds/1563 04:29:51 <instant-buildbot> build #1783 of win32-nightly-default is complete: Success [3build successful] Build details are at http://buildbot.instantbird.org/builders/win32-nightly-default/builds/1783 04:54:50 <instant-buildbot> build #2949 of macosx-nightly-default is complete: Success [3build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-nightly-default/builds/2949 05:34:26 --> mpmc has joined #instantbird 06:06:52 <instant-buildbot> build #1784 of win32-nightly-default is complete: Success [3build successful] Build details are at http://buildbot.instantbird.org/builders/win32-nightly-default/builds/1784 06:50:41 <-- EionRobb has quit (Connection closed) 07:26:13 --> EionRobb has joined #instantbird 07:54:50 --> gerard-majax has joined #instantbird 08:18:41 <-- gerard-majax has quit (Ping timeout: 121 seconds) 08:32:16 --> chrisccoulson has joined #instantbird 08:41:53 --> aleth has joined #instantbird 08:41:53 * ChanServ sets mode +o aleth 09:12:33 --> gerard-majax has joined #instantbird 09:34:34 <-- Alex1 has quit (Quit: Instantbird 1.5 -- http://www.instantbird.com) 09:37:23 <-- gerard-majax has quit (Ping timeout: 121 seconds) 09:41:01 --> Bollebib has joined #instantbird 09:43:07 --> flo-retina has joined #instantbird 09:43:07 * ChanServ sets mode +qo flo-retina flo-retina 09:45:28 --> gerard-majax has joined #instantbird 09:53:30 <-- aleth has quit (Ping timeout: 121 seconds) 09:56:15 <instant-buildbot> build #473 of linux64-nightly-default is complete: Failure [4failed compile] Build details are at http://buildbot.instantbird.org/builders/linux64-nightly-default/builds/473 10:00:01 <-- flo-retina has quit (A TLS packet with unexpected length was received.) 10:01:28 <-- EionRobb has quit (Connection closed) 10:04:24 --> mpmctoo has joined #instantbird 10:09:26 <-- gerard-majax has quit (Ping timeout: 121 seconds) 10:12:36 --> flo-retina has joined #instantbird 10:12:36 * ChanServ sets mode +qo flo-retina flo-retina 10:49:05 --> clokep has joined #instantbird 10:49:05 * ChanServ sets mode +o clokep 10:52:57 --> gerard-majax has joined #instantbird 11:26:31 <-- flo-retina has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 11:26:40 --> flo-retina has joined #instantbird 11:26:40 * ChanServ sets mode +qo flo-retina flo-retina 11:27:54 <flo-retina> things like bug 1218193 make me sigh... 11:27:56 <instantbot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1218193 nor, --, ---, nobody, NEW, Tab strip background colour incorrect on OS X 11:28:12 <flo-retina> why do these colors need to change every other year? :( 11:31:56 <clokep> Because...progress. 11:33:28 <clokep> (I agree, it seems silly.) 11:42:39 <-- clokep has quit (Ping timeout: 121 seconds) 11:49:50 --> aleth has joined #instantbird 11:49:50 * ChanServ sets mode +o aleth 11:50:24 <-- aleth has quit (Quit: :tiuQ) 11:51:05 --> aleth has joined #instantbird 11:51:05 * ChanServ sets mode +o aleth 12:13:24 --> clokep_work has joined #instantbird 12:13:24 * ChanServ sets mode +o clokep_work 12:16:21 --> PingWiN has joined #instantbird 12:18:21 <-- pWnnn has quit (Ping timeout: 121 seconds) 12:28:01 <nhnt11> flo-retina: The colours didn't change 12:28:08 <nhnt11> On OS X I mean 12:28:23 <nhnt11> Ib looked fine until a recent nightly 12:39:39 --> afiksof has joined #instantbird 12:47:08 <clokep_work> So I left a build running last time I slept my computer. 12:47:14 <clokep_work> It's now finished...and I don't know why I was building. :-D 12:49:11 <flo-retina> nhnt11: do you mean the IB colors haven't changed, or the Firefox colors haven't changed and something else broke on IB? 12:49:34 <nhnt11> Oh, are you saying the colours changed upstream and that broke us? 12:49:56 <nhnt11> I thought you were referring to the colours changing subtly in os x releases 12:50:18 <-- afiksof has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 12:50:47 <aleth> Considering we're not using Australis, some unrelated change might have broken it 12:56:50 <-- aleth has quit (Ping timeout: 121 seconds) 13:08:56 --> aleth has joined #instantbird 13:08:56 * ChanServ sets mode +o aleth 13:09:35 <-- nhnt11 has quit (Ping timeout: 121 seconds) 13:15:00 <-- aleth has quit (Ping timeout: 121 seconds) 13:23:55 --> aleth has joined #instantbird 13:23:55 * ChanServ sets mode +o aleth 13:42:32 <-- mpmc has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 13:53:06 --> nhnt11 has joined #instantbird 13:53:06 * ChanServ sets mode +h nhnt11 14:21:29 <-- aleth has quit (Ping timeout: 121 seconds) 14:24:32 --> nhnt12 has joined #instantbird 14:24:32 * ChanServ sets mode +h nhnt12 14:25:46 <-- nhnt11 has quit (Ping timeout: 121 seconds) 14:25:46 * nhnt12 is now known as nhnt11 14:37:35 <-- flo-retina has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 14:37:51 <-- nhnt11 has quit (Ping timeout: 121 seconds) 14:53:07 --> aleth has joined #instantbird 14:53:07 * ChanServ sets mode +o aleth 15:01:14 --> flo-retina has joined #instantbird 15:01:14 * ChanServ sets mode +qo flo-retina flo-retina 15:07:48 --> nhnt11 has joined #instantbird 15:07:48 * ChanServ sets mode +h nhnt11 15:23:52 --> spz has joined #instantbird 15:26:08 <-- spz has quit (Quit: Instantbird 1.5 -- http://www.instantbird.com) 15:40:01 <-- nhnt11 has quit (Ping timeout: 121 seconds) 15:47:19 --> nhnt11 has joined #instantbird 15:47:19 * ChanServ sets mode +h nhnt11 16:05:26 --> arlolra has joined #instantbird 16:18:29 --> nhnt12 has joined #instantbird 16:18:29 * ChanServ sets mode +h nhnt12 16:19:37 <-- nhnt11 has quit (Ping timeout: 121 seconds) 16:19:37 * nhnt12 is now known as nhnt11 16:36:57 <-- nhnt11 has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 16:37:06 --> nhnt11 has joined #instantbird 16:37:06 * ChanServ sets mode +h nhnt11 16:43:37 <-- gerard-majax has quit (Ping timeout: 121 seconds) 16:49:14 <-- nhnt11 has quit (Ping timeout: 121 seconds) 16:57:00 --> nhnt11 has joined #instantbird 16:57:00 * ChanServ sets mode +h nhnt11 17:07:07 <-- nhnt11 has quit (Ping timeout: 121 seconds) 17:09:18 <-- mpmctoo has quit (A TLS packet with unexpected length was received.) 17:11:57 --> gerard-majax has joined #instantbird 17:21:04 <sukhe> hi. in a window with multiple conversations, assume a conversation is pushed to the end (and then you can navigate it by clicking on the ">") 17:21:34 <sukhe> but if you are in the first conversation (left most) and you get a message in the last conversation (right most), is there a way to get notified of the tab in which there was an event? 17:21:45 <sukhe> (conversation = tab) 17:22:10 <aleth> iirc the > is supposed to change colour? 17:22:30 <sukhe> right, but other than that, you still have to navigate to the tab 17:22:45 <sukhe> there is an option "notify of messages received in inactive windows" 17:23:07 <sukhe> I tried that it seems to work with varying degrees of success (sometimes it work and I get a notification on which if I click, takes me to the tab) 17:23:34 <sukhe> other times it doesn't. is that the usecase for that option? 17:24:04 <flo-retina> you get a notification only when the window isn't focused 17:24:29 <flo-retina> The ">" turns blue for a second or so when a new conversation tab is opened in a place where it's hidden. 17:24:30 <sukhe> oh I see. so if I am in the first tab, I wouldn't get a notification for the last tab? 17:24:47 <flo-retina> I think it should turn blue (and maybe even stay blue) whenever a message is received in a hidden tab 17:24:53 <flo-retina> right 17:25:44 <aleth> I'm not sure that's implemented though 17:26:19 <aleth> Could be added to tabbrowser.xml if it isn't. 17:26:23 <flo-retina> "it should" in that we would be happy to take a patch 17:26:27 <flo-retina> not in that it's currently working 17:26:45 <aleth> It sounds like the kind of thing Mic would have filed a bug for... 17:26:55 <sukhe> ok. I see. thanks. would you be willing to consider a discussion to improve this behaviour? I can open a ticket with the problem reported to us and then possible ways to fix it. 17:27:45 <aleth> sukhe: Sure, like flo-retina said, patches welcome :-) 17:27:55 <-- gerard-majax has quit (Quit: Leaving) 17:28:01 <sukhe> thanks! 17:28:19 <sukhe> (read that later) 17:31:55 <aleth> This is where the tabs change colour https://dxr.mozilla.org/comm-central/source/im/content/conversation.xml#268 17:34:28 <clokep_work> I'm 99% sure I filed a bug about this. 17:34:43 <aleth> Those attributes are watched by tabbrowser. 17:36:15 <clokep_work> bug 953890 17:36:17 <instantbot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=953890 enh, --, ---, nobody, NEW, Use arrowscrollbox buttons to notify of unread messages in tab overflow mode. 17:36:19 <clokep_work> Quite the technical title. :-D 17:36:27 <clokep_work> sukhe: ^ 17:37:07 --> gerard-majax has joined #instantbird 17:37:46 <sukhe> clokep_work: yes! same issue. thanks. 17:55:57 <-- gerard-majax has quit (Ping timeout: 121 seconds) 18:16:37 --> nhnt11 has joined #instantbird 18:16:37 * ChanServ sets mode +h nhnt11 18:30:07 --> Mnyromyr has joined #instantbird 18:42:18 --> nhnt12 has joined #instantbird 18:42:18 * ChanServ sets mode +h nhnt12 18:43:33 <-- nhnt11 has quit (Ping timeout: 121 seconds) 18:43:33 * nhnt12 is now known as nhnt11 19:05:09 --> gerard-majax has joined #instantbird 19:08:03 <-- aleth has quit (Ping timeout: 121 seconds) 19:12:53 --> nhnt12 has joined #instantbird 19:12:53 * ChanServ sets mode +h nhnt12 19:13:20 <-- gerard-majax has quit (Ping timeout: 121 seconds) 19:13:46 <-- nhnt11 has quit (Ping timeout: 121 seconds) 19:13:46 * nhnt12 is now known as nhnt11 19:14:29 --> aleth has joined #instantbird 19:14:29 * ChanServ sets mode +o aleth 19:40:29 --> gerard-majax has joined #instantbird 19:43:15 <-- nhnt11 has quit (Ping timeout: 121 seconds) 19:45:14 <-- gerard-majax has quit (Ping timeout: 121 seconds) 19:53:41 <-- aleth has quit (Ping timeout: 121 seconds) 19:55:17 --> nhnt11 has joined #instantbird 19:55:17 * ChanServ sets mode +h nhnt11 20:24:10 --> aleth has joined #instantbird 20:24:10 * ChanServ sets mode +o aleth 20:28:36 <-- nhnt11 has quit (Ping timeout: 121 seconds) 20:33:13 --> nhnt11 has joined #instantbird 20:33:13 * ChanServ sets mode +h nhnt11 20:49:11 --> abdelrhman has joined #instantbird 20:54:01 --> EionRobb has joined #instantbird 21:03:26 --> nhnt12 has joined #instantbird 21:03:26 * ChanServ sets mode +h nhnt12 21:04:26 <-- nhnt11 has quit (Ping timeout: 121 seconds) 21:04:26 * nhnt12 is now known as nhnt11 21:08:38 <-- abdelrhman has quit (Quit: Leaving) 21:18:12 <-- clokep_work has quit (Ping timeout: 121 seconds) 21:33:38 --> abdelrhman has joined #instantbird 21:34:51 --> nhnt12 has joined #instantbird 21:34:51 * ChanServ sets mode +h nhnt12 21:35:03 <-- nhnt11 has quit (Ping timeout: 121 seconds) 21:35:03 * nhnt12 is now known as nhnt11 21:43:14 --> gerard-majax has joined #instantbird 21:53:16 <-- instant-buildbot has quit (Quit: buildmaster reconfigured: bot disconnecting) 21:53:17 --> instant-buildbot has joined #instantbird 21:53:17 * ChanServ sets mode +v instant-buildbot 21:53:53 <flo-retina> aleth: do you remember what I should look at for the tooltool stuff? 21:54:27 <aleth> It should be in the logs 21:55:08 * aleth reaches for grep 21:57:06 <aleth> flo-retina: http://log.bezut.info/instantbird/151007/#m141 21:57:31 <aleth> oh, and you have to repush the no_tooltool removal patch 21:58:02 <flo-retina> so I've got 2 slaves at http://buildbot.instantbird.org/builders/linux64-nightly-default 21:58:09 <flo-retina> I wonder how I can select which one starts a build 22:00:12 <flo-retina> I guess removing the rj45 cable of the old slave is a fail-proof way to select the new slave 22:00:15 <instant-buildbot> build #474 of linux64-nightly-default is complete: Failure [4failed hg] Build details are at http://buildbot.instantbird.org/builders/linux64-nightly-default/builds/474 22:01:56 <flo-retina> bah, what does http://buildbot.instantbird.org/builders/linux64-nightly-default/builds/474/steps/hg/logs/stdio mean :( 22:02:54 --> mpmctoo has joined #instantbird 22:03:08 <Mook_as> Did you (or your package manager?) update buildbot on the slave? 22:03:09 <flo-retina> hmm, I have " Buildbot-Slave 0.9.0b3 " on the new slave and " Buildbot-Slave 0.8.9 " on the old one 22:03:40 <-- gerard-majax has quit (Ping timeout: 121 seconds) 22:03:47 <aleth> install buildbot.plugins.hg? 22:03:55 <aleth> whatever that is... 22:06:06 <flo-retina> well, that will force me to change the master's configuration, and possibly update buildbot on each existing slave, right 22:06:07 <flo-retina> ? 22:06:16 <aleth> uh... 22:06:43 <-- nhnt11 has quit (Ping timeout: 121 seconds) 22:08:16 * flo-retina installed 0.8.9 above the existing install, and is rebooting the slave 22:08:24 --> nhnt11 has joined #instantbird 22:08:24 * ChanServ sets mode +h nhnt11 22:09:00 <aleth> ah, I thought the mozilla centos repo would only have the one version 22:09:30 <flo-retina> it's not there 22:09:37 <flo-retina> it's installed separately using easy_install 22:13:52 <flo-retina> so... that old version doesn't start because my twisted is too new 22:16:54 <-- mpmctoo has quit (A TLS packet with unexpected length was received.) 22:17:43 --> mpmctoo has joined #instantbird 22:20:44 <flo-retina> so according to that log, I just need to download tooltool.py and put it in /tools 22:20:52 <flo-retina> But we need other changes, don't we? 22:22:10 <aleth> in im/, there's that patch I landed that got backed out again 22:22:46 <flo-retina> do you have a link? 22:23:30 <aleth> changeset: 18290:3b9fd652481c 22:23:35 <flo-retina> don't we need something like http://mxr.mozilla.org/comm-central/source/mail/config/tooltool-manifests/ ? 22:23:59 <aleth> hmm 22:24:17 <aleth> seems likely 22:24:25 <aleth> I thought that was in build/ 22:24:34 <flo-retina> that would be too easy 22:24:58 <flo-retina> I wonder if we could find some magic to make it use the tooltool config from mail/ automatically 22:27:44 <aleth> symlink? 22:28:50 <aleth> Though those tooltool-manifests are just a straight copy from mozilla/, so it seems like until a merge happens just copying it to im/config should be fine 22:29:38 <-- abdelrhman has quit (Ping timeout: 121 seconds) 22:30:10 --> abdelrhman has joined #instantbird 22:30:27 <aleth> hmm, they are not shared even between browser and b2g 22:31:09 <flo-retina> ah, the m-c clone worked the first time, in 572s :) 22:31:23 <flo-retina> fiber connection + wired network -> awesome :) 22:31:24 <aleth> good connection! :-) 22:43:04 <arlolra> flo-retina: where are you on https://trac.torproject.org/projects/tor/ticket/16759 22:46:15 <flo-retina> I don't really mind either way. I'm not an expert of en-US typography 22:47:14 <arlolra> k, thanks 22:51:04 <flo-retina> aleth: so, that build is in the 'compiling' step 22:51:11 <aleth> :-) 22:51:15 <flo-retina> weren't we supposed to fail during configure when the gtk version wasn't right? 22:51:21 * flo-retina is confused 22:51:32 <aleth> I don't think gtk2 exists any more? 22:51:42 * aleth doesn't remember 22:51:57 <-- mpmctoo has quit (A TLS packet with unexpected length was received.) 22:52:09 --> mpmc has joined #instantbird 23:11:03 <-- Mnyromyr has quit (Quit: ChatZilla 0.9.92 [SeaMonkey 2.38/20150923193515]) 23:15:49 <flo-retina> so, that build hasn't failed yet 23:16:59 <flo-retina> there's no way a build can finish successfully on that slave, as I haven't put the ssh private key 23:17:23 <aleth> plus there's the compiler issue (assuming you haven't landed the tooltool patch yet) 23:18:35 <aleth> but, the slave hasn't died again! 23:21:06 <-- PingWiN has quit (Client exited) 23:21:24 <flo-retina> I downloaded https://raw.githubusercontent.com/mozilla/build-tooltool/master/tooltool.py into the /tools/ folder on the slave 23:21:34 <flo-retina> so it's possible we can do the rest without physical access to the slave 23:22:11 <aleth> hopefully the rest is just a c-c commit 23:22:16 <flo-retina> yeah 23:22:24 <flo-retina> I don't know what decides which manifest file is used though 23:22:55 <instant-buildbot> build #475 of linux64-nightly-default is complete: Failure [4failed compile] Build details are at http://buildbot.instantbird.org/builders/linux64-nightly-default/builds/475 23:23:05 --> pWnnn has joined #instantbird 23:23:08 <flo-retina> I'm hoping it's not http://mxr.mozilla.org/comm-central/source/mozilla/testing/taskcluster/scripts/misc/build-cctools.sh#46 23:23:25 <flo-retina> "This script is for building cctools (Apple's binutils) for Linux" hmm, probably not :) 23:23:36 * aleth goes to commit the no_tooltool patch 23:24:56 <flo-retina> the build failed in vp9 asm stuff 23:25:04 <flo-retina> could be the yasm version mismatch Fallen mentioned 23:27:14 <aleth> flo-retina: Shall I go ahead and land a copy of mail/config/tooltool-manifests for im as well? 23:27:21 <flo-retina> maybe? 23:27:32 <flo-retina> AFAIK we have no clue of what that would do 23:28:20 <flo-retina> hmm http://mxr.mozilla.org/comm-central/source/mail/Makefile.in 23:28:29 <flo-retina> I wonder why this isn't just a build step copying the folder from browser/ 23:28:46 <aleth> That would be nicer. 23:29:06 * aleth thinks just landing it for now is a good way to see what it does ;) 23:31:20 <aleth> OK? 23:31:40 <flo-retina> I somehow suspect using tooltool isn't automatic, and we need to add a buildbot step for it 23:32:48 <flo-retina> looking at http://archive.mozilla.org/pub/thunderbird/nightly/2015/10/2015-10-23-03-02-34-comm-central/comm-central-linux64-nightly-bm77-build1-build1.txt.gz 23:32:49 <aleth> I'm more concerned it will get used but somehow fail in accessing the repo 23:33:04 <flo-retina> buildbot runs |tools/scripts/tooltool/tooltool_wrapper.sh mail/config/tooltool-manifests/linux64/releng.manifest https://api.pub.build.mozilla.org/tooltool/ setup.sh /builds/tooltool.py| 23:33:25 <aleth> hmm 23:33:58 <aleth> apart from buildbot needing to do that, looks like it has to live in build/ (too?) 23:34:22 <aleth> ah, Fallen put it there as well. 23:35:01 <aleth> builds/, I mean 23:35:29 <flo-retina> so, if the command is issued by buildbot, we can totally use the mail/ folder 23:35:51 <aleth> yeah 23:36:56 <flo-retina> so I probably need https://github.com/mozilla/build-tools/blob/master/scripts/tooltool/tooltool_wrapper.sh 23:37:01 <flo-retina> or maybe even that whole repo 23:37:42 <aleth> ah, and for TB looks like that's called by buildbotcustom/process/factory.py 23:38:22 <aleth> it's confusing though. 23:39:20 <flo-retina> I agree on the last part, it's confusing 23:56:51 --> hadi has joined #instantbird