[00:38] <asac> yeah
[09:13] <asac> hi
[09:53] <fta> asac, <fta> asac, http://paste.ubuntu.com/125513/
[10:42] <asac> fta: i will poke some nm folks to see if they have an idea. for me it looks a bit like a ppp issue
[10:42] <asac> [reed]: do you have a bug that tracks the launchpad plugin enabling in bmo?
[10:46] <asac> [reed]: filed mozilla bug 481161 now
[10:46] <asac> if its a dupe, please dupe it
[12:01] <asac_ubufine> somehow mibbit UI is not that great ... i better stop this
[12:37] <asac> fta: do you have a log with a successful connect?
[12:40] <asac> fta: so there are a few things you could try.
[12:40] <asac> one idea is to reduce the Nacks you get (modem can hang up if you get those)
[12:41] <asac> to do that you could go to options file and disable those parts where you get a nack (e.g compression)
[12:41] <asac> i dont think its a problem because i get those nacks too, but it could depend on your provider pppd server being picky
[13:30] <fta2> asac, could you please have a look at prism? there's something wrong with the xpi since the last update
[13:30] <fta2> lp:~mozillateam/prism/prism/ #105
[13:32] <asac> i saw the build failures, yes.
[13:33] <asac> fta2: whats the problem? seems you fixed the patch divergance
[13:34] <fta2> yes, but now, there's a problem with the xpi inside
[13:40] <fta2> prism-runtime@developer.mozilla.org and refractor@developer.mozilla.org, something is messed up no
[13:40] <fta2> w
[13:43] <asac> now building ;)
[13:43] <asac> had to fix python again ;)
[13:56] <james_w> asac: freeze exception requested for a new bzr-builddeb to re-instate export-upstream
[13:56] <james_w> thanks for your help in convincing me that was the right thing to do
[14:09] <asac> james_w: heh. cool.
[14:28] <asac> bfiller: hi ;)
[14:28] <asac> bfiller: you got mail
[14:44] <bfiller> asac: oh really, I'll take a look
[14:44] <asac> bfiller: from bugzilla ;)
[14:45] <bfiller> asac: I see, thanks for signing me up :)
[14:45] <asac> bfiller: please confirm and make your boss confirm too ;)
[14:46] <bfiller> asac: just confirmed mine, I'll bug pat now
[14:46] <asac> thanks
[16:18] <fta2> asac, prism? any idea?
[16:18] <asac> fta2: yes
[16:19] <asac> fta2: do you have a upstream diff from the last that work to this?
[16:19] <asac> fta2: i guess when i see this, i know how to fix it ;)
[16:19] <asac> i see the problem ;) ... but i dont see whats the new plan is
[16:21] <fta2> http://paste.ubuntu.com/125874/
[16:22] <fta2> -	$(INSTALL) $(DIST)/bin/extensions/prism-runtime@developer.mozilla.org/components/* $(FINAL_TARGET)/components
[16:22] <fta2> +	$(INSTALL) $(DIST)/bin/components/* $(FINAL_TARGET)/components
[16:22] <fta2> ???
[16:23] <fta2> maybe prism-runtime is just gone
[16:27] <asac> fta2: yes. thats what i suspected
[16:27] <asac> its not really gone, its moved into the main extension from what i can tell
[16:46] <fta2> asac, http://www.sofaraway.org/ubuntu/tmp/karma-asac.png
[16:47] <fta2> asac, you now do more bugs than code
[16:49] <asac> fta2: well. thats interesting. i didnt do anything ;)
[16:49] <asac> just very low bug at least
[16:49] <asac> just for subscribed bugs
[16:49] <asac> no bug batch since more than a month i think
[16:51] <fta2> http://www.sofaraway.org/ubuntu/tmp/karma-fta.png
[17:01] <asac> fta2: yes. daily commits give you something ;)
[17:06] <fta2> asac, you don't want to see seb's karma ;)
[17:08] <asac> why not ;)
[17:08] <asac> i dont envy him for his bug karma actually
[17:08] <asac> thats painful work for sure ;)
[17:08] <asac> you can also track pitti ... who gains a lot of karma by making lots of -> fix released transitions
[17:09] <asac> a good other thing would be to get a "bug mail" count
[17:09] <asac> so you see how much mail gives how much karma
[17:09] <asac> i am pretty sure that some work patterns just give plenty of karma ;)
[17:13] <fta2> asac, http://www.sofaraway.org/ubuntu/tmp/karma-seb128.png
[17:14] <asac> coo
[17:14] <asac> i guess the answer tracker karma also gets added to bug karma  ;)
[17:14] <asac> maybe not in absolute amount, but similar
[17:14] <BUGabundo> hi guys
[17:14]  * asac wonders why he lost so much karma at some point
[17:14] <BUGabundo> just peeping in, for a bit
[17:15] <fta2> answer tracker is the light blue line
[17:15] <asac> poor seb ... doing all this bug crap ;)
[17:15] <asac> fta2: i know. what i mean if you close a bug by making an ansewr out of it you get
[17:15] <asac> answer karma ... and bug karma
[17:15] <asac> and bug karma is probably higher than just invalid because its a different op and not so many use that feature ;)
[17:17] <fta2> maybe
[17:17] <fta2> basically, you lost a lot of karma in this cycle :P
[17:45] <asac> fta: sure. its letss than i would have expected. as i said, i ignore bugwork until beta i guess
[18:29] <asac> fta: can you pleaes move your gnome-settings-daemon.desktop file out of autostart?
[18:29] <asac> fta: and see if all your font issues are cured?
[18:29] <asac> (besides from getting no theme at all)
[18:45] <nonZero> Hi Guys!  following the last discussion regarding firefox/linux performance, did anyone succeed running ff 3/3.1 w/PGO?
[18:47] <asac> nonZero: i think archlinux ;)
[18:47] <asac> for me this is getting higher on prio list for karmic
[18:47] <asac> i seriously doubt we can still do such experiments in jaunty
[18:47] <asac> in ppa we could try though. but no on the -3.0.head branches obviously
[18:47] <asac> so just 3.2 head
[18:47] <asac> also we have a problem because we need to pgo xulrunner somehow
[18:48] <nonZero> Actually I mean, did anyone try it on it's own PC, not for release?
[18:48] <asac> which means we probably need to fix the pgo testcase
[18:48] <asac> nonZero: not me. probably [reed]
[18:49] <nonZero> mmm... :-(
[18:50] <[reed]> there's a bug open on fixing pgo on linux
[18:50] <nonZero> if I apt-get firefox-dev, will it compile with 'make', or do I need lots of other stuff?
[18:50] <nonZero> oh pgo is broken in gcc?
[18:52] <asac> [reed]: archlinux already does that ;)
[18:52] <fta> i wanted to experiment with pgo in my own ppa, but i got distracted by setting up the dailies
[18:53] <asac> fta: we cannot do it because we cannot profile xulrunner
[18:53] <asac> fta: what we need is to invent something to get a profile for xulrunner
[18:53] <asac> which isnt even supported when mozilla fixes their firefox pgo
[18:53] <fta> why can't we?
[18:54] <asac> fta: we can. but its harder than just doing a few packaging tweaks
[18:54] <nonZero> asac: what will happen if firefox runs with pgo and xulrunner without?
[18:54] <asac> fta: firefox pgo is generated on the fly by starting a webserver during build that then runs a testcase (e.g. let firefox render real websites)
[18:54] <asac> fta: so what we would need to do is startup xulrunner with a basic browser against that proxy
[18:54] <asac> fta: so we need to ship a basic browser i guess
[18:55] <fta> hm
[18:55] <asac> nonZero: not much
[18:55] <asac> nonZero: you wont get much benefit because firefox has almost no performance sensitive code
[18:55] <fta> is bzr-builddeb fixed? or not yet?
[18:55] <asac> all rendering stuff and javascript is in xul
[18:55] <nonZero> i see.
[18:55] <asac> fta: did you get a bzr or bzr-builddeb update yet>?
[18:56] <nonZero> anyway, I am sure you are following http://brainstorm.ubuntu.com/idea/18058/ :-)
[18:57] <nonZero> good luck guys - thanks for the great work!!!
[18:57] <asac> nonZero: i am aware of that idea
[18:57] <asac> nonZero: but i am not following it
[19:04] <nonZero> asac: why do you need a webserver?
[19:04] <nonZero> asac: you can automate ff to browse static files as well
[19:04] <nonZero> asac: or files on a central webserver
[19:05] <nonZero> asac: or even the internet!
[19:06] <fta> our builders don't have access to internet, security reasons
[19:06] <nonZero> a small webserver on the lan is good enough
[19:09] <fta> but that's not something we can do ourselves, we need help from the launchpad admins
[19:12] <asac> nonZero: webserver is actualyl a proxy
[19:12] <asac> nonZero: doesnt matter if we hav ea we webserver or not... what we need is a browser that can cope with such a stream ;)
[19:13] <asac> fta: so maybe we should do an initial biuld: firefox, run pgo, then build xulrunner with that profile
[19:13] <nonZero> http://quality.mozilla.org/mozmill-docs automates browser test
[19:13] <asac> not sure how that would screw things up
[19:13] <asac> nonZero: the server is not the problem as i said
[19:13] <nonZero> ???
[19:14] <asac> the problem is the browser that doesnt exist in xulrunner builds ;)
[19:14] <asac> so we need a test shell ... which might not be perfect for optimizing the actually used xul of firefox
[19:15] <asac> but well thats ignorable for now i guess
[19:15] <asac> we could make use of most widgets in that browser ... so thats ok
[19:15] <asac> but we need to make that browser ;)
[19:16] <nonZero> i think mozmill can run with xulrunner
[19:16] <nonZero> it's not a firefox only tool
[23:09] <fta> SEAMONKEY_1_1_15_RELEASE
[23:10] <fta> THUNDERBIRD_2_0_0_21_RELEASE