[02:34] Has anybody else had trouble accessing Gmail with Shiretoko? [04:36] whos awake? [04:53] Yo [04:53] I'm awake === thunderstruck is now known as gnomefreak [05:32] * gnomefreak needs to find out if we patched the pango build failures [06:48] asac / fta: ping? === reed is now known as Guest85285 [09:07] [reed]: ? [09:12] asac: mozilla bug 487170 [09:12] Error: Error getting Mozilla bug #487170: NotPermitted [09:12] let me check [09:13] just keeping you informed :09 [09:13] -9 [09:13] -0 [09:13] s/09/)/ [09:16] guud morning [09:19] Guest85285: why the hell did you make the lp private? [09:19] pedro said it was public for 5 month ;) [09:19] or is this a new bug [09:20] same bug, but the pango bug was embargoed [09:20] (just recently) [09:20] and the mozilla bug tracking it is private, too [09:21] timeless felt it would be good to close the lp ones, too, so I pinged here first to ask what best to do, but nobody was around :) === Guest85285 is now known as reed_ [09:22] well. closing up a bug that was 5 month open feels kind of wrong. but ok ;) [09:22] just that i probably cannot access it anymore ;) [09:23] why can't you access it? [09:23] ok i can see it at least [09:23] I would hope you would be on ubuntu's security group or whatever it's called :) [09:24] reed_: all fine [09:24] i can see it [09:24] k [09:26] reed_: bug control, is the team name [09:26] I was very surprised I was able to make the bugs private [09:26] didn't know I had any special rights [09:26] reed_: heh [09:26] reed_: i am not sure about that either [09:26] e.g. why can you make it private ;) [09:27] anyone can make reports private [09:27] BUGabundo_: bug control can see all private bugs? [09:27] just not the other way around [09:27] i doubt that [09:27] only bug control (or above) and OP can make it public [09:27] asac: AFAIK yes [09:27] I may apply to it, since i already do so much bug triage [09:28] https://wiki.ubuntu.com/UbuntuBugControl [09:28] i thin kbug control is for crashes [09:28] "What sensitive data should you look for in a private Apport crash report bug before making it public? See Bugs/HowToTriage for more information. " [09:29] yes. but thats just crashers [09:29] not all private bug [09:29] okay [09:29] ask Daniel or some leader of the team [11:41] asac, if you care to fix the dailies, that would be nice. i didn't have time in the last two days, and i still don't have much time right now [11:42] asac, that's mozilla 423756 [11:42] Mozilla bug 423756 in GFX: Thebes "Request: Switch for authors to turn on/off bilinear filtering when enlarging images" [Enhancement,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=423756 [11:44] fta: that one caused the regression? [11:44] yes [11:54] ok cool [11:54] asac: did had an chance to review my patch? [11:56] reed_: who would be best to ask about 480290 ? [11:56] oh, the colorful openoffice icons are gone [11:58] fta: colorful? [11:58] BUGabundo_: let me kick off a moz central clone and then look [11:59] desktop icons with blue, green, red, etc.. [11:59] BUGabundo_: do you have the merge url at hand? [11:59] nope. but since i only have that on my code.lp its wasy to find [11:59] fta: was that bug? [11:59] BUGabundo_: please url ;) [11:59] or request merge [11:59] ;) [12:00] thats actually much beter [12:00] because i can review online [12:00] no need to pull etc. [12:00] asac: https://code.launchpad.net/~bugabundo/mobile-broadband-provider-info/bug-312376-353957-280490 [12:00] i did request the merge [12:00] "i think". it was late in the night, and i already had failed 3 times [12:01] BUGabundo_: please request merge into the .ubuntu package branch [12:01] and how do i do that? [12:01] BUGabundo_: i assumed you worked on the packaging branch [12:01] and not the upstream branch [12:02] dunno [12:02] it was my ever lp branch [12:03] ok, ill start over and see if i get it better! [12:03] BUGabundo_ in the package there is a debian/control file [12:03] that should reference the packaging branch [12:03] asac: https://code.edge.launchpad.net/~bugabundo/mobile-broadband-provider-info/bug-312376-353957-280490/+merge/5213 [12:04] this was the merge request [12:04] asac: i just branched the trunk code, fixed the MBPI xml, commited and pushed to lp [12:04] then requested the merge [12:05] thought was the *way* of distrubuted coding of baazar [12:05] lunch! bbl [12:05] so the idea i had in mind was that you update the package and not the upsream branch [12:05] did not know it was required [12:05] lol [12:05] talk to u latter [12:13] damn it again its crashing [12:19] fta: /home/asac/Development/upstream/mozilla/mozilla-central/storage/src/mozStorageEvents.cpp:454: error: ‘PR_ASSERT_CURRENT_THREAD_OWNS_LOCK’ was not declared in this scope [12:19] i get that on trunk [12:19] didnt you see that too? === thunderstruck is now known as gnomefreak [12:30] gwibber is really working to piss me off this morning [13:17] asac: any chance the pango_font errors are fixed in firefox-3.5/3.6 or seamonkey-2? for some reason the dailies are not failing for tb and ff did you patch it or it never happened? [13:24] asac, http://www.sofaraway.org/ubuntu/tmp/oo-icons-before.png vs http://www.sofaraway.org/ubuntu/tmp/oo-icons.png [13:24] asac, ‘PR_ASSERT_CURRENT_THREAD_OWNS_LOCK’, i bumped the req for nspr already [13:25] yeah [13:25] its nspr [13:25] my build tree doesnt have that magi [13:25] now i bumped into DFB [13:25] interesting that all this starts suddenly i am sure i built with the same config not that long ago [13:25] now i bumped into the context_subst [13:25] ;) [13:26] context_substitute pango [13:27] lets see what happend to my pango bug [13:29] can someone paste me my quit message [13:30] * gnomefreak testing to see if it gets set [13:34] stupid damn /save crap [13:54] <[reed]> gnomefreak: SeaMonkey? [13:54] <[reed]> it's Core code [13:54] <[reed]> it affects all Mozilla projects building from that code [13:54] [reed]: yes [13:54] oh ok [13:54] than why does tb and ff build [13:55] <[reed]> I think fta has patched it with one of the earlier patches [13:55] <[reed]> even though that's wrong [13:57] patch will have to be removed once commited to hg i'm guessing within the next week or 2 it should be commited < probably less than that [14:04] it does seem like a fairly simple patch but i can wait, this late in the bug its not worth it [14:08] its just the way its called from what i can see I'm hoping this is a perm fix instead of changing it for each pango release [14:16] i think i found the reason for gwibber crashes but doesnt make any sense [14:33] its gnome-keyring by the looks of it that is causing the crash [14:42] noone else noticed gnome-keyring(deamon) is failing? [14:43] [reed]: so we have to back-in the localized locale thing (which made this blocklist url so ugly) [14:43] [reed]: we have a regression that navigator.language (for websites) is always en-US [14:43] so its the good old problem with matchOS = true [14:44] <[reed]> asac: so, what's the solution for this? [14:44] theres a few bugs on that in Lp and upstream [14:45] <[reed]> well, Pike calls matchOS ugly code :) [14:45] <[reed]> mozilla bug 331779 [14:45] Mozilla bug 331779 in Internationalization "Please enable intl.locale.matchOS by default" [Enhancement,New] http://bugzilla.mozilla.org/show_bug.cgi?id=331779 [14:47] [reed]: yes. but it doesnt help to say matchOS is broken ... distros obviously need this to make firefox work in a multi lang environment [14:48] [reed]: so for now i will go back and we should redicuss this imo [14:48] <[reed]> k, maybe we should get the other distros involved and work out what they need Mozilla upstream to fix [14:49] <[reed]> since there's a problem somewhere [14:50] [reed]: yeah. i think what it needs is a evalution where the intl.general.locale property is used in code and fix all occurences to properly deal with a localized pref [14:50] [reed]: we use it for quite some time, but when we submit patches they alwasy get rejected like the one i provided for this blocklist url: [14:51] e.g. "matchOS isnt supported, and there are other places that would break2 [14:51] however, we - as in distros - dont see many places that break [14:51] so it might be a red herring [14:52] so i could conduct a code review and see where that pref is used [14:52] but i dont want to do that if whatever we do gets rejected with "matchOS -> not supported" [14:53] its general.useragent.locale [14:55] i think i will just do that ;) === ubott2 is now known as ubottu [15:50] fta2: what did you do against the pango API change? [15:50] its still broken here in upstream central [15:50] did you pick the latest patch from bugzilla? [17:06] asac, i took the patch mentioned in the filename [17:25] fta2: wow ... that looks hackish ;) [17:25] ? [17:25] what? [17:26] asac, the patch? [17:26] it's not mine [17:29] yeah. didnt claim its yours ;) [17:29] but its tiny and serves my purpose to get further during build ;) [17:29] so i will take it localle here [17:59] fta2: asac: ok so apparently ryan didn't merge the stuff he was supposed to in the gwibber 1.0 branch [17:59] I am going to get ahold of him today and make him do it [18:00] jcastro: yes. whip whip ;) [18:00] I want to kill him [18:00] but no worries [18:00] jcastro: but rmember that i never committed to get 1.0 into jaunty still [18:00] I would like to try [18:01] the thing is sabdfl was mailing him convincing him to do all this m-i stuff [18:01] trying like: "throw in and see" is kind of late now [18:01] we need to thoroughly review the code [18:01] we have been testing 1.0 this whole time. [18:01] so tell me what i need to review ;) [18:01] I have been anyway [18:01] yes, the messaging-indicator stuff would be it [18:01] the rest has been pure bugfixes [18:02] yeah. i would have to look at the code changes for uploading anyway [18:02] if someone else uploads "just" on the ppa basis thats fine ;) [18:10] I've been running the m-i branch for a few days now [18:10] fta2: where is gwibber packagin branch that was released to jaunty? [18:10] there's one issue I know about [18:10] ok i found i [18:17] so the mi is already in the packaging branch? [18:17] it shouldn't be [18:17] err in the 1.0 branch i mean ;) [18:17] no, it isn't [18:17] [Merge] sync with lp:gwibber (but retain VERSION_NUMBER 0.9.1 [18:17] that comes with a bunch of indicate stuff [18:17] its 252 [18:19] wait [18:19] so there's a bunch of indicator stuff in 1.0? [18:19] revno: 237.3.36 [18:20] committer: Ryan Paul [18:20] branch nick: main [18:20] timestamp: Sat 2009-03-21 09:59:11 -0700 [18:20] message: [18:20] Merged in support for the messaging indicator [18:20] so they landed it [18:20] jcastro: yes. they made a huge "sync from trunk commit, but keep version low thing" [18:20] thats bad [18:20] ... [18:20] meaning 1.0 is now trunk [18:20] when did they do that, march 21? [18:21] on trunk they landed it on timestamp: Sat 2009-03-21 09:59:11 -0700 [18:21] trunk was synched to 1.0 on timestamp: Thu 2009-03-26 12:20:25 +0000 [18:22] man, that was like 3 weeks ago, why didn't they just tell us to put it in jaunty then? [18:22] dont ask me [18:22] well it didnt land until 26 march [18:22] thats two weeks ;) [18:22] * jcastro head-desks [18:22] question is why they merge in full trunk and pretend to be stable ;) [18:23] feeping creatureism [18:23] hehe [18:23] but well. [18:24] could be tha ti look at wrong branch [18:24] its bzr+ssh://bazaar.launchpad.net/%7Egwibber-committers/gwibber/gwibber-1.0/ [18:24] well, if 1.0 doesn't make it then they won't want .8 either [18:25] huh? [18:25] we have 0.8 in the archive [18:25] they don't want .8 as it is in jaunty [18:25] right, they don't want people reporting bugs on it, etc. [18:25] who doesnt want that? [18:25] ryan, he wants people using 1.0 because .8 is too old. [18:26] upstream always wants the latest crack [18:26] they have no real say what we distribute. they failed here [18:26] he's just going to end up telling people to use the PPA [18:26] they can come up with clean bug fixes ... not the whole trunk [18:26] thats ok. dont see why thats bad ;) [18:27] right [18:27] so what's the point of shipping .8 then? [18:27] so users get something by default [18:27] to install [18:27] without knowing the ppa [18:27] yeah but upstream won't fix their bugs and all that [18:27] the world is much larger than those that file bug reports [18:27] upstream never fixes bugs for old releases [18:27] right [18:28] question is if there are release critical bugs right now [18:28] if so we have to look if we can cherry pick the fixes [18:28] if not then there is no real problem. we distribute software like that all the time [18:28] i want the latest stuff in there, but they just were too late [18:28] we already put lots of work into getting their stuff into jaunty [18:28] If we could just get 1.0 without the m-i stuff [18:28] that would be ideal [18:29] but there's no way to do that is there? [18:29] i dont care about the mi stuff [18:29] right, me either [18:29] its just not promissing to look in the stable branch and see that its the trunk now ... just with version lower :) [18:29] yeah so I don't know why they did that [18:29] they should join the community or accept that we just dont take whatever they relesae in whatever form ;) [18:30] jcastro: anyway, i dont want to be really picky here [18:30] if folks really run this for a while ites probably ok [18:30] I've been running it [18:31] jcastro: but i want at least a bug that is kind of release critical to justify that [18:31] but I was not aware that trunk was synced back into 1.0 [18:31] I was under the impression that 1.0 was basically .8 that we had already with just fixes cherry picked [18:31] but now I am looking through the commit log ... [18:35] asac: ok stepping out for lunch, bbiab [18:35] jcastro: they also changed translatable resources, aka strings ;) [18:35] we have to talk to them about cherry picking a few things so they are still happy ;) [18:36] hmm i think string is not that important as its not translated in rosetta [18:36] not sure if they have translations at all === rZr is now known as RzR [18:43] asac: hi , i was busy [19:03] RzR: hehe. me too ;) .. so not an issue at all [19:32] asac: what is the status of bug 187313? I noticed there is an upstream patch now. [19:32] Launchpad bug 187313 in iceweasel "[MASTER] right click (with button release) might activate random popup-menu-item" [Low,Confirmed] https://launchpad.net/bugs/187313 [19:33] bdmurray: we would get it through upstream if they agree that this should land [19:57] ok [20:16] <[reed]> yeah, mozilla bug 406646 [20:16] Mozilla bug 406646 in XP Toolkit/Widgets: Menus "Clicking to open slow menu (e.g. Bookmarks) invokes first item in menu (e.g. "Bookmark This Page")" [Normal,Verified: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=406646 [20:16] <[reed]> it's waiting on approval for the branch [20:17] asac: will you need me this evening ? or before freeze ? [20:17] <[reed]> which is waiting on 3.0.9 to finish [20:20] RzR: yes. iwill look now. [20:20] ok here i am [20:21] * asac branches [20:24] [reed]: http://git.gnome.org/cgit/pango/commit/?id=dd6ce709db5872132335fef9f75aa16a33d6e5aa [20:25] <[reed]> I know [20:25] good [20:25] <[reed]> hopefully, behdad can do a release of pango soon that distros can take [20:26] he has a few days left for jaunty [20:29] RzR: * debian/watch: [20:29] - Renamed to watch.ex since it wont work on .xpi / cvs tree [20:29] you should have just removed it ;) [20:29] anyway [20:29] not an issue [20:29] do that next time [20:29] k will not next time [20:30] i wish i could track the version in the xpi [20:30] RzR: why "prefer ff 3.5"? [20:30] that gnomefreak recommandations [20:30] he told this here [20:30] i am clues [20:30] i have ... [20:30] RzR: we can track version of xpi ... but for that it has to be a non-native extensoin that ships a proper license file in top level dir [20:30] k [20:31] i think he ment to use 3.5 and not 3.1 [20:31] but ok [20:31] firefox is still preferred which currently points to 3.0 [20:31] so its good [20:31] ok [20:32] i dont log this channel [20:32] but if someone does, maybe he explained about ff3.5 i dont remember [20:40] RzR: uploaded [20:40] RzR: please trash your branch then [20:40] great work asac you're the best [20:40] and next teim start from the ubuntu-dev again [20:41] RzR: sorry for delay [20:41] sure i will [20:41] now lets watch a german documentary [20:41] we feed the world [20:41] maybe it's from austria [20:41] on arte.tv [20:41] thx === RzR is now known as rZr [20:48] asac: just checking... what has happened with nspluginwrapper we finished few days ago? it didn't make it to jaunty? [20:50] Jazzva: still on my list ;) [20:50] back [20:50] Jazzva: i need to do the flashplugin-nonfree rename and do the auto upgrade stuff in that same turn [20:51] asac, so.. i see xul failed once again, you didn't fix it, right? [20:51] fta: i did [20:51] asac: ok. we should document the option in the manpage for the next upload. do you think it's the patch to be worthy enough to send it upstream? [20:51] s/it's// [20:51] umm. let me rephrase that [20:52] asac: do you think the patsh is worthy enough to send it upstream? [20:52] s/patsh/patch/ (argh) [20:52] Jazzva: this patch only makes sense with the other NSPLUGIN env part [20:52] i think for upstream we would need to make proper options out of that [20:52] instead of the env approach [20:53] fta: its Committed revision 438. [20:53] fta: my commit got stuck because i had no ssh agent running ;) [20:53] asac: mhm. ok. we can see to work on that. I think it would be a nice addition. anyway, I'm back to painting the room. [20:53] Jazzva: have fun [20:54] thanks, you too [20:56] asac, let me know when it's in. 3 or 4 days without a green 3.6, i can respin it manually [20:57] fta: its in [20:57] i can also upload the current orig [21:02] no need, the bot will take care of that === Jazzva_ is now known as Jazzva [22:29] asac, any news about your gtk patch? [22:37] fta: i found out that i need a runtime abi check to finish this in a way that doesnt break in no-biarch case [22:37] at least i think that the issuse i saw here need that [22:38] could you please grab bug 190227? [22:38] Launchpad bug 190227 in ia32-libs "ia32 apps look for libs on the wrong place" [Low,Confirmed] https://launchpad.net/bugs/190227