[01:48] <micahg> fta: asac: anyone around?
[05:45] <micahg> asac: don't release Firefox 3.6 in the morning...I need to talk to you first
[06:05] <fta> micahg, hmm.. build/rules.mk?
[06:05] <micahg> fta: Do we have to edit that with a patch?
[06:06] <fta> if you need to fix it, yes
[06:06]  * fta out for work
[06:06] <micahg> My stuff builds, it just doesn't clean since I needed to add 2 dirs to the build system (only 2 files)
[06:06] <fta> you can do it in d/rules too then
[06:07] <micahg> 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] <micahg> fta: when is distclean triggered?
[06:08] <fta> moz uses GARBAGE and GARBAGE_DIR for that (each makefile could set thos)
[06:08] <fta> e
[06:08] <fta> off for real now.
[06:08] <micahg> fta: ah, ok, you have that in your makefile
[06:08] <micahg> ok
[06:08] <micahg> fta: have a good day :)
[08:56] <BUGabundo_remote> morning
[08:59] <BUGabundo_remote> kenvandine: couch broken again? http://paste.ubuntu.com/390913/
[09:02] <asac> hmm ... wonder what was the prob with fffox36
[13:04] <sindhudweep> asac: you there?
[13:40] <micahg> asac: available?
[13:41] <asac> micahg: yes
[13:41] <asac> micahg: whats going on?
[13:41] <asac> i saw you writing about ffox not releasable
[13:41] <micahg> asac: k, first, the mozilla-kde patch won't build on hardy as it uses a newer GTK function
[13:42] <asac> sindhudweep: sigh
[13:42] <asac> sindhudweep: i will do that now. i think all is ready?
[13:42] <asac> micahg: sigh too ... push that back to devfx
[13:42] <micahg> 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] <asac> micahg: for the hardy security update we dont want to use it
[13:42] <asac> we need to branch for that
[13:42] <asac> and remove it
[13:42] <asac> for all stable releases actually
[13:43] <micahg> asac: k, but for lucid, it's fine?
[13:43] <micahg> it breaks the daily build though
[13:43] <micahg> for hardy at least
[13:44] <asac> !info gnash
[13:45] <asac> sindhudweep: we merged ubuntu2 stuff to ubuntu.head at some point
[13:45] <asac> your new packaging asks for merge into ubuntu
[13:45] <asac> does it include all that was previously in .head?
[13:46] <asac> sindhudweep: you didnt include the files changed in changelog
[13:47] <asac> ok merged packaging
[13:49] <asac> sindhudweep: upstreampkg+bzrbd+py2.6 isnt a merge request?
[13:49] <asac> e.g. ok to release without that?
[13:54] <sindhudweep> asac: just one second.
[13:55] <asac> i am fine to trash the .head
[13:55] <asac> please check ;)
[13:55] <asac> i committed your parts there
[13:55] <asac> if you could add the changed filenames for each of the changes in changelog that would be better
[13:55] <asac> its always a mystery from outside to see that
[13:56] <sindhudweep> 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] <sindhudweep> It's purely and experiment and wont have any of the history we have in bzr.
[13:57] <sindhudweep> please ignore ubuntu.head as that was a bad attempt at fixing the missing kde4-gnash packages.
[13:58] <sindhudweep> 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] <sindhudweep> but i'm not sure if that's feasable this cycle.
[13:59] <sindhudweep> 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] <sindhudweep> thoughts?
[14:03] <asac> sindhudweep: i think its fine what you did
[14:03] <asac> i assume you tested stuff?
[14:03] <asac> sindhudweep: can you add the files changed for each changelog entry please? i already committed your merge, so  base that on ubuntu
[14:03] <asac> i think you can also commit
[14:03] <sindhudweep> 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] <sindhudweep> I will fix the files changed in the changelog entry and push it to the ubuntu branch.
[14:04] <sindhudweep> I'll let you know when that's done
[14:04] <asac> ok thanks
[14:04] <sindhudweep> thanks!
[14:04] <asac> i will upload directly when thats done
[14:04] <asac> maybe do a final test round
[14:04] <sindhudweep> great!
[14:04] <asac> if you thin that would be helpful
[14:04] <sindhudweep> will do
[14:05] <micahg> 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] <asac> micahg: we are fine for now
[14:06] <asac> we can fix that later
[14:06] <micahg> asac: k, then ubuntu6 is tagged and ready for release :)
[14:06] <asac> cool
[14:06] <micahg> asac: what to do when I push to PPA (disable on hardy only)?
[14:07] <micahg> firefox-stable
[14:08] <asac> micahg: the tag doesnt include the kde patch
[14:08] <asac> ?
[14:08] <micahg> what?
[14:09] <micahg> it should
[14:09] <asac> oh right
[14:09] <asac> ok
[14:09] <asac> micahg: how were you able to bake a release on a normal revision?
[14:09] <asac> i thought the stuff was already ahead
[14:09] <micahg> asac: I did it before I fixed it for 3.6.2
[14:09] <asac> ah ok
[14:10] <micahg> next release will be trickier
[14:10] <asac> why?
[14:10] <micahg> but I think we might need to do one more before beta hard freeze
[14:10] <asac> ah
[14:10] <asac> in case we need another one
[14:10] <asac> right
[14:10] <asac> lets hope for .2/3
[14:10] <micahg> that's at the end of the month, may we can wait...the other fixes are minor IMHO
[14:11] <micahg> *maybe
[14:11] <asac> we shouldnt wait for fixes just because of this
[14:11] <asac> rather take the pain and branch old/merge after release ;)
[14:11] <asac> but lets see whats coming up
[14:11] <micahg> asac: k, then I'll prepare another release over teh weekend :)
[14:12] <micahg> asac: should I tag TB3, I prepared it but not tag?
[14:12] <asac> micahg: there are apport fixes not documented in changelog?
[14:13] <micahg> asac: which ones?  I thought all the apport fixes were in there
[14:13] <micahg>   [ Kees Cook <kees@ubuntu.com> ]
[14:13] <micahg>   * fix LP: #531581 - cannot report bugs or crashes when profile names contains
[14:13] <micahg>     spaces; concatenate non alnum characters in profile name for apport use
[14:13] <micahg>     - update debian/apport/firefox.py
[14:13] <asac> right
[14:13] <asac> ok
[14:13] <micahg> is there another one?
[14:13] <asac> no didnt spot
[14:13] <asac> that
[14:13] <asac> because too long changelog entry ;)
[14:14] <micahg> :) he made the patch
[14:14] <micahg> asac: you told me not to worry about space in changelog
[14:15] <asac> yes, i usually start with "fix apport hook to do this, that etc."
[14:15] <asac> e.g. dont have the subject of the fix at the end ;)
[14:15] <asac> uploading
[14:15] <micahg> asac: k, should I tag TB3 for upload?
[14:15] <asac> micahg: yes
[14:15] <asac> unless you have fixes
[14:15] <asac> we should forward bugs
[14:16] <micahg> asac: yes, and there was one fix I already made
[14:16] <asac> ok
[14:16] <asac> in future just ping chrisccoulson to update tbird ... so you can focus on porting
[14:16] <asac> also for daily build failures he wants to help ;)
[14:16] <asac> :-P
[14:16] <chrisccoulson> hi :)
[14:16] <asac> hi!
[14:16] <micahg> asac: I had to make the at least one of th efixes as I knew the issue :)
[14:17] <asac> sure
[14:17] <micahg> asac: should chrisccoulson prepare the TB2.0.0.24 release?
[14:17] <asac> just saying we should get him involved ;)
[14:17] <asac> yeah. that would be a good excersize
[14:17] <asac> to get started
[14:17] <kecsap> 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:19] <chrisccoulson> micahg - did you say you couldn't recreate the openjdk build failure locally?
[14:19] <micahg> chrisccoulson: right, well, I'm still on karmic
[14:20] <micahg> but it built fine locally, but I didn't test in a clean environment either
[14:20] <chrisccoulson> micahg - ah, that's probably why. the version currently in the archive also fails against xulrunner 1.9.1
[14:20] <chrisccoulson> in a clean environment here
[14:20] <micahg> chrisccoulson: I tested locally against xul192 though
[14:20] <asac> i think it needs 1.9.2 now
[14:20] <micahg> and that's what the PPA should've used
[14:20] <asac> 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] <chrisccoulson> micahg - it fails against xulrunner 1.9.2 locally here too
[14:21] <micahg> asac: yes, well it's hard coded to build the proper plugin against 192
[14:21] <micahg> chrisccoulson: same build failure or different?
[14:21] <chrisccoulson> i've got a shell open in the failed build environment later, so i will try and figure out why it failed
[14:21] <chrisccoulson> same failure...
[14:21] <micahg> chrisccoulson: k, that would be great
[14:21] <asac> pasting build failures is often helpful ;)
[14:22] <chrisccoulson> oh, i meant to say " i've got a shell open in the failed build environment right now"
[14:22] <asac> sometimes i just know whats going on from lookig at it ... sometimes not :)
[14:22] <micahg> asac: is this changelog fine or should the line start at the beginning: http://pastebin.com/xM04hb1b
[14:22] <asac> ah
[14:22] <chrisccoulson> asac - http://launchpadlibrarian.net/40287073/buildlog_ubuntu-lucid-amd64.openjdk-6_6b18~pre1-1ubuntu1.0ffox36.1_FAILEDTOBUILD.txt.gz
[14:23] <asac> micahg: if you dont have a USN/CVE below it, i think not having empty line is ok
[14:23] <micahg> asac: I was referring to the line with the bug fix
[14:23] <chrisccoulson> anyway, i'm disappearing for lunch for a bit, i've not eaten anything yet today
[14:23] <micahg> I wrapped the text under the rest of the title
[14:23] <asac> chrisccoulson: ok. thats feeling like a bug in the script ;)
[14:24] <asac> but would need to look
[14:24] <chrisccoulson> 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] <micahg> chrisccoulson: then how did doko get it to build 2 weeks ago?
[14:25] <chrisccoulson> i'm not too familiar with openjdk though, so i was going to ping doko about it, but he's not around
[14:25] <asac> that feels like a CFLAGS somehow ending up at  the command line ;)
[14:25] <chrisccoulson> micahg - not sure
[14:25] <micahg> I made no packaging changes
[14:25] <asac> unless that thing is supposed to build something of course
[14:25] <micahg> except for the maintainer
[14:26] <micahg> asac: so the fix LP: line in the changelog is ok with the wrapping underneath?
[14:27] <asac> micahg: i usually dont indent
[14:27] <asac> just same indent as prvious line
[14:27] <micahg> asac: that's what I wanted to check, I'll fix, tag, and push :)
[14:27] <asac> that looks a bit odd that way
[14:27] <asac> kk
[14:27] <asac> let me know
[14:29] <micahg> asac: done
[14:30] <micahg> 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] <chrisccoulson> asac - i can reproduce the error that triggers the openjdk build failure manually in the failed pbuilder environment i have
[14:30] <chrisccoulson> so i could probably look at that after lunch
[14:33] <asac> micahg: libnotify-dev?
[14:33] <asac> it fails without it?
[14:33] <micahg> asac: yes, that's one of the new requires
[14:34] <micahg> in configure
[14:37] <micahg> asac: BTW, I only had to add 2 files to the build system :)
[14:38] <asac> good
[14:38] <asac> well. for now ad libnotify-dev
[14:38] <micahg> asac: where?
[14:38] <asac> feels wrong, but ok
[14:38] <asac> to xulrunner-1.9.2-dev i guess
[14:38] <micahg> we added it to firefox 3.6 and xul192
[14:39] <micahg> k
[14:39] <micahg> asac: will shlibdeps add it to the package if it's required?
[14:39] <micahg> I mean prism
[14:40] <micahg> that was my main question as to where to add it
[14:41] <micahg> asac: it's required because libnotify was enabled in 192
[14:42] <asac> it will add it if its required
[14:42] <asac> imo it shoudnt e required to build
[14:42] <asac> its a biuld system bug to require it imo
[14:42] <asac> maybe worth upstream discussion
[14:43] <micahg> asac: k, I'll add to xul192dev and test, thanks
[14:52] <micahg> 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] <micahg> I added them to GARBAGE_DIRS, but that didn't seem to help
[14:53] <micahg> rather GARBAGE_DIRS in the build system
[14:56] <asac> micahg: what do you mean?
[14:56] <asac> in debian/rules?
[14:56] <asac> otherwise i would have thought that the build system doesnt get removed
[14:56] <micahg> asac: the build system has a makefile with GARBAGE_DIRS
[14:57] <asac> yeah
[14:57] <micahg> so I added there so I wouldn't have to add to every app
[14:57] <micahg> but it didn't work
[14:57] <asac> what are you trying to remove?
[14:57] <asac> build/ ?
[14:57] <micahg> tools and testingf
[14:57] <micahg> oops
[14:57] <micahg> testing
[14:57] <asac> why those?
[14:57] <micahg> I added 2 files under there
[14:58] <micahg> and make clean won't remove it
[14:58] <asac> the rest of the build system already gets removed?
[14:58] <micahg> but removes the rest
[14:58] <micahg> yes
[14:58] <micahg> I was wondering if you knew where it did that :)
[14:58] <asac> make clean removes the build system? how is it extracted?
[14:58] <asac> i mean ... how does it come back?
[14:58] <micahg> it's untarred again
[14:58] <asac> i would have thought that debian/rules clean removes it
[14:58] <asac> thats where it should get removed ... not in the Makefile
[14:59] <asac> unless i fail so see the point
[14:59] <micahg> asac: then it has to be added to every app that uses the build system
[14:59] <asac> right. but its the same for build/ etc.
[15:00] <micahg> no
[15:00] <micahg> somehow, that's taken care of with the build system
[15:00] <asac> hmm
[15:00] <asac> please post the top level Makefile.in
[15:00] <micahg> from teh buidl system?
[15:01] <asac> what else would be doing it ;)
[15:01] <micahg> http://pastebin.com/XDXzdpkj
[15:02] <micahg> I added them to line 62, but that didn't seem to work
[15:02] <asac> i dont see biuld/ config/ getting removed there
[15:02] <asac> so after make clean
[15:02] <asac> what is left?
[15:02] <micahg> this gets run at the end:
[15:03] <micahg> http://pastebin.com/JBpL1NSn
[15:03] <micahg> just tools and testing
[15:03] <asac> where is "Drop build-system" ?
[15:03] <asac> i dont see that anywhere in build system
[15:04] <micahg> asac: that's what I'm wondering
[15:04] <micahg> I'm guess in one of the .mk files...I'll grep for it
[15:04] <asac> i grepped for it
[15:04] <asac> nothing
[15:04] <micahg> hmm
[15:04] <asac> my guess is that its all in rules
[15:04] <micahg> weird
[15:04] <asac> or in prism/build.mk
[15:09] <micahg> it's not anywhere in the build directory that I can see
[15:10] <asac> when do you get it?
[15:11] <micahg> when fakeroot debian/rules clean is run, it's at the end
[15:11] <asac> yeah. that could be rules then
[15:11] <asac> you should see if it really happens on make clean
[15:11] <asac> or make distclean
[15:11] <asac> without rules
[15:11] <micahg> make clean
[15:11] <micahg> oops
[15:12] <micahg> nope, no clean target in the file
[15:12] <micahg> can I add a clean target to the Makefile then?
[15:12] <sindhudweep> 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] <sindhudweep> Thanks again!
[15:13] <asac> let me lkook
[15:14] <asac> ok producing stuff
[15:49] <ccheney> asac: did you get my email from friday?
[15:58] <micahg> asac: I got it, it's in mozilla-devscripts...
[16:01] <micahg> asac: so, should I propose a change for mozilla-devscripts, or move that to xulrunner-1.9.2-dev?
[16:01] <micahg> xulapp.mk I mean
[16:03]  * micahg needs to get ready for $WORK...bbi 10 min
[16:18] <mahfouz> jdstrand, is apparmor at all active right now in fx 3.6?
[16:18] <micahg> asac: so what to do with xulapp.mk
[16:19] <mahfouz> I'm in lucid right now and have no apparmor problems atm
[16:23] <jdstrand> mahfouz: it is enabled in the default install, and working, yes
[16:23] <mahfouz> hmm, but my scid runs from fx
[16:23] <mahfouz> I filed that bug
[16:24] <mahfouz> /usr/games/scid
[16:29] <mahfouz> emacs also open files from fx
[16:29] <mahfouz> I have firefox daily build and running lucid
[16:30] <mahfouz> there seem to be no apparmor restrictions at all
[16:32] <jdstrand> mahfouz: you likely have to do:
[16:33] <micahg> asac: I goofed on the sparc fix...I'll fix it for ubuntu7 :(
[16:33] <mahfouz> don't get me wrong, I don't need apparmor restrictions :)
[16:33] <jdstrand> sudo aa-enforce /etc/apparmor.d/usr.bin.firefox
[16:33] <mahfouz> jdstrand, yes
[16:33] <mahfouz> jdstrand, I was just wondering if this is default or maybe a bug
[16:33] <jdstrand> mahfouz: it is probably not enabled due to the firefox-3.x -> firefox name transition and running the dailies
[16:34] <mahfouz> I'm actually happy without apparmor
[16:34] <micahg> 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] <micahg> I just enabled mine locally so I can do more testing
[16:37] <asac> micahg: really? hmm. did the sparce fix break anything?
[16:37] <micahg> asac: no, the flag was just ignored
[16:37] <asac> k
[16:37] <micahg> asac: k, I just discovered another dependency
[16:37] <asac> thats fine. commit the correct fix
[16:37] <asac> done
[16:37] <micahg> libiw-dev
[16:38] <micahg> 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] <asac> you know the troubles with that ,)
[16:39] <asac> backbranch/merge etc.
[16:39] <micahg> right, so isn't it better to wait to commit it then until I'm ready to do all that?
[16:40] <micahg> asac: now xul build system wants libiw-dev as well
[16:40] <asac> micahg: you know the schedule for .1
[16:40] <asac> ?
[16:40] <micahg> asac: .2 actually
[16:40] <asac> yeah
[16:40] <asac> you said end of month?
[16:40] <micahg> asac: yes
[16:40] <micahg> but you said that we should get more fixes in Lucid before that I thought
[16:41] <asac> is there anything?
[16:42] <micahg> there are a few bugs...I can't really go into it now
[16:43] <micahg> asac: once they do the QA builds, can we throw that in Lucid, or we have to wait for release?
[16:44] <ejat> asac: im having problem with NM .. wireless keep reconnecting ..
[16:44] <ejat> and i need to manually request dhcp for any interface :(
[16:49] <ejat> !ping asac
[17:10] <mahfouz> ejat, that's a lucid bug
[17:10] <ejat> mahfouz: know the bug #
[17:10] <mahfouz> probly this one:
[17:11] <mahfouz> https://bugs.launchpad.net/ubuntu/lucid/+source/network-manager-applet/+bug/445487
[17:11] <mahfouz> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/496093
[17:12] <ejat> mahfouz: thanks
[19:30] <ccheney> asac: ping again :)
[19:37] <asac> ccheney: hi
[19:38] <asac> ccheney: have you bootstrapped the libs somewhere?
[19:38] <asac> in appa?
[19:38] <micahg> 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] <asac> ah
[19:39] <asac> micahg: yeah. i think thats where it belongs for now
[19:39] <micahg> asac: so, should I propose a merge for m-devscripts?
[19:40] <micahg> so I can add tools and testing to that clean rule?
[19:43] <micahg> 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] <asac> micahg: yes
[19:43] <asac> yeah. we should come up with a patch for the build system imo
[19:44] <asac> that makes those go away again
[19:44] <asac> for now its ok
[19:44] <asac> just file a bug while doing that
[19:44] <asac> so we dont forget
[19:44] <micahg> asac: since xulrunner's already compiled against it, the apps woudl be able to use them anyways?
[19:45] <micahg> s/it/them/
[19:45] <asac> well. the iw and notify stuff is not needed
[19:45] <asac> because its hidden
[19:45] <asac> so that depends are useless
[19:45] <asac> and wrong
[19:45] <asac> so yeah. apps can use that ... through the xulrunner apis
[19:45] <micahg> asac: well, what if a xul app wants to use either is my question
[19:46] <asac> dont undersatnd that question
[19:46] <asac> toolkit has a API that allows notifications
[19:46] <asac> and also scanning for networks
[19:46] <asac> the app doesnt know what its using in the back
[19:46] <micahg> k, so once the toolkit is built against the libs, the program doesn't need to be?
[19:46] <asac> yes
[19:46] <micahg> k, same for notifications?
[19:46] <asac> because the program doesnt use the libnotify nor libiw apis directly
[19:46] <micahg> k
[19:46] <asac> just the toolkit api
[19:46] <micahg> fine, I'll file a bug then
[19:47] <micahg> in LP I'm asumming, then upstream when we have a patch?
[19:47] <asac> yeah
[19:47] <micahg> asac: what should I do with xulapp.mk though?
[19:47] <asac> we can also open upstream directly and explain whats the prob
[19:47] <asac> update it
[19:47] <asac> to remove the new files
[19:47] <micahg> k, I'll do that then
[19:47] <asac> actually maybe it should be shipped by xulrunner-dev
[19:48] <asac> but well. lets keep it the way it is by now
[19:48] <micahg> asac: xulrunner-dev pulls in the versioned -dev
[19:49] <micahg> asac: but what to do about the clean rule...
[19:56] <ccheney> 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
[20:04] <ccheney> will be at http://people.canonical.com/~ccheney/2010-03-08/ when it is done
[20:32] <asac> ccheney: cant you make proper packages out of them?
[20:32] <asac> so i can install everything instead of bootstrapping and stuff
[20:38] <ccheney> asac: ok will do
[20:38] <ccheney> i am on amd64, hopefully you too :)
[20:59] <fta> asac, i still have to push the chromium codecs to lucid, is it too late?
[22:13] <BUGabundo> o/
[22:22] <micahg> asac: BTW, thunderbird 3.0.3 is tagged
[22:22] <asac> ccheney: ppa? amd64 shouldnt mater there ;)
[22:29] <asac> fta: we need a FFe bug
[22:29] <asac> file one i can argue why we want that.
[22:30] <asac> is the licensing all properly documented? e.g. is it ready?
[22:53] <jdstrand> asac: is firefox-3.6.head where to commit to lucid, or does lucid have its own branch now?
[22:53] <asac> jdstrand: that commits to lucid
[22:53] <ccheney> 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] <asac> though if we need to releas another 3.6.0 we have to do some shuffeling
[22:53] <ccheney> asac: almost have all of it uploaded though as debs to p.c.c
[22:53] <asac> but we will ensure stuff that gets landed there gets released
[22:54] <asac> ccheney: we need to do that anyway
[22:54] <jdstrand> asac: thanks
[22:54] <asac> ccheney: debs are not that useful
[22:54] <ccheney> yea was hoping to have an answer for rickspencer3 for tomorrow about how to get it finished :)
[22:54] <asac> i need all the debs with sources so i can hack on it
[22:54] <ccheney> the sources are already up there
[22:54] <ccheney> you then asked for debs which i uploaded
[22:54] <asac> i asked for proper packages
[22:54] <ccheney> :)
[22:54] <asac> not just crazy debs where i cant see the diff etc.
[22:54] <asac> or source tarballs
[22:55] <ccheney> the diffs are already up there
[22:55] <asac> so you uploaded proper source packages?
[22:55] <asac> with minimal patches?
[22:55] <asac> ok
[22:55] <ccheney> yea its inside all the *-backport.tar.gz
[22:55] <ccheney> including the bzr dir everything
[22:55] <micahg> jdstrand: that first line in your changelog is missing an LP #
[22:55] <ccheney> its not completely minized yet, since some of them require re autoconfing to be able to build :-\
[22:56] <asac> ccheney: what does "including the bzr dir" mean?
[22:56] <asac> is that against upstream bzr?
[22:56] <ccheney> i'm not sure what to do about that as far as a final patch is concerned
[22:56] <asac> or against packaging bzr?
[22:56] <ccheney> foo/.bzr
[22:56] <asac> well i know that
[22:56] <asac> but what kind of tree?
[22:56] <ccheney> the original ubuntu package unpacked with bzr init run then checked in, so bzr diff shows everything that has been changed
[22:57] <ccheney> i'm not sure if there are really upstream bzr for the various packages
[22:57] <asac> hmm
[22:57] <ccheney> at least not in a manner i could easily use for this
[22:57] <asac> thats really an odd way to do things
[22:57] <asac> not really organized
[22:57] <asac> but ok
[22:57] <asac> i can see
[22:58] <ccheney> i guess for the final diff i should remove anything autoreconf did and then put the resulting patch into debian/patches and a patch adding the autoreconf cruft as a second patch?
[22:59] <asac> well. you should make proper patches out of it
[22:59] <asac> without the autoconf stuff of course
[22:59] <asac> its just painful to work on this
[22:59] <ccheney> then it won't build because many of them REQUIRE autoreconf to build at all
[22:59] <asac> but yes, in general what you outlined ;)
[22:59] <ccheney> unless you mean manually hack up the resulting automake output files?
[23:00] <ccheney> everything i had to add file wise had to be added to Makefile.am configure.in etc then rerun of the various autotools to use it, etc
[23:00] <asac> what i would have loved to see was a upstream bzr tree
[23:00] <asac> with stuff committed without autoconf
[23:00] <asac> then i could run autoreconf or something on my own etc.
[23:00] <asac> but well. thats too late now
[23:01] <ccheney> i'm a bit rusty on the tools since the only thing i normally use rcs for is debian dirs
[23:01] <asac> also i now how to go through the painful libsoup bootstrapping etc. would have been great t ohave this in a ppa properly where we could just work on
[23:01] <ccheney> OOo is a just set of tarballs that no one wants to use via a rcs :-\
[23:02] <asac> anyway
[23:02] <asac> i will pull that stuff now and see how far i get
[23:02] <ccheney> the libsoup debs are up there already
[23:02] <ccheney> along with the build log, diff etc
[23:03] <asac> ccheney: ok so you are working on ephy and gtk atm?
[23:03] <asac> e.g. the rest i can juzst install?
[23:03] <ccheney> yea trying to figure out what to do with ephy with respect to the entry stuff
[23:04] <ccheney> the rest should be installable as is
[23:04] <ccheney> i am uploading webkit atm and then have to determine why libproxy no longer patches properly so i can get it uploaded
[23:05]  * ccheney thinks he didn't even modify that package so wonders what is up
[23:07] <ccheney> hmm i think it just won't cleanly rebuild a second time
[23:07] <ccheney> reverted everything in the package and rebuilt fine
[23:10] <ccheney> ok proxy is uploaded there now, just waiting on webkit to finish
[23:13] <ccheney> done
[23:18] <asac> i dont have amd64
[23:20] <asac> so the glib thing doesnt have a bzr dir
[23:21] <ccheney> hmm, looking
[23:21] <ccheney> uh the one i uploaded did before it got to the server
[23:21]  * ccheney looks at the version on the server to see if its still there
[23:21] <asac> oh it had
[23:21] <asac> sry
[23:22] <ccheney> ok np
[23:22] <asac> is it usable with bzr from hardy?
[23:22] <asac> asac@tinya:~/ccheney/glib2.0-backport/glib2.0-2.16.6$ bzr info
[23:22] <asac> bzr: ERROR: Unknown working tree format: 'Bazaar Working Tree Format 6 (bzr 1.14)\n'
[23:22] <asac> asac@tinya:~/ccheney/glib2.0-backport/glib2.0-2.16.6$
[23:22] <ccheney> oh apparently not :-\
[23:23] <ccheney> i'm doing the work inside a chroot but did the bzr from outside apparently when i grabbed the packages
[23:24]  * asac mumbles about bzr
[23:24] <asac> so i need soup for glib?
[23:24] <asac> or for proxy?
[23:24] <ccheney> you need proxy for soup and proxy needs webkit
[23:24] <asac> where was the circle?
[23:24] <ccheney> and webkit needs soup
[23:25] <ccheney> so disable gnome support in soup then build webkit and proxy then rebuild soup with gnome enabled
[23:25] <asac> yeah. first need to build glib
[23:25] <asac> so guess i wont be of much help today
[23:25] <ccheney> ok
[23:29] <asac> ccheney: so where is ephy failing and how?
[23:31] <asac> if (priv->search_terms)
[23:31] <asac> there is a huge block of code rmeove there
[23:32] <asac> ephy-location-entry.c
[23:32] <asac> in editable_changed_cb
[23:32] <asac> just an experiment? or is that needed?
[23:33] <asac> ccheney: ?
[23:33] <asac> 1st. where is the current problem ;)
[23:39] <ccheney> oh sorry was on the phone
[23:39] <ccheney> just an experiment
[23:39] <ccheney> i was trying to forward port the old code to the new in that part and it wasn't working out
[23:40] <ccheney> backporting the entry code from gtk just into ephy doesn't look like it will work, or without a lot of effort since it changes already existing structs in hardy gtk
[23:41] <ccheney> so wasn't sure if trying to backport the entry code directly into gtk would work out, or if some other direction should be tried
[23:41] <asac> ccheney: what i mean is ... i take the current tarballs nad build them
[23:41] <asac> what happens?
[23:41] <asac> and what is in current tarballs? is there a port attempt?
[23:42] <asac> ccheney: i need to see where the new API is used in epiphany to check what to do
[23:42] <ccheney> it currently fails to build in ephy
[23:42] <asac> where and how?
[23:43] <asac> thats what i asked initially
[23:43] <ccheney> oh ok
[23:44] <ccheney> checking to see where it fails
[23:44] <ccheney> its failing in lib/widgets/ephy-location-entry.c
[23:44] <ccheney> due to the changes for the entry code
[23:45] <asac> error?
[23:45] <ccheney> if the various files related to that are reverted to original state they fail due to gtkentry not having new enough api in hardy
[23:45] <ccheney> as the code currently it fails due to: http://pastebin.ubuntu.com/391366/
[23:46] <asac> libxslt1-dev ... is that in universe?
[23:46] <asac> (in hardy)
[23:46] <asac> !info libxslt1-dev hardy
[23:46] <asac> hmm
[23:47] <asac> ok misinterpreted the apt error
[23:47] <asac> now its installing
[23:47] <ccheney> ok
[23:48] <asac> ok currently webkit is building
[23:48] <asac> then proxy
[23:48] <ccheney> ok
[23:48] <asac> then second soup run
[23:48] <asac> then i get to it i guess
[23:48] <asac> might need gtk too?
[23:49] <asac> thats a small patch adding two enums
[23:49] <ccheney> yea i think it needs those two enums at the moment anyway
[23:49] <asac> ccheney: so in the current epiphany its some incomplete state?
[23:49] <asac> or did you remove the experiemnts?
[23:50] <asac> ccheney: any other API parts you spotted that epiphany devs jumped on ?
[23:50] <asac> (of gtk)
[23:50] <asac> guess you didnt get that far
[23:52] <ccheney> yea its incomplete state
[23:52] <ccheney> not yet, i got part of it working then ran into entry bits that got me stuck
[23:53] <ccheney> the parts i backported that are still in the build are under lib/
[23:53] <ccheney> lib/gtk-* lib/gdk-* lib/glib-*
[23:55] <asac> ccheney: what api parts of gtkentry is ephy using that doesnt exist?
[23:56] <ccheney> https://wiki.ubuntu.com/epiphany-browser-backport-hardy
[23:56] <ccheney> lots of them
[23:57] <ccheney> it appears it was originally written in ephy then moved to gtk but changed a bit then ephy updated to use it and also a list of icons or something to that effect
[23:58] <asac> ok so for the entry stuff you cannot implement because you cant access the Private struct?
[23:58] <ccheney> from what i recall that the biggest part of the issue yes the private struct changes between hardy gtk and karmic gtk and the new entry stuff needs bits of the new private struct
[23:59] <ccheney> iirc they rewrote how the gtkentry code works as well when they added the new functions so i am not sure if the api is compatible