[01:19] asac, can I/you rename nss-svn.debian.org.trunk ? s/-/./ [01:19] at least [01:28] gnomefreak, when the new LP will be released ? [01:28] s/new/next/ [01:28] Ubulette: dont know [01:29] last i heard this week but hter eis no telling [01:29] same time as ppa ? [01:30] i doubt PPA will be released with 1.1.9 last i heard they havent made much headway with features but that really doesnt mean much i wouldnt think [01:32] don't they have a blog/rss when they speak about that ? [01:34] asac: do have plans on releasing 2.0.0.7 this week? [01:34] Ubulette: not that i know of [01:34] just the mailing list [01:35] We were planning to release Launchpad 1.1.9 on Wednesday the 19th [01:35] September. Following quality assurance testing, we've chosen to delay [01:35] the release to allow for further testing. [01:35] We'll post updates to the launchpad-users mailing list and via the [01:35] Launchpad News blog at http://news.launchpad.net/ [01:35] good timing [01:35] i found that in email right after i commented [01:36] "The next release of Launchpad is due on the 19th September." [01:36] hmm [01:36] yesterday for me [01:38] gnomefreak: no its win only issue [01:38] no its released for mac win and linux [01:38] Bug 43808 [01:38] Launchpad bug 43808 in launchpad-bazaar "Create and display bug-branch from the branch page" [Medium,Fix committed] https://launchpad.net/bugs/43808 [01:39] oh you mean the bug? [01:39] gnomefreak: its a spinoff release that just fixes one bug [01:39] gnomefreak: that bug is win only [01:39] gnomefreak: they released all because of techinical issues [01:39] omg [01:39] thats stupid [01:39] release win only for win only fix but hell fix 30 things not 1 [01:40] gnomefreak: hey [01:40] gnomefreak: thank god they didn't [01:40] lol [01:40] true [01:40] but i cant see a whole upgrade for one issue [01:40] gnomefreak: i hate that ... i have to backport stuff ... if they do out of schedule mass bug-fixes its really a big pain [01:40] seems like a waste unless it was a big issue [01:40] so we will wait for 2.0.0.8? [01:40] its important to have a more or less reliable schedule [01:41] yes ... because 2.0.0.7 doesn't fix anything for us [01:41] lol we wont get 2.0.0.8 for atleast another month or 2 [01:41] no ... this is a non-regular release [01:42] they will just push the planned release back for a week or so [01:42] so 2-3 weeks is my guess [01:42] oh ok [01:42] cool [01:43] asac: btw if you comment on the iceape bug in debian about not recommending -gnome-support tell him thats why it a recommend not a depend [01:43] gnomefreak: my bug backlog is huge [01:43] i will probably not come to that for a few days [01:44] i've renamed the branches [01:44] debian bug 443219 [01:44] Debian bug 443219 in iceape-browser "iceape-browser: should not recommend iceape-gnome-support" [Normal,Open] http://bugs.debian.org/443219 [01:44] updated nspr source name [01:45] updated nspr.dev source name but not nspr as it will prevent the pull [01:46] i have a problem with nss. I've renamed my own branch nss.head, 2 or 3 commits ahead of nss.dev, itself ahead of nss [01:46] gnomefreak: i think the claim is that it should suggest it [01:46] how can I change source name? [01:46] what differnece does it make debians apt doesnt install recommends unless they changed that the same time we did [01:46] Ubulette: source name? [01:47] package source name [01:47] Ubulette: i don't think i understand your question [01:47] in changelog? [01:47] control [01:47] Source: [01:47] to what? [01:48] is that your question? [01:48] not to what as I thought we agreed on that. but to how ? [01:48] no idea... pick one ;) [01:48] nss3 [01:48] or wait [01:48] eh ? [01:49] just use nss [01:49] yes [01:49] thats the name of the official package [01:49] but to which of the 3 branches ? [01:50] would be logical to push to head, then pull dev, then plain nss [01:50] its always the "release branch" that doesn't have a suffix imo [01:50] s/pull/merge/ ... yes [01:51] but head is a tarball away already [01:51] yes ... i think we cannot get rid of a branch [01:51] head can follow real HEAD [01:51] yep [01:51] that's the idea [01:52] so we forget about merging head in dev ? [01:52] or cherry pick maybe [01:52] point is we should not try to use real head for our dev releases [01:52] that i agree [01:52] cherry-picking the right firefox/xulrunner revision is straight forward [01:53] but how do we find the right nss/nspr revision on head [01:53] (given that head is always perfect) [01:53] i think we need the dev branch ... because we might need to bump changelog a-posteriori [01:54] as we never know where the next tag might be set we might not have the proper changelog committed to head [01:54] today, the 3 branches are in sync. rev 13, 15, 17 respectively [01:54] and updating/commiting changelog version for each update on head would be too much? [01:54] i am not sure, maybe thats even ok [01:55] i mean whenever your bot receives a checkin it should bump changelog, try to build and if build successful, commit with a parsable commit message :) [01:56] it does just that [01:56] to your local bzr? [01:56] oh no [01:56] to a local db [01:57] why not to local bzr? [01:57] could be anything [01:57] do you still have .bzr dir in your build tree? [01:57] no [01:57] or do you use export or something [01:58] if you would do that it would be simple to commit and auto push i guess [01:58] I drop the tree at the end of the build. I just keep logs and all the files produced [01:58] no no [01:59] my questin is if the .bzr directory is in tree during build ;) [01:59] oh.. hm. no, I drop it before it gets there [02:00] but I can probably keep it [02:00] yes ... then if build succeeds just do bzr commit -m "CHECKPOINT: 20070606t1231 successfully build." [02:01] and bzr push [02:01] to publish to head ;) [02:01] actually you could also commit if it fails ;) [02:02] bzr commit -m "CHECKPOINT: 20070606t1231 failed to build - RED LIGHT BLINKING." [02:03] then i would add a bot here that regularaly looks at top log entry on .head branch and adds the info that tree is broken to TOPIC :) [02:03] what a tailored thing ;) [02:04] anyway ... the question still remains: "how to easily identify the right nss/nspr revision" [02:04] I have a dozen or more reasons for failure, some not related to build, but that's possible. I'll think about it. [02:05] actually the build failure commit was more like a brainstorming thing ... nothing well thought out [02:06] btw, I can probably just export the logs and the reports within my minirepos [02:06] I have an internal web portal quite similar to lp :) [02:07] but that doesn't help us in forking of bzr checkpoints to our release branches [02:07] or is it unrelated? [02:07] unrelated [02:08] yes logs would be fine [02:08] just brainstorming too :) [02:09] Ubulette: ok lets go this way for now: [02:09] i also plan to preserve the last x successful builds [02:09] until nss/nspr are uploaded to gutsy we don't have any problems [02:09] we just use nss.HEAD and nspr.HEAD ... and plain nss/nspr [02:09] plain nss/nspr would serve as ppa release branch for now [02:10] once we upload to gutsy we can do something [02:12] so I drop, nss (rev13), rename nss.dev (rev15) to nss, keep nss.head (rev18 now) [02:14] Ubulette: dropping is bad ... better merge nss.dev on nss and then mark nss.dev as merged in launchpad [02:15] if you prefer, bzr log will show no difference [02:16] he? [02:16] there is one commit in nss that isn't in nss.dev [02:16] if you merge your merge will be one major revision in bzr log ... with subcommits nested [02:16] otherwise it will stay flat [02:17] you want non flat ? I thought you didn't [02:17] just try cd nss; bzr merge https://code.edge.launchpad.net/~mozillateam/nss/nss.dev; bzr commit -m "merging branch https://code.edge.launchpad.net/~mozillateam/nss/nss.dev" [02:17] thats what i mean [02:18] the look at bzr log |more [02:19] too bad nm failed to build on amd64 [02:19] because of missing depends [02:19] same for ia64 [02:21] you didn't try on your own box ? [02:22] yes i did [02:22] i think its just a matter of giving back once the gnome stuff is build [02:23] hopefully tomorrow [02:32] asac, got some diffs ? [02:40] asac, nss/nspr/xul should be ok. ff need serious work. [02:40] but not today [02:41] yes got the diffs for nss [02:41] and nspr [02:43] i am out for this night [02:44] me too [02:44] 'night [02:44] me 3 === beans [n=beans@c-69-247-126-91.hsd1.ar.comcast.net] has joined #ubuntu-mozillateam [03:44] when will we be able to apt-get firefox 2.0.0.7 ? === tonyyarusso [n=anthony@ubuntu/member/tonyyarusso] has joined #ubuntu-mozillateam === bluekuja_ [n=andrea@host104-235-dynamic.1-79-r.retail.telecomitalia.it] has joined #ubuntu-mozillateam === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-mozillateam === asac [n=asac@debian/developer/asac] has joined #ubuntu-mozillateam === rhelmer [n=rhelmer@people.mozilla.com] has joined #ubuntu-mozillateam === paran [n=paran@cl-56.sto-01.se.sixxs.net] has joined #ubuntu-mozillateam === Mirv [n=tajyrink@pdpc/supporter/active/Mirv] has joined #ubuntu-mozillateam === IdleOne [n=idleone@unaffiliated/idleone] has joined #ubuntu-mozillateam [08:47] asac: Ubulette do either of you have the songbird svn link if your awake or here [08:57] i got it nvm forgot i filed bug with the info on it [09:05] !info nspluginwrapper gutsy [09:05] Package nspluginwrapper does not exist in gutsy [09:05] yes it does [09:05] !info nspluginwrapper [09:05] Package nspluginwrapper does not exist in feisty, feisty-seveas [09:26] asac: im looking at fixing nspluginwrapper bug but its just a depend bug easy to fix do you have any other fixes that need to be done? i looked at bugs and there wasnt enough info on them to seek a fix, let me know if you want me to wait a bit or go ahead and fix the depend right now depends on linux32 and should depend on util-linux since it brings in linux32 and conflicts with linux32 (is this worth uploading for just this fix? [09:26] maybe tomorrow ill fix it and make a branch for it [09:29] its already 3:30 [09:29] :( [09:31] ok im going for smoke than gonna lay down and try to get some sleep so i can be awake for more paperwork [10:32] gnomefreak: what bug? [10:32] i knew you would ask that :( [10:32] ill find it in a minute [10:33] does tbird import CSV for addressbook? [10:33] no idea :) [10:34] 138265 [10:34] bug 138265 [10:34] Launchpad bug 138265 in nspluginwrapper "Nspluginwrapper depencies should be updated" [Undecided,New] https://launchpad.net/bugs/138265 [10:34] asac: i looked it up and hes right on what he stated about depends [10:35] btw tbirds --help page can use some clean up [10:35] its all over the place [10:35] is that true? [10:35] about the deps? [10:35] yes very much so [10:35] show util-linux [10:36] or whateve rthe package is it contains linux32 and under conflicts it lists linux32 [10:36] cant understand why it would conflict with it if it installs it anyway [10:36] well ... but it should not be broken [10:36] because util-linux provides linux32 [10:37] thats why the conflict bothers me a bit [10:37] no util-linux now provides linux32 [10:37] why would it conflict with it if its gonna install it [10:37] so installingb linux32 should bring you util-linux [10:37] let me check that [10:38] anyway ... we can update that [10:38] ARNING: The following essential packages will be removed. [10:38] This should NOT be done unless you know exactly what you are doing! util-linux [10:38] yeah [10:38] thats bad [10:38] thats bullshit [10:38] so is freeze lifted? [10:38] i guess remove it from depends and just add until-linux [10:39] asac: no it just started afaik [10:39] aeh inforst [10:39] i mean ;) [10:39] enforced [10:39] damn [10:39] today is the day we freeze [10:39] for a week :( [10:39] is it already started? [10:39] im not sure what time it starts [10:40] ive been up all night and havent seen anyone say anything other than today we freeze [10:40] is tbird in main now? [10:40] i think it is but cant remember [10:40] its always been in main [10:40] edgy it was in universe iirc [10:41] there was a bug to move it to main (i remmber commenting on it) but it was a long time ago [10:42] gnomefreak: ok i milestoned the bug and assigned to me [10:42] i will try to get this in during freeze then [10:47] k [10:47] asac: tbird handles CSV but it handles it like shit [10:48] it imporrts the address book but it leaves the display and email fields blank and just lists first name and email under last name [10:55] ok im gonna try to get some sleep since its alread almost 5am [11:06] gnomefreak: hmm ... i doubt that there is a standard csv format for emails === cwong1 [n=chatzill@pool-71-182-72-50.ptldor.fios.verizon.net] has joined #ubuntu-mozillateam [03:19] asac: ping [03:26] cwong1: hey [03:27] asac: can you make a release with the latest from WORKING, please? [03:28] hmmm ... how about adding more features? [03:28] btw, the archive is frozen anyway ... so lets use this week to add more things we want. [03:29] ok [03:29] I am working on the signleton stuff now [03:30] singleton? [03:30] whats that? [03:31] We are not going to allow more than 1 copy of browser running at the same time [03:31] and how do you prevent that from happening? just through config? [03:32] I added a bug to launchpad on this. [03:32] ok [03:32] ah cool a few more bugs ;) [03:32] Need a service file and some code at startup to check for it. [03:32] Also, we need to remove "New Window" feature from browser. [03:32] cwong1: are you aware of the fact that there is no more than one instance running anyway? [03:33] its just new windows [03:33] so if you stop the start code to do anything on startup you will break the "open new link from outside applications" ... [03:34] ah... [03:34] cwong1: i will add the infos needed to the bug [03:34] ok [03:34] cwong1: "replace it with "Load URL into the same Window"." [03:34] yes [03:35] we can use "open links in new tab" [03:35] is that suitable as well? [03:35] also I need to raise the window to the top [03:35] new tab is a good option [03:35] cwong1: ok thats just settings ... we have that in gutsy firefox already [03:36] which setting? [03:36] can you still access the preferences dialog? [03:36] I though this is the default [03:37] no idea if its the default ... we should verify [03:37] cwong1: try to open chrome://browser/content/preferences/preferences.xul [03:37] in location bar [03:38] then verify that in Content ... its set to "in new tab" [03:38] "New pages should be opened" ... a new tab [03:38] is that what is currently set? [03:38] It is the default. [03:39] ok ... so are there any bugs you see? e.g. links from external applications still open a new window? [03:40] not sure. But we still need to remove the "New window" menu from the popup [03:40] yes, but thats trivial i guess, right? [03:40] yes [03:41] ok, I will take a look at this and take care of it [03:41] what about hildonize the window? [03:41] cwong1: cool ... ok one more thing for the link thing [03:41] look at about:config [03:41] search for browser.link [03:41] ok [03:41] you will see the settings browser.link.open_external [03:41] browser.link.open_newwindow [03:42] both should be 3, right? [03:42] maybe you want to set open_external to 1 ... or even 0 (no idea which setting) [03:43] yes both are 3 [03:43] i think there should be a value that will open in the current active tab [03:43] (if that is what we want) [03:43] ok. I will give that a try [03:43] anyway ... i think opening a new tab is good [03:43] we just have to decide if we want the new tab to be active or the old tab [03:43] agree [03:43] i think default is to keep the old tab in foreground [03:43] the new tab most likely [03:44] yeah ... we should research why the firefox default is on keep old tab [03:44] there might be a sane reason :) [03:44] (in usability) [03:44] (or confusion) ;) [03:45] but maybe its different for us because of the different screen layout approach [03:45] yes, I will let the usability folks tell me what to do after they do the study [03:45] :) [03:46] what about hildonize toplevel window? [03:46] cwong1: i commented in bug afaik [03:46] bug 140525 [03:46] Launchpad bug 140525 in midbrowser "hildonize the toplevel window" [Undecided,New] https://launchpad.net/bugs/140525 [03:47] cwong1: basically the idea is that we hildonize by implementing hildon features in our hildon service component [03:47] cwong1: as the hildon api is too GTK focussed [03:47] and firefox/midbrowser isn't a real gtk application [03:48] so we should analyse the hildon features we want and i can implement them [03:48] So eveytime we goto a different page, we need to reset the title. [03:48] can you add that info to the bug [03:48] ? [03:48] ok [03:48] e.g. add cases that don't work [03:49] ok [03:49] you can add examples of missing hildonfeatures to the summary [03:49] by editing description/tags [03:49] great [03:49] I will do that. Goto go. Need to get kid ready to school and go to work. [03:49] talk to u later. [03:49] cwong1: ah still at home [03:49] kudos === AlinuxOS [n=vsichi@87.16.133.72] has joined #ubuntu-mozillateam [03:49] cu [03:50] hi AlinuxOS [03:50] Hello all, [03:50] cu [03:50] so what is the case? [03:50] hello asac [03:50] i tested all here [03:50] e.g. i installed all .debs and then looked at each locale one time [03:51] here is my latest apt-get upgrade result: [03:51] http://paste.ubuntu-nl.org/37985/ [03:51] AlinuxOS: can you please paste that again to http://paste.ubuntu.com [03:51] ah ok [03:51] btw paste.ubuntu.com exists now ;) [03:51] asac, great!!! [03:51] finally :D [03:52] I sometimes I don't remeber about ubuntu-nl :D [03:52] AlinuxOS: please tell me which version the mozilla-firefox-locale-ka that you have installed has [03:52] its probably a hand crafted thing (3rd party package) [03:52] but pleaes tell me [03:52] what i asked before you remove it [03:53] mozilla-firefox-locale-ka-ge 2.0.0.1ubuntu-1 [03:53] and it's not hand made... [03:53] it's official update [03:53] AlinuxOS: where do you have it rom?= [03:53] really? [03:53] let me look [03:53] yes. [03:54] asac, I can also try to purge that.... but upgrade had ^ this kind of problems. [03:54] so I contacted you to be sure. [03:54] AlinuxOS: no [03:55] not the version of that package, but the one of mozilla-firefox-locale-ka [03:55] i want [03:56] asac, howto see that ? (I'm confused little bit) :) [03:56] dpkg -l mozilla-firefox-locale-ka [03:57] dpkg -l mozilla-firefox-locale-ka [03:57] Desired=Unknown/Install/Remove/Purge/Hold [03:57] | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend [03:57] |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) [03:57] ||/ Name Version Description [03:57] +++-==========================-==========================-==================================================================== [03:57] ii mozilla-firefox-locale-ka 2.0.0.7-0ubuntu1 Mozilla Firefox Georgian language/region package [03:57] alinux@brugherio:~/Desktop$ [03:58] asac, I've purged mozilla-firefox-locale-ka [03:58] and made sudo apt-get dist-upgrade [03:58] everything installed now. [03:59] but when I launch Firefox [03:59] I got a pop-up window [03:59] with a message: [03:59] ^ ----^ ----^ ----^ [04:01] asac, I restart X server. [04:01] see you soon === AlinuxOS [n=vsichi@host72-133-dynamic.16-87-r.retail.telecomitalia.it] has joined #ubuntu-mozillateam [04:09] asac: you there? [04:09] any probs? [04:10] asac: bitstormlite made a new upstream release [04:10] that fixes that problem [04:10] he added a .desktop too [04:10] the package is ready [04:10] bluekuja_: you know the procedure ;) [04:10] asac: yup, diff.gz etc on mail this time? [04:11] (we dont have a branch for it) [04:12] bluekuja_: yes ... maybe consider to setup a branch ... its easier to share [04:12] and making a debdiff of a new upstream is not good [04:12] right [04:12] asac: ok, this time I send you a mail, and gonna setup a branch for future use [04:12] ;) [04:17] bluekuja_: please don't put the orig et al in the maiul [04:17] better provide links to download [04:18] asac: mmm [04:18] need to find an host then [04:18] ^^ [04:18] asac: gonna setup my server [04:18] again [04:19] bluekuja_: get an alioth account [04:19] you can put files there [04:20] asac: I have alioth already [04:20]