[01:48] fta: asac: anyone around? [05:45] asac: don't release Firefox 3.6 in the morning...I need to talk to you first [06:05] micahg, hmm.. build/rules.mk? [06:05] fta: Do we have to edit that with a patch? [06:06] if you need to fix it, yes [06:06] * fta out for work [06:06] My stuff builds, it just doesn't clean since I needed to add 2 dirs to the build system (only 2 files) [06:06] you can do it in d/rules too then [06:07] fta: well, anyone building against the build-system will have the issue, so I figured I needed it to be global in scope [06:08] fta: when is distclean triggered? [06:08] moz uses GARBAGE and GARBAGE_DIR for that (each makefile could set thos) [06:08] e [06:08] off for real now. [06:08] fta: ah, ok, you have that in your makefile [06:08] ok [06:08] fta: have a good day :) [08:56] morning [08:59] kenvandine: couch broken again? http://paste.ubuntu.com/390913/ [09:02] hmm ... wonder what was the prob with fffox36 === BUGabundo_remote is now known as BUGabundo_lunch [13:04] asac: you there? === BUGabundo_lunch is now known as BUGabundo_remote [13:40] asac: available? [13:41] micahg: yes [13:41] micahg: whats going on? [13:41] i saw you writing about ffox not releasable [13:41] asac: k, first, the mozilla-kde patch won't build on hardy as it uses a newer GTK function [13:42] sindhudweep: sigh [13:42] sindhudweep: i will do that now. i think all is ready? [13:42] micahg: sigh too ... push that back to devfx [13:42] asac: so, I didn't know if you wanted to drop it till they fix or release it and not use it on hardy [13:42] micahg: for the hardy security update we dont want to use it [13:42] we need to branch for that [13:42] and remove it [13:42] for all stable releases actually [13:43] asac: k, but for lucid, it's fine? [13:43] it breaks the daily build though [13:43] for hardy at least [13:44] !info gnash [13:44] gnash (source: gnash): free SWF movie player. In component universe, is optional. Version 0.8.6-0ubuntu1 (karmic), package size 220 kB, installed size 800 kB [13:45] sindhudweep: we merged ubuntu2 stuff to ubuntu.head at some point [13:45] your new packaging asks for merge into ubuntu [13:45] does it include all that was previously in .head? [13:46] sindhudweep: you didnt include the files changed in changelog [13:47] ok merged packaging [13:49] sindhudweep: upstreampkg+bzrbd+py2.6 isnt a merge request? [13:49] e.g. ok to release without that? [13:54] asac: just one second. [13:55] i am fine to trash the .head [13:55] please check ;) [13:55] i committed your parts there [13:55] if you could add the changed filenames for each of the changes in changelog that would be better [13:55] its always a mystery from outside to see that [13:56] upstreampkg+bzrbd+py2.6 is rob savoye's packaging. It's based off of your packaging from gnash 0.8.2 and his changes since then. I've merely added a few fixes to get it to work with lucid. [13:56] It's purely and experiment and wont have any of the history we have in bzr. [13:57] please ignore ubuntu.head as that was a bad attempt at fixing the missing kde4-gnash packages. [13:58] I would like you to review and merge lp:~sindhudweep-sarkar/gnash/gnash0.8.7packaging into lp:~gnash/gnash/ubuntu if it's suitable. I think in the long term going with rsavoyes packaging would be better [13:58] but i'm not sure if that's feasable this cycle. [13:59] please let me know any changes you need to make lp:~sindhudweep-sarkar/gnash/gnash0.8.7packaging mergable or if you want to switch to the upstream packaging. [14:01] thoughts? [14:03] sindhudweep: i think its fine what you did [14:03] i assume you tested stuff? [14:03] sindhudweep: can you add the files changed for each changelog entry please? i already committed your merge, so base that on ubuntu [14:03] i think you can also commit [14:03] Yes the gnashteam ppa has all revisions in the branch you merged except the last one which disabled explicitly enabling jemalloc as that is the default. [14:04] I will fix the files changed in the changelog entry and push it to the ubuntu branch. [14:04] I'll let you know when that's done [14:04] ok thanks [14:04] thanks! [14:04] i will upload directly when thats done [14:04] maybe do a final test round [14:04] great! [14:04] if you thin that would be helpful [14:04] will do [14:05] asac: so, back to firefox, are we ok for lucid and do I need add something to that the dailies don't build with the firefox-kde patch on hardy? [14:06] micahg: we are fine for now [14:06] we can fix that later [14:06] asac: k, then ubuntu6 is tagged and ready for release :) [14:06] cool [14:06] asac: what to do when I push to PPA (disable on hardy only)? [14:07] firefox-stable [14:08] micahg: the tag doesnt include the kde patch [14:08] ? [14:08] what? [14:09] it should [14:09] oh right [14:09] ok [14:09] micahg: how were you able to bake a release on a normal revision? [14:09] i thought the stuff was already ahead [14:09] asac: I did it before I fixed it for 3.6.2 [14:09] ah ok [14:10] next release will be trickier [14:10] why? [14:10] but I think we might need to do one more before beta hard freeze [14:10] ah [14:10] in case we need another one [14:10] right [14:10] lets hope for .2/3 [14:10] that's at the end of the month, may we can wait...the other fixes are minor IMHO [14:11] *maybe [14:11] we shouldnt wait for fixes just because of this [14:11] rather take the pain and branch old/merge after release ;) [14:11] but lets see whats coming up [14:11] asac: k, then I'll prepare another release over teh weekend :) [14:12] asac: should I tag TB3, I prepared it but not tag? [14:12] micahg: there are apport fixes not documented in changelog? [14:13] asac: which ones? I thought all the apport fixes were in there [14:13] [ Kees Cook ] [14:13] * fix LP: #531581 - cannot report bugs or crashes when profile names contains [14:13] spaces; concatenate non alnum characters in profile name for apport use [14:13] - update debian/apport/firefox.py [14:13] right [14:13] ok [14:13] is there another one? [14:13] no didnt spot [14:13] that [14:13] because too long changelog entry ;) [14:14] :) he made the patch [14:14] asac: you told me not to worry about space in changelog [14:15] yes, i usually start with "fix apport hook to do this, that etc." [14:15] e.g. dont have the subject of the fix at the end ;) [14:15] uploading [14:15] asac: k, should I tag TB3 for upload? [14:15] micahg: yes [14:15] unless you have fixes [14:15] we should forward bugs [14:16] asac: yes, and there was one fix I already made [14:16] ok [14:16] in future just ping chrisccoulson to update tbird ... so you can focus on porting [14:16] also for daily build failures he wants to help ;) [14:16] :-P [14:16] hi :) [14:16] hi! [14:16] asac: I had to make the at least one of th efixes as I knew the issue :) [14:17] sure [14:17] asac: should chrisccoulson prepare the TB2.0.0.24 release? [14:17] just saying we should get him involved ;) [14:17] yeah. that would be a good excersize [14:17] to get started [14:17] asac: hi! thanks for merging one of my branches at ubufox. I have submitted more branches with simple fixes for review. Now I have 4 branches waiting for review/merge and bugs 493805 and 123713 have patches to be reviewed and committed. When will you have time to check them? Anyway I will check more (harder) bugs to reproduce/fix this week. [14:17] Launchpad bug 493805 in ubufox "ubufox 0.8 leaves FF 3.0 folder in /etc" [Low,In progress] https://launchpad.net/bugs/493805 [14:17] Launchpad bug 123713 in ubufox "package description needs rewrite" [Low,Confirmed] https://launchpad.net/bugs/123713 [14:19] micahg - did you say you couldn't recreate the openjdk build failure locally? [14:19] chrisccoulson: right, well, I'm still on karmic [14:20] but it built fine locally, but I didn't test in a clean environment either [14:20] micahg - ah, that's probably why. the version currently in the archive also fails against xulrunner 1.9.1 [14:20] in a clean environment here [14:20] chrisccoulson: I tested locally against xul192 though [14:20] i think it needs 1.9.2 now [14:20] and that's what the PPA should've used [14:20] because they needed to fix it in order to work with 1.9.2 at all (thats what i got from random chatter) [14:21] micahg - it fails against xulrunner 1.9.2 locally here too [14:21] asac: yes, well it's hard coded to build the proper plugin against 192 [14:21] chrisccoulson: same build failure or different? [14:21] i've got a shell open in the failed build environment later, so i will try and figure out why it failed [14:21] same failure... [14:21] chrisccoulson: k, that would be great [14:21] pasting build failures is often helpful ;) [14:22] oh, i meant to say " i've got a shell open in the failed build environment right now" [14:22] sometimes i just know whats going on from lookig at it ... sometimes not :) [14:22] asac: is this changelog fine or should the line start at the beginning: http://pastebin.com/xM04hb1b [14:22] ah [14:22] asac - http://launchpadlibrarian.net/40287073/buildlog_ubuntu-lucid-amd64.openjdk-6_6b18~pre1-1ubuntu1.0ffox36.1_FAILEDTOBUILD.txt.gz [14:23] micahg: if you dont have a USN/CVE below it, i think not having empty line is ok [14:23] asac: I was referring to the line with the bug fix [14:23] anyway, i'm disappearing for lunch for a bit, i've not eaten anything yet today [14:23] I wrapped the text under the rest of the title [14:23] chrisccoulson: ok. thats feeling like a bug in the script ;) [14:24] but would need to look [14:24] asac - yeah. i'm not sure what has changed though - i can recreate the same issue with the version already built in the archive against xulrunner 1.9.1 [14:25] chrisccoulson: then how did doko get it to build 2 weeks ago? [14:25] i'm not too familiar with openjdk though, so i was going to ping doko about it, but he's not around [14:25] that feels like a CFLAGS somehow ending up at the command line ;) [14:25] micahg - not sure [14:25] I made no packaging changes [14:25] unless that thing is supposed to build something of course [14:25] except for the maintainer [14:26] asac: so the fix LP: line in the changelog is ok with the wrapping underneath? [14:27] micahg: i usually dont indent [14:27] just same indent as prvious line [14:27] asac: that's what I wanted to check, I'll fix, tag, and push :) [14:27] that looks a bit odd that way [14:27] kk [14:27] let me know [14:29] asac: done [14:30] asac: about xulrunner, the new build system rquires libnotify-dev, should that be a dep on xulrunner-1.9.2-dev or on the app itself? [14:30] asac - i can reproduce the error that triggers the openjdk build failure manually in the failed pbuilder environment i have [14:30] so i could probably look at that after lunch [14:33] micahg: libnotify-dev? [14:33] it fails without it? [14:33] asac: yes, that's one of the new requires [14:34] in configure [14:37] asac: BTW, I only had to add 2 files to the build system :) [14:38] good [14:38] well. for now ad libnotify-dev [14:38] asac: where? [14:38] feels wrong, but ok [14:38] to xulrunner-1.9.2-dev i guess [14:38] we added it to firefox 3.6 and xul192 [14:39] k [14:39] asac: will shlibdeps add it to the package if it's required? [14:39] I mean prism [14:40] that was my main question as to where to add it [14:41] asac: it's required because libnotify was enabled in 192 [14:42] it will add it if its required [14:42] imo it shoudnt e required to build [14:42] its a biuld system bug to require it imo [14:42] maybe worth upstream discussion [14:43] asac: k, I'll add to xul192dev and test, thanks [14:52] asac: the other think with xulrunner, is I wasn't able to clean out the 2 new directories I added on make clean [14:52] I added them to GARBAGE_DIRS, but that didn't seem to help [14:53] rather GARBAGE_DIRS in the build system [14:56] micahg: what do you mean? [14:56] in debian/rules? [14:56] otherwise i would have thought that the build system doesnt get removed [14:56] asac: the build system has a makefile with GARBAGE_DIRS [14:57] yeah [14:57] so I added there so I wouldn't have to add to every app [14:57] but it didn't work [14:57] what are you trying to remove? [14:57] build/ ? [14:57] tools and testingf [14:57] oops [14:57] testing [14:57] why those? [14:57] I added 2 files under there [14:58] and make clean won't remove it [14:58] the rest of the build system already gets removed? [14:58] but removes the rest [14:58] yes [14:58] I was wondering if you knew where it did that :) [14:58] make clean removes the build system? how is it extracted? [14:58] i mean ... how does it come back? [14:58] it's untarred again [14:58] i would have thought that debian/rules clean removes it [14:58] thats where it should get removed ... not in the Makefile [14:59] unless i fail so see the point [14:59] asac: then it has to be added to every app that uses the build system [14:59] right. but its the same for build/ etc. [15:00] no [15:00] somehow, that's taken care of with the build system [15:00] hmm [15:00] please post the top level Makefile.in [15:00] from teh buidl system? [15:01] what else would be doing it ;) [15:01] http://pastebin.com/XDXzdpkj [15:02] I added them to line 62, but that didn't seem to work [15:02] i dont see biuld/ config/ getting removed there [15:02] so after make clean [15:02] what is left? [15:02] this gets run at the end: [15:03] http://pastebin.com/JBpL1NSn [15:03] just tools and testing [15:03] where is "Drop build-system" ? [15:03] i dont see that anywhere in build system [15:04] asac: that's what I'm wondering [15:04] I'm guess in one of the .mk files...I'll grep for it [15:04] i grepped for it [15:04] nothing [15:04] hmm [15:04] my guess is that its all in rules [15:04] weird [15:04] or in prism/build.mk [15:09] it's not anywhere in the build directory that I can see [15:10] when do you get it? [15:11] when fakeroot debian/rules clean is run, it's at the end [15:11] yeah. that could be rules then [15:11] you should see if it really happens on make clean [15:11] or make distclean [15:11] without rules [15:11] make clean [15:11] oops [15:12] nope, no clean target in the file [15:12] can I add a clean target to the Makefile then? [15:12] asac: I've fixed the changelog and pushed it to https://code.launchpad.net/~gnash/gnash/ubuntu. I have built a package from that branch in one of my personal ppas and tested it out a bit. I think we're good here. [15:12] Thanks again! [15:13] let me lkook [15:14] ok producing stuff [15:49] asac: did you get my email from friday? [15:58] asac: I got it, it's in mozilla-devscripts... [16:01] asac: so, should I propose a change for mozilla-devscripts, or move that to xulrunner-1.9.2-dev? [16:01] xulapp.mk I mean [16:03] * micahg needs to get ready for $WORK...bbi 10 min === _Tsk__ is now known as _Tsk_ [16:18] jdstrand, is apparmor at all active right now in fx 3.6? [16:18] asac: so what to do with xulapp.mk [16:19] I'm in lucid right now and have no apparmor problems atm [16:23] mahfouz: it is enabled in the default install, and working, yes [16:23] hmm, but my scid runs from fx [16:23] I filed that bug === _Tsk___ is now known as _Tsk_ [16:24] /usr/games/scid [16:29] emacs also open files from fx [16:29] I have firefox daily build and running lucid [16:30] there seem to be no apparmor restrictions at all [16:32] mahfouz: you likely have to do: [16:33] asac: I goofed on the sparc fix...I'll fix it for ubuntu7 :( [16:33] don't get me wrong, I don't need apparmor restrictions :) [16:33] sudo aa-enforce /etc/apparmor.d/usr.bin.firefox [16:33] jdstrand, yes [16:33] jdstrand, I was just wondering if this is default or maybe a bug [16:33] mahfouz: it is probably not enabled due to the firefox-3.x -> firefox name transition and running the dailies [16:34] I'm actually happy without apparmor [16:34] jdstrand: didn't you make it so if it was disabled before it remains that way in teh dailies [16:34] * jdstrand nods [16:34] I just enabled mine locally so I can do more testing [16:37] micahg: really? hmm. did the sparce fix break anything? [16:37] asac: no, the flag was just ignored [16:37] k [16:37] asac: k, I just discovered another dependency [16:37] thats fine. commit the correct fix [16:37] done [16:37] libiw-dev [16:38] asac: well, if I commit it on top of what's there, won't that not get into the next 3.6.0 upload? [16:38] you know the troubles with that ,) [16:39] backbranch/merge etc. [16:39] right, so isn't it better to wait to commit it then until I'm ready to do all that? [16:40] asac: now xul build system wants libiw-dev as well [16:40] micahg: you know the schedule for .1 [16:40] ? [16:40] asac: .2 actually [16:40] yeah [16:40] you said end of month? [16:40] asac: yes [16:40] but you said that we should get more fixes in Lucid before that I thought [16:41] is there anything? [16:42] there are a few bugs...I can't really go into it now [16:43] asac: once they do the QA builds, can we throw that in Lucid, or we have to wait for release? [16:44] asac: im having problem with NM .. wireless keep reconnecting .. [16:44] and i need to manually request dhcp for any interface :( [16:49] !ping asac [17:10] ejat, that's a lucid bug [17:10] mahfouz: know the bug # [17:10] probly this one: [17:11] https://bugs.launchpad.net/ubuntu/lucid/+source/network-manager-applet/+bug/445487 [17:11] Launchpad bug 445487 in network-manager-applet "Network-Manager fails WPA2 Enterprise configuration" [Undecided,Confirmed] [17:11] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/496093 [17:11] Launchpad bug 496093 in linux "[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured wireless networks" [Unknown,Confirmed] [17:12] mahfouz: thanks === dpm is now known as dpm-afk [19:30] asac: ping again :) [19:37] ccheney: hi [19:38] ccheney: have you bootstrapped the libs somewhere? [19:38] in appa? [19:38] asac: so, what should I do about xulapp.mk in m-devscripts <--- that's where the clean rule is for the build system [19:39] ah [19:39] micahg: yeah. i think thats where it belongs for now [19:39] asac: so, should I propose a merge for m-devscripts? [19:40] so I can add tools and testing to that clean rule? [19:43] asac: I also added libiw-dev to xulrunner-1.9.2-dev...fennec and prism built after that and libnotify-dev were added [19:43] micahg: yes [19:43] yeah. we should come up with a patch for the build system imo [19:44] that makes those go away again [19:44] for now its ok [19:44] just file a bug while doing that [19:44] so we dont forget [19:44] asac: since xulrunner's already compiled against it, the apps woudl be able to use them anyways? [19:45] s/it/them/ [19:45] well. the iw and notify stuff is not needed [19:45] because its hidden [19:45] so that depends are useless [19:45] and wrong [19:45] so yeah. apps can use that ... through the xulrunner apis [19:45] asac: well, what if a xul app wants to use either is my question [19:46] dont undersatnd that question [19:46] toolkit has a API that allows notifications [19:46] and also scanning for networks [19:46] the app doesnt know what its using in the back [19:46] k, so once the toolkit is built against the libs, the program doesn't need to be? [19:46] yes [19:46] k, same for notifications? [19:46] because the program doesnt use the libnotify nor libiw apis directly [19:46] k [19:46] just the toolkit api [19:46] fine, I'll file a bug then [19:47] in LP I'm asumming, then upstream when we have a patch? [19:47] yeah [19:47] asac: what should I do with xulapp.mk though? [19:47] we can also open upstream directly and explain whats the prob [19:47] update it [19:47] to remove the new files [19:47] k, I'll do that then [19:47] actually maybe it should be shipped by xulrunner-dev [19:48] but well. lets keep it the way it is by now [19:48] asac: xulrunner-dev pulls in the versioned -dev [19:49] asac: but what to do about the clean rule... [19:56] asac: i can put the rest up, but epiphany-browser is at http://people.canonical.com/~ccheney/ [19:59] * ccheney will upload up to date version for all of them === yofel_ is now known as yofel [20:04] will be at http://people.canonical.com/~ccheney/2010-03-08/ when it is done [20:32] ccheney: cant you make proper packages out of them? [20:32] so i can install everything instead of bootstrapping and stuff [20:38] asac: ok will do [20:38] i am on amd64, hopefully you too :) [20:59] asac, i still have to push the chromium codecs to lucid, is it too late? [22:13] o/ [22:22] asac: BTW, thunderbird 3.0.3 is tagged [22:22] ccheney: ppa? amd64 shouldnt mater there ;) [22:29] fta: we need a FFe bug [22:29] file one i can argue why we want that. [22:30] is the licensing all properly documented? e.g. is it ready? === rickspencer3__ is now known as rickspencer3 [22:53] asac: is firefox-3.6.head where to commit to lucid, or does lucid have its own branch now? [22:53] jdstrand: that commits to lucid [22:53] asac: would take a while to get it actually build for ppa due to version changes, and needing to determine what to do with libsoup bootstraping itself, etc [22:53] though if we need to releas another 3.6.0 we have to do some shuffeling [22:53] asac: almost have all of it uploaded though as debs to p.c.c [22:53] but we will ensure stuff that gets landed there gets released [22:54] ccheney: we need to do that anyway [22:54] asac: thanks [22:54]