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