[00:05] <asac> fta: hmm our gnome default is broken?
[00:05] <asac> sounds like a bug
[00:06] <asac> kde doesnt have apturl in hardy - jaunty by default; in karmic they will provide it
[00:06] <aleron6> whats up guys
[00:06] <asac> for me "xdg-open apt:flashplugin-installer" works
[00:07] <asac> aleron6: no sure ;)
[00:07] <asac> not
[00:07] <fta> asac, could you please add a comment?
[00:08] <aleron6> wawt version of ubuntu you running
[00:08] <asac> fta: does that work for you too?
[00:08] <fta> yes
[00:08] <asac> k
[00:08] <asac> i can comment
[00:09] <asac> if i remember my login ;)
[00:10] <asac> fta: remind me tomorrow want to understand where the default is actually shipped
[00:11] <asac> dont see it right now
[00:11] <asac> at least not in apturl afaict
[00:15] <asac> commented ... will check hardy tomorrow
[00:15] <asac> mozclient will take a few more days i would think
[00:30] <fta> thanks
[00:31] <asac> now that i think about it, i feel like i remember someting with hardy wrt escaping of url arguments
[00:31] <asac> at least "ubuntu-bug" and apport had issues in the past
[00:31] <asac> that sound familiar
[00:53] <fta> asac, ff3.7 is red, in case you missed it
[00:53] <fta> ok, enough for today
[00:53] <fta> 'night
[00:54] <BUGabundo> night fta
[01:46] <aleron6> anybody active heah
[07:52] <eagles0513875> hey guys
[08:29] <asac> hi
[13:34] <eagles0513875> hey guys
[13:48] <eagles0513875> asac: any word on alpha 6 or is todays release of it being postponed
[14:18] <asac> eagles0513875: didnt even know that until you said
[14:18] <asac> ;)
[14:18] <asac> wouldnt be too bothered
[14:18] <asac> just normal delay because something came too late ;)
[14:18] <asac> and caused more bugs than expected
[14:18] <eagles0513875> blarg
[14:18] <eagles0513875> ahhh
[14:18] <eagles0513875> well im having problems out the rump with 5 im wondering if 6 has them fixed
[14:20] <eagles0513875> how are things looking on the extension front
[14:20] <eagles0513875> now that i finished up the wiki
[14:30] <eagles0513875> asac anything you would like me to help out with
[14:51]  * gnomefreak not really here. only here for updates and email
[14:52]  * eagles0513875 waves to gnomefreak and lets him go about his business
[14:53] <gnomefreak> eagles0513875: firegpg needs some work on rules file for clean before we can do anything. also we will not push it to Ubuntu we will push it to Debian since its not in Ubuntu. when i get back i will get with asac about it.
[14:54] <eagles0513875> if you want i can get asac to help me with it while u are gone
[14:54] <eagles0513875> *you
[15:03] <asac> eagles0513875: i will be back soon for you
[15:03] <gnomefreak> eagles0513875: he already has the diff to work on it. its not a trival fix
[15:03] <eagles0513875> ok asac
[15:03] <eagles0513875> gotcha gnomefreak
[15:03] <eagles0513875> i gotta start somewhere
[15:04] <gnomefreak> paths changed and we need to update clean in rules for them. asac can we make it a general clean instead of only looking for FireGPGCall in each path?
[15:06] <gnomefreak> it doesnt build with clean enabled :)
[15:08] <eagles0513875> O_o
[15:13] <asac> gnomefreak: we should fix upstream clean target and submit that to the author
[15:15] <gnomefreak> asac: ok sounds good but does he really care for Linux as much as windows?
[15:16] <eagles0513875> another valid question brought up by gnomefreak
[15:16] <gnomefreak> i would love a generel clean rule to find it and remove it instead of having to fix this every time he changes where FireGPGCall is moved
[15:17] <gnomefreak> we have had him fix a few things (not much) but we can email him once we figure this out <before sending this to SId>
[15:20] <gnomefreak> mostly License issue(s)
[15:46] <gnomefreak> ok first round of email done. one more round and updates
[15:46] <gnomefreak> be back
[15:50] <gnomefreak> they dropped the getmail>get all mail (or whatever it said) in tbird-3
[15:55] <gnomefreak> oh and <insert build ID into text box> doesnt work. it is not seeing the reply text box as a text box in tbird-3
[16:18] <gnomefreak> asac: do you know that n-m is showing disconnected when there is a connection? at least here it is
[16:29] <asac> gnomefreak: nm-tool output ... paste please
[16:30] <gnomefreak> ** (process:5179): WARNING **: error: could not connect to NetworkManager
[16:35] <gnomefreak> that was the only output worth showing you
[16:40] <gnomefreak> ok updated review page to list all bug numbers.
[16:46] <gnomefreak> ok im gone
[17:08] <fta2> asac, friendly reminder for the apturl bug
[17:17] <asac> i asked on -testing if someone has hardy
[17:17] <asac> or intrepid or jaunty ;)
[18:41] <fta> asac, micahg: ff3.7 still red
[18:42] <micahg> fta: I don't know how to fix this one
[18:42] <micahg> asac: I think it had to do with that patch I showed you about removing gnomevfs and gio
[21:53] <[reed]> fta: mozilla bug 512671
[22:01] <fta> [reed], i know, the idea was that i let someone else fix it ;) ok, i fixed it this time
[22:02] <[reed]> posted a patch somewhere?
[22:03] <[reed]> ah
[22:03] <[reed]> it's an ubuntu-specific thing
[22:03] <fta> [reed], is the electrolysis branch somewhat usable?
[22:04] <fta> i mean, buildable
[22:04] <[reed]> fta: I do not know.
[22:05] <fta> lol http://hg.mozilla.org/projects/electrolysis/rev/6fd4bb500d42
[22:08] <BUGabundo> asac: I sincerily hope this was just a big typo
[22:08] <BUGabundo> removing NM on updates????
[22:08] <BUGabundo> are you joking ?
[22:09] <[reed]> fta: yeah, I know we're partnering with the chromium team on the ipc stuff
[22:09] <[reed]> to develop something that we can both work
[22:09] <[reed]> s/work/use/
[22:10] <fta> makes sense, for once ;)
[22:14] <mac_v> asac: whats with NM applet failing on updates! :( is it a known issue?
[22:15] <mac_v> on recent updates , after an update... it just switches off networking
[22:50] <BUGabundo> mac_v: start NM again
[22:50] <BUGabundo> it dies on update
[22:50] <BUGabundo> very *very* bad
[22:50] <BUGabundo> even for devel cycle
[22:51] <BUGabundo> mac_v: $ sudo NetworkManager
[23:17] <asac> BUGabundo: thats fixed
[23:17] <asac> if you look in launchpad ... i didnt do the updates ;)
[23:18] <BUGabundo> so you did??
[23:18] <BUGabundo> *who
[23:18] <asac> you can see it in launchpad
[23:18]  * BUGabundo dribbles changes logs
[23:19] <asac> i didnt know that this was going to happen until it already happened ;)
[23:19] <BUGabundo>  -- Scott James Remnant <scott@ubuntu.com>  Wed, 16 Sep 2009 20:50:31 +0100
[23:19] <BUGabundo> debian/rules: We never previously started or restarted network manager on install or upgrade, and instead flagged a reboot
[23:20] <BUGabundo> well aint that a briliant idea!
[23:20] <BUGabundo> to leave a system WITHOUT network
[23:20] <BUGabundo> DUH
[23:20] <asac> hey
[23:20] <asac> its not a big deal
[23:20] <crimsun> right, it's an alpha, we can all deal :)
[23:20] <asac> i would have preferred if he had talked to me, but if you have to touch like so many packages you cannot wait ;)
[23:21] <asac> and i understand that
[23:21] <asac> and he fixed his regressions ;) ... which is definitly good
[23:21] <BUGabundo> asac: I know how to fix it
[23:21] <BUGabundo> I wonder *how* many users got stuck
[23:22] <asac> all uploads happened in 24h or something
[23:22] <asac> so its not a big time frame ;)
[23:22] <asac> and thats how you learn how to recover from it ;)
[23:22] <asac> by stepping into these bugs
[23:22] <BUGabundo> grrr
[23:22] <fta> want a respin?
[23:22] <asac> me?
[23:23] <fta> yes
[23:23] <asac> hmm. the dailies are still in semi state. right
[23:23] <asac> why not ;)
[23:23] <asac> just network-manager package
[23:24] <asac> and jaunty is broken now ;)
[23:24] <asac> collateral damage ;)
[23:24] <fta> too late, I did the whole thing
[23:25] <asac> heh
[23:25] <asac> ok
[23:26] <asac> fta: you fixed 3.7=
[23:26] <asac> ?
[23:26] <fta> yep, broken for 2+ days
[23:26] <asac> brave
[23:27] <fta> i pasted the log 3 times, reed answered with the same bmo bug twice, so i did it
[23:28] <fta> Scott is doing nm packaging now?
[23:28] <asac> no
[23:28] <asac> he did the upstart transition uploads for everything that uses /etc/init.d
[23:29] <fta> http://paste.ubuntu.com/273140/
[23:29] <fta> lol 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6
[23:29] <fta> a snapshot with 0ubuntu6
[23:29] <asac> yes he was so kind to publish a bzr branch
[23:31] <asac> probably have to clean that up in some way
[23:32] <asac> most likely by upstreaming something sensible that auto detects whether to install upstart or old-init style things
[23:32] <asac> so it can build on jaunty again ;)
[23:32] <asac> but i am currently in the middle of pushing hard for the applet UI changes we are doing this cycle as we already are past UI freeze
[23:33] <asac> once thats out i hope i can only do bug fixing.
[23:33] <asac> and normal work ;)
[23:38] <micahg> asac: I looked at the 3.7 failure yesterday, but didn't know how to fix it
[23:39] <micahg> it turns out it was that bug I mentioned
[23:40] <fta> asac, you now have a network-manager.prerm script calling "stop network-manager || :", will that even work in jaunty?
[23:41] <fta> micahg, yep, that + a patch to rebase
[23:42] <fta> micahg, but dailies are full of surprises, you'll have your share of fixes to do ;)
[23:43] <micahg> fta: yep, I've been fixing what I can
[23:43] <fta> chromium is green, a last, too much red those past 2 weeks