=== micahg1 is now known as micahg [11:15] hi gnomefreak :) [11:15] gnomefreak, do you know when asac will be back? [11:16] andv: hi [11:16] andv: tomowwor last i heard [11:16] ok great [11:16] september 1st [11:16] yep, tomorrow then [11:29] fta: is crhomuim really that big of a package? [11:29] sorry for typo its still too early [15:18] hi [15:21] asac: welcome back [15:29] hi [15:32] thx [15:32] anything i missed? [15:32] anything i should know before start reading my mailbox gigante. [15:32] asac: welcome back [15:32] hi gnomefreak [15:42] only 3 hours to do email. brb smoke [16:24] asac, the v8 builds are useless, nothing is using the 1.2 branch [16:26] sure. i can bump them to latest or whatever. [16:26] what would you suggest? [16:26] trunk [16:27] btw, i had to drop system sqlite [16:27] hmm [16:27] for c or f? [16:27] c [16:28] because they patched it or running something to bleeding for us now? [16:30] they patched it [16:36] http://src.chromium.org/viewvc/chrome/trunk/src/third_party/sqlite/README.chromium?r1=24807&r2=24806&pathrev=24807 [16:37] http://src.chromium.org/viewvc/chrome/trunk/src/third_party/sqlite/src/os_unix.c?r1=24807&r2=24806&pathrev=24807 [16:37] trivial but enough to break the system lib [16:43] asac, i also stopped the backports of gwibber daily [16:52] fta2: backports < jaunty or <=jaunty ? [16:52] is it brokenb ecause of webklit? [16:53] python [16:53] /usr/share/cdbs/1/class/python-distutils.mk:185: *** invalid setting for XS-Python-Version. Stop. [16:55] gasp, i broke the bot [16:59] so gwibber needs new python now? or just hardcoded version for karmic in branch? [17:00] Ken and jcastro told me it's ok to stop [17:00] i didn't investigate further [17:00] feel free [17:02] bot fixed, hopefully [17:06] asac, your nmt also has some issues [17:07] the applet pkg needs a bt dep iirc === jtv1 is now known as jtv [17:10] fta2: yes. bittorrent and also a change of polkit (like what i had for nm) [17:10] awe is working on the breakage -finally [17:10] today [17:10] otherwise i will finish that up tomorrow [17:10] also thx for including a sensible mail title now in logs [17:11] asac, bittorrent? lol, no bluetooth [17:13] asac, the title is just part of my new idea for the logs, i committed phase 1 yesterday [17:13] ripps, ^^ [17:14] (and some fixes today) [17:14] fta2: yeah, I noticed. New email option [17:14] ripps, you need r121 [17:15] I'm updating my repo dirs now [17:15] maybe you should subscribe to the branch on lp and ask for email notifications [17:17] I have a dozens of repos that I update daily and I have a script that automatically scans them for upstream changes. [17:21] ripps, do you use that with my bot or instead of my bot? [17:22] Well, I keep my bot in a seperate directory and I manually sync changes between my repo dir and my version of the bot, just so I can learn a little about what was changed [17:23] I use meld, very useful for automatically sync changes between 2 dirs, but still having some control over it [17:23] ripps, oh, so you have a fork? [17:24] not really, just some stuff in my daily.sh, but pretty much 99% of it is identical to yours [17:25] ripps, hm, would you mind sharing? so i can see if it's generic enough to be merged, or if i should add some hooks to allow you do what you need without patching [17:29] i have to run, be back in ~1h. feel free to talk to fta ;) [18:20] hello asac!! [18:21] welcome back! [18:21] asac, you forgot to push all-in-one before going to holidays [18:21] you pushed mozilla-devscripts only :) [18:26] hi. yeah. it didnt make the cut unfortunately ... will happen today or tomorrow morning (most likely) ... i am already on my way out again for dinner et al [18:29] asac, please remember to add DM tag [18:30] asac, if you want I can do it myself on the branch [18:43] asac, I've added it ;) [18:43] asac, and gave a release commit [18:45] Hi [18:45] hi [18:45] I've just upgraded to Karmic, and the "Keep 3.5 settings" option doesn't work (it just scared me to hell! :D) [18:45] it worked for me [18:46] It created a new profile and my Shiretoko stuff ended up in ~/.mozilla/firefox.3.0-replaced/firefox [18:46] I would suggest you to open a bug and asac will have a look at it [18:47] anyway it worked fine for me [18:47] some days ago I upgraded [18:48] (in case it matters, I had Shiretoko open during the update, once it completed I attempted to open a link from another app and I got the dialog where I checked "keep 3.5" - nothing happened. Now I've closed Shiretoko, opened Firefox, got asked again -clicked on "keep 3.5 settings" again- and got the explained result) [18:49] it's seems not a bug then [18:49] you just kept it opened during an update [18:49] which is a bit not safe [18:49] I had it working coz my firefox was closed during the update [18:49] Well, it should be made safe then, shouldn't it? :) [18:49] keeping it open and having the 'keep' stuff working? [18:50] during an update? [18:50] Yep [18:50] But hey, nevermind if nobody else complains - Just thought I'd mention it :) [18:50] usually firefox after installing any kind of update (addons / lang packs / whatever) it requires to be restarted [18:50] RainCT: one quick comment. we have a bug open for that [18:50] and i think we need to somehow address that better [18:51] not exactly sure how though [18:51] asac, I think it's normal to restart an application after an update [18:51] or not? [18:51] its unacceptable that it does the wrong thing if the user has it open during update [18:51] yes. but we dont force a restart ... we just give user the hint to trestart it [18:51] with a button so they can do that easily [18:51] true [18:51] it's not forced but suggested [18:51] right [18:52] obvious solution i suggested in the bug is that the script probes whether there is a remote firefox running [18:52] and if it is, dont do the migration [18:52] only when its a "real" start [18:52] i think there were a few corner cases tricky with that [18:52] but in general thats the way to go [18:52] (however, the bug most likely existed in firefox 3.0 transition too - not saying we shouldnt fix it of course) [18:53] corner cases -> mostly "multi profile" cases [18:53] ok out for dinner [18:53] bbl [18:53] (I didn't get a "restart required" bubble either, btw) [18:53] asac: ok, enjoy your meal :) [18:55] cya [19:13] gasp, my pc crashed during the day [19:14] when did i disappear? [19:31] 15:28:59 <-- fta has quit (Read error: 110 (Connection timed out)) [19:31] hmm === zbraniecki is now known as gandi [20:30] asac, did you send your dch patch for integration in u or d? [20:38] fta or asac: can one of you sponsor gwibber so we can get 2.0 in pls? [20:38] jcastro, is it considered stable enough? [20:39] yeah [20:39] jcastro, i just have an empty window in my laptop [20:39] it's not going into main though is what I was told [20:39] hmm, let me find vandine [20:41] fta, empty window? [20:41] fta, seems more stable to me [20:41] i meant, no dent at all, in any tab/stream/whatever [20:42] humm [20:42] have you tried running the daemon and the client in a terminal? [20:42] get some output [20:43] ..and many features regressed compared to 1.2.*, themes, auto ":" after nicks, avatars no longer cached, etc. [20:43] themes are broken... yes [20:43] avatar caching has never worked well... [20:44] that's why i asked if it was considered stable enough (for me, it isn't, but if others think it's ok, i'm fine) [20:44] it is "feature complete" for karmic [20:44] but there are known bugs for sure... [20:44] it is definately less "crashy" than the 1.2 series [20:48] 2.0 already crashed 3 times for me, while 1.2 didn't since asac patched it, not even once [20:49] nothing enlightening in the terminals [20:52] humm [20:52] i haven't had any crashes [20:53] so no output? [20:53] and what revision are you running? [20:56] r396 [20:57] ok.. i have 393 [20:57] * kenvandine pulls [20:58] oh... what happens when you hit the refresh button? [20:59] i wonder if it never auto refreshes on startup [20:59] http://www.sofaraway.org/ubuntu/tmp/gwibber2.ogv [21:00] hm, i see some dents now [21:00] ok [21:00] weird [21:01] i didn't even hit refresh (i couldn't find it) [21:01] ok [21:04] the 1st "Loading Complete" appeared several minute after the launch [21:04] it needs to call refresh once on startup [21:05] i think it waits until the configured interval to refresh [21:06] hey aquarius [21:07] hey kenvandine [21:10] fta, so can you get it uploaded? [21:10] that is stuff we will get fixed as bug fixes [21:10] not features :) [21:11] ok, which branch is it? i don't remember [21:11] bug 420034 [21:11] Launchpad bug 420034 in gwibber "Update to 2.0.0 snapshot" [Undecided,In progress] https://launchpad.net/bugs/420034 [21:11] lp:~gwibber-team/gwibber/packaging [21:12] fta, thx! [21:19] kenvandine, hm, I will just bump it to 396, no other change, 393 was spitting too many errors via apport [21:22] boas noites [21:22] /me waves [21:28] fta, sure [21:28] fta: asac: wasn't I clear on my request??? [21:35] kenvandine, done [21:35] BUGabundo, apparently not === BUGabundo1 is now known as BUGabundo [21:41] fta, awesome [21:41] fta: well I remember asac opening bugs, and have written a blog post I think [21:42] on how web designers should not filter Firefox for it string [21:42] but the proper agent [21:42] or else stuff like shireoko or abrowser will not get caught [21:43] i have the same problem with chromium [21:44] upstream hardcoded Chrome, i wanted to change it to Chromium, they said it's a bad idea [21:44] :( [21:44] yeah but at work [21:44] i then changed it to mention both Chrome and Chromium, they said it's too long [21:44] I noticed today on their css lots of Firefox agent hardcoded [21:44] and I wanted proof that that was *wrong* [21:45] just showing them abrowser was enough [21:45] *wasnt [21:45] hey micahg [21:45] i have no solution for that [21:45] hi BUGabundo [21:45] but I'm sure I read something from asac on that [21:45] micahg: do you know? [21:46] well I remember asac opening bugs, and have written a blog post I think [21:46] (09:42:21 PM) freenode: on how web designers should not filter Firefox for it string [21:46] (09:42:28 PM) freenode: but the proper agent [21:46] (09:42:45 PM) freenode: or else stuff like shireoko or abrowser will not get caught [21:46] when we change the branding in firefox, it also changes the user agent, that is an upstream choice to tie the two together [21:46] sorry, i missed the Q [21:46] ah [21:46] yes [21:46] is asac around? [21:47] so it's expected to break web site hardcoding stuff for firefox [21:47] siteS [21:48] well, depending on what it checks for it can break sites [21:50] bug 397211 [21:50] Launchpad bug 397211 in firefox-3.5 "Shiretoko user agent string breaks compatibilty with major websites" [Undecided,Confirmed] https://launchpad.net/bugs/397211