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