[00:55] <micahg> nigelb: wow, you're on planet mozilla before me...not surprising, I'm not on planet ubuntu yet
[04:44] <nigelb> micahg: :)
[13:00] <m_conley> chrisccoulson: #thunderbird-unity?
[13:20] <MissDjax> hello !
[13:20] <MissDjax> :)
[13:21] <MissDjax> I am new to Thunderbird... I installed it from synaptic (ubuntu natty), version 3.1.13, according to the web, the latest stable version is 6.*, I am a bit confused about that
[13:21] <MissDjax> could someone explain ?
[13:28] <MissDjax> oh well, fuck off
[13:34] <chrisccoulson> oh, lovely, polite person :)
[13:34] <chrisccoulson> doesn't realize that we don't spend every waking minute staring at IRC channels ;)
[13:55] <bhearsum> hehe
[14:08] <knome> chrisccoulson, wait, what, you don't?!
[14:15] <chrisccoulson> knome, i don't ;)
[14:18] <chrisccoulson> micahg, now i've got an environment in the datacenter that can create our source packages, i might write a cron job which monitors the upstream repo's and automatically builds and publishes a new tarball on p.c.c/~chrisccoulson every time a new tag is added ;)
[14:35] <micahg> chrisccoulson: wow, that's an interesting proposition
[14:35] <chrisccoulson> it should be pretty easy to do
[14:35] <micahg> I still feel better about manually generating them though
[14:36] <chrisccoulson> and the package already contains everything we need to automatically get the correct translations
[14:36] <micahg> chrisccoulson: unless we'll be able to verify against an upstream hash
[14:36] <chrisccoulson> there already automatically created though. the cron job would just run the same command as i do manually to create the tarball
[14:38] <micahg> chrisccoulson: right, I guess I'm just paranoid about stuff :)
[15:07] <joelesko> micahg: I just looked at the firefox packaging and I didn't realize how much it changed.
[15:08] <joelesko> chrisccoulson: The new packaging system looks really nice and it has the information I needed to build seamonkey for lucid
[15:11] <joelesko> I will  convert seamonkey to the firefox packaging method. It looks very clean.
[15:13] <micahg> joelesko: great, if you can start from the packaging we have and prepare a merge I'd be happy to review next week
[15:13] <micahg> joelesko: please use one bzr commit for each groups of changes
[15:18] <chrisccoulson> hi joelesko
[15:18] <chrisccoulson> which firefox branch did you look at btw?
[15:23] <joelesko> I looked at ~mozillateam/firefox/firefox-trunk.head
[15:23] <joelesko> I hope that is the right one.
[15:24] <chrisccoulson> joelesko, yeah, that's the right one
[15:25] <chrisccoulson> does that mean seamonkey will get language packs? :)
[15:25] <joelesko> Very easy to read, I like the formatting.
[15:26] <joelesko> If it's in the firefox package, I'll see what I can do. Since seamonkey, firefox, thunderbird are all based on the same code, it should.
[15:27] <joelesko> I'm sure I'll need your help when I get there.
[15:27] <joelesko> micahg: Can you define 'group of changes'. This is going to be a big change from what is out there now for seamonkey
[15:28] <joelesko> I checked out the current seamonkey branch and was going to work from there.
[15:30] <joelesko> I was planning on modifing the firefox files and then after a local build works, check it in.
[15:30] <joelesko> Is that what you were thinking?
[15:39] <micahg> joelesko: basically something that would be one changelog entry
[15:40] <joelesko> That makes sense. Thanks
[15:41] <micahg> joelesko: thank you!  2.3.3 is out, so we can go with that
[15:42] <joelesko> Yeah. I packaged it for lucid, maverick, natty and oniric and that what I wanted to go with.
[15:42] <micahg> joelesko: once we get caught up, if we can get someone to do the testing/packaging prep, I'm happy to upload seamonkey with everything else and push it out on release day
[15:43] <joelesko> That would be awesome. You would want it for the releases as well, right?
[15:44] <joelesko> There was a problem with yasm in lucid becaused of the accelerated jpeg processor, but there is a flag in the config to disable it for lucid
[15:44] <joelesko> The rules file in firefox showed me how you do that.
[15:45] <micahg> joelesko: yes, lucid-oneiric would be great
[15:45] <micahg> joelesko: we might be able to push a yasm-1.1.0 package to lucid, but I'd have to look into that next week
[15:46] <chrisccoulson> yes, we need the latest yasm for firefox at some point
[15:46] <chrisccoulson> joelesko, you can use this patch in seamonkey - http://bazaar.launchpad.net/~mozillateam/firefox/firefox-beta.lucid/view/head:/debian/patches/use-new-yasm-in-lucid.patch
[15:46] <chrisccoulson> and the versioned yasm package from the firefox-next PPA is what we'll push to lucid (which is co-installable with the current version in lucid)
[15:47] <micahg> chrisccoulson: there's no need to version the binary since it's a build time dependency
[15:48] <chrisccoulson> micahg, right, but upgrading the current version might make something else in lucid unbuildable in the future
[15:48] <chrisccoulson> should you need to rebuild something else which uses it
[15:48] <chrisccoulson> which is why i created a co-installable version
[15:48] <micahg> chrisccoulson: I'd just push a new source and change the binary package name, not the yasm binary
[15:48] <chrisccoulson> micahg, then they wouldn't be co-installable
[15:49] <chrisccoulson> they would conflict with each other
[15:49] <micahg> they don't have to be and that's fine
[15:49] <micahg> I need to finish with NSS right now, happy to debate this later
[15:53] <chrisccoulson> ok, i need to disappear for a bit and do some exercise before dinner
[15:54] <chrisccoulson> woohoo - fully automatic, without touching my connection at all - https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/ :)
[15:54] <micahg> awesome!
[17:15] <bhearsum> chrisccoulson: wait, the normal course of action is to require someone to push a button to generate builds?
[17:17] <chrisccoulson> bhearsum, yeah, that person is currently me. i've been turning the handle manually on daily builds because i need to sign the uploads
[17:18] <bhearsum> ah
[17:18] <bhearsum> right, i forgot about the signing stuff
[17:18] <chrisccoulson> bhearsum, i still need to sign them, but i've created a separate account (https://launchpad.net/~chrisbot) with its own key, which can't upload to our primary archive
[17:19] <chrisccoulson> so i can have a passwordless key, which is hosted in our datacenter
[17:19] <bhearsum> ah
[17:20] <chrisccoulson> i wouldn't do that any of my other keys though :)
[17:22] <chrisccoulson> hmmm, i've got to wait a whole week for my new laptop :(
[17:23] <chrisccoulson> lets hope my current one doesn't die completely before then
[17:29] <debfx> m_conley: what do you think about my patch on bug #817598? it would make the messaging menu work on kde
[17:29] <ubot2`> Launchpad bug 817598 in messagingmenu-extension "Doesn't work when libunity isn't installed" [Undecided,New] https://launchpad.net/bugs/817598
[17:29]  * m_conley looks
[17:31] <m_conley> debfx: i think your patch might be slightly out of date - can you rebase it, and do a review request on lp:messagingmenu-extension?
[17:33] <debfx> ok, will do
[17:35] <chrisccoulson> what's wrong with installing libunity on KDE? it's not like it pulls in unity, and it's, like 350kB
[17:36] <knome> i suppose the "wrong" in that is kde
[17:36]  * knome hides
[17:36] <chrisccoulson> KDE already gives us enough pain, especially with that monstrous patch we have in firefox which breaks every couple of days ;)
[17:39] <knome> eww
[17:41] <debfx> chrisccoulson: more like 1MB due its dependencies
[18:01] <debfx> m_conley: https://code.launchpad.net/~debfx/messagingmenu-extension/lp817598/+merge/74489
[18:02] <m_conley> debfx: thanks
[19:05] <micahg> bhearsum: launchpad also supports automatic daily builds, but they require a vcs hosted on LP which doesn't import from hg yet
[19:05] <bhearsum> ah
[19:06] <micahg> I'm considering that for chromium which is hosted in svn
[19:06] <bhearsum> ok, so it's saner than it sounded earlier :)
[19:16] <chrisccoulson> micahg, that wouldn't work for thunderbird anyway, as the thunderbird source comes from multiple repo's, and i think the launchpad recipes can only come from one source branch
[19:17] <chrisccoulson> i don't think that chromium is hosted in a single repo is it?
[19:17] <micahg> chrisccoulson: I think so, not sure
[19:18] <chrisccoulson> micahg, yeah, the chromium source is hosted in multiple repo's, like thunderbird is
[19:18] <chrisccoulson> so launchpad recipe's are pretty much a non-starter for that
[19:19] <micahg> chrisccoulson: well, I'll figure that out later
[20:40] <FernandoMiguel> evening