[00:33] <cwillu_at_work> ... because I _like_ it when reloading a page with only javascript crashes the browser...
[00:35] <asac> heh. thats an extension ;)
[00:35] <asac> ccheney: so seems you make progress?
[00:35] <asac> nice
[00:39] <cwillu_at_work> that's not an extension, that's a fun little issue with webworkers while using XMLHttpRequest with multipart
[01:54] <ccheney> asac: well yea i got the code back unbroken from what i had last time i worked on it, now i just have the new override stuff to do (i think)
[01:55] <ccheney> i'll pastebin the current error list
[01:55] <ccheney> http://pastebin.ubuntu.com/420139/
[01:56] <ccheney> i should debdiff vs the ppa to see exactly how much is different
[01:57] <ccheney> i might have done something else different as well that shouldn't still be in there
[04:52] <ccheney> ok got it cleaned up and got the patch updated except for the gtkentry class, reduced the number of errors that are showing up when running but it crashes the same way, so now on to doing the override
[05:13] <micahg> ccheney: still around?
[05:32] <ccheney> micahg: yea
[05:32] <ccheney> whats up?
[05:32] <ccheney> sorry i didn't look in here earlier
[05:33] <micahg> ccheney: does OO.o still need the symlinks from dictionaries-common?
[05:33] <ccheney> micahg: i don't think so
[05:33] <ccheney> micahg: at least not on lucid afaik
[05:34] <ccheney> oh hold on let me see
[05:34] <micahg> ccheney: ok, because Firefox and Thunderbird were patched not to need them and now everything's doubled
[05:34] <micahg> so if OO.o doesn't need them, we can drop them either now or with an SRU later
[05:34] <ccheney> micahg: do you mean the symlinks in eg /usr/share/myspell/dicts/ ?
[05:35] <micahg> ccheney: yep
[05:35] <ccheney> i'm not sure slangasek will want us changing that in either lucid or an SRU, but if you want to go right ahead :)
[05:35] <ccheney> unless it actually helps us in some way
[05:36] <micahg> ccheney: well, if it's not needed, it'll be nice not to show double dictionaries
[05:36] <ccheney> oh it shows up double in some app?
[05:36] <micahg> ccheney: Firefox and Thunderbird
[05:37] <ccheney> micahg: so they now look in both places instead of just the new location, or what?
[05:37] <micahg> ccheney: right, both are now valid in those apps
[05:37] <ccheney> or are you talking about the symlinks for eg
[05:37] <ccheney> en_AU.dic vs en-AU.dic
[05:37] <ccheney> ok
[05:38] <ccheney> afaik OOo only looks in the new location and not in the old at all anymore
[05:39] <micahg> which is new and which is old?
[05:41] <ccheney> old /usr/share/myspell/dicts and new /usr/share/hunspell
[05:41] <micahg> ccheney: ah, ok
[05:41] <ccheney> at least for OOo, i think that is documented in the dictionary policy
[05:42] <ccheney> hyphen and mythes moved into their own dirs and used to be in myspell
[05:45] <micahg> k
[05:45] <micahg> I think an SRU is better at this point
[05:45] <micahg> then we can write a test case an have it veririfed
[05:46] <ccheney> i'm not sure if the old dir is completely obsolete, i would have to look it up, but if so you could just have the other apps not look in the old dir anymore if so
[05:46]  * micahg didn't think of that...is everything using hunspell now, I thought some packages were myspell only
[05:46] <ccheney> updating all the dictionaries to remove the old symlinks would take some effort i think, but not undoable, maybe annoying for SRU though
[05:47] <micahg> ccheney: no, it's a flag in dictionaries-common
[05:47] <micahg> oh, would a new package not remove the symlinks
[05:47] <ccheney> er the symlinks are in the dictionary packages themselves at least in many cases
[05:47] <ccheney> maybe all (not sure)
[05:48] <micahg> ccheney: I thought that dictionaries-common created them
[05:48]  * micahg checks
[05:48] <ccheney> some of them are using the proper dictionaries-common method which might get fixed like you mention, but at least some are really old manual symlinks in the packages
[05:48] <ccheney> at least from what i recall when updating them a while back
[05:48] <ccheney> the ones not using the new method probably should be updated
[05:49]  * micahg sees what you mean
[05:49] <micahg> dictionaries-common isn't involved at all :(
[05:49] <ccheney> i didn't fully read the policy before updating the packages so didn't realize they were out of date until i had already fixed them up for the new symlinks
[05:49] <micahg> I guess this is another cleanup project for Maverick
[05:50] <ccheney> i would recommend whoever does the cleanup fully read dictionary policy first, like i should have, heh :-\
[05:50]  * micahg should propose a blueprint?
[05:51] <ccheney> micahg: maybe so
[05:52] <ccheney> would probably be good to see if any myspell apps are still around to see if we need to leave the symlinks there, as i think removing them would make those stop working, right?
[05:52] <ccheney> in any case we should at least get the dictionary packages working with the new policy properly instead of the mess they are in now
[05:53] <micahg> ccheney: probably, that would be part of the blueprint I guess
[05:53] <ccheney> yea
[05:53]  * micahg has a browser triage blueprint in mind as well
[05:53] <ccheney> micahg: add me to the dictionary one once you create it
[05:54] <micahg> ccheney: k, let me make a note for myself
[05:54]  * micahg guesses he'll make these after Lucid is released
[05:57] <ccheney> ok
[06:51] <ddecator> is there no PPA for getting the latest stable release of thunderbird?
[06:53] <micahg> ddecator: not yeah, been busy :P
[06:53] <ddecator> micahg: ok, i'm just helping someone on the forums who wants the latest stable and i wanted to try to use a PPA hosted by you guys
[06:54] <micahg> indeed
[06:54] <micahg> it will be soon
[07:05] <micahg> ddecator: once we work out the final things with the packages I should be able to backport them quickly
[07:06] <ddecator> micahg: alright, sounds good. thanks
[09:10] <BUGabundo_remote> Get up on your Horse, and Ride till the Sunset 0/
[09:18] <micahg> fta: fixing xul193?
[09:20] <micahg> fta: it's probably going to FTBFS again, just 25 minutes into the build like before
[09:21] <micahg> fta: but thanks for trying
[10:08] <fta2> asac, any hint for http://launchpadlibrarian.net/45009120/buildlog_ubuntu-lucid-i386.xulrunner-1.9.3_1.9.3~a5~hg20100422r41148%2Bnobinonly-0ubuntu1~umd2_FAILEDTOBUILD.txt.gz ???
[10:08] <fta2> it's been broken for too long
[10:14] <fta2> mozilla 547964
[10:14] <fta2> grrr
[10:14] <fta2> asac, ^^ help
[10:17] <BUGabundo_remote> eheh
[10:28] <[reed]> fta2: what about that bug?
[10:29] <fta2> mozilla 560582
[10:29] <[reed]> ah
[10:30] <[reed]> fta2: so, you need to do a new nspr, I guess?
[10:31] <[reed]> yeah
[10:31] <[reed]> indeed
[10:36] <fta2> 4.8.5 is not even released, shame on you
[10:36] <fta2> mozilla 558967
[10:36] <fta2> pff
[10:36] <fta2> no time to loose with this
[15:31] <chrisccoulson> hey micahg
[15:31] <micahg> hi chrisccoulson
[15:32] <chrisccoulson> what happened with libjdic-java? i saw it got rejected by an archive admin, but i don't know who did and there was no comment
[15:33] <micahg> chrisccoulson: oh, ScottK noticed that it was xul version dependent and suggested the build-dep be the same way and I agreed
[15:33] <chrisccoulson> micahg - ok, no problem
[15:35]  * micahg should have put that in the comment
[15:35]  * micahg is about to test the thunderbird upgrade
[15:38] <micahg> k, looks like it worked, so I'll push it up
[15:40] <micahg> chrisccoulson: could you please look at bug 568275
[15:41] <micahg> chrisccoulson: BTW, I asked wgrant to give us a xulrunner category for the multidistrotools on ubuntuwire
[15:42] <chrisccoulson> micahg - yeah, that was deliberate. it was still depending on libmozjs, and i had a look at getting it to work with the latest xulrunner and the build system is looking in all the wrong places for spidermonkey
[15:42] <chrisccoulson> so i just disabled it
[15:43] <micahg> chrisccoulson: right, I saw, so what do you want to do, we can fix it for maverick and backport maybe
[15:44] <chrisccoulson> yeah, possibly. it's not using pkg-config for finding headers, but hardcoding all the paths instead, and i just don't have the time to fix that
[15:45] <micahg> chrisccoulson: right, it doesn't seem that popular anyways
[15:46] <micahg> chrisccoulson: do you want to write a response?
[15:46] <chrisccoulson> yeah, i'll do that now
[15:47] <micahg> chrisccoulson: thanks
[16:11] <micahg> chrisccoulson: do you know dictionary policy
[16:20] <ccheney> micahg: its here if you didn't happen to find it: http://dict-common.alioth.debian.org/dsdt-policy.html
[16:29] <micahg> ccheney: thanks
[16:44]  * micahg gets ready for the flurry of bugs in the rdepends from the RC upgrades :-/
[16:48] <micahg> chrisccoulson: what are we doing about lightning?
[16:51]  * BUGabundo_remote gets ready to mute all #s 
[16:56] <ccheney> when is the freeze lifted?
[16:58] <ccheney> chrisccoulson: did you see my email from last night?
[16:59] <chrisccoulson> ccheney, i did, but i've not had a chance to have a proper look at it yet. i'll do that today though
[16:59] <chrisccoulson> the freeze isn't lifted now btw ;)
[16:59] <chrisccoulson> we're frozen all the way to release
[17:01] <ccheney> chrisccoulson: ah ok, thanks
[17:03] <micahg> chrisccoulson: thunderbird fix is pushed
[17:04] <micahg> chrisccoulson: hopefully I'll have the conkeror upload ready when I get to $WORK
[17:04] <chrisccoulson> micahg - thanks. i will test and upload this afternoon
[17:04] <chrisccoulson> did you do an upgrade test?
[17:04] <micahg> chrisccoulson: yes, I installed the current package version then installed a local build with this fix
[18:00] <fta> BUGabundo_remote, http:// is back?? wtf
[18:01] <BUGabundo_remote> is it ????
[18:01] <BUGabundo_remote> LOLOLOLOL it is
[18:02] <BUGabundo_remote> we will talk later
[18:02] <BUGabundo_remote> gym time
[18:02] <BUGabundo_remote> nothing in the bugs :\
[18:54] <micahg> chrisccoulson: is it worth trying to remove the recursive symlink in the next TB update?
[18:55] <chrisccoulson> micahg - are we still getting users report the issue?
[18:55] <micahg> chrisccoulson: had one yesterday
[18:55] <chrisccoulson> i don't think it's worth trying to fix it up in the wrapper script. if we had lots of people experiencing it, then it might be worth it
[18:56] <micahg> chrisccoulson: k
[19:13] <micahg> fta: thanks for fixing firefox/xul trunk, I'm sure it'll make quite a few people happy
[19:32] <chrisccoulson> micahg - you don't need to worry about a build log, i always test build things i upload anyway ;)
[19:33] <micahg> chrisccoulson: bug 568610
[21:52] <fta> BUGabundo, http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/c6838bc81b7f1f49#
[21:54]  * BUGabundo reads
[21:55] <BUGabundo> fta: you know what's funny? I have got NO bug mail from chromium bts :S
[21:55] <fta> ever?
[21:55] <BUGabundo> no, recently
[21:56] <BUGabundo> I didn't even get anyting from the reverting of http
[21:56] <BUGabundo> and I was subbed to at least 2 bugs of it
[21:57] <fta> maybe they didn't. you probably see saw the re-target to M6
[21:57] <fta> -see
[21:57] <BUGabundo> "Please don't debate whether particular things should or shouldn't be 
[21:57] <BUGabundo> reverted, or ask for precise details on whether change X is going to be 
[21:57] <BUGabundo> reverted, as the folks in charge of doing this are heads-dow"
[21:58] <BUGabundo> wow
[21:58] <BUGabundo> even pidgin devs aren't so single minded :(
[22:01] <fta> well, i'm back with the window buttons on the left in ubuntu, and i kind of like it now. so why not http:// now that the paste is ok (at least it is for me)
[22:01] <BUGabundo> 9 out of 10 wfm
[22:01] <BUGabundo> I still got a few situations where it doesn't work
[22:01] <BUGabundo> I'll wait for the new m6
[22:02] <BUGabundo> and then report back with *proper* use cases
[22:02] <BUGabundo> maybe its not only chromium, but also the way the app works
[22:02] <micahg> so chromium is going to end up with 3 different versions now?
[22:02] <BUGabundo> fta: that would be which Friday ?
[22:02] <BUGabundo> tomorrow or next week ?
[22:03] <fta> ??
[22:03] <fta> BUGabundo, i guess you already read http://pthree.org/2010/04/18/chromium-removing-http/
[22:03] <fta> micahg, ??
[22:04] <micahg> fta: 4.x, 5.x, 6.x?
[22:04] <BUGabundo> fta: of course
[22:04] <fta> no, 4 will die
[22:04] <micahg> fta: ah
[22:04] <BUGabundo> fta: they say that m6 will land on Friday....
[22:04] <BUGabundo> which Friday is what I'm asking
[22:05] <BUGabundo> no canonical date there
[22:05] <BUGabundo> and tomorrow *is* Friday
[22:05] <fta> not sure
[22:11] <Barkhorn> isn't the whole point of displaying http to have a semantically correct URI in the address bar?
[22:11] <BUGabundo> Barkhorn: don't get me started
[22:11] <BUGabundo> I've ranted enough on it
[22:11] <Barkhorn> :D
[22:12] <BUGabundo> and if you know anything about me, I hate ranting and ranters
[22:12] <BUGabundo> so see how must all this situation took me, to act like that
[22:12] <Barkhorn> no i don't know you very well i'm afraid. but pointless ranting gets on my nerves too.
[22:14] <ddecator> +1
[22:18] <chrisccoulson> micahg - ok, i'm going to upload TB in a bit. i think the symlink fix should probably have a version check in though (and only run when the package is configured)
[22:18] <chrisccoulson> but i can quickly add that in before i upload
[22:18] <chrisccoulson> i'm just being a bit cautious after last week ;)
[22:19] <micahg> chrisccoulson: well, I thought about that, but once the link is there, it'll short circuit anyways, so I didn't see the point
[22:20] <micahg> chrisccoulson: you mean the old one?
[22:20] <micahg> chrisccoulson: which symlink?
[22:28] <BUGabundo> fta: found those lost email: spam inbox
[22:47] <BUGabundo> http://code.google.com/p/chromium/issues/detail?id=41954	+++1
[22:47] <BUGabundo> http://code.google.com/p/chromium/issues/detail?id=41954