| micahg | mdeslaur: ping | 01:22 |
|---|---|---|
| mdeslaur | micahg: yes? | 01:28 |
| mdeslaur | bbl | 01:35 |
| micahg | mdeslaur: ah, sorry | 01:43 |
| micahg | mdeslaur: flash version in Hardy/multiverse causing warnings in FF3.6 | 01:44 |
| * ddecator works on building the latest FF to see if the feedback menu is there.. | 01:48 | |
| * micahg will bbiab | 01:59 | |
| ddecator | micahg: btw, SB daily is now 1.9.0, now sure how you want me to handle that (since nothing has merged yet i could redo the commits so it doesn't go from 2.0 to 1.9 since that wouldn't take very long) | 02:00 |
| Mook_sb | yeah, sorry about that :( | 02:01 |
| ddecator | Mook_sb: not a big deal, but what was the reasoning? just didn't think there would be enough changes to justify a jump to 2.0? | 02:02 |
| Mook_sb | ddecator: yeah, basically that. | 02:02 |
| ddecator | Mook_sb: yah, i figured | 02:02 |
| * ddecator needs to figure out an xml error with SB | 02:02 | |
| Mook_sb | I guess they decided just going to XR192 wasn't enough (because it wasn't really user-visible) | 02:02 |
| Mook_sb | where? | 02:03 |
| Mook_sb | (if it's in prefs, probably using the wrong mozbrowser?) | 02:03 |
| ddecator | when i try to launch Add-ons, not sure if it's because i'm missing an XR192 patch or what | 02:03 |
| Mook_sb | yeah, that's the pref window too. | 02:03 |
| ddecator | wrong mozbrowser? hm... | 02:04 |
| Mook_sb | (190 vs 192) | 02:04 |
| ddecator | Mook_sb: we pull yours...you have both on your servers like XR don't you -_- | 02:05 |
| ddecator | or not.. | 02:08 |
| Mook_sb | sigh, now I'm confused too | 02:08 |
| Mook_sb | that *should* be the right one... | 02:09 |
| Mook_sb | sigh, we seem to be pulling http://publicsvn.songbirdnest.com/vendor/trunk/xulrunner-1.9.2/mozilla/browser/ instead | 02:10 |
| Mook_sb | http://src.songbirdnest.com/source/xref/client/songbird.mk#130 - sorry about that too :( | 02:10 |
| ddecator | Mook_sb: so we need to pull from /xulrunner-1.9.2/mozilla/browser/ instead of /mozbrowser/ ? | 02:11 |
| Mook_sb | ddecator: right. at least, it seems like it. stuff is just being confusing because we're working too much on the 1.8 branch still | 02:12 |
| ddecator | Mook_sb: sign -_- alright, i'll get that setup later, thanks for pointing that out to me | 02:12 |
| ddecator | s/sign/sigh | 02:12 |
| bobby_ | Anyone know if JavaScript bug has been fixed yet? I haven't gotten any site with JScript running *cough*NEWEGG*cough* | 02:21 |
| * ddecator didn't know there was a JS problem.. | 02:22 | |
| ddecator | micah would know more about that than me | 02:24 |
| bobby_ | Yeah, he said he was working on it... | 02:26 |
| mdeslaur | micahg: flash 9 isn't supported in the new firefox? | 02:56 |
| micahg | mdeslaur: I thought about it, since it's supported and patched by Adobe still, Firefox shouldn't recognize it as unsupported | 02:56 |
| micahg | mdeslaur: I'll file a bug with Mozilla for it and if they won't fix it, we might have to go to 10.1 in hardy | 02:56 |
| mdeslaur | micahg: I vaguely remember us going to 10.x in hardy, and it was causing sound problems, so we reverted :( | 02:58 |
| micahg | mdeslaur: yeah, that was in backports | 02:58 |
| mdeslaur | (although I may be remembering wrong...off to look...) | 02:59 |
| micahg | mdeslaur: idk, should I subscribe you to the upstream bug that I file? | 02:59 |
| mdeslaur | micahg: please do | 02:59 |
| micahg | mdeslaur: which address should I use? | 03:00 |
| mdeslaur | micahg: let me check, hold on a sec | 03:00 |
| mdeslaur | micahg: marc.deslauriers@canonical.com | 03:02 |
| micahg | mdeslaur: k, thanks | 03:02 |
| mdeslaur | micahg: you know, 10.1 must not totally be broken on hardy, as we do ship it in the partner repo | 03:08 |
| mdeslaur | it was probably gutsy that was causing all the grief | 03:08 |
| micahg | mdeslaur: that's a good point | 03:08 |
| micahg | mdeslaur: well, I know it was yanked from Hardy, but the issues might have been fixed | 03:08 |
| mdeslaur | micahg: It seems to have been pulled because of bug #239182, which doesn't apply any longer | 03:13 |
| ubot2 | Launchpad bug 239182 in flashplugin-nonfree (Ubuntu) (and 2 other projects) "Segfault in cairo_draw_with_xlib (dups: 3) (heat: 9)" [Undecided,Fix released] https://launchpad.net/bugs/239182 | 03:13 |
| micahg | mdeslaur: k, could you check a non-security changelog entry for how it looks? | 03:13 |
| mdeslaur | how it looks? | 03:14 |
| micahg | mdeslaur: spacing and such | 03:14 |
| mdeslaur | oh, you have one already? :) | 03:14 |
| micahg | mdeslaur: http://pastebin.ubuntu.com/460049/ | 03:14 |
| micahg | looking to do one upload tonight :) | 03:14 |
| mdeslaur | micahg: looks good to me. I would probably just add the original description for the two patches that you are still including | 03:16 |
| mdeslaur | micahg: but that's just a nitpick | 03:17 |
| micahg | mdeslaur: actually, after looking at the diff, I think they are the inverse of each other, so they can both be dropped :) | 03:17 |
| mdeslaur | oh, hehe | 03:17 |
| micahg | mdeslaur: so, do I need to enumerate each patch that I drop, or just say that all patches are included upstream | 03:19 |
| mdeslaur | micahg: I would enumerate them | 03:22 |
| micahg | mdeslaur: k, I think I'm done then, so it's just dput package-version.dsc? | 03:22 |
| mdeslaur | you need to sign it first, and then dput | 03:23 |
| micahg | mdeslaur: k, thanks | 03:23 |
| micahg | mdeslaur: mozilla 516167 | 03:31 |
| ubot2 | Mozilla bug 516167 in www.mozilla.com "detect-flash.js should not warn users for Flash Player 9.0.246.0 (latest secure Flash v9)" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=516167 | 03:32 |
| mdeslaur | micahg: how are users getting that warning? when they visit mozilla.com? | 03:36 |
| micahg | mdeslaur: on upgrade, there's a new version page that shows what's new and that checks | 03:36 |
| mdeslaur | ah, that sucks | 03:36 |
| micahg | mdeslaur: right, we'll see if my comment picks up any support for action | 03:37 |
| ddecator | micahg: should our daily builds of FF have the Feedback menu? | 03:41 |
| micahg | ddecator: idk, I haven't been following the progess of it | 03:45 |
| ddecator | micahg: ok. i know it's in the first beta, but idk if it's just in the milestone releases and not the trunk (since it's more unstable) | 03:46 |
| micahg | ddecator: it would be the opposit | 03:46 |
| ddecator | micahg: i guess that makes sense.. | 03:47 |
| ddecator | oh, there is a feedback thing in the tools menu :) | 03:58 |
| Milos_SD | any info on Firefox 4 beta1 landing in ppa? :D | 12:37 |
| Dimmuxx | 4.0b2pre isn't in daily yet so will probably be some time | 13:09 |
| === BUGabundo_fewd is now known as BUGabundo_remote | ||
| BUGabundo_remote | Milos_SD: Dimmuxx: FF 3.7 == 4.x | 13:12 |
| Dimmuxx | BUGabundo_remote: I know but 3.7 haven't been updated in daily since they bumped it to 4.0 | 13:25 |
| === yofel_ is now known as yofel | ||
| chrisccoulson | micahg - i've figured out why all the apps i'm porting on karmic don't reregister all the components | 16:37 |
| micahg | chrisccoulson: why? | 16:37 |
| chrisccoulson | it's because i'm installing the old version, testing them with 1.9.1 (which creates a fresh profile) before i port them to 1.9.2. i'm doing this with 1.9.2 already on the system | 16:38 |
| chrisccoulson | so the timestamp on the compreg.dat is always newer than the timestamp of .autoreg | 16:38 |
| chrisccoulson | so the components aren't re-registered when i run the apps with 1.9.2 | 16:39 |
| chrisccoulson | that shouldn't happen on a normal upgrade though | 16:39 |
| micahg | ok | 16:39 |
| chrisccoulson | theoretically, there is a small window in which this could happen, but it's unlikely | 16:40 |
| micahg | chrisccoulson: we still need to update xul191 on karmic and jaunty though | 16:40 |
| chrisccoulson | micahg - yeah, that's no problem. it's already in the PPA | 16:40 |
| chrisccoulson | so, if a user install xul1.9.2 without upgrading any applications, then runs a particular application for the first time, and then upgrades that application, they could be affected by this problem | 16:41 |
| chrisccoulson | but i would think the chances of that are fairly remote | 16:41 |
| chrisccoulson | what happens on chromium if you navigate to a page which requires a plugin that you don't have? | 16:52 |
| === fta_ is now known as fta | ||
| === fta_ is now known as fta | ||
| chrisccoulson | micahg - i got kazehakase working on karmic and jaunty in the end | 21:50 |
| chrisccoulson | and i've finally upgraded to maverick :) | 21:50 |
| chrisccoulson | heh, i wonder if asac was watching the football? | 21:52 |
| micahg | chrisccoulson: I'm suprised that the jaunty version works | 21:52 |
| chrisccoulson | micahg - how come? | 21:52 |
| micahg | chrisccoulson: I wouldn't think it had most of hte changes for xul19 | 21:52 |
| micahg | xul192 | 21:52 |
| === fta__ is now known as fta | ||
| chrisccoulson | micahg - it didn't need many. i applied the karmic patch for the xul191 changes, and then i had to make a small change to both karmic and jaunty to port them both to xul192 | 21:53 |
| chrisccoulson | hardy will be the more difficult one ;) | 21:54 |
| micahg | chrisccoulson: I think I forgot the xul191 patch for hardy :( | 21:55 |
| micahg | maybe that's why I was having so many issues | 21:55 |
| chrisccoulson | micahg - hardy is still using xul1.8 isn't it? so, it needs extra work just to get it to 1.9 | 21:56 |
| micahg | chrisccoulson: I thought it was using 1.9 | 21:56 |
| chrisccoulson | micahg - i don't think so, i might be wrong though | 21:56 |
| chrisccoulson | i know the package depends on libxul0 | 21:56 |
| chrisccoulson | which is part of 1.8 isn't it? | 21:56 |
| micahg | chrisccoulson: oh, yeah, maybe that's it then | 21:57 |
| chrisccoulson | i don't consider a high priority really, seeing as 1.8 hasn't had any updates for so long anyway ;) | 21:57 |
| micahg | chrisccoulson: k, BTW, I was wondering if I should copy FF3.6.6 from the security PPA to the stable PPA | 21:59 |
| chrisccoulson | micahg - yeah, feel free to do that | 21:59 |
| chrisccoulson | micahg - i didn't realise until yesterday that applications using the standalone XPCOM glue don't always load the newest matching GRE on the system | 22:08 |
| chrisccoulson | they had been doing that in my testing on hardy and jaunty | 22:08 |
| chrisccoulson | but when i started testing karmic, they all loaded the old 1.9.1 GRE | 22:09 |
| chrisccoulson | i didn't realise that it picks the first matching GRE returned from readdir() | 22:09 |
| chrisccoulson | which doesn't seem to give a predictable order ;) | 22:09 |
| chrisccoulson | i assume that it returns files based on inode numbers or something | 22:09 |
| micahg | chrisccoulson: yeah, not sure, that's why we usually depend directly on the minimum supported version | 22:11 |
| micahg | or tweak the GRE version | 22:11 |
| chrisccoulson | micahg - i'm wondering whether to provide a /etc/gre.config file, which points to one of the files in /etc/gre.d/ using update-alternatives, and that we can switch at any point to change the default GRE on the system | 22:12 |
| chrisccoulson | /etc/gre.config is searched for a matching GRE before anything in /etc/gre.d | 22:12 |
| chrisccoulson | it might make these backports a little less painful in future | 22:12 |
| micahg | chrisccoulson: well, that means we have to migrate all the apps on a system at once | 22:12 |
| chrisccoulson | micahg - not necessarily. if the GRE in /etc/gre.config doesn't match, then applcations search in /etc/gre.d | 22:13 |
| micahg | chrisccoulson: well, then we still need to do both, so what's the advantage of the gre.config? | 22:13 |
| chrisccoulson | so, for karmic, we would have kept /etc/gre.config pointing to 1.9.1, and then just updated the applications we wanted to port to 1.9.2 | 22:14 |
| chrisccoulson | rather than having to update applications we want to keep on 1.9.1 because they break if they load 1.9.2 | 22:14 |
| micahg | chrisccoulson: ah, ok | 22:14 |
| chrisccoulson | eg, yelp had to be updated on all of the releases to not load 1.9.2 | 22:14 |
| * micahg can't wait for yelp webkit | 22:15 | |
| chrisccoulson | well, that might be here soon :) | 22:15 |
| micahg | chrisccoulson: I saw :) | 22:15 |
| chrisccoulson | i'm going to start looking at getting that in to maverick, as it's needed to get chromium on to UNE | 22:15 |
| chrisccoulson | but it will likely need some work, seeing as the GNOME platform is using gtk3 now | 22:16 |
| micahg | chrisccoulson: and I filed the bug w/Debian for miro 3.0.2 which is webkit based and will merge to Maverick once it hits debian (even experimental) | 22:16 |
| chrisccoulson | cool | 22:16 |
| chrisccoulson | don't feel like you need to wait on debian though, if you want to just upload it to ubuntu then feel free to do that instead ;) | 22:16 |
| micahg | chrisccoulson: 10 months of pain (Lucid and later will be much easier to maintain since we cut the number of apps) | 22:16 |
| chrisccoulson | yeah, hopefully :) | 22:17 |
| micahg | chrisccoulson: I still have a long list, if it gets too close to feature freeze, I might | 22:17 |
| chrisccoulson | ok, no problems | 22:17 |
| chrisccoulson | micahg - what's happening with the FF3.7/4.0 dailies atm? | 22:18 |
| micahg | chrisccoulson: this weekend I'll fix them | 22:18 |
| micahg | chrisccoulson: there are merges proposed ATM to fix them, I haven't had tiem to review/merge | 22:18 |
| chrisccoulson | micahg - ok, thanks. if you need me to do anything, then just let me know | 22:18 |
| chrisccoulson | heh, it's great, i actually feel like i can relax a little now ;) | 22:19 |
| micahg | chrisccoulson: cool | 22:19 |
| chrisccoulson | i'm not at work for the rest of the week btw, although i'll probably pop online a few times | 22:19 |
| micahg | chrisccoulson: k, enjoy the time off, I'll try to keep things running :) | 22:20 |
| chrisccoulson | thanks | 22:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!