[00:03] <micahg> chrisccoulson: what did you have in mind WRT the internal libpurple in instantbird WRT purple CVEs?
[00:04] <chrisccoulson> how often does libpurple get updated?
[00:05] <chrisccoulson> oh, of course, it's just pidgin really ;)
[00:05] <micahg> chrisccoulson: right
[00:05] <chrisccoulson> we should make it build with system libpurple when we do the xul2.0 update
[00:05] <micahg> 8 this year
[00:06] <micahg> chrisccoulson: well, it can't ATM since that would defeat the purpose of instantbird instead of pidgin
[00:06] <chrisccoulson> how come?
[00:06] <micahg> chrisccoulson: see discussion I had on #instantbird on i.m.o yesterday
[00:06] <micahg> it's heavily patches
[00:06] <micahg> *patched
[00:07] <micahg> the integration between libpurple and GTK is very high, whereas instantbird wants to use xul
[00:08] <chrisccoulson> ah, ok
[00:08] <micahg> There's a fedora guy with some ideas on how to fix it, I asked him to ping me when he gets that going
[00:08] <micahg> in the mean time, one of the instantbird maintainers offered to backport the CVEs and make a new release upstream, I figured if I helped a little with that, it would take care of our immediate issue
[00:13] <micahg> chrisccoulson: did you decide when to go on holiday yet?
[00:13] <chrisccoulson> i should be on holiday already really :/
[00:13] <chrisccoulson> trying to get things done before the platform sprint though
[00:14] <micahg> isn't that in Feb?
[00:16] <chrisccoulson> micahg - it's the second week of jan ;)
[00:16] <chrisccoulson> pretty much right after i get back
[00:17] <micahg> chrisccoulson: ah, earlier this year
[00:17] <micahg> I guess it makes sense, the release was 3 weeks early
[00:38] <fta> BUGabundo, \o/
[00:39] <fta> BUGabundo, got my galaxy tab today
[00:40] <BUGabundo> cool
[00:40] <BUGabundo> how are you liking it so far?
[00:40] <BUGabundo> a very diff experience from amazon reader
[00:44] <fta> BUGabundo, i'd say it's complementary
[00:44] <fta> BUGabundo, there's something wrong with my 3G services, i'm supposed to have 60 TV channels, for free, nada
[00:45] <BUGabundo> wrong APN maybe?
[00:45] <fta> BUGabundo, it's my 1st android, i like it, except for the ads everywhere
[00:45] <BUGabundo> fta: you gonna really *like adams tablet*
[00:45] <BUGabundo> its the best of both world
[00:46] <BUGabundo> really awesome android tablet
[00:46] <BUGabundo> with a secondary screen layer in eink tecnology
[00:46] <fta> BUGabundo, i think i'll wait. i already have enough, desktop/laptop/netbook/2 ereaders/tablet
[00:47] <BUGabundo> lol
[00:47] <BUGabundo> I have two android phones (3.2" and 4.3") and a 13.3" laptop
[00:48] <BUGabundo> need a 13" (10-15") tablet with android/chromeos/ubuntu boot :)
[00:49] <fta> BUGabundo, i'll wait for the bigger tablet market to mature a bit
[00:49] <BUGabundo> 6 to 12 months will be more then enough for it to mature
[00:50] <BUGabundo> at the pace of android devices and releases come out
[00:50] <fta> probably 2y, until my tablet contract expires
[00:50] <BUGabundo> I've been using android for almost 18 months now, and the world changed upside down twice already
[00:50] <fta> so i can have the next one cheap too
[00:50] <BUGabundo> 2y contracts are a bust in this day and age
[00:51] <fta> depends on the price
[00:51] <fta> got that tablet for 39€
[00:52] <BUGabundo> lol
[00:53] <BUGabundo> it costs over 600€ in retail
[00:55] <fta> BUGabundo, i can't automount it on ubuntu, any idea what that could be?
[00:55] <BUGabundo> its a samsung limitation, I think
[00:56] <BUGabundo> usually ppl new to android forget the notification bar, mount SD option
[00:56] <BUGabundo> but I think samsung limits their device to KIES software or something
[00:57] <BUGabundo> *OR* you may need to run their app in the tab, that allows you to mount it
[00:57] <BUGabundo> there's no automount.... at least not with stock
[00:57] <BUGabundo> I bough an app for mounting the SD both in the device and PC
[00:59] <fta> hm
[01:00] <BUGabundo> let me check
[01:08] <BUGabundo> ahhh
[01:08] <jewsucanuse> chris, you still around?
[01:08] <BUGabundo> fta: you need to enable usb debug
[01:09] <fta> BUGabundo, in android? how do i do that?
[01:09] <jewsucanuse> or anyone familiar with firefox's bugzilla componenets
[01:10] <BUGabundo> fta: menu, settings, applications, devel, usb debug
[01:11] <BUGabundo> fount it? http://img.funtasticus.com/2008/nov/121410daily/daily_9.jpg
[01:11] <fta> BUGabundo, no devel in there :(
[01:11] <fta> lol
[01:11] <BUGabundo> don't you see a Development?
[01:12] <BUGabundo> last entry
[01:12] <BUGabundo> what do you see?
[01:16] <fta> BUGabundo, \o/
[01:16] <BUGabundo> you did it ?
[01:18] <fta> yes
[01:19] <fta> it's less sexy than mounting the kindle but it works
[01:19] <BUGabundo> lol
[01:36] <fta> BUGabundo, is there a good pdf reader?
[01:36] <BUGabundo> there are few
[01:37] <BUGabundo> non AWESOME
[01:37] <BUGabundo> some ppl like adobe's but its slow
[01:37] <BUGabundo> I have a friend who says he has the best one (for him)
[01:38] <BUGabundo> but SGT brings a *very* cool ebook app, doesn't it ?
[01:40] <fta> SGT?
[01:41] <BUGabundo> Samsung Galaxy Tab
[01:42] <fta> hm, maybe
[01:42] <fta> BUGabundo, you do I close for real those apps, some does, some just hide there and i have to kill them
[01:43] <BUGabundo> YOU DON'T
[01:43] <BUGabundo> that's the worse habbit (windows)users  have
[01:43] <BUGabundo> please DON'T
[01:43] <BUGabundo> read android dev blog, there are *two* great posts on that
[01:43] <fta> well, it just piles up
[01:43] <BUGabundo> so what?
[01:44] <BUGabundo> does it really bother you ?
[01:44] <BUGabundo> its linux, who cares!
[01:44] <fta> i don't know yet ;) i'm new to this world
[01:44] <BUGabundo> *if* you reach a point where the OS needs more ram for an app
[01:44] <BUGabundo> it will suspend or terminate a non foreground app
[02:46] <jewsucanuse> bugabundo, can you test a bug for me?
[02:46] <jewsucanuse> oh he's gone
[04:44] <AnAnt> anyone using cowbuilder ? xulrunner-1.9.2 doesn't seem  to install in a maverick cowbuilder chroot
[04:45] <AnAnt> also it causes the processor usage to be 100%
[04:45] <AnAnt> I mean when it gets installed in a maverick cowbuilder chroot
[16:48] <fta> dpm, ping
[16:48] <fta> dpm, (have time for my question from yesterday?)
[16:48] <dpm> hi fta, yes
[16:48] <fta> good
[16:49] <dpm> (let me think for a sec first...)
[16:54] <dpm> I think having milestones as you suggested and doing regular calls for translations would help getting people motivated and focused. In addition to that, I can try to blog about it again, to see if we get more people interested. Milestones and calls for translation work for the majority of OSS projects with a regular schedule, but for Chromium I'm not sure whether we can do this. Is there some sort of roadmap and predictable milestones? That'd be
[16:54] <dpm> a good start
[16:54] <dpm> fta, ^
[16:55] <fta> dpm, upstream, it's now one major version every 6 weeks
[16:55] <fta> dpm, and we follow that
[16:56] <dpm> in any case, I think it would also be useful to have a wiki to put all the information related to Chromium translations, as right now we've only got the announcement and the info you've been adding on e-mails. I had a quick look at the wiki you pointed me to yesterday, but I couldn't figure out a way of editing pages
[16:58] <fta> dpm, have a look at this page: http://people.ubuntu.com/~fta/ppa-dashboard/chromium-daily.html  (ch 10 in trunk & dev, 9 in beta and 8 in stable, it's a faster pace than before, when lucid got v5 and maverick v6)
[17:01] <fta> at this pace, natty will be released with v11 or v12
[17:02] <dpm> fta, thanks. Is there any place with the exact schedule? I.e. with dates or with a calendar that people can subscribe to? This way translators could follow it and better coordinate their work
[17:03] <fta> dpm, hm, i don't think so, they officially announced the 6 weeks schedule a few months ago. but i will check
[17:03] <dpm> fta, ok, thanks. And do you know more about their wiki? i.e. the question above ^
[17:11] <fta> dpm, http://blog.chromium.org/2010/07/release-early-release-often.html
[17:13] <fta> dpm, oh, http://dev.chromium.org/developers/calendar
[17:18] <dpm> ah, nice. Although they only seem to mark releases for dev in their calendar. Am I getting something wrong? I'd expect the stable releases to be there as well
[17:20] <fta> dpm, hm, right. i assume it's because the other channels are less predictable. look at the generic workflow at the bottom
[17:22] <jdstrand> chrisccoulson, micahg: do you have any idea why seamonkey keeps ending up in main? how is it getting uploaded?
[17:22] <jdstrand> http://people.canonical.com/~ubuntu-archive/component-mismatches.txt
[17:24] <dpm> fta, hm, but is that not the old release cycle? It looks to me like the 12 week cycle, rather than the newer 6 week one. I guess the 6 week cycle must look the same but compressed, though
[17:24] <fta> dpm, doh!
[17:27] <micahg> jdstrand: could the source have accidentally been promoted?
[17:27] <fta> dpm, can't find anything about who's allowed to edit the wiki. i think having a login is enough, but i'm not sure
[17:28] <jdstrand> micahg: yes, it was. that was why I asked :)
[17:28] <jdstrand> micahg: what was the process to get it uploaded?
[17:28] <micahg> jdstrand: I thought that had to be done by an AA though
[17:28] <jdstrand> micahg: not if it was pocket copied from a ppa
[17:29] <jdstrand> micahg: was it pocket copied from a ppa?
[17:29] <micahg> jdstrand: well, the last one I uploaded
[17:29]  * micahg checks logs
[17:30] <micahg> jdstrand: oh, 2.0.10 was probably copied from the security PPA to maverick and then to natty
[17:31] <jdstrand> micahg: 2.0.11+build1+nobinonly-0ubuntu2
[17:31] <fta> jdstrand, hi, thanks for chromium
[17:31] <micahg> jdstrand: no, that one I uploaded straight to natty
[17:31] <jdstrand> fta: sure thing! thanks for the updated packages
[17:32] <jdstrand> micahg: 2.0.11+build1+nobinonly-0ubuntu1?
[17:32] <micahg> jdstrand: idk, chrisccoulson did that
[17:32] <jdstrand> so, 2.0.10+build1+nobinonly-0ubuntu0.10.10.1 was in main, which would explain the subsequent promotions
[17:33] <jdstrand> I don't recall doing that, but oh well, it is fixed now
[17:33] <fta> jdstrand, i see in http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt that emacs21/22 are blacklisted, but emacs23 is not, is that issue solved?
[17:33] <jdstrand> if you weren't aware of the ppa issue, if you ever ask an AA to pocket copy from a ppa to the archive, give them the overrides that need to be applied
[17:34] <jdstrand> micahg: ^
[17:34] <jdstrand> micahg: though, if I had to guess, I made the mistake, though I really don't remember it...
[17:34] <micahg> jdstrand: ok, I'll keep that in mind, thanks
[17:35] <jdstrand> fta: I am not familiar with the issue with emacs23
[17:56] <fta> jdstrand, ok, n-m. i guess someone forgot to update the blacklist rules
[18:11] <chrisccoulson> what's up with seamonkey?
[18:12] <chrisccoulson> micahg - you haven't tested the 2.0.11 releases by any chance have you?
[18:13] <micahg> chrisccoulson: not yet
[18:34] <micahg> chrisccoulson: do you need me to test this weekend?
[18:34] <chrisccoulson> micahg - if you don't mind please. i've not had a chance to do it yet
[18:35] <micahg> chrisccoulson: ok, thanks
[18:35] <micahg> oops
[18:35] <micahg> I meant will do :)
[18:35] <chrisccoulson> thanks :)