[12:31] then nss and nspr should be in gutsy [12:31] maybe i we need to give back nss one more time :) [12:47] nss is not yet [12:47] nspr is -0d-dev and 0d\ [12:47] or something like that [12:51] 4-dev & -0d [12:51] yeah [12:52] lets see if nss respins automatically [12:52] at least launchpad shows that depedency wait is not true anymore [12:52] if smart new build attempt will follow :/ [12:53] https://launchpad.net/ubuntu/+source/nss/3.11.5-3 [12:53] great is building [12:53] at least on amd64 and i64 [12:53] nice ;) [12:53] tomorrow things can go up :) [12:54] lets see how hell's coming :) [12:54] hmmm again dependency wait :/ [12:57] :) === asac night [01:18] have a nice trip gnomefreak [01:22] night === [Cade] [n=[Cade] @adsl-35-6-219.asm.bellsouth.net] has joined #ubuntu-mozillateam [04:37] <[Cade] > hmm - what else is holding Firefox and TB updates up? I saw libnspr and libhunspell have updates now =D [05:38] define updates? [05:38] err updates* [05:40] <[Cade] > they have updates in the gutsy repos [05:41] i'm not sure I know what your question is [05:42] <[Cade] > ah - I'm referring to FF update and TB2 for gutsy [05:42] <[Cade] > ;) [05:43] <[Cade] > mainly because the updated version of libhunspell breaks the current ff packages [05:43] <[Cade] > just as a note, here's the relevant packages that got upgrades: libnspr4-0d libnspr4-0d-dbg libstdc++6 hunspell-1.1.0 libhunspell-1.1.0 [05:44] ah its probably because our packaging people aren't at their computers [05:44] <[Cade] > :P [05:45] <[Cade] > I've been chomping at the bit ever since TB2 was released. I'm just so fed up with Evo :/ [05:54] i need to try evolution, i heard it can handle outlook or something like that [05:54] you could build the binary [05:54] err install [05:55] <[Cade] > I'm a fan of font-rendering patches =P === sanityx [n=sanityx@pool-68-160-199-176.ny325.east.verizon.net] has joined #ubuntu-mozillateam [08:09] Anybody know of a way to sync Palm contacts with Thunderbird? === poningru [n=poningru@adsl-074-245-140-197.sip.gnv.bellsouth.net] has joined #ubuntu-mozillateam [08:36] ! [08:36] doh === sanityx [n=sanityx@pool-68-160-199-176.ny325.east.verizon.net] has left #ubuntu-mozillateam ["Ex-Chat"] [10:05] [Cade] : we need a few packages in first before we can spin against gutsy [10:05] they started pouring in late yesterday [10:07] [Cade] : should be fixed in next day or 2 (depending on any problems that arise) [10:16] so did nss build? [10:22] not here yet [10:23] i just did updates for gutsy and not yet. im setting up for iceape build incase it comes in in time. [10:35] hmm ... ok nspr ended up in universe (e.g. just the binaries) [10:35] so nss didn't build because source was in main as well [10:35] should be fixed now [10:35] why universe? [10:36] but takes some time until builders do i [10:36] error by the one processing the NEW binaries [10:36] the source is in main [10:36] i dont expect to spin it before i leave but would have been nice [10:36] but it should be fixed now [10:37] asac: congrats on reviewer status ;) [10:37] he? [10:37] ah ;) [10:39] Bug 50768 .. is it fixed now? [10:39] Launchpad bug 50768 in firefox "Strange artifacts in text fields within web applications when moving cursor with keyboard" [Medium,Confirmed] https://launchpad.net/bugs/50768 [10:41] not sure thats the first time ive seen that [10:41] yeah just read the last comment which ended up in my inbox [10:42] looks like its not firefox [10:42] its upstream bug [10:42] from what it shows [10:42] https://bugzilla.mozilla.org/show_bug.cgi?id=345438 [10:42] Mozilla bug 345438 in Layout "Moving cursor back/forward in all forms and in the location bar leaves caret turds (with nv video driver installed)" [Normal,New] [10:42] is the workaround in bugzilla?` [10:43] is bugzilla reporter same as ubuntu reporter? [10:43] and no patch yet [10:43] no [10:44] unless they use a different nick in LP and mozilla bugtracker [10:54] workaround [10:54] is in bug [10:54] why i said its fixed for us :) [11:37] asac: do i need to learn dput for revu or am i gonna put sources somewhere else? [11:40] hmmm [11:40] good idea :) [11:40] e.g. to upload to revu [11:40] yes then use dput or dupload [11:40] later you will push that way to preview archive as well [11:40] e.g. as soon as we have incoming processing [11:45] k [11:46] i will see if i can find docs on it than [11:54] hmm we get more and more @gtk_widget_event_internal now [11:54] feisty? [11:55] bug 94749 is master [11:55] Launchpad bug 94749 in firefox "MASTER firefox crash [@gtk_widget_event_internal] " [High,Confirmed] https://launchpad.net/bugs/94749 [11:55] we have way too many bugs with @gtk_* :( [11:55] yeah ;) [11:56] mozilla projects need some gtk experts :) [11:56] which they lack [11:56] yeah finall libnspr4-dev is in main [11:56] at least on my mirror [11:56] thanks god === gnomefreak checking update [11:57] asac == gtk expert no? ;) [11:58] hehe [11:58] i can code gtk ;) ... but i am far away from being a gtk core developer :) [11:58] gtk is a lang? i thought it was just widgets [11:59] a lib [11:59] like python+gtk [11:59] a widget toolkit library [11:59] gtk+ is C [11:59] oh [11:59] and there are several bindings for other languages [11:59] e.g. like python-gtk +perl-gtk [11:59] yuck @ C [11:59] et al === gnomefreak hasnt played with C in years [12:00] C is great ;) [12:01] python is easier (from what i hear) i dropped C for python and than got too busy to learn python === hjmf [n=hjmf@6.Red-88-25-28.staticIP.rima-tde.net] has joined #ubuntu-mozillateam [12:06] hey hjmf :) [12:06] welcome [12:07] hello [12:08] http://people.ubuntu.com/~cjwatson/uds-sevilla/ [12:08] schedule? [12:08] maybe you find something interesting :) [12:08] awesome === ajmitch looks at what he shoudl attend [12:09] might change a bit ... but main tracks should be rather fixed now [12:09] hmm it's too far from my house [12:09] oh, definitely ubuntu server forum :) [12:09] are you traveling ? === ajmitch just put in an application to hr@canonical for server stuff [12:09] i will be there :) [12:09] probably no chance of getting it, but oh well :) [12:09] there is Bug/Crash reporting forum on thursday morning :) [12:10] I see you're in the server track, asac [12:10] I've merged together all those [@gtk_widget_event_internal] [@??] [12:10] probably the same crash [12:11] hjmf: yeah ... you know when this first popped up? recently? [12:11] ajmitch: yeah ;) [12:11] couple of weeks maybe, not sure [12:12] will be video live/recorded sessions at UDS-Sevilla? [12:13] ok so probably gtk+ update for latest gnome [12:13] asac: will look [12:13] hjmf: hmm i have no idea ;) [12:13] they haven't been in the past [12:13] too much equipment to setup [12:13] what a pitty! :( [12:13] sessions aren't really that interesting by video [12:14] since it's usually people sitting round a table discussing [12:14] or crammed into a room somehow [12:14] I see [12:14] maybe some video feed from the pool :) [12:14] haha [12:14] there's a pool there? [12:14] I thought it would be more like a conference, then discussion [12:14] nah [12:15] :) [12:15] it's nearly all discussion & spec sessions [12:15] ah [12:15] "intense" [12:15] good luck then ... [12:15] :) === ajmitch is used to it by now ;) [12:15] gnomefreak: libnss is in gutsy ... lets go :) [12:16] excellent === ajmitch updates FDS packaging [12:17] asac: about the gtk_widget_event_internal there were some reports before, but the last *bunch* is from last week of april [12:17] till now [12:17] hmm ... feisty? [12:18] yes [12:19] the last 7 are from feisty [12:20] but we have edgy as well? [12:21] sure, the master is from edgy [12:22] but the last ones are all from feisty (probably because of dissabling apport in edgy) [12:22] ... not all, the last one is from edgy (bug 111875) [12:22] Launchpad bug 111875 in firefox "[EDGY] firefox crashed [@gtk_widget_event_internal] [@ ??] [@vtable for nsDOMConstructor at #12] (dup-of: 94749)" [High,Needs info] https://launchpad.net/bugs/111875 [12:22] Launchpad bug 94749 in firefox "MASTER firefox crash [@gtk_widget_event_internal] " [High,Confirmed] https://launchpad.net/bugs/94749 [12:23] 6:1 feisty:edgy since last week of april [12:23] hmm ... isn't apport disabled for feisty as well now? [12:23] not sure, probably [12:24] I don't have crashes Ubuntu rocks :-P [12:27] /etc/default/apport [12:27] # set this to 0 to disable apport [12:27] enabled=1 [12:27] but I guess that ^^^ is not what I had to look [12:29] i don't know [12:29] i would think so [12:29] but it doesn't work for me iirc :) [12:29] I think that that sets apport to collect crashes [12:30] but to auto-upload there must be another setting somewhere [12:30] mine is set to 1 but still never gives me the dialog. i meant to ping pitti about it but i keep forgeting [12:31] yes, it might be this one though: [12:32] gconf-editor: /apps/update-notifier/show_apport_crashes false [12:32] ah right [12:32] f this is disabled, the user will not be notified about pending apport crash reports. [12:32] probably thats the one [12:32] it's disabled on feisty [12:33] so thats why we are able to reduce bug count :) [12:33] not bad ;) [12:33] yeah! [12:33] well thats not good [12:33] I can see your point gnomefreak [12:33] 609 open bugs :) [12:33] pretty nice [12:34] he gave me command to turn it on [12:34] :) [12:34] 1291 with dupes [12:34] and most of them can be close too [12:34] of the 609 ? [12:34] closed* [12:34] yes [12:35] gconftool-2 -s --type boolean /apps/update-notifier/show_apport_crashes true [12:35] I meant many not most [12:35] yeah ;) [12:35] to turn on dialog [12:35] oh you already said tha :( [12:35] :) [12:36] we can always have for fun the mess on mozilla-thunderbird reports [12:36] yes ... we probably shouldn't ignore them anymore [12:37] do retraces work? [12:37] yes [12:37] or are dbgsym packages still broken? [12:37] ah ok [12:37] I still using mines, but apport retracing service can handle them too [12:37] so dbgsyms are OK now [12:37] https://bugs.launchpad.net/ubuntu/+source/mozilla-thunderbird/+bug/71131 [12:37] Launchpad bug 71131 in mozilla-thunderbird "Thunderbird crashes if you change Gnome theme while it is running" [High,Needs info] [12:37] can you confirm this? [12:38] e.g. thats without totem apparently ;) [12:38] but sounds like our totem crash ;) [12:38] that looks like same issue with firefox [12:38] maybe its the initial theme crasher ... for which we have a patch in firefox [12:38] tryin gnow [12:39] trying now even [12:39] a crash report on that one would have been nice [12:39] failed to crash with 2.0 [12:39] gnomefreak: yes ... the patch i was refering to landed for 2.0 [12:39] ah [12:40] hjmf: do your retrace scripts work for tbird as well .... like on bug 72160 [12:40] Launchpad bug 72160 in mozilla-thunderbird "TB crashed while writing reply email" [High,Needs info] https://launchpad.net/bugs/72160 [12:40] ? [12:40] will tell you in a couple of minutes === gnomefreak wonders what we fixed [12:44] asac: you can check [12:44] it worked [12:44] though I still have broken the autopost stuff [12:44] so I have to do it manually [12:45] hjmf: i looked into backtrace stuff ... the code that the retrace service uses is in apport bzr [12:46] i found the place where the top 5 stack elements are extracted [12:46] yes, I borrowed from they some time ago. [12:46] I have to check what had changed [12:46] so probably almost all is there already ... do we see summaries of stacks retraced by service? [12:47] but HTMLOperations.Bug is still the same that it was yesterday [12:47] and then it worked [12:48] the apport service only shows the first 3-4 stacks and we need from the 4th to the 7th as the fist three are always the same on most of the cases [12:49] hmmm ... if that is true for non mozilla packages as well, we should probably try to fix it there [12:50] that can be changed easily by you or pitty on report['StacktraceTop'] [12:50] from apport [12:50] yes ... we should look how other traces look like ... maybe we can try to better detect where to start. [12:51] what has to be changed i believe that is at apport/report.py [12:52] yes i think so ... iirc [12:52] yes, nowadays is StacktraceTop: simplified stacktrace (topmost 5 functions) for inline === asac searching for apport on ubuntu distribution to find other retraces [12:52] and it should include 3 or 4 more [12:53] Changing toptrace = [''] * 5 for toptrace = [''] * 9 [12:53] might do it [12:53] though It is just the first sight [12:54] hmmm ... i can talk to pitti [12:54] with that we can handle both the usual stacktrace and those w/o the 3# if you run apport locally ... do you see the StacktraceTop results as well? [12:55] yeah [12:55] mozilla is a bit special because they catch signals on their own [12:55] maybe at some point packages can ship infos about "where does stacktrace start" [12:55] ... I don't run apport as it should, I'm still at apport 0.61 [12:55] but maybe just using 9 is ok as well [12:55] hjmf: ouch :) [12:56] yes with 9 it will be OK [12:56] on my retraces I use by default from 3 to 12 [12:56] but 0-9 will be ok too [12:56] afaik latest apport should be usable as the good old 0.61 ... but what can i say :) ? [12:56] not tested [12:57] that's another thing I want to do [12:57] use current apport [12:57] but as long as old roks to me I've been a little bit lazy [12:57] at best use it from bzr :) [12:57] so you can contribute best to development [12:57] will have to, sure [01:02] hey you are bughelper-dev as well :) [01:02] welcome [01:08] haha yes! :P [01:12] asac: can you do me a quick favor [01:13] depends :) ... but I'll try [01:13] I'm stuck with this error with all my autopost routines [01:13] can you fire up python and [01:13] type [01:13] >>> from launchpadBugs.HTMLOperations import Bug [01:13] >>> bugnumber = 104533 [01:13] >>> cookiefile="/home/hjmf/.mozilla/firefox/oicl0ue1.default/cookies.txt" [01:13] >>> bug = Bug(bugnumber, cookie_file=cookiefile) [01:13] >>> bug.get_metadata() [01:13] >>> bug.__dict__['tags'] =['mt-confirm'] [01:13] >>> bug.set_metadata() [01:13] of course changing your cookie file [01:14] with that bug number [01:15] i get [01:15] > [01:15] now what? [01:15] should this have updated the bug? [01:15] bug 104533 [01:15] Launchpad bug 104533 in firefox "firefox crashed" [Undecided,Rejected] https://launchpad.net/bugs/104533 [01:15] yes it works for you [01:16] are you using the last bzr merge? [01:16] yeah [01:16] thank you [01:16] no ... i just used what is here on my system [01:16] nss hit [01:16] I'll will work on this later [01:16] so it is my fault somewher [01:16] e [01:16] in universe though [01:17] hmm [01:17] ok [01:18] for seamonkey source do i want the tar.gz or the bz2? i cant remember :( [01:18] rules doesnt say [01:18] cy all till this evening [01:18] hjmf: have fun [01:20] yeah bye hjmf [01:20] gnomefreak: he? [01:20] whatever is released upstream as "source" [01:20] i see both [01:20] ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/1.1.1 [01:20] in source? [01:21] File: seamonkey-1.1.1.source.tar.bz2 34176 KB 02/22/2007 02:15:00 PM [01:21] File: seamonkey-1.1.1.source.tar.gz [01:21] it doesn't matter [01:21] k [01:21] as you have to extract it on your own [01:21] then build your own orig out of if [01:21] it [01:22] and than i can just run dpkg-buildpackage -S -sa -kKEYID? than dput the .changes file? === gnomefreak will more than likely get to it around sat. or sun. [01:27] yes [01:27] should work that way [01:28] e.g. you don't need -kKEYID [01:28] if you are the last in changelog [01:28] which you probably should [01:28] and remember to use ubuntu version [01:28] oh ok [01:28] yeah 1.1.1-3ubuntu0 [01:28] e.g. version that is lower than the debian one [01:28] debians is 1.1.1-3 iirc [01:28] if debian was 1.1.1-3 ... then we use 1.1.1-2ubuntu0 [01:29] oh [01:29] if we used wrong version in preview [01:29] then we have bad luck [01:29] and preview customers won't get an upgrade to official [01:29] let me check changelog [01:29] but i don't think we have to bother about them :) [01:29] we should fix that as soon as debian uses a new version [01:30] until then preview users just have the preview build :) [01:30] iceape (1.1.1-3) unstable; urgency=low is the last from Mike [01:30] we just added .mt0 to the end [01:30] gnomefreak: i am really not sure atm [01:30] maybe ask on motu :) [01:30] e.g. what version to choose so that merge-o-matic and stuff like that works [01:31] ok ill ping one of them when i get home or maybe monday the latest [01:31] maybe its indeed 1.1.1-3ubuntu0 [01:31] i can see benifits from both :) [01:31] ok [01:32] since its the same as in preview that should be fine. we can bump preview when new version goes in [01:32] preview == unofficial is how i came up with that but i will ask them when i return [01:35] just ask what the right version for ubuntu merge is if 1.1.1-3 is debian version [01:35] that will give you an answer :) [01:37] ok nss should be in main on next push [01:37] we can then probably drop it from gutsy preview archive [01:59] should i drop the mt versions from changelog? [02:05] for upload to revu? [02:05] yeah [02:06] you can keep them if there are important infos ... or merge all content into your "new" changelog entry [02:07] ok merging them into one would be good :) [02:07] im getting a couple of differnet answers on versioning [02:21] which? [02:22] you have changes: new upstream tarball ;) [02:22] oh [02:22] that said ;) [02:22] you have to bump upstream version :) [02:23] as you have changed branding [02:24] gnomefreak ... guess 1.1.1+1-0ubuntu1 then [02:24] sorry for the confusion [02:24] but i think that would be right [02:24] changed branding in mt release [02:25] you have to change it for offical as well and call upstream tarball with other version [02:25] like above [02:26] the upstream tarball is the same that ive been using. they havent changed it since feb. [02:27] anyway ... WE changed it [02:27] so WE need a different version [02:27] k [02:27] we fixed debian->ubuntu ... remember? [02:27] yep [02:27] yeah ... so just rename the tarball with new version [02:28] then change changelog version appropriately so build will use that tarball done [02:28] no need to regen tarball [02:28] just a move/rename [02:29] ok cool. im thinking of what to add to changelog for ubuntu version since all changes were made for mt release [02:30] just talk about new upstream version tarball because of branding [02:30] and that this is motu release [02:30] and remember to use Maintainer: MOTU developers [02:30] or something [02:31] i think thats the way it has to be ;) [02:31] if you build add -vLAST_VERSION_BEFORE_MT_RELEASE for dpkg-buildpackage [02:31] in this way mt changes will end up in changelog as well [02:31] Ubuntu MOTU Developers [02:32] thanks [02:32] and Original-Maintainer: ?? [02:32] what is done about Uploaders: ? [02:32] XSBC-Original-Maintainer: can be whatever [02:32] ajmitch: ^^^ [02:32] Uploaders is ignored [02:32] ok [02:32] Uploaders only affects debian NMU rules [02:34] gnomefreak: got it? [02:34] i think so [02:34] ;)+ [02:35]