[00:55] nigelb: wow, you're on planet mozilla before me...not surprising, I'm not on planet ubuntu yet [04:44] micahg: :) === chrisccoulson_ is now known as chrisccoulson === m_conley_away is now known as m_conley [13:00] chrisccoulson: #thunderbird-unity? [13:20] hello ! [13:20] :) [13:21] 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] could someone explain ? === m_conley is now known as m_conley_away [13:28] oh well, fuck off [13:34] oh, lovely, polite person :) [13:34] doesn't realize that we don't spend every waking minute staring at IRC channels ;) [13:55] hehe [14:08] chrisccoulson, wait, what, you don't?! [14:15] knome, i don't ;) [14:18] 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 ;) === m_conley_away is now known as m_conley [14:35] chrisccoulson: wow, that's an interesting proposition [14:35] it should be pretty easy to do [14:35] I still feel better about manually generating them though [14:36] and the package already contains everything we need to automatically get the correct translations [14:36] chrisccoulson: unless we'll be able to verify against an upstream hash [14:36] there already automatically created though. the cron job would just run the same command as i do manually to create the tarball [14:38] chrisccoulson: right, I guess I'm just paranoid about stuff :) [15:07] micahg: I just looked at the firefox packaging and I didn't realize how much it changed. [15:08] chrisccoulson: The new packaging system looks really nice and it has the information I needed to build seamonkey for lucid [15:11] I will convert seamonkey to the firefox packaging method. It looks very clean. [15:13] 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] joelesko: please use one bzr commit for each groups of changes [15:18] hi joelesko [15:18] which firefox branch did you look at btw? [15:23] I looked at ~mozillateam/firefox/firefox-trunk.head [15:23] I hope that is the right one. [15:24] joelesko, yeah, that's the right one [15:25] does that mean seamonkey will get language packs? :) [15:25] Very easy to read, I like the formatting. [15:26] 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] I'm sure I'll need your help when I get there. [15:27] 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] I checked out the current seamonkey branch and was going to work from there. [15:30] I was planning on modifing the firefox files and then after a local build works, check it in. [15:30] Is that what you were thinking? [15:39] joelesko: basically something that would be one changelog entry [15:40] That makes sense. Thanks [15:41] joelesko: thank you! 2.3.3 is out, so we can go with that [15:42] Yeah. I packaged it for lucid, maverick, natty and oniric and that what I wanted to go with. [15:42] 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] That would be awesome. You would want it for the releases as well, right? [15:44] 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] The rules file in firefox showed me how you do that. [15:45] joelesko: yes, lucid-oneiric would be great [15:45] 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] yes, we need the latest yasm for firefox at some point [15:46] 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] 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] chrisccoulson: there's no need to version the binary since it's a build time dependency [15:48] micahg, right, but upgrading the current version might make something else in lucid unbuildable in the future [15:48] should you need to rebuild something else which uses it [15:48] which is why i created a co-installable version [15:48] chrisccoulson: I'd just push a new source and change the binary package name, not the yasm binary [15:48] micahg, then they wouldn't be co-installable [15:49] they would conflict with each other [15:49] they don't have to be and that's fine [15:49] I need to finish with NSS right now, happy to debate this later [15:53] ok, i need to disappear for a bit and do some exercise before dinner [15:54] woohoo - fully automatic, without touching my connection at all - https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/ :) [15:54] awesome! === ejat is now known as fenris === fenris is now known as Guest40004 === Guest40004 is now known as ejat [17:15] chrisccoulson: wait, the normal course of action is to require someone to push a button to generate builds? [17:17] 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] ah [17:18] right, i forgot about the signing stuff [17:18] 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] so i can have a passwordless key, which is hosted in our datacenter [17:19] ah [17:20] i wouldn't do that any of my other keys though :) [17:22] hmmm, i've got to wait a whole week for my new laptop :( [17:23] lets hope my current one doesn't die completely before then [17:29] m_conley: what do you think about my patch on bug #817598? it would make the messaging menu work on kde [17:29] 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] 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] ok, will do [17:35] what's wrong with installing libunity on KDE? it's not like it pulls in unity, and it's, like 350kB [17:36] i suppose the "wrong" in that is kde [17:36] * knome hides [17:36] KDE already gives us enough pain, especially with that monstrous patch we have in firefox which breaks every couple of days ;) [17:39] eww [17:41] chrisccoulson: more like 1MB due its dependencies [18:01] m_conley: https://code.launchpad.net/~debfx/messagingmenu-extension/lp817598/+merge/74489 [18:02] debfx: thanks [19:05] bhearsum: launchpad also supports automatic daily builds, but they require a vcs hosted on LP which doesn't import from hg yet [19:05] ah [19:06] I'm considering that for chromium which is hosted in svn [19:06] ok, so it's saner than it sounded earlier :) [19:16] 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] i don't think that chromium is hosted in a single repo is it? [19:17] chrisccoulson: I think so, not sure [19:18] micahg, yeah, the chromium source is hosted in multiple repo's, like thunderbird is [19:18] so launchpad recipe's are pretty much a non-starter for that [19:19] chrisccoulson: well, I'll figure that out later [20:40] evening === m_conley is now known as m_conley_away