[02:20] <joelesko> chrisccoulson: I noticed I think is what a bug with the client.py and added 2 lines in create_tarbar to get around the issue.
[02:21] <joelesko> In post_checkout, it seems like client.py sets the top directory to the wrong release. I kept getting 2.3 instead of 2.3.3
[02:21] <micahg> joelesko: that should come from the tag, not a directory
[02:22] <joelesko> Hi micahg.
[02:22] <micahg> hi joelesko
[02:22] <joelesko> It does get passed the tag, but when I was making the build yesterday, I kept getting 2.3 instead of 2.3.3
[02:24] <joelesko> I have DEBIAN_TAG := SEAMONKEY_2_3_3_RELEASE, but when I check what was actually in the directory, it was the 2.3
[02:24] <micahg> I'm not very familiar with the new build system
[02:24] <joelesko> I added an hg update -r TAG after client.py ran and I got the right version.
[02:25] <micahg> interesting
[02:25] <joelesko> Where TAG is the release I wanted.
[02:25] <micahg> that's what the old script used to do
[02:25] <joelesko> It looks like they changed the way client.py works.
[02:25] <micahg> well, chrisccoulson should be back in 5-7 hours
[02:26] <joelesko> I'll be offline by then.
[02:26] <joelesko> It looks like I got the build to work from lucid throug oneiric
[02:27] <micahg> that's great news!
[02:27] <joelesko> I've been using the natty build all day.
[02:27] <micahg> well, you can leave him a note here or an e-mail and he'll get back to you
[02:28] <joelesko> I need help with the globalmenu stuff. Should that also be packaged with seamonkey?
[02:28] <micahg> probably
[02:28] <joelesko> It looks like it would conflict with firefox.
[02:29] <micahg> why? seamonkey-globalmenu would just have seamonkey in its rdf file
[02:29] <joelesko> oh, you are right. I just looked and it's going into a different directory
[02:30] <joelesko> I checked in the code and it's current if you have a chance to look at it this week.
[02:30] <micahg> joelesko: sure, just propose a merge into lp:seamonkey
[02:30] <joelesko> It's a branch on seamonkey
[02:31] <joelesko> ok. Will do as soon as the maverick and oneiric builds complete.
[02:32] <joelesko> The lucid version will compile without having yasm 1.0 and I tested it and it seems to be working fine.
[06:37] <chrisccoulson> joelesko, don't worry about the globalmenu stuff at the moment, as it will need some support for seamonkey adding to it
[06:37] <chrisccoulson> note that development of that happens at https://launchpad.net/globalmenu-extension
[06:49] <micahg> chrisccoulson: BTW, latest firefox in oneiric works on arm
[06:49] <micahg> and good morning :)
[14:29] <joelesko> micahg: I did the merge proposal. It built on all 4 releases and I have been testing on 2 of them.
[14:30] <joelesko> I'm sure it will need more testing, but I think we have a good start
[18:30] <chrisccoulson> joelesko, thanks for working on the seamonkey packaging :)
[18:30] <chrisccoulson> i've added some comments now, but i've not had a chance to review everything yet
[19:37] <joelesko> chrisccoulson: thanks for the feedback. Do I reply to the email or do a reply on the webpage?
[19:38] <joelesko> Your comments were perfect. I wasn't sure about the globalmenu stuff and wanted to drop it, but I left it in figuring it would be easier to pull if needed.
[20:01] <FernandoMiguel> oias
=== ripps_ is now known as help
=== help is now known as ripps_
=== ripps_ is now known as ripps
[23:59] <joelesko> micahg:  I'm modifying the package. Do I delete the current proposal or resubmit when ready?