[00:17] http://lwb.lawnet.com.sg/legal/lgl/rss/legalnews/57100.html === asac_ is now known as asac [07:50] hi [10:09] jimmy_: cwong1: what is the merge path: mergerc1 -> master -> [hardy, gaston] or ... master -> hardy -> gaston [10:23] asac: are you able to push to backports? and do you have a bug for backporting FF3RC1? [10:24] gnomefreak: did jdong say anything about his plans to backport those? [10:24] asac: i havent heard from him but ill do xul and ff if someone can push [10:24] afaik he has the sufficient privileges to do that [10:25] gnomefreak: its not a simple task [10:25] at best synch up with jdong ask most tweaks we needed on last backports should be valid too [10:25] well if i cant find him ill ping crimsun afaik he can still push to backports [10:25] gnomefreak: i can push, but you have to do it properly :) [10:26] for that its easiest to talk to jdong [10:26] crimsun doesnt know about these specificfs [10:26] asac: properly as in? example i have flash 10 done for hardy and gutsy in my PPA already [10:26] he should hes been pushing to backports for a while [10:27] gnomefreak: yes. for flash 10 you should talk to crimsun maybe we want to push the fixes that came with it in intrepid to backports too [10:27] but for ffox and xul go jdong ;) [10:27] gnomefreak: i meant ffox+xul specifics; not backports specifics [10:27] asac: ok ill ping him again as soon as im done with email and see how he wants to handle ff and xul [10:28] good ;) [10:28] we really shouldnt need to backport them since they are security updates for most part. [10:29] well, backports is better [10:29] security doesnt really have a testing stage [10:30] no? i thuoght proposed was testing stage? [10:31] ah well [10:31] sorry, my confusion [10:31] gutsy was not really supported and -backports worked quite well [10:32] we could however consider to sync through -proposed when ffox 3 is final [10:32] lets keep that on the radar [10:32] backports is fine but security has a better testing period AFAIK [10:32] gnomefreak: s/security/-proposed -updates/ [10:32] security has no testing period at all [10:33] its just rolled out [10:33] oh thats right [10:33] proposed does go to updates [10:33] thought it was other way around [10:34] but that sounds right now [10:35] <[reed]> by the time asac gets rc1 out to users, rc2 will be out [10:35] <[reed]> :P [10:37] asac: im reading something and wondering if we shouldnt wait for RC2 for gutsy backports, by the looks of it its looking like builds start on tomorrow [10:37] [reed]: bah! [10:37] and QA tomorrow [10:37] gnomefreak: doing the RC1 work wont hurt the RC2 work [10:38] asac: by the tim RC1 gets into backports rc2 will be ready to spin [10:38] from what i can tell by this email [10:38] he proposed, estimated RC2 schedule is as follows: Code Freeze: Wed, May 28, noon PDT Start Builds: Thu, May 29, early am PDT Start QA: Thu, May 29, noon PDT (as builds become available) QA Complete: Thu, June 5 [10:39] final push for RC2 is next week [10:39] gnomefreak: yeah, jdong can also work on RC2 directly. no need to wait for the release [10:39] should be tagged by tomorrow - when builds start [10:39] asac: ok but hes been a pain to get intouch with the past week or so [10:40] gnomefreak: let me know when you see him active [10:40] i can prod him directly [10:41] crimsun: anything you need for my Flash10 push for hardy and gutsy backports? i have them built on my PPA waiting approval im going through email atm so im not sure if anyone commented on the bug yet but if you can let me know what you need me to do, i know target needs to be changed from hardy to hardy-backports and a bug # added to changelog everything is there i just need to fill in bug # to close it. [10:42] asac: i will [10:43] :( they are not changing the logo for FF3 anymore [10:43] why would they? [10:45] there were plans to [10:45] On 27-May-08, at 4:37 PM, Omega X wrote: [10:45] > > [10:45] > > Some time ago Alex Faaborg reported that HicksDesign was working on an [10:45] > > updated Firefox logo for the 3.0 release. However, other than a small [10:45] > > teaser some time ago, there is zero information on what happened to [10:45] > > it. [10:45] > > [10:45] > > Was this project abandoned? [10:45] For this release, yes. [10:45] cheers, [10:45] mike [10:49] <[reed]> yeah [10:53] asac: how far are you on Hardys RC1? [10:53] [reed]: why was it abandoned? [10:54] gnomefreak: all uploaded [10:54] <[reed]> not abandoned [10:54] waiting for langpacks to arrive [10:54] <[reed]> just postponed [10:54] asac: ok cool [10:54] <[reed]> until some future release [10:54] [reed]: ah ok thanks [10:54] <[reed]> the rough drafts look pretty awesome [10:54] <[reed]> :) [10:54] i hope that they will enter proposed today [10:55] <[reed]> asac: can you read up on mozilla bug 424626 and see if you can help any? [10:56] Mozilla bug 424626 in OS Integration "(linux) Firefox is put into offline mode on startup when user is using PPP and has networkmanager installed" [Major,New] http://bugzilla.mozilla.org/show_bug.cgi?id=424626 [11:09] not that again :( [11:12] [reed]: commented ... still have to wade through the complete report ;) [11:12] <[reed]> thanks [11:14] why are we rejecting confirmed and in progress bugs? [11:16] gnomefreak: depends on what the bug is [11:17] its hes only waiting ~30 days before rejecting bugs [11:17] i thought that is why incomplete has a 60 day time [11:18] they are old bugs but would be nice to find out the result. one we sent bug/patch upstream and never heard back freedy never gave link to bug maybe just an email [11:19] and this one you marked mt-eval in 02/2007 disable pango better preformance [11:19] bug 64844 [11:19] Launchpad bug 64844 in firefox "Firefox starts very slowly" [Low,Invalid] https://launchpad.net/bugs/64844 [11:20] bug 64844 [11:21] asac: also any chance of geting network manager to not use verbose when shutting down? [11:22] that is strage :( [11:22] if you type /win you get info that ive never seen before [11:23] brb smoke [11:52] asac: im thinking sometime this week im gonna work on states and tags page. tags: get rid of unused tags states: example confirm if you think the bug needs to be confirmed please tag bug as mt-confirm than one of the mozilla team members will move it to confirmed or ask for more info before we move to confirm. that will get rid of confusion on how bugs prgress to confirm since people are confused by the wiki and instead of taggi [11:52] but today im gonna be a bit on the busy side with drs. and shit [11:54] gnomefreak: lets talk about that page first [11:54] i want to improve the procedure for forwarding bugs upstream in particular [11:56] asac: ok thats fine but sooner the better since both pages are outdated and pointing people there isnt helping much. i was looking at sending an email out for a meeting on a few things one being those pages, but pretty much a status meeting [11:57] maybe ill send out email by friday asking for dates and times that people are free other than june 11 24 and 25 [11:58] but i have to see when im out of meetings so a round about date can be given so we have starting point [12:01] gnomefreak: better just ask the most important folks here in channel, then send out a meeting date without asking for input [12:01] seems more reasonable to do it that way [12:01] we are unlikely to get everything right [12:05] asac: true [12:06] when i get home from drs. today ill ask and start there. bug since i may be back a bit on later side maybe wait till tomorrow. [12:08] asac: would like to concider moving from mt-eval > mt-upstream asap and than we can look upstream for bug or report as needed. but we can get into more detail in meeting on how to handle all that. [12:11] there was some UDS discussion on this. ill come up with a separate document just for how to better organize upstream bug coordination [12:11] we want the QA team to get involved in the long run, so we have to tailor our workflows in that direction [12:13] ok sounds good [12:14] asac: people are asking about triaging bug 163481 in #ubuntu-bugs, since your the main n-m dev i relaied to you [12:14] Launchpad bug 163481 in network-manager "Gutsy: USB devices stop working" [Undecided,In progress] https://launchpad.net/bugs/163481 [12:19] ok time to get ready to leave. ill see you later [12:24] cu [12:30] bye asac *g* [12:31] i'll check if rc1 still gives sigbus on sparc [12:33] i am here [12:35] lies! [12:36] i'll file a bug for the hppa thing as well [12:36] armin76: do you get a sigbus on sparc on hardy? [12:38] i don't remember [12:40] i'll try [12:56] Setting up firefox-3.0 (3.0~b3~cvs20080101t1000+nobinonly-0ubuntu1) ... <- thats what hardy has [12:59] asac: yeah, it does [12:59] it doesn't even start [13:00] i'll try with intrepid [14:11] re [14:23] bah [14:23] i hit bug 234345 [14:23] Launchpad bug 234345 in findutils "xargs: xargs.c:443: main: Assertion `bc_ctl.arg_max <= (131072-2048)' failed." [Critical,Confirmed] https://launchpad.net/bugs/234345 [14:23] asac: fixor [14:24] armin76: you need to update your system [14:24] thats what i am doing :P [14:28] lets see if i'm able to do the chroot from intrepid [14:53] jt1: there is a bunch of imports waiting for review in https://translations.edge.launchpad.net/midbrowser/+imports === jt1 is now known as jtv [14:54] for now i need to use the product as it will take a while before we can enable midbrowser translations in langpack-o-matic [14:54] asac: OK, going to look... [14:54] jtv: interestingly the other all imported and got auto approved [14:54] asac: since this is an original product, that's fine. [14:54] maybe because we approved them once [14:54] good [14:55] asac: turns out that auto-approval doesn't kick in if (1) you upload for a specific template, and (2) the auto-approver doesn't recognize the filename as a language code. [14:55] hmm [14:55] i uploaded all you see there throgh the same form [14:55] so (1) isnt the case here [14:55] asac: with names like zh-CN (note dash instead of underscore!) it's conservative and assumes it may not be a language code. [14:55] not sure why (2) would be a problem ... most likely because of region code [14:55] yes. [14:56] asac: it's the combination that matters. [14:56] ok the pattern matches here [14:56] asac: the region code isn't the problem—the dash is! [14:56] hmm ... but importing works ;) [14:56] ah [14:56] asac: I'm planning to fix this. It's a very small tweak to the auto-approval code. [14:56] ok so i can rename it on next upload? [14:56] can you approve for now or is that a problem? [14:56] asac: you can always do that, and then approval should be automatic. I'll approve these right now though. [14:56] great [14:57] as long as the import at least figures the proper locale it should be fine [14:57] asac: the fix should even deal with the "es-ES" case (which is really an incorrect language code from our point of view) [14:58] kk [14:59] asac: approvals are all done. [14:59] great. thanks [15:47] asac: same on intrepid [16:41] oh... [16:42] asac: fta: remember the hppa failure? sparc had the same issue, mozilla bug 417345 [16:43] Mozilla bug 417345 in XPCOM "build broken on sparc" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=417345 [16:43] 17:37 < asac> jtv: is there a chance that the ui https://translations.edge.launchpad.net/midbrowser/trunk/+pots/midbrowser isnt up-to-date? [16:43] 17:38 < asac> though imported there are a bunch of strings that should be there in theory [16:43] 17:38 < asac> oh wait ... those make actually sense [16:43] 17:39 < asac> nevermind [16:43] [reed]: ^ should i open a new bug or reopen that one? [16:44] armin76: does a similar fix work? [16:44] let me try [16:44] but it should [16:50] unfortunately the only thing mozilla is going to do is ignore those reports, not fix the alignment thing :/ === asac_ is now known as asac [16:51] armin76: why? [16:51] armin76: if you have a fix, open a new bug, reference the sparc bug as a blocker for that [16:51] and let me know. [16:52] maybe open an ubuntu bug so we can properly track it here too ;) [16:52] because thats what mozilla did for sparc and ia64 :) [16:52] https://bugzilla.mozilla.org/attachment.cgi?id=309157 [16:57] armin76: so sparc is broken now? [16:57] or do you just disagree that removing those warnings was a good thing? [17:06] asac: no, sparc was broken because it was spewing those warnings about alignment stuff [17:07] so it didn't build, like hppa doesn't now [17:07] and considering that sparc and hppa segfault with bad alignments... [17:11] but again, mozilla doesn't care, as per comments on bug 411292 [17:11] mozilla bug 411292 [17:11] Mozilla bug 411292 in Networking: Cookies "Build failure in cookies on ia64" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=411292 [18:12] <[reed]> armin76: file a bug [18:21] [reed]: i did already, mozilla bug 436133 :) [18:22] Mozilla bug 436133 in Networking: Cookies "Cookies build failure on hppa" [Normal,Assigned] http://bugzilla.mozilla.org/show_bug.cgi?id=436133 [18:22] <[reed]> k [18:23] <[reed]> looks good [18:23] <[reed]> ted will get to it [18:26] :) === asac is now known as asac1 === asac1 is now known as asac [20:19] * asac off doing NM stuff [22:52] mozilla 402240 [22:52] Mozilla bug 402240 in General "[RTL] Need a better way to control the statusbar direction" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=402240 [22:56] hes not here? [22:56] Jazzva: you here? [22:56] present... [22:59] Jazzva: the firegpg is in bzr if you want to peek and find out why its not installing. When you have time [23:00] Jazzva: i left you a note on the bug report that was reported on it not working with mac-intel [23:00] gnomefreak: Ok, I'll take a look in 10-20 minutes. BTW, I closed that bug report, because it seemed like it's not related to the package, since it's still not in the archives. [23:01] Jazzva: thats fine [23:01] i also left a note i remember reading that it didnt support mac but not sure if they meant intel or pre intel [23:02] !info firefox-3.0 hardy [23:02] firefox-3.0 (source: firefox-3.0): safe and easy web browser from Mozilla. In component main, is optional. Version 3.0~b5+nobinonly-0ubuntu3 (hardy), package size 1001 kB, installed size 3436 kB [23:02] hmmmm [23:07] Jazzva: before i forget here is bzr link https://code.edge.launchpad.net/~gnomefreak/firefox-extensions/firegpg.ubuntu it has upstream and ubuntu mixed in i have a separate upstream as well [23:08] I found it ;)... branching [23:08] ah [23:09] holy shit thats alot of deps [23:12] gnomefreak: Seems that upstream version is 0.4.9, in debian/changelog you're using 0.1 for base version. I think we should go with the current upstream, and just add -0ubuntu1. Also, you're missing a right bracket in LP: #bugnumber, and there's one typo. [23:12] did i? [23:12] yep [23:12] i didnt mean to :( [23:12] * gnomefreak not sure wher ei got .1 form [23:12] from [23:13] but that wont make it fail to install :) [23:13] It's no problem... [23:13] right, I'm looking at the rest now [23:13] its easy enough for me to fix for the build. I dont remember seeing a perminstall postinstall dirs inside debian [23:14] For debian/control, I think we're trying to keep the lines at 80 char max. It's not an error, though... [23:14] and the same for debian/changelog... [23:15] if its over 80 i didnt add anything so the template needs to be fixed (for control) [23:16] It's in the description... [23:16] Just break the lines :)... [23:20] ah [23:30] i have to be stupid as shit tonight. WTH is the "bottom boarder"? [23:31] Maybe "bottom border"? [23:36] Jazzva: bug 205076 [23:36] Launchpad bug 205076 in firefox-3.0 "Widges in search bar in Firefox 3 are not properly painted" [Undecided,Incomplete] https://launchpad.net/bugs/205076 [23:36] that bottom boarder. if you see what they mean please explain [23:43] when the hell did gmail start using imap :( [23:50] be back in a bit i need to eat dinner.