[01:49] firefox 3.0.10-nobinonly on the karmic repositories returns with "bus error", gdb reports that /usr/bin/firefox is not in valid executable format. Is this a known bug? What additional information can I provide? [01:50] clearscreen: we are all a sleep in here at this time :) [01:50] What?! :P it's just 2:50:00 AM! [01:53] Thu Apr 30 01:53:46 WEST 2009 [01:54] clearscreen: ping asac on it... fta is MIA [02:01] asac: http://www.macno.org/denticator.php?user=asac&weekchart=bar&daychart=bar [02:22] disregard my previous stupidity, bash file in gdb? heh yeah. [10:08] clearscreen: ? [10:08] restart your system [10:09] dtchen: just run pulseaudio on the console [10:12] asac: I did restart it, I'll try again.. hold on [10:15] alright, brb [10:18] asac: same error, hold on.. trying to pastebin gdb output through links [10:21] asac: http://pastebin.com/m145d7c61 this _should_ work [10:21] bus error is strange [10:22] usually hardware issues on x86 architecture i would think [10:22] clearscreen: thats normal. run firefox -g [10:22] to start ffox in debugger [10:22] I did, it's in the pastebin [10:23] clearscreen: thats on jaunty? [10:23] asac: karmic repo, I'm not sure if 3.0.10 is even in jaunty repo yet :P [10:23] clearscreen: well [10:24] clearscreen: thats the problem then [10:24] clearscreen: jaunty is definitly available [10:24] (even before karmic was) [10:25] clearscreen: so you upgraded to karmic completely? or just ffox? [10:25] I dont mind stuff breaking, that's why I switched to karmic repositories (feature freeze on jaunty), the thing is that precompiled firefox binaries from the official website work, and they appear to be broken here [10:26] just trying to help it get fixed :) [10:26] yeah [10:26] sounds like a toolchain issue [10:26] clearscreen: can you try to respin xulrunner-1.9 locally? [10:26] asac: completely, although I think it broke after the recent libc6 upgrade [10:26] wasnt a problem with newer binutils [10:27] clearscreen: yeah there are often toolchain issues right after archive opens. try to respin firefox-3.0 then ;) [10:27] do you know how to do it? [10:28] asac: I'll probably sound like a total noob, but I have no idea what the word respin is supposed to mean :D [10:29] clearscreen: sudo apt-get install build-essential; sudo apt-get build-dep firefox-3.0; apt-get source firefox-3.0; cd firefox-3.0*/; [10:29] dpkg-buildpackage -rfakeroot [10:29] you might need to install fakeroot package [10:29] already have both those package [10:29] lets see [10:29] packages* [10:30] sudo apt-get build-dep firefox-3.0 [10:30] -> thats not a package [10:30] but a complete set of packages ;) [10:30] yeah I was refering to the build-essential metapackage and fakeroot :p [10:30] kk [10:31] the thing I dont understand is it working with precompiled binaries from the official website, but I guess I'm not too familiar with the arch to make any guesses about that :) [10:32] Jazzva: would you be interested in helping keeping the daily builds not fail ;)? https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/ [10:32] usually its just adjusting patches [10:32] so they apply cleanly again - or dropping patches that were applied upstream :) [10:33] Was that aimed at me or Jazzva? [10:33] at Jazzva ;) [10:33] clearscreen: not saying you are not invited to do so ;) [10:34] I'd be willing to, but probably far from knowledgable enough to actually do it [10:34] heh [10:35] clearscreen: for now "respin" firefox-3.0. thats a good start :) [10:35] cd: 11900: can't cd to /usr/lib/xulrunner-devel- [10:35] configure: error: /sdk/include/xpcom-config.h doesn't exist [10:35] clearscreen: you didnt install the build-dep [10:35] I did :) [10:35] firefox-3.0 [10:35] clearscreen: dpkg -L xulrunner-1.9-dev [10:35] daniel@ubuntu:~/firefox-3.0-3.0.10+nobinonly$ sudo apt-get build-dep firefox-3.0 [10:35] Reading package lists... Done [10:35] Building dependency tree [10:35] Reading state information... Done [10:35] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded [10:36] excuse my lack of usage of pastebin, it's a pain in the ass with a console browser [10:36] clearscreen: apt-get install pastebinit [10:36] echo hall | pastebinit [10:36] ;) [10:36] anyway [10:36] cool :) [10:36] clearscreen: run dpkg -L xulrunner-1.9-dev above [10:37] does that do anything? [10:37] asac: plenty of output [10:37] http://pastebin.com/f4851a4ca [10:38] clearscreen: so how does firefox-3.0 fail to build? [10:38] i need more context [10:38] that issue looks to strange [10:38] let me give you a full log [10:39] its really hard to get firefox-3.0 fail to build nowadays ;) [10:39] its just tiny and usually wouldnt fail even if you tried ;) [10:39] http://pastebin.com/feaab4d7 [10:39] thats not complete :) [10:40] maybe pastebin.com has a upper bound [10:40] you can try paste.ubuntu.com [10:40] I'll try [10:40] clearscreen: http://paste.ubuntu.com/161278/ [10:40] thats i have in $HOME/.pastebinit.xml [10:43] asac: mmmmpf, should I clean up somehow between building? seems to fail a lot more quickly now (doesnt even get to configure) [10:43] nevermind [10:43] remove it ... apt-get source it again [10:43] was in wrong directory [10:44] http://paste.ubuntu.com/161284/ [10:44] heh [10:44] its still not complete [10:44] there is no error [10:44] I'm just piping to pastebinit :P [10:45] thats a bad idea i guee [10:45] I'll try to c/p it through links [10:45] just copy the last 100 lines to a file and cat thatfile | pastebinit [10:46] http://paste.ubuntu.com/161286 [10:46] there. [10:48] ls -ld /usr/lib/xulrunner-devel* [10:48] and also [10:48] ls -ld /usr/lib/xulrunner-* [10:48] or only the last ;) [10:48] http://paste.ubuntu.com/161288/ [10:48] urgh [10:49] xulrunner-1.9 --gre-version [10:49] bus error :) [10:50] heh [10:50] ok [10:50] so you need to rebuild xulrunner-1.9 [10:50] same way [10:50] ;) [10:50] alright, lets see [10:51] apt-get build-dep xulrunner-1.9 [10:51] before running the build [10:51] yeah [10:51] also to safe time use dpkg-buildpackage -rfakeroot -b [10:52] k, that failed pretty quickly :D sec [10:54] disregard that [10:55] ;) [10:55] silly me, grabbing source through sudo [10:55] ouch [11:00] should've figured it was gonna take a while, with a 40MB compressed package with source :) [11:19] clearscreen: yeah. usually 20-50 minutes build [11:29] asac: after a ~35min build: dpkg-buildpackage: failure: debian/rules build gave error exit status 2.... too much output before that, but I'll try to give ~50 lines or so before fail [11:30] asac: http://paste.ubuntu.com/161317/ [11:32] he ok [11:32] thats a build failure because of new gcc [11:32] let me check [11:35] clearscreen: so download http://paste.ubuntu.com/161320/ [11:36] and in top level dir of xul [11:36] patch -p1 < /tmp/fileyoudownloaded [11:36] alright, hold on [11:36] http://paste.ubuntu.com/161320/plain/ [11:36] download that ;) [11:38] done. rebuild time? [11:38] asac: highlighting :) [11:38] clearscreen: did you apply to the same tree where the build failed? [11:39] applied to top level dir of xul, like you said :D [11:39] clearscreen: right. but did you keep the build that failed? [11:39] you can just continue to build it if thats the case [11:39] otherwise building time [11:40] asac: I re-ran the dpkg-build command, and that seemed to have cleaned all the object files.. so yeah, rebuild time [11:40] learning the harsh way :( [11:40] heh [11:40] yeah [11:40] thats ok [11:40] its just that mozilla builds usually take long and always clean building to try something wastes a lot of time ;) [11:42] * asac sent out a call for help aout daily archive on identi.ca ;) [11:43] alright, it's building now.. guess I have some time to do some groceries [11:45] Bug 478843 [11:45] [11:45] mozilla Bug 478843 [11:45] Error: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/478843/+text) [11:45] Mozilla bug 478843 in Startup and Profile System "/toolkit/xre/nsAppRunner.cpp:1424:6: error: #elif with no expression" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=478843 [11:51] asac: I can try. Is it too much time-consuming? [11:52] Jazzva: no ;) [11:52] Jazzva: there are two ways to approach this. one is really unconsuming: [11:53] 1. when daily build fails, check if its a patch that doesnt apply .... then just make that patch apply and commit .... wait if next daily build works [11:53] 2. same as 1. but try to build before committing (takes a bit more time obviously :)) [11:54] might take two or more days to fix it with 1. but it doesnt take too much time ;) [11:54] if patches fail regularly we should really consider to upstream them or drop them (not that we shouldnt look hard at all patches anyway) [11:54] asac: I guess I can try, then :) (have to finish two school projects by 10th May, that's the reason I asked if it's time-consuming) [11:55] heh [11:55] ok. [11:55] no hurry [11:55] for now i can cope with it [11:55] but those are regular failures, so having more than me and fta look at those would be helpful [11:55] its not time consuming, but frequent. balancing the load helps to make it easy [11:56] asac: Ok. Could you just give me instructions how to do it (where are the branches and similar)? [11:57] so the ppa is https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa [11:57] i fixed all branches yesterday ... except for thunderbird and prism [11:57] but thunderbird is a good example to show: [11:57] it fails to apply a pango patch (which was fixed upstream, so can be dropped) [11:58] so the procedure is: branch the proper .head branch (e.g. mozillateam/thunderbird/thunderbird-3.0.head i guess) [11:58] bump current changelog version (if its UNRELEASED) to the most recently failed on in ppa [11:59] so just copy the upstream version strings there [11:59] and commit that with a "New snapshot ..." commit (look at bzr log for examples) [11:59] you can download the orgi.tar.gz from ppa to the tarballs/ dir used for bzr builddeb [11:59] then you just fix the patch [11:59] and commit that to head [12:00] next daily will pick that up [12:00] so in this case its branching tbird ... bumping changelog, dropping patch ... done [12:00] to be sure that there are no other patches failing start a build and see if it gets over the patch stage [12:01] but usually its one or two patches [12:01] asac: Ok, understood... [12:19] asac: it seems to have succeeded :) [12:19] dpkg-deb: building package `xulrunner-1.9-gnome-support' in `../xulrunner-1.9-gnome-support_1.9.0.10+nobinonly-0ubuntu0.9.04.1_i386.deb'. [12:19] etcetera [12:22] Should I install them myself with dpkg? Do i need to remove old packages first? In other words: what do I do next :) [12:23] clearscreen: yes [12:23] clearscreen: just install all .deb fiels produced [12:24] then try to run xulrunner-1.9 --gre-version [12:24] would 'dpkg -i *.deb' be good enough? [12:24] y [12:24] sudo* [12:24] y [12:24] daniel@ubuntu:~$ xulrunner-1.9 --gre-version [12:24] 1.9.0.10 [12:25] good [12:25] and firefox is working again, cool [12:25] so firefox might even just work [12:25] yup [12:25] odd [12:25] thats i386? [12:25] amd64 is confirmed to work with our archive binaries [12:25] anyway. let me just upload the build failure fix then [12:25] yup i386 [12:26] asac: alright [12:27] * sebner waves at asac :) [12:27] * asac waves at sebner [12:27] ;) [12:28] asac: how is life going in fox's world? [12:28] asac: will you need my deb files or can I trash it all :) [12:29] you can trash all [12:29] sebner: always too much to do ;) [12:29] heh [12:31] firefox 3.5 b4 is out ;) [12:32] clearscreen: uploaded to karmic. thanks [12:32] asac: you're welcome [12:33] will take a bit: buildqueue: 2343 builds waiting in queue [12:33] i386 [12:33] https://edge.launchpad.net/builders/ [12:49] asac: what should I do when trying to install deb packages that depend on xulrunner-1.9? [12:49] moonlight-plugin-mozilla depends on xulrunner-1.9 | xulrunner-1.9.1; however: [12:49] Package xulrunner-1.9 is not configured yet. [12:49] install deb packages = install packages through apt** [12:51] I suppose I should just apt-get upgrade since you've added updated version of xulrunner to the repo [12:53] clearscreen: you isntalled all with dpkg -i *.deb [12:53] so xulrunner-1.9 should be installed [12:53] asac: well im trying to install moonling-plugin-mozilla but getting dependency errors [12:54] Package xulrunner-1.9 is not configured yet. [12:54] Package xulrunner-1.9.1 is not installed. [12:54] sudo dpkg --configure -a [12:54] or sudo apt-get install -f [12:54] but dont just hit y [12:54] same errors [12:55] install -f [12:55] same [12:55] without package [12:55] ^^ [12:55] remove moonlight again [12:55] you have to finish the xulrunner install [12:55] which isnt configured yet [12:56] same thing after moonlight removal :P [12:56] well. as i said [12:56] your dpkg -i *.deb failed [12:56] not sure why, you should have seen a failure [12:56] now you have to remove packages that cause conflict [12:56] also you cannot get the same issue after moonlight removal [12:56] because the error refers to moonlight [12:57] well after removal, it's a similar error with a different package [12:57] xulrunner-1.9-dev depends on xulrunner-1.9 (>= 1.9.0.10+nobinonly); however: [12:57] Package xulrunner-1.9 is not configured yet. [12:57] yes [12:57] but its installed. you you need to finish configure [12:57] or remove whatever package makes this not configure [12:58] you definitly had an error when installing the .debs initially [12:58] having that would help [12:58] I cant recall seeing an error and i closed that window a long time ago :P [12:58] yeah. but it errored [12:58] otherwise you wouldnt have this problem now [12:59] but.. since you've added an updated xulrunner to repo, should I just be able to remove & upgrade/install? [12:59] COLUMNS=200 dpkg -l xulrunner* [12:59] clearscreen: will take days to build [12:59] as i wrote above [12:59] ah, soz [12:59] there are 2500 builds waiting [12:59] you have to resolve this manually [12:59] you also shouldnt have removed .debs [12:59] aha ok [12:59] thats always a bad idea ;) [13:00] You told me to! :D [13:00] is not worth the space saving [13:00] no [13:00] i never told you to [13:00] you asked if you can remove them after installing [13:00] Well, yeah I guess [13:00] so you wanted to have them remove ... whihc i just answered with yes [13:00] but i didnt know your install failed ;) [13:01] so post the output above [13:01] http://paste.ubuntu.com/161389/ [13:01] but yeah, learning the hard way :) [13:02] clearscreen: so dpkg --configure -a gives the error above? [13:03] http://paste.ubuntu.com/161393/ [13:03] erm [13:03] hold on [13:03] that looks not that bad [13:03] http://paste.ubuntu.com/161394/ [13:03] asac: I wish it was only doing that :) [13:04] /var/lib/dpkg/alternatives/xulrunner [13:04] whats in there? [13:05] nothing [13:05] does that file existß [13:05] ? [13:05] yes [13:05] empty, though [13:05] try remove it and run again [13:05] that worked. [13:05] so yeah [13:05] now run apt-get update upgrade [13:06] and if that works install moonlight [13:06] yup, thanks :) [13:06] what is in that file now? [13:06] http://paste.ubuntu.com/161397/ [13:06] guess that file got corrupted on last upgrade when there was a bus error still [13:06] yeah thats ok [13:07] ok cool [13:19] so xulrunner 1.9 will take a bit longer [13:19] failed because of xcb-util transition as it seems [14:40] asac: mind if I try to fix thunderbird build fail now? === jtv1 is now known as jtv === rickspencer3 is now known as rickspencer3-afk === rickspencer3-afk is now known as rickspencer3 [15:04] Jazzva: sure [15:04] go ahead [15:23] [reed]: where send our new translation coordinator to to talk to mozilla folks [15:23] [reed]: is that #i18n? [15:23] <[reed]> #l10n [15:23] <[reed]> on moznet [15:23] <[reed]> Specifically, Pike, stas, gandalf, and sethb [15:26] [reed]: great [16:08] asac: I've downloaded the .orig.tar.gz, and after I run bzr builddeb it seems not to extract it to build area, and because of that quilt complains it can't find a file that needs to be patched. any idea what I'm doing wrong? [16:17] Jazzva: well ... usually you link the patches dir to the top level mozilla/ dir [16:17] and then do quilt push [16:17] in this case its just dropping the patch as upstream fixed it [16:17] quilt push -f [16:17] (to get reject files to fix and afterwards run quilt refresh) [16:17] asac: and if I want to do a test build? [16:17] but yeah in this case you see that the push fails and then quilt delete that patch and quilt push -a [16:18] Jazzva: just do a build after dropping the patch then [16:18] or isnt that the question [16:18] you need to run bzr bd --merge --dont-purge [16:18] asac: the problem is that I don't have anything in the mozilla/ dir, which should contain the source. How do I get bzr builddeb to extract .orig.tar.gz and then try to apply patches? [16:18] (--merge is important) [16:19] asac: Ok, I'll try [16:19] Jazzva: i usually run bzr bd --merge --dont-purge [16:19] and abort after patches are applied [16:19] then go to the build tree and work there [16:19] when finished copy the patches and whatelse i modified to the bzr tree [16:19] and commit that [16:20] asac: yeah, I missed the --merge part. Ok, seems it's working now. I dropped the patch, so I'll just let builddeb finish [16:21] Jazzva: better commit before ;) ... in case it doesnt work you can still connect [16:21] the daily run is in about 1.5 hours ;) [16:21] e.g. 1900 [16:21] ah... ok [16:21] might be that its UTC [16:21] we should at least try to commit before the next run ;) [16:23] asac: pushed to lp:~mozillateam/thunderbird/thunderbird-3.0.head [16:24] great [16:25] Jazzva: did you bump the changelog version to the current date? [16:25] (obviously ... otherwise it would fail to bzr bd) [16:26] Jazzva: hmm. i think you should have kept fta as maintainer [16:26] Jazzva: err as changelog owner [16:26] at least his bots signs with his key [16:26] not sure if it will fail now ;) [16:27] Fabien Tassin [16:27] consider to keep him in there ,) [16:27] we could also try what happens now ;) [16:28] maybe he runs dch -r before uploading anyway [16:30] ah... ok, sorry [16:30] no worry. we can also see if it works ;) [16:30] whatever you prefer [16:30] I can push another commit with fta as maintainer, if you want to be safe :) [16:31] asac: I'll take a look at prism later [16:32] great [16:32] Jazzva: prism is a bit unobvious to me [16:33] maybe its a simple fix [16:33] asac: I'll see if I can find out what's wrong :) [16:33] could be that the orig tarball doesnt contain all files [16:33] creating prism/components/Makefile [16:33] make[4]: *** No rule to make target `common/Makefile.in', needed by `common/Makefile'. Stop. [16:35] maybe just trunk is broken [16:39] Jazzva: so maybe top level Makefile.in needs common removed from DIRS [16:39] there is nothing in that dir anymore [16:40] asac: ok, I'll check. I still haven't downloaded yet, will do it after lunch [17:02] bom dia [17:13] hi BUGabundo [17:20] * asac out for some more errands [17:50] [reed]: mozilla bug 330626 checkin checkin [17:50] ! [17:51] Mozilla bug 330626 in Build "coreconf/Linux.mk does not detect mips64" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=330626 [17:51] * armin76 sees younger asac in that bug [17:51] when he cared about weird arches! :D [17:54] asac: looks like removing "common" from DIRS in prism's Makefile did work... [17:58] Jazzva: yeah cool. so do a patch for that. commit it (if thats quick it might catch todays run) [17:58] Jazzva: and send it upstream [17:58] let me check if he is online now ;) [17:59] ok [17:59] so he isnt. seems we need to file a bug then ;) [17:59] but for now add that as a patch to the branch (just against Makefile.in) [17:59] cool. assuming that the daily runs in 60 minutes [17:59] we might have all green today again \o/ [18:00] well. except hardy prism ... which doesnt build because we dont have a build system in there [18:08] asac: just to check, ~mozillateam/prism/prism is main dev branch for prism? [18:10] asac: pushed [18:10] let's see if it will work :) [18:13] i think thats the right branch. yes [18:13] yes. at least its the one i know of [18:14] Jazzva: can you file that as a bug: https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla+Labs&component=Prism [18:14] tell them ubuntu dailies failed [18:14] and that this seems to be the problem [18:14] but maybe wait till the build worked ,) [18:15] ok, I will :) [19:22]