[08:13] <Admiral_Chicago> here is a wild question. how do we deal with stack traces of bugs like Bug #117827
[08:13] <ubotu> Launchpad bug 117827 in firefox "[apport]  firefox-bin crashed with SIGSEGV in __kernel_vsyscall()" [Undecided,Unconfirmed]  https://launchpad.net/bugs/117827
[08:31] <Admiral_Chicago> also, i think https://wiki.ubuntu.com/MozillaTeam/Bugs/Procedures could use some major love
[08:40] <hjmf> Admiral_Chicago: that crash looks a dup of bug 91519
[08:40] <ubotu> Launchpad bug 91519 in firefox "MASTER Firefox Crash [@~nsCOMPtr_base]  [@~nsInstallInfo]  [@nsSoftwareUpdate::InstallJarCallBack] " [High,Confirmed]  https://launchpad.net/bugs/91519
[08:41] <Admiral_Chicago> really? i'm not good with retraces yet, working on it
[08:42] <hjmf> not sure, but the retrace is quite close
[08:42] <hjmf> however, lets wait for reporters feedback
[08:43] <hjmf> he/she hasn't described what happened
[08:43] <Admiral_Chicago> hjmf: ah so it is..
[08:43] <Admiral_Chicago> perhaps installing an extension..the "Install jar" leads me to think so
[08:46] <hjmf> I think so too
[08:47] <hjmf> If you look at the *master's* duplicate, the guy was installing a extension when it crashed
[08:48] <hjmf> ... bug 107245
[08:48] <ubotu> Launchpad bug 107245 in firefox "[EDGY]  firefox crashed [@ ??]  [@ ~nsCOMPtr_base]  [@ ~~nsInstallInfo]  (dup-of: 91519)" [High,Needs info]  https://launchpad.net/bugs/107245
[08:48] <ubotu> Launchpad bug 91519 in firefox "MASTER Firefox Crash [@~nsCOMPtr_base]  [@~nsInstallInfo]  [@nsSoftwareUpdate::InstallJarCallBack] " [High,Confirmed]  https://launchpad.net/bugs/91519
[08:48] <Admiral_Chicago> ah yes. probably all related
[08:48] <Admiral_Chicago> brb, runing bughelper for a second...
[08:50] <Admiral_Chicago> okay, we may need to create a clue file for this case then, i'm looking for the -nd fix to be released
[09:00] <Admiral_Chicago> bughelper -T firefox "dapper" "possibly related to #89704" -A -U -p firefox
[09:00] <Admiral_Chicago> crap...thats not what i wanted to say...
[09:00] <Admiral_Chicago> asac: isn't bug 89704 fix release? i could have sworn there was a backport...
[09:00] <ubotu> Launchpad bug 89704 in firefox "No backport of Firefox 2.o to Dapper" [Wishlist,Needs info]  https://launchpad.net/bugs/89704
[10:17] <asac> Admiral_Chicago: no we have no backport yet ... we started
[10:25] <Admiral_Chicago> ah okay. i thought it was released...
[10:26] <asac> ffox is out
[10:26] <asac> 2.0.0.4
[10:27] <Admiral_Chicago> yea i saw, should be released in a few days in the repos then?
[10:28] <Admiral_Chicago> bughelper is not playing nice on my computer, refuses to run any commands i pass it
[10:28] <Admiral_Chicago> bughelper -T audacity "XFreeFont" "possible duplicate of 87434" -A -U -p audacity
[10:28] <Admiral_Chicago> and it gives me a crash output
[10:40] <asac> i dislike mozilla today ... they really released with 1.5 days prenotice
[10:41] <asac> Admiral_Chicago: i will look into your bughelper when i need a break from firefox upgrading
[10:41] <asac> have you asked dholbach?
[10:42] <asac> or mr. korn :)?
[10:42] <Admiral_Chicago> i got someone to run it for me, i just get some off output
[10:42] <Admiral_Chicago> IOError: [Errno socket error]  (-2, 'Name or service not known')
[10:42] <Admiral_Chicago> which refers to bzr: ERROR: Connection error: Couldn't resolve host 'bazaar.launchpad.net' (-2, 'Name or service not known')
[10:43] <Admiral_Chicago> now I have a problem with some of the dups being marked as dupes incorrectly...not my problem right now.
[10:43] <Admiral_Chicago> i'll look at them after i update my blog.
[10:49] <asac> Admiral_Chicago: so clue files work ... but command-line doesn't ... wierd
[10:50] <Admiral_Chicago> i think i found an old bug report from a similar issues.
[10:51] <asac> anyone heard of david btw?
[10:51] <asac> when was his last mail about his father?
[10:57] <asac> hmm last mail mar 20
[11:27] <asac> source download creeping at 15k
[11:43] <gnomefreak> no
[11:50] <asac> dapper is spinning
[11:52] <gnomefreak> 2.0.0.4?
[12:00] <asac> no 1.5.0.12
[12:00] <asac> edgy and feisty get 2.x update
[12:02] <asac> gutsy is not yet prepared ... but won't be much a problem i guess
[12:02] <asac> only the mime patch has to be updated
[12:02] <asac> at best take the one released with xulrunner 1.8.0.4
[12:02] <asac> (in debian)
[12:03] <gnomefreak> illl look at it sometime this morning
[12:04] <asac> yeah its all hurrily
[12:05] <asac> because mozilla again failed to give decent prenotice
[12:05] <asac> always the same
[12:05] <asac> probably we need to do daily builds to get security updates out in time
[12:06] <asac> nothing you need to bother of course
[12:06] <asac> solely my business to get this sorted out upstream
[12:14] <asac> :(
[12:21] <gnomefreak> failing to build?
[12:31] <asac> no ... just not happy about moz release procedures
[12:31] <asac> :)
[12:31] <asac> i am still on track
[12:31] <asac> :)
[12:32] <asac> gnomefreak: if you try gutsy, replace the gnome-mime patch with:
[12:32] <asac> http://people.ubuntu.com/~asac/25_gnome_helpers_with_params.dpatch
[12:33] <gnomefreak> ok ill start on it in about hour or so
[12:34] <asac> gnomefreak: bz273524-gnome-mime-registry-ubuntu.patch ... thats the patch to replace
[12:34] <asac> at best just replace the contents of that patch
[12:34] <asac> e.g. not remove and add new file
[12:34] <asac> and if you do so ... leave behind all the dpatch headings ... e.g. just the patch part in 25_gnom...
[12:35] <asac> ok ... edgy spinning
[12:54] <asac> ok everything spinning again ... had to adapt that patch properly for edgy and feisty as well
[12:54] <asac> should work out of the box for gutsy though
[01:03] <gnomefreak> grabbing sources
[01:04] <gnomefreak> version number should be 2.0.0.4+4-0ubuntu1?
[01:04] <asac> he?
[01:04] <asac> please rethink :)
[01:04] <asac> use +1
[01:04] <asac> 2.0.0.4+1-0ubuntu1
[01:04] <gnomefreak> +1 oh becuse its a new version
[01:05] <asac> wait a second
[01:05] <gnomefreak> i added this upstream source to the +3
[01:05] <asac> might be wrong
[01:05] <asac> ok
[01:05] <asac> egdy will get 2.0.0.4+0dfsg-0ubuntu0.6.10
[01:05] <asac> feisty will get 2.0.0.4+0-0ubuntu1
[01:05] <gnomefreak> what about feisty?
[01:06] <gnomefreak> so we can use +1-0ubuntu1
[01:06] <asac> sorry ... feisty will get 2.0.0.4+1-0ubuntu1
[01:06] <gnomefreak> ah
[01:06] <asac> so gutsy will get +1
[01:06] <asac> +2
[01:06] <asac> :)
[01:06] <gnomefreak> that wont work than
[01:06] <asac> 2.0.0.4+2-0ubuntu1
[01:06] <gnomefreak> so go with +2-0ubuntu1
[01:06] <asac> :)
[01:06] <asac> yep
[01:06] <gnomefreak> ok
[01:07] <asac> unfortunately all orig.tar.gz balls differ ... so this is really the way we have to go :(
[01:08] <gnomefreak> quick question after chaning debian/configure.in file is there something i need to run? example: aclocal or autoconf
[01:15] <DrMax_> I have a technical question about the cache
[01:15] <DrMax_> How are generated the "unique" filenames like F6E02EC4d01 ?
[01:15] <DrMax_> what hash function is used and does the filename have a structure ? (i.e, they're all ending in d01)
[01:15] <DrMax_> and, hi ;)
[01:16] <asac> why?
[01:16] <asac> why you wanna know?
[01:16] <asac> its usually just random
[01:17] <asac> maybe with a commom extension (e.g. d01)
[01:17] <DrMax_> it's probably not random because it must associate some kind of signature to a media
[01:18] <DrMax_> I want to know because I have a cache management system to code: I'm comparing options
[01:19] <asac> ah ok ... i have to do lunch  now ... will be back at 1200 UTC ... if you stay we can discuss thne
[01:19] <DrMax_> sure
[01:20] <bluekuja> gnomefreak, what?
[01:21] <gnomefreak> bluekuja: nevermind gwget was regenerating the control file. i am working on fixing that
[01:21] <gnomefreak> i changed debina/configure.in just not sure if i need to run anything after changing that
[01:21] <bluekuja> I changed the build deps
[01:21] <bluekuja> and it was building
[01:22] <bluekuja> dont know what you mean then
[01:22] <gnomefreak> bluekuja: clean was regenerating control file so when i grabbed source it was still << 2.19
[01:22] <gnomefreak> bluekuja: grab source and see what i mean
[01:22] <bluekuja> gnomefreak, oh ok^^
[01:23] <bluekuja> thanks for the info anyway
[01:25] <gnomefreak> bluekuja: yw this package has beena frigging nightmare
[01:26] <bluekuja> gnomefreak: I looked at it for the first time when I merged it
[01:26] <bluekuja> so I didnt know problems related
[01:26] <bluekuja> :)
[01:26] <gnomefreak> i got them
[02:49] <asac> hi porthose :)
[02:49] <porthose> Hi
[02:50] <porthose> I was still in the class room
[02:50] <asac> nice to have you here ... if you want you can take a look at the spec ... which basically outlines what to do
[02:50] <asac> porthose: yes lets talk later :)
[02:50] <asac> i am there as well
[02:52] <porthose> Works for me, the better half just got home and she want some attention
[02:52] <porthose> what time is good for you
[02:53] <asac> porthose: i am usually here during daylight in europr
[02:53] <asac> europe
[02:53] <asac> ... and at night often as well :)
[02:54] <porthose> lololo k Im in usa going back to class-room
[03:34] <asac> hjmf: have you read the mail from pitti to devel-discuss?
[03:36] <hjmf> asac: no. reading it now  thanks :)
[03:51] <asac> hjmf: if you have some time (no hurry) ... ping pitti on -devel
[03:53] <hjmf> ok
[03:54] <hjmf> asac: btw I've reviewed those mt-needtestcase I marked yesterday
[03:54] <asac> already finished?
[03:54] <hjmf> yes
[03:54] <asac> fine ... do we have a tag in wiki for that?
[03:54] <asac> so i can just press :)
[03:55] <hjmf> we haven't mt-reject-candidate yet on the wiki
[03:55] <hjmf> I guess
[03:55] <asac> right
[03:55] <asac> do we have candidates already?
[03:55] <asac> guess we have to add it manually once
[03:56] <asac> otherwise launchpad will confuse your script :)
[03:56] <hjmf> already done ^_^
[03:56] <asac> cool
[03:56] <hjmf> I'll fire up the script to append  that tag, it will be run daily, OK?
[03:57] <asac> sure
[03:57] <hjmf> then run! :)
[04:05] <hjmf> asac: https://bugs.launchpad.net/ubuntu/+source/firefox?field.tag=mt-reject-candidate
[04:08] <asac> hjmf: are those already auto-tagged?
[04:09] <hjmf> yes
[04:09] <asac> cool
[04:09] <hjmf> :)
[04:10] <gnomefreak> asac: what is best way to add contents of one patch to another already exsiting one?
[04:10] <asac> all?
[04:10] <asac> or just hunks?
[04:10] <gnomefreak> did you want me to add hunks or all
[04:10] <gnomefreak> the new patch you wrote
[04:10] <asac> i am missing the context atm
[04:10] <asac> sorry
[04:11] <asac> ah ... the new patch ... just replace all that is in current file with all that is in dpatch file
[04:12] <gnomefreak> you mean replace everything in the .patch file with everything from the .dpatch file (i hope or you spent the time to make patch for nothing)
[04:13] <gnomefreak> and leave everything down to Index: mozilla/uriloader/exthandler/Makefile.in
[04:18] <gnomefreak> nothing is really the same in the 2 patches  example Index: mozilla/uriloader/exthandler/Makefile.in 'VS'   [04:19] <gnomefreak> and everything above that point in orig patch
[04:23] <gnomefreak> asac: my questions summed up with parts of file.. http://gnomefreak.pastebin.ca/525749
[04:24] <asac> gnomefreak: just replace all
[04:24] <asac> its safer
[04:24] <asac> there is lots of unchanged stuff
[04:24] <gnomefreak> k
[04:24] <asac> and some changes have been dropped
[04:24] <asac> because have been dealt with by another bug-fix upstream
[04:24] <asac> etc.
[04:24] <gnomefreak> should i use old name or keep new name also
[04:24] <asac> its too hard to figure out by just looking at patches
[04:24] <asac> you would have to look at old code + new code + both bugs
[04:24] <asac> gnomefreak: wait a sec
[04:25] <gnomefreak> k
[04:25] <asac> drop the old patch from series and bzr
[04:26] <asac> and then call the new one
[04:26] <asac> bz273524-gnome-mime-registry-AFTER-bz373955.patch
[04:27] <asac> you have to add that to series (at the same position the old one was)
[04:28] <gnomefreak> ok gone from series and ill drop it from patches dir. but what do you mean from bzr as in the dir .bzr in source dir?
[04:29] <asac> bzr rm path/to/old/patch
[04:29] <asac> e.g.
[04:29] <asac> bzr add path/to/new/patch
[04:29] <asac> bzr rm path/to/old/patch
[04:30] <asac> edit path/to/series
[04:30] <asac> bzr commit -m "YOUR MESSAGE" path/to/new/patch path/to/old/patch path/to/series
[04:30] <asac> then push that branch to your private space in launchpad
[04:30] <asac> so I can pull yur changes and spin/upload
[04:30] <asac> of course please don't push unless you have sucessfully build from that
[04:31] <gnomefreak> k
[04:31] <asac> :)
[04:34] <gnomefreak> hmmmm
[04:35] <asac> did you fail?
[04:35] <gnomefreak> i guess that would mean i have to clone firefox branch first.
[04:35] <asac> yeah ... build from bzr of course :)
[04:35] <gnomefreak> not a problem
[04:35] <asac> yeah :) ... its the new way .... so easy to *not* remember ;)
[04:36] <asac> soon there is devel meeting
[04:36] <asac> lets see what i can do before
[04:36] <asac> @schedule berlin
[04:36] <ubotu> Schedule for Europe/Berlin: 31 May 17:00: Ubuntu Development Team | 31 May 23:00: Kubuntu Developers | 05 Jun 21:00: Technical Board | 06 Jun 22:00: Edubuntu | 07 Jun 22:00: Ubuntu Development Team | 12 Jun 17:00: Kernel Team
[04:37] <gnomefreak> im gonna grab bzr and head to lunch/late breakfast
[04:37] <asac> yep
[04:38] <gnomefreak> bbiab
[06:06] <gnomefreak> asac: real fast: im supposed to upack upstream source and mv mozilla/* . right? (i havent build ff in a while)
[06:06] <asac> no
[06:06] <asac> ffox
[06:06] <asac> has unmodified
[06:06] <asac> just drop the tarball in the main dir
[06:07] <gnomefreak> thought so
[06:07] <asac> and tar it up (e.g. just tar cvzf ...orig.tar.gz firefox-xxxx/firefox*.tar.bz2
[06:07] <gnomefreak> what no update-orig?
[06:08] <asac> no
[06:08] <asac> its simple
[06:08] <asac> we don't modify
[06:08] <asac> or is there an update target?
[06:08] <asac> oh yeah there
[06:08] <asac> is
[06:08] <asac> .... you can use update-orig as well then
[06:08] <asac> :)
[06:08] <asac> gnomefreak: ^^^
[06:09] <asac> sorry for confusion
[06:09] <asac> if there is update-orig ... you can use it of course
[06:09] <gnomefreak> its all good
[06:09] <gnomefreak> ther eis
[06:09] <gnomefreak> there is
[06:38] <gnomefreak> well this is always a good frigging error :( ok i need to go for a bit. btw update-orig fails with cd: 1: can't cd to build-tree/mozilla
[06:38] <gnomefreak> make: *** No rule to make target `firefox-2.0.0.3-source.tar.bz2', needed by `/home/gnomefreak/gutsy_builds/firefox2.0.0.4/ubuntu-2.0.0.x/../firefox_2.0.0.3+3.orig.tar.gz'.  Stop.
[06:38] <gnomefreak> and no i dont have source for 2.0.0.3
[06:40] <asac> hehe
[06:40] <asac> change version in changelog
[06:41] <asac> actually a good thing of update-orig is that it catches such a common glitch :)
[06:41] <asac> gnomefreak: ^^^
[06:41] <gnomefreak> k
[07:03] <gnomefreak> i think gutsy's dpkg is borked (it works with a non up-to-date dpkg but fails with a fully up-to-date dpkg) im out for a while will let you know if it fails later
[07:13] <gnomefreak> asac: i have to go for a while my carpel tunnel is acting up bad and i just took som muscle relaxers and pain killers. problem with build == bz366844-mozilla-configure-in-patch-to-workaround-gcc-visibility-bug.patch fails to apply. i will have to look at it tonight or tomorrow (as it stands atm)
[07:13] <gnomefreak> error == Hunk #1 FAILED at 2513.
[07:13] <gnomefreak> Hunk #2 FAILED at 2548.
[07:13] <gnomefreak> 2 out of 2 hunks FAILED -- rejects in file configure.in
[07:13] <gnomefreak> cu later
[07:15] <asac> gnomefreak: that patch as to be dropped
[07:15] <asac> same for bz358930-gradient-spread-method-pad-fix
[07:15] <asac> bz312998-GetVisibility-patch
[07:15] <asac> dunno if they are named exactly like that
[07:15] <asac> but i think so
[07:16] <gnomefreak> ok ill try again later
[08:42] <asac> k i am out ... will come by later maybe
[11:17] <Admiral_Chicago> back...
[11:24] <gnomefreak> asac: im not gonna beable to do this. more patches are failingPatch ubuntu-look-and-feel-patch.patch does not apply
[11:24] <gnomefreak> patching file browser/locales/en-US/chrome/browser-region/region.properties
[11:24] <gnomefreak> Hunk #1 FAILED at 8.
[11:24] <gnomefreak> 1 out of 1 hunk FAILED -- rejects in file browser/locales/en-US/chrome/browser-region/region.properties
[11:25] <gnomefreak> this is gonna need a full work up. you may want to build it (it would be faster and from what im seeing it is gonna be a long one.)
[11:26] <gnomefreak> bunch of Hunk #1 succeeded at 1525 (offset 2 lines).  with different patches different #'s and diff. lines