[00:05] <rickspencer3> hi RAOF
[00:05] <rickspencer3> hi TheMuso
[00:06] <TheMuso> Hey rickspencer3.
[00:06] <RAOF> Morning rickspencer3
[01:04] <rickspencer3> good night all, time for a bit of a break
[07:26] <didrocks> good morning
[08:21] <pitti> Good morning
[08:22] <didrocks> Guten Morgen pitti
[08:31] <didrocks> pitti: I didn't see seb128 yesterday evening. I think e-d-s hasn't been copied to -updates
[08:32] <pitti> ok, will do that
[08:33] <didrocks> thanks pitti :)
[09:17] <seb128> pitti, hey
[09:17] <pitti> bonjour seb128
[09:17] <seb128> pitti, do you have any opinion on what to do with GNOME 2.30.2 updates which only have translation updates?
[09:17] <seb128> is that worth doing sru uploads for those?
[09:18] <pitti> hm, good question
[09:18] <pitti> in theory we could just upload the .po files to rosetta
[09:19] <pitti> that would avoid a rebuild/SRU and should not be a lot of effort (one tar and one web ui upload per package)
[09:19] <seb128> ok
[09:19] <pitti> not sure, WDYT?
[09:19] <seb128> let me see if dpm can help me to get that done
[09:19] <seb128> I would agree with uploads
[09:19] <seb128> rosetta uploads I mean
[09:19] <seb128> dpm, hey
[09:19] <pitti> hm, I don't see an "upload" button on https://translations.edge.launchpad.net/ubuntu/lucid/+source/gnome-panel
[09:20] <pitti> I have one on my own project pages
[09:20] <pitti> seems that requires some super-powers?
[09:20] <pitti> seb128: so if you or dpm could just upload the tarballs, that seems easiest to me, and safe as well
[09:20] <seb128> pitti, ok, what I think as well, thanks
[09:21] <seb128> pitti, I will still do the gnome-desktop one to have the "about GNOME" version updated, I guess that's ok?
[09:21] <pitti> oh, sure
[09:21] <seb128> thanks
[09:21] <seb128> pitti, how are you otherwise? ;-)
[09:22] <pitti> I'm good, thanks!
[09:22] <pitti> had some fun with apt yesterday, I did what I'm best at and broke everything :)
[09:22] <seb128> hehe
[09:22] <pitti> and seems I'm now getting pulled into a second OEM project
[09:22] <seb128> I'm glad I'm still on lucid :p
[09:23] <seb128> pitti, getting busier every day? ;-)
[09:23] <pitti> seb128: oh, I broke the OEM projects, not Maverick
[09:23] <pitti> it was just because C++ sucks :)
[09:23] <seb128> pitti, I've a feeling they will not want to let you come back after 6 months once they see what you can get done ;-)
[09:23] <pitti> seb128: oh yes :) but that's a good thing
[09:24] <pitti> I recently created https://wiki.ubuntu.com/ReducingDiskFootprint
[09:24] <seb128> "Use XFCE instead of GNOME"
[09:24] <pitti> but seems I'm done with that topic now, and back to boot speed :)
[09:24] <seb128> ;-)
[09:25] <pitti> seb128: there are some focus changes for me right now, indeed :)
[09:25] <seb128> I was thinking about speed the other day
[09:25] <seb128> seems we stopped doing any chart for a while now
[09:25] <seb128> or a least watching how those are doing
[09:25] <pitti> right, would be interesting
[09:26] <vish> seb128: hi, regarding papercuts and the gnome problem for maverick, we had decided to milestone more of non-gnome/non-gtk3-required bugs , so that will solve part of the problem..
[09:27] <vish> regarding gnome packages , how can we ensure the non-gtk3-required bugs get fixed in Maverick?  you are probably not going to be backporting all those gnome changes from upstream regularly. is there some way to ensure they get patched in maverick?
[09:28] <seb128> vish, ok
[09:28] <seb128> vish, I can backport all the fixes to papercuts if they apply to the current codebase
[09:28] <seb128> vish, if upstream refactored the code it might not be as easy though
[09:29] <vish> seb128: yeah, it would be awesome if you can backport the changes.  shall i ping you regularly about the papercuts , or are you having a schedule to check those regularly?
[09:29] <pitti> seb128: hmm, seems bootchart stopped creating .pngs.. I just get the .tgz
[09:30] <seb128> vish, I will check the fix commited tasks
[09:31] <seb128> pitti, do you have pybootchart-gui?
[09:31] <vish> seb128: cool , thanks. :)
[09:31] <pitti> seb128: yes; I'll run it manually now to see what's going on
[09:33] <pitti> seb128: ah, crashes
[09:36] <pitti> seems it's looking for something "RSDTZXW" in /proc and doesn't find it
[09:37] <seb128> weird
[09:38] <pitti> oh, that's the list of prossible process states
[09:38] <pitti> "RSDTZXW".index(flag) + 1
[09:38] <pitti> i. e. some process is in a state which isn't contained there
[09:40] <pitti> ok, got it fixed
[09:41] <seb128> nice
[09:41] <seb128> pitti, https://wiki.ubuntu.com/ReducingDiskFootprint is interesting reading
[09:43] <pitti> seb128: http://people.canonical.com/~pitti/bootcharts/daniel-maverick-20100622-1.png
[09:43] <pitti> doesn't look that much different from lucid, I think
[09:43] <pitti> except that nm-applet seems to have regressed
[09:43] <pitti> hm, hang on; I think I set an empty keyring password this time, so it'd connect automatically
[09:44] <pitti> that might explain the difference
[09:44] <seb128> right
[09:44] <pitti> but the applet still seems to consume an inordinate amount of CPU
[09:44] <pitti> it should be wpasupplicant and N-M doing all the work
[09:44] <pitti> this is still the -4 kernel, but userspace should be current as of yesterday
[09:45] <seb128> I'm wondering if they do but that just reflects on the applet on the chart for some reason
[09:46] <pitti> hm, I don't think bootchart is that bad
[09:46] <pitti> they are just connected via dbus, it's not the same process or so
[09:46] <seb128> ok, so I've no clue why it's taking so much cpu
[09:47] <seb128> I don't think nm-applet changed since lucid and we did solve the icon loading issue
[09:47] <pitti> I'm going to trash the mini now and install something else, but this one has zero customizations, so I guess there's not much evidence to kill
[09:47] <seb128> well we do lazy load animation icons
[09:47] <pitti> but good to know that there are no obvious regressions by now
[09:47] <seb128> but if you autoconnect you do load those
[09:47] <seb128> still it should not create that much cpu use
[10:06] <chrisccoulson> good morning everyone
[10:16] <seb128> hey chrisccoulson, how are you?
[10:18] <chrisccoulson> hi seb128, i'm good thanks (much better than yesterday). how are you?
[10:19] <seb128> I'm fine thanks
[10:20] <seb128> oh, you were not feeling ok yesterday? side effect from weekend gardening?
[10:21] <chrisccoulson> seb128 - yeah, i didn't feel too good yesterday. i got quite badly sunburnt at the weekend, and i ached a lot from doing gardening too
[10:22] <seb128> chrisccoulson, so next weekend less effort and a bit extra relaxing ;-)
[10:22] <chrisccoulson> yeah, i intend to do nothing next weekend ;)
[10:25] <rodrigo_> I just did a gnome-settings-daemon-2.30.2 release, can someone please upload it (we need it for u1), or should I submit a branch?
[10:27] <seb128> ?
[10:27] <seb128> to lucid or maverick?
[10:28] <seb128> you need the .pc there?
[10:28] <seb128> what is u1 doing with it?
[10:43] <rodrigo_> seb128, to maverick
[10:44] <rodrigo_> seb128, we need the .pc file changes because we're writing a gsd plugin
[10:47] <seb128> rodrigo_, to do what?
[10:47] <seb128> rodrigo_, I'm just being curious ;-)
[10:47] <seb128> rodrigo_, I will do the update today
[10:49] <huats> morning
[10:51] <rodrigo_> seb128, to listen for changes in config and notify users of quota exceeded in u1 server, and other things not yet defined
[10:51] <rodrigo_> seb128, if you want, I can submit a branch with the changes?
[10:52] <seb128> rodrigo_, changes to what? g-s-d for the update?
[10:52] <seb128> lut huats
[10:52] <seb128> rodrigo_, I'm not sure I like adding things to g-s-d, it makes it fragile and slow desktop login
[10:53] <zyga> hmm, is it just me or is terminal background handling broken in lucid? selecting 'solid color' makes the background partially transparent?
[10:53] <zyga> while selecting 'transparent background' allows me to select fully opaque background?
[10:54] <seb128> it's a theme issue
[10:54] <seb128> try with an another theme
[10:54] <huats> hello seb128
[10:56] <zyga> seb128, I selected custom colors... anyway - checking with other theme
[10:56] <seb128> zyga, known issue with the theming change done in lucid
[10:56] <seb128> "solid color" means "what the theme used define"
[10:57] <rodrigo_> seb128, yes
[10:57] <seb128> which is translucid background for the light themes
[10:57] <zyga> seb128, I see
[10:57] <seb128> rodrigo_, if you have it ready feel free to hand it to me for review
[10:57] <rodrigo_> seb128, it's a very lightweith plugin, don't worry
[10:57] <rodrigo_> seb128, we thought about having it as a separate daemon, but that would slow things more
[10:57] <seb128> rodrigo_, well I don't like much things watching files and servers, it means ios and that's often slow
[10:58] <seb128> rodrigo_, but let's see how it behaves in practice
[10:58] <rodrigo_> seb128, it doesn't watch files or servers, it just listens to dbus signals
[10:58] <seb128> so you have another service running which sends those signal?
[10:58] <rodrigo_> seb128, yes, syncdaemon
[10:58] <seb128> couldn't the said service displays the informations directly?
[10:59] <rodrigo_> well, it's too heavyweight already to have more code added to it, and we don't want gtk usage there
[10:59] <seb128> ok
[10:59] <seb128> let's see how it goes in practice
[11:00] <rodrigo_> anyway, you just reminded me that we should connect to dbus after a timeout long enough that we don't interfere with the desktop login
[11:00] <rodrigo_> as the screensaver and other gsd plugins do
[11:06] <seb128> rodrigo_, would be nice yes
[11:07] <seb128> rodrigo_, so where is your gsd update for review?
[11:07] <rodrigo_> seb128, just a minute
[11:07] <seb128> ok, no hurry
[11:08] <rodrigo_> I get this btw when branching:
[11:08] <rodrigo_> Doing on-the-fly conversion from RemoteRepositoryFormat(_network_name='Bazaar pack repository format 1 (needs bzr 0.92)\n') to RepositoryFormat2a().
[11:08] <rodrigo_> This may take some time. Upgrade the repositories to the same format for better performance.
[11:09] <rodrigo_> I hope it's not a problem, kenvandine had a hard time merging some of my branches for couchdb-glib and evo-couchdb
[11:09] <seb128> should not
[11:17] <rodrigo_> seb128, ok, pushing, it takes time it seems, because of the different branch formats
[11:17] <seb128> ok
[11:19] <rodrigo_> seb128, https://code.edge.launchpad.net/~rodrigo-moya/ubuntu/maverick/gnome-settings-daemon/2_30_2_release/+merge/28154
[11:27] <seb128> rodrigo_, thanks, will review that after lunch
[11:27] <rodrigo_> ok, thanks
[11:45] <Zdra> seb128, maverick GTK package depends on recent version of libx*
[11:45] <Zdra> seb128, is there a reason for that?
[11:46] <Zdra> those libs are not in lucid
[11:46] <Zdra> removed the versionned dep, rebuild on lucid, and it works fine...
[11:49] <Zdra> seb128, we need gtk 2.21 for Empathy, so we are going to backport glib/gtk/dconf from maverick into our ppa. Is there any issue you think we could have?
[11:59] <dpm> pitti, seb128, sorry for the late reply. The "upload button" is here -> https://translations.edge.launchpad.net/ubuntu/lucid/+source/gnome-panel/+pots/gnome-panel-2.0/+upload
[11:59] <seb128> Zdra, hi
[11:59] <pitti> dpm: ah, nice; thanks! must have overlooked it
[11:59] <seb128> Zdra, not really, debian updated those requirement for the udeb changes, the udeb are special debs for the installer
[11:59] <mpt> mvo, good morning, did you get details from the Launchpad team on the archive index stuff?
[12:00] <seb128> Zdra, if you don't plan to build installation using the debian d-i you should have no issue
[12:00] <seb128> dpm, hi, thanks
[12:00] <Zdra> seb128, cool thanks :)
[12:01] <seb128> dpm, will those upload count as upstream translations or ubuntu ones?
[12:01] <seb128> Zdra, you're welcome
[12:01] <dpm> pitti, it's a bit difficult to find, actually. You have to first click on " View template & all languages..." and then you get to the upload link
[12:02] <dpm> that's probably why you did not find it, it's a bit hidden, tbh
[12:02] <pitti> that's probably half of a feature to prevent accidental uploads ;)
[12:05] <seb128> dpm, ?
[12:05] <pitti> seb128: those are ubuntu translations; upstream ones are lp.net/gnome-panel/+pots
[12:06] <seb128> pitti, right but I though there was a difference between strings coming from upstream and rosetta overrides
[12:06] <pitti> ah, I see what you mean
[12:06] <seb128> pitti, I want to make sure those are correctly flagged as upstream ones, ie will change in the next version if upstream change those
[12:06]  * pitti defers to dpm
[12:07] <seb128> pitti, rather than staying with what is uploaded because they count as ubuntu overrides of upstream strings
[12:07] <zyga> mvo, hi - are you familiar with a software-center but where authorization popup freezes and has to be closed by clicking on 'x' (lucid). Authorization works the second time you try
[12:09] <james_w> zyga: amd64?
[12:09] <didrocks> seb128: if you can have a minute this afternoon, I'm stuck with a libtool issue for evo express branch (no hurry though)
[12:09] <zyga> james_w, yes
[12:10] <seb128> didrocks, tell me
[12:10] <didrocks> seb128: http://paste.ubuntu.com/453328/plain/. Context is: plugins/sa-junk-plugin/em-junk-filter.c calls e_shell_get_default defined in shell/e-shell.h
[12:10] <james_w> zyga: it's a well-known bug with packagekit-gnome, I wonder if it's 64-bit specific, or more likely to happen on 64 bits.
[12:11] <didrocks> seb128: em-junk-filter.c contains the right include, as -I../.., which makes it build successfully with gcc (first lines)
[12:11] <zyga> james_w, I experience it every time I try - I actually learned to work around it without thinking
[12:11] <didrocks> seb128: however, nothing linked and available from libtool
[12:11] <james_w> zyga: debugging would be great, I can't reproduce
[12:12] <zyga> james_w, any hints on how to start?
[12:12] <zyga> I'm a little bit familiar with software-center
[12:12] <zyga> but I never used policykit
[12:12] <zyga> wait, did you say packagekit?
[12:12] <zyga> or policykit?
[12:12] <seb128> didrocks, in what object is e_shell_get_default defined?
[12:13] <james_w> zyga: I meant polkit
[12:13] <seb128> didrocks, you lack a -l<lib_having_the_symbol_you_use>
[12:13] <didrocks> seb128: I think it should be built in libeshell_la-e-shell.lo
[12:13] <seb128> didrocks, do you likely need a -llibeshell
[12:13] <glatzor> hello mvo
[12:13] <didrocks> seb128: let me have a try
[12:13] <glatzor> mvo, do you remeber the spec about installing updates on shutdown?
[12:14] <didrocks> seb128: I should change the rpath to to point to shell/ directory too
[12:14] <didrocks> seb128: it's not a shared library btw, from what I see
[12:14] <seb128> I don't know about rpath and never use those
[12:14] <seb128> what you need is -L../..../eshelldir -llibeshell
[12:15] <seb128> rather -leshell
[12:15] <didrocks> seb128: and the difference with adding ../../shell/libeshell.la (which works?)
[12:16] <seb128> that should work as well
[12:16] <seb128> the .la will define those things for you
[12:17] <didrocks> oh right, seeing in the header
[12:17] <didrocks> ok, now I have to find the autofoo to get that working properly :)
[12:17] <didrocks> do you think that I should add that in a separate patch than the express one?
[12:17] <seb128> but upstream likely fixed that in their express codebase
[12:17] <seb128> no
[12:18] <didrocks> ok, I'll summit that upstream so
[12:18] <didrocks> thanks seb128 :)
[12:18] <seb128> you're welcome
[12:18] <dpm> seb128, pitti, let me check something with the lp devs about upstream/ubuntu uploads and I'll come back to you
[12:18] <zyga> mvo, james_w: I ran software-center --debug, but it does not mention the policykit transaction, I still get to reproduce this every time I try
[12:19] <seb128> dpm, thanks
[12:20] <james_w> zyga: it's a race between polkit-gnome and polkit I think, so you need to look that those components
[12:23] <rodrigo_> appindicator-cil fix is in maverick now, right?
[12:23] <rodrigo_> so, I can submit a new tomboy package?
[12:24] <didrocks> ok, fixed, thanks again ;)
[12:27] <rodrigo_> didrocks, fixed the appindicator-cil thing you mean? or were you talking to someone else? :)
[12:27] <didrocks> rodrigo_: was talking about the libtool issue I had (few lines before :)), sorry ;)
[12:27] <seb128> rodrigo_, yes
[12:27] <didrocks> rodrigo_: but yeah, appindicator-cil is fixed normally now
[12:27] <seb128> rodrigo_, that got uploaded today
[12:27] <dpm> seb128, pitti, when uploading a tarball, all translations uploaded in that tarball are marked as upstream. So an option for those updates (if there aren't many, because the tarball uploads when not going through package uploads must be done manually - i.e. there is no API for that) would be to fetch them from git upstream, put them in a tarball along with the template and upload them through that form. The caveats I see though: a) if there are many su
[12:27] <dpm> ch updates, doing all this manually might be quite an overhead b) As we'll be uploading a POT template (otherwise the PO files won't be imported), that POT template must be the one from the Ubuntu package if there has been any string modification or addition in the package. I'm not too sure what implies the most overhead: the manual uploads or SRU'ing, what do you think?
[12:27] <rodrigo_> didrocks, ah, ok, thus my confusion :)
[12:28] <rodrigo_> seb128, ok, uploading tomboy then
[12:28] <rodrigo_> seb128, we backported the patch to 1.2 btw, so we'll leave to you the decision to move to 1.3 :)
[12:28] <seb128> rodrigo_, ok, how come you didn't go for 1.3? upstream are not sure they will not depends on gtk3?
[12:29] <pitti> seb128, dpm: I think manually creating and uploading a tarball should not make too much work; less work than a full SRU, in any case
[12:29] <pitti> and we are speaking about an order of 5 packages here, not 50, right?
[12:29] <rodrigo_> seb128, yes, they are sure, but just in case some other dep pulled gtk3
[12:29] <seb128> dpm, pitti: hum, I'm unsure now, I think I will be lazy and let translation team pick those updated po if they want
[12:29] <seb128> pitti, yes, I've exactly 5 of those on my list right now
[12:29] <rodrigo_> seb128, we have the patch for 1.3, so for alpha3 we might want to upgrade, but we really don't need it, thus our conservative behavior :)
[12:29] <pitti> they don't need to be from git upstream (although that wouldn't make much difference wrt. efforts involved), we'd just need to tar cv po/ and upload that, right?
[12:29] <seb128> rodrigo_, ok, thanks
[12:30] <seb128> pitti, tar wouldn't give us the right pot though
[12:30] <dpm> pitti, yeah, we'd need the pot as well
[12:30] <seb128> pitti, we need to apply patches and run intltool-update then do a tarball I think but yes
[12:30] <pitti> seb128: ah, right, because of the pot
[12:30] <dpm> either generating it or simply downloading the one from rosetta and putting it into the tarball
[12:30] <pitti> but you'd need to do that for an SRU as well
[12:31] <seb128> right, it's just that I know what I'm doing when I do a SRU
[12:31] <pitti> seb128: so, if you decide to do full SRUs
[12:31] <seb128> I feel less confident with tweaking launchpad
[12:31] <pitti> then it's fine, but it involves an additional verification step again, and the additional overhead of users having to download the package for zero changes (well, hopefully :) )
[12:31] <seb128> right, I don't want to SRU those
[12:32] <seb128> I think I will just let things the way they are
[12:32] <pitti> seb128: since these aren't urgent, perhaps just try with one package for now, and see how it goes?
[12:32] <pitti> or ignore them, right
[12:32] <seb128> translation team can upload updated po files themself if they want
[12:32] <rodrigo_> seb128, so, if someone can merge https://code.edge.launchpad.net/~rodrigo-moya/ubuntu/maverick/tomboy/1_2_with_proxy_support/+merge/28162 please?
[12:32] <seb128> rodrigo_, ok, doing that
[12:32] <rodrigo_> thanks
[12:33] <seb128> dpm, pitti: thanks, I will let that on the side for now and might have a try to uploading a set of updated po later on to see how it goes
[12:33] <pitti> right
[12:33] <pitti> dpm: so if you just upload .po files it doesn't use the previous pot by default? that'd make a nice addition
[12:33] <pitti> because then we coudl even write a script which does git pull, bundle po/, and upload it to LP
[12:34] <pitti> lunch, bbl
[12:34] <seb128> well apparently rosetta is getting that feature of importing from upstream git
[12:34] <dpm> pitti, currently, you can only do that for individual PO files. When you upload a tarball, it needs to have a POT files to attach the PO files to
[12:35] <seb128> dpm, so can I do upload 5 po files rather than a tarball?
[12:35] <seb128> dpm, in which case do I need a pot as well?
[12:35] <seb128> dpm, and would translations still count as upstream ones?
[12:37] <pitti> individual po files sounds fine, as long as we script it
[12:37] <dpm> seb128, in general only translation team members can do that, but perhaps maintainers can do it as well. In order to mark them as upstream ones, you'd simply have to tick the "Imported translation" checkbox. We can try. Can you upload files there? ->
[12:37] <dpm> https://translations.edge.launchpad.net/ubuntu/lucid/+source/gnome-panel/+pots/gnome-panel-2.0/ca/+upload
[12:37] <seb128> dpm, pitti: ok, I think I've all the info, will figure what to do later on, thanks
[12:38] <dpm> ok, great
[12:38] <rodrigo_> seb128, ugh, my tomboy upload was rejected, but I have permissions on that package AFAICS
[12:38] <rodrigo_> where can I check my per package permissions?
[12:40] <geser> rodrigo_: AFAIK only with the LP API
[12:40] <rodrigo_> geser, ok, but how?
[12:41] <didrocks> rodrigo_: ./edit_acl.py query -p <person> from ubuntu-archive-tools
[12:41] <rodrigo_> what API calls I mean?
[12:41] <didrocks> lp:~ubuntu-archive/ubuntu-archive-tools/trunk
[12:41] <rodrigo_> ok
[12:41] <didrocks> you can also -s <source_package>, but I don't know if that only should groups
[12:41] <dpm> seb128, pitti, just for the sake of completeness, there's more info on how to do manual uploads here: https://wiki.ubuntu.com/UbuntuTranslationsCoordinators/Actions/LpTemplateAdministration#Manual%20template%20upload For the lack of an API, there is also the lp-translations-tools project to automate a bit the upload part. cjwatson uses it to upload the d-i translations, but in the current state the script needs a bit of tweaking to log into LP. Ok, I
[12:41] <dpm> shut up and get something to eat now
[12:41] <didrocks> because you're not for tomboy at least
[12:42] <seb128> dpm, thanks ;-) enjoy your lunch
[12:42] <ara> chrisccoulson, hey! I have been testing some of the cases in Karmic, and some failed. Have a look when you can, and let me know any information you might need
[12:43] <rodrigo_> ugh, it just shows permissions for couchdb-glib and evolution-couchdb
[12:43] <rodrigo_> I'll talk to persia
[12:43] <chrisccoulson> hi ara - the ctxextensions issue is because i removed the updated version from the PPA
[12:43] <chrisccoulson> i will reupload a working version later
[12:43] <seb128> rodrigo_, I will sponsor the upload for this one
[12:43] <rodrigo_> seb128, yes, please
[12:43] <ara> chrisccoulson, OK, I will retest then
[12:44] <chrisccoulson> ara - i don't think that diggler worked before did it?
[12:44] <ara> chrisccoulson, I am afraid I didn't try
[12:44] <chrisccoulson> ara, IIRC, diggler wasn't detected before, so I removed the update from the PPA
[12:45] <ara> chrisccoulson, OK
[12:45] <chrisccoulson> ara - the same also for itsalltext
[12:46] <seb128> rodrigo_, or, merged and uploaded
[12:48] <seb128> rodrigo_, g-s-d the version should be -0ubuntu1 not -1ubuntu1, I'm fixing that before uploading
[12:49] <rodrigo_> seb128, ah, sorry
[12:49] <geser> rodrigo_: did we (the DMB) formal finish your application? I checked the minutes and two items got deferred to e-mail votes. But I don't remember if we did an followup :(
[12:49] <seb128> rodrigo_, no worry
[12:50] <rodrigo_> geser, persia told me at UDS that I got the permissions, so I guess it was finalized
[12:50] <rodrigo_> geser, I assumed it was done, but this is the 1st upload of the other packages that I do
[12:53] <geser> rodrigo_: then talk to cjwatson as the DMB can decide on PPU but only TB members can implement them
[12:54] <rodrigo_> geser, ok
[13:02] <didrocks> well, the archive admin tool seems to tell that you should have the right
[13:03] <didrocks> maybe somes dots are badly connected :)
[13:04] <didrocks> evolution express backported to 2.30.2 \o/
[13:04] <seb128> nice
[13:06] <didrocks> it seems so… fast :) (non blocking ui)
[13:07] <seb128> didrocks, what do you mean non blocking ui?
[13:07] <chrisccoulson> ara - ok, ctxextensions is back in the PPA again. i will look at your other issues shortly
[13:08] <didrocks> seb128: you know, sometime (and especially on slow machine), when evolution is scanning for your ldap account name for instance, you got a slowdown and you can't do nothing else in evolution. That doesn't happen in express mode
[13:09] <chrisccoulson> i've noticed that with evolution ;)
[13:09] <chrisccoulson> with the combination of evolution and U1, i can't do anything at all on my laptop for 5 minutes after logging on
[13:09] <seb128> didrocks, dunno about this one but I though issues were due to eds api being synchronous so I'm wondering how express can be different
[13:11] <didrocks> seb128: that's a good question, it doesn't happen there (and no eds change)… but I didn't tried evo 2.30 yet on a netbook before express, so maybe it's in 2.30 as well
[13:11] <seb128> didrocks, that would make sense
[13:12] <didrocks> seb128: I remember to have read about it somewhere, not sure if it was related to express or not
[13:21] <mvo> chrisccoulson: if you could have a quick look over the debdiff of https://edge.launchpad.net/~mvo/+archive/ppa/+packages?field.name_filter=flash&field.status_filter=published&field.series_filter= that would be nice. this should be enough to make the flash upgrade not fail
[13:57] <chrisccoulson> mvo - thanks, i will take a look at that shortly
[13:57] <fta2> didrocks, seb: (fyi) since i moved to maverick, evo takes a long while to appear (often more than a minute). in lucid, the UI used to appear quickly, followed by a quite long sync of my folders. now, it takes a while just to see the UI, and even more time to update the folders.
[13:58] <didrocks> fta2: more than a minute? I dont reproduce that here. evo happens in some seconds and then sync…
[13:58] <didrocks> when did you upgraded? did you have the same issue with 2.30.1?
[13:59] <didrocks> (just uploaded 2.30.2 yesterday)
[14:01] <mvo> chrisccoulson: thanks, it looks good in my test so far, I will probably upload shortly (test upgrade is at 94%)
[14:01] <fta2> didrocks, several weeks ago
[14:03] <didrocks> fta2: hum, and does 2.30.2 changed anything?
[14:05] <fta2> didrocks, will tell you that when i'm back at home
[14:05] <didrocks> fta2: ok, keep me posted
[14:09] <rickspencer3> msg seb128 hi
[14:09] <rickspencer3> msg chrisccoulson hi
[14:09] <chrisccoulson> hi rickspencer3
[14:09] <chrisccoulson> how are you today?
[14:09] <rickspencer3> lol
[14:09] <rickspencer3> did I forget a couple of slashes there?
[14:09] <chrisccoulson> i think so ;)
[14:09]  * rickspencer3 sips coffee
[14:10] <chrisccoulson> i'm on red bull today, it's far too warm for coffee ;)
[14:10] <rickspencer3> chrisccoulson, anyway I was wondering if you were coming to the meeting that beuno scheduled that's in 50 minutes?
[14:10] <chrisccoulson> rickspencer3, yeah, i planned to
[14:11] <rickspencer3> since he works in online services, he'll handle some of the search engine integration stuff going forward
[14:11] <rickspencer3> so this should alleviate a bit of work for you
[14:11] <chrisccoulson> cool :)
[14:12] <seb128> hey rickspencer3
[14:12] <rickspencer3> hi seb128
[14:12] <rickspencer3> seb128, I can only make the first 30 minutes of the team meeting
[14:12] <rickspencer3> which, btw, I haven't created the wiki for yet, etc...
[14:12] <rickspencer3> :(
[14:12] <seb128> rickspencer3, ok, seems it's plenty of time to cover your part, then I can take over for work items tracking etc
[14:12] <rickspencer3> thanks seb128
[14:13] <seb128> np ;-)
[14:13] <rickspencer3> I'll just want to talk about guadec and distro sprint
[14:13] <rickspencer3> after I dig out from my email, I'll get the page set up
[14:13] <seb128> ok
[14:14] <didrocks> seb128: ok to convert evolution-indicator to "merge-upstream" mode?
[14:14] <didrocks> hey rickspencer3 (without msg ;))
[14:14] <seb128> didrocks, your call since you maintain it
[14:15] <seb128> didrocks, but yes
[14:15] <rickspencer3> msg didrocks I think seb128 is going crazy, can you help him?
[14:15] <rickspencer3> dang it!
[14:15] <didrocks> seb128: oh, I won evolution-indicator too? ;)
[14:15] <didrocks> rickspencer3: heh :-)
[14:15] <seb128> lol
[14:15] <didrocks> seb128: damn, I know I should have never looked at evo :-)
[14:23] <rickspencer3> didrocks, can I talk you into doing a quickly session at developer week?
[14:23] <rickspencer3> actually ...
[14:23]  * didrocks checks when devweek is
[14:24] <rickspencer3> didrocks, I moved it to #quickly
[15:29] <rickspencer3> seb128, sorry to surprise you with this ...
[15:29] <rickspencer3> but we should have Alpha 3 work items set up by eod this Thursday
[15:29] <rickspencer3> (in 2 days)
[15:30] <seb128> rickspencer3, why? don't those start after alpha2 is released?
[15:30] <rickspencer3> seb128, it doesn't need to be final, right
[15:30] <rickspencer3> so this would be one week before
[15:31] <seb128> we mostly have those defined already I think
[15:31] <rickspencer3> I need to tell Jane, Mark, and the community about what we will focus on
[15:31] <rickspencer3> we should readjust next week, but we should scrub our A3 work items this week
[15:31] <seb128> ok, will check what is missing
[15:31] <rickspencer3> right now we have about 76 work items targeted for A3
[15:31] <seb128> I guess didrocks needs to set some
[15:32] <rickspencer3> but that will be too many
[15:32] <rickspencer3> or it might be
[15:32] <rickspencer3> we should only put in as many work items for A3 as we got done in A2
[15:32] <didrocks> seb128: I'm going to trade between alpha2 and alpha3 + add last minute packaging ones
[15:32] <seb128> didrocks, ok
[15:33] <rickspencer3> so, everyone should only have as many work items in A3 as they think they will get done in A2
[15:33] <seb128> rickspencer3, so around an hundred
[15:33] <rickspencer3> it's the best approximatin
[15:33] <rickspencer3> 100?
[15:33] <seb128> yes
[15:33] <rickspencer3> seb128, sure, if that's what we get done
[15:33] <seb128> http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html
[15:33] <rickspencer3> or if that's your estimate
[15:33] <seb128> we started around 130
[15:33] <rickspencer3> seb128, right, if we stay under the trend line
[15:34] <seb128> I've looked at the list
[15:34] <rickspencer3> ack
[15:34] <seb128> we will get at least 110 done I think
[15:34] <rickspencer3> so we didn't overshoot by much
[15:34] <seb128> no
[15:35] <seb128> well we did defer some
[15:35] <seb128> so right, our DONE count will be around 80
[15:35] <rickspencer3> ok, so we should for 80
[15:35] <rickspencer3> I want the milestoned worked items to be a solid commitment, rather than a goal
[15:35] <seb128> which is what we roughly have now
[15:36] <rickspencer3> of course, if someone has a goal to get more things done, they should strive for that
[15:36] <seb128> the current alpha-3 list seems something we can commit to
[15:36] <rickspencer3> seb128, right
[15:36] <rickspencer3> maybe some tweaks next week depending on what we get done this week
[15:37] <rickspencer3> but I guess it looks about right
[15:37] <seb128> right
[15:37] <seb128> I think we have the rough idea done
[15:37] <seb128> and we have one week for tweaking
[15:37] <seb128> hum
[15:37] <rickspencer3> so maybe no action for you
[15:37] <seb128> we need to get chromium on that list though
[15:37] <rickspencer3> across Ubuntu, though ...
[15:37] <rickspencer3> http://people.canonical.com/~pitti/workitems/maverick/all-maverick-alpha-2.html
[15:38] <rickspencer3> we are waaaay over the trend line :/
[15:38] <seb128> yeah
[15:38] <rickspencer3> seb128, in terms of chromium, is that chrisccoulson?
[15:38] <seb128> but robbie said something about teams being mostly on the trend
[15:38] <seb128> not sure where the extra items come from and where they are tracked
[15:38] <rickspencer3> seb128, me either
[15:38] <seb128> so we have a no-team-listed graph?
[15:38] <rickspencer3> I'll figure it out
[15:39] <seb128> ok
[15:39] <seb128> rickspencer3, chromium would be chrisccoulson yes once the firefox stable updates settle
[15:40] <rickspencer3> I'm wondering if A2 was a special case for chrisccoulson
[15:40] <chrisccoulson> that should be this week :)
[15:40] <rickspencer3> because the FF thing was such a distraction
[15:40] <chrisccoulson> (it will be mostly testing and a bit of bug fixing after that)
[15:40] <rickspencer3> it was all maintainer work, not a lot of time for work items
[15:40] <seb128> rickspencer3, I would think so, we will not change our firefox packaging model every cycle
[15:40] <rickspencer3> but maybe it will always be like that?
[15:41] <rickspencer3> but there will be security updates and such every cycle
[15:41] <seb128> right, but those will be like one week every month
[15:41] <chrisccoulson> there will be less work to do once hardy, jaunty and karmic are EOL, as we removed a lot of extensions
[15:41] <seb128> not like one month every month ;-)
[15:41] <chrisccoulson> but there will still be a lot of work when a new major version comes along
[15:41] <seb128> rickspencer3, I think maintaining firefox is like maintaining GNOME at some extend
[15:42] <rickspencer3> yeah
[15:42] <seb128> the updates and bug tracking take quite some time
[15:42] <seb128> but it should not be full time
[15:42] <seb128> like one or two weeks a month
[15:42] <seb128> which let some half capacity for work items
[15:42] <seb128> or for other webbrowser, n-m, etc
[15:50] <chrisccoulson> mvo - the flashplugin change looks ok (but i see it's uploaded anyway ;) )
[15:50] <chrisccoulson> sorry i didn't get a chance to look at it sooner
[15:50] <mvo> chrisccoulson: thanks, if you could just add a comment in the bug, that would be nice (comment that it looks ok)
[15:52] <seb128> rickspencer3, seems lot of the over trend on alpha2 is due to arm work items
[15:52] <seb128> rickspencer3, ie http://people.canonical.com/~pitti/workitems/maverick/arm-user-platforms-maverick-alpha-2.html
[15:53] <rickspencer3> seb128, ack
[15:53] <pitti> . o O { I really wish I wouldn't have used my own home dir for those; I get 20 highlights a day due to that :-) }
[15:53] <rickspencer3> I'll have to roll my own Ubuntu Engineering burn down
[15:53] <pitti> hello rickspencer3, good morning
[15:53] <rickspencer3> hi pitti
[15:53] <pitti> rickspencer3: you pung last night?
[15:53] <rickspencer3> yeah
[15:53] <seb128> pitti, you should filter out those url from highlights ;-)
[15:53] <rickspencer3> let me PM
[15:55] <fta> didrocks, the last evo doesn't have the fix for gnome 619959, right?
[15:55] <ubot2> Gnome bug 619959 in Mailer "Crash in format_itip at itip-formatter.c line 2567" [Critical,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=619959
[15:56] <didrocks> fta: no, it's hasn't
[15:57] <fta> ok
[15:57] <didrocks> fta: I'll integrate it in next upload, this is pretty annoying for users
[15:57] <fta> indeed
[15:57] <didrocks> fta: oh no, remember now, it was slowing down a lot evo
[15:58] <fta> well, it was slow before here
[15:58] <didrocks> I experienced the slowiness only with that patch
[15:58] <didrocks> I'll give it a shot again this week, to see how it fits in .2
[15:58] <fta> well, i use evo for work, so i need the patch to prevent the crash
[15:59] <fta> i roll my own builds anyway
[15:59] <didrocks> fta: keep me posted if you have bad side effects
[16:00] <fta> didrocks, just timed the last update (+ 2 patches i have to carry), 28 sec to see the UI
[16:01] <didrocks> fta: let me try there
[16:01] <fta> it's an idle quad-core
[16:01] <didrocks> fta: 6s, idle dual-core
[16:05] <fta> didrocks, 20sec for the next 3 startups
[16:05] <fta> didrocks, same with --offline
[16:06] <fta> same with --express
[16:06] <didrocks> fta: that's weird, need upstream investigation (and try to remove the evolution-indicator and evolution-couchdb) :/
[16:07] <fta> oh, it's fast with --disable-eplugin
[16:07] <vish> didrocks: hi , remember Bug #111939 ;) , you and nigelb reviewed it last cycle , but was too late , can we get that in for Maverick?
[16:07] <ubot2> Launchpad bug 111939 in metacity (Ubuntu) (and 4 other projects) "Not possible to alt-tab during a drag-and-drop operation (affects: 8) (dups: 3) (heat: 79)" [Wishlist,Triaged] https://launchpad.net/bugs/111939
[16:07] <fta> ..faster, but still not very fast
[16:07]  * didrocks adds to his TODO, thanks vish :)
[16:07] <vish> didrocks: awesome ,thanks :)
[16:21] <seb128> didrocks, chrisccoulson has 2 c (you wrote it with one in the UNE work items changes you just did)
[16:21] <chrisccoulson> heh ;)
[16:21] <didrocks> seb128: hum? I moved one
[16:21] <chrisccoulson> that always confuses people
[16:21] <didrocks> (targetted for alpha3)
[16:21] <seb128> didrocks, well that one has a typo then
[16:22] <seb128> I noticed in the email I received
[16:22] <didrocks> seb128: the [chriscoulson]separate spidermonkey from xulrunner ?
[16:22] <seb128> yes
[16:23] <didrocks> it was untargetted before, and I moved it to alpha3
[16:23] <didrocks> where is the other one? one the une-default-app blueprint too?
[16:23] <seb128> didrocks, I'm not saying you did a typo right now, I'm saying the item will not match chrisccoulson because it has a typo
[16:23] <seb128> didrocks, nm, I'm changing it now
[16:23] <didrocks> seb128: thanks
[16:23] <seb128> didrocks, no, that was the one I noticed
[16:27] <fta> didrocks, found it. it's caused by the "SpamAssassin Junk Filter" plugin
[16:28] <didrocks> fta: that's why, I don't have it activated there.
[16:28] <didrocks> fta: so, it has a huge regression, it seems
[16:30] <fta> didrocks, ohoh, in my profile, the default junk plugin was unset. setting to the only available option (bogofilter) fixed it
[16:30] <fta> +it
[16:31] <didrocks> fta: hum, interesting, maybe the schema should be changed there
[17:26] <fta> seb128, since you told me to change my keyboard layout, i have 2 (fr and fr alt). if i delete fr alt, everything is fine until i restart: fr alt keeps coming back as the active layout :(
[17:27] <seb128> fta, it's likely either in .dmrc config to console-setup in etc one
[17:27] <seb128> to -> or
[17:28] <fta> .dmrc is fine
[17:29] <rickspencer3> ArneGoetje, chrisccoulson, didrocks, kenvandine, pedro_, Riddell, seb128, tremolux
[17:29] <rickspencer3> meeting time in 1 minute
[17:29] <seb128> hey rickspencer3
[17:29] <didrocks> hey o/
[17:29] <ArneGoetje> o/
[17:29]  * pedro_ waves
[17:29] <kenvandine> hey
[17:29] <tremolux> heya everybody
[17:30] <chrisccoulson> hi
[17:30] <rickspencer3> https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-06-22
[17:30]  * ccheney is watching as well :)
[17:30]  * rickspencer3 taps gavel
[17:30] <rickspencer3> hi ccheney
[17:30] <rickspencer3> so, i only have 30 mintues
[17:31] <rickspencer3> I know you are all devastated by this news
[17:31] <kenvandine> :)
[17:31] <rickspencer3> but if we run over, seb128 said he can finish up with release stuff
[17:31] <seb128> yes ;-)
[17:31] <rickspencer3> first is outstanding actions:
[17:31] <rickspencer3> OneConf testing (https://wiki.ubuntu.com/OneConf/Testing)
[17:32] <didrocks> so, who tested? :-)
[17:32] <rickspencer3> did anyone help out with this didrocks?
[17:32] <didrocks> I asked the french community and got some feedbacks (6 people)
[17:32] <didrocks> they have the list of apps and diff they expected
[17:32] <didrocks> I'm still sure there are apps that shows that shouldn't and on the opposite too
[17:32] <didrocks> but we'll figure out for A3
[17:33] <didrocks> mpt is working on design now and mvo will work soon on USC plugin system
[17:33] <rickspencer3> very cool
[17:33] <rickspencer3> didrocks, is this in A2?
[17:34] <didrocks> rickspencer3: the USC task was for A2, but I just postponed it to A3 as I'm blocking on design and USC
[17:34] <rickspencer3> ok
[17:34] <didrocks> things should be on track now, people got some time to work on what's blocking me :)
[17:34] <rickspencer3> good job didrocks
[17:35] <rickspencer3> awesome contribution
[17:35] <didrocks> thanks :)
[17:35] <rickspencer3> moving on ...
[17:35] <rickspencer3> Guadec
[17:35] <rickspencer3> https://wiki.canonical.com/Marketing/Events/2010/GUADEC
[17:35] <rickspencer3> jono has kindly stepped in to coordinate us
[17:36] <rickspencer3> so, I'll be there the whole time
[17:36] <rickspencer3> but I haven't added myself to the wiki yet
[17:36] <rickspencer3> anyone else going
[17:36] <rickspencer3> ?
[17:36] <didrocks> me o/ I was wondering if going the whole time was needed too or not, but after discussing with seb128, it seems most of people are going Monday and Tuesday too
[17:36]  * rickspencer3 taps fingers
[17:37] <seb128> I'm going
[17:37] <seb128> will do that today
[17:37] <rickspencer3> didrocks,  I think you should go on Monday and Tuesday if you want to hang out
[17:37] <chrisccoulson> i wasn't sure whether i should go or not
[17:37] <rickspencer3> but if you have other stuff that you want to do, in personal life, etc...
[17:37] <pedro_> I'm going as well, i'll be there for almost the whole conference, i'm leaving on Friday noon
[17:37] <rickspencer3> showing up Wednesday would be great as well
[17:37] <rickspencer3> chrisccoulson, I think you should absolutely go if you want to
[17:37] <pedro_> there's a couple of interesting BoFs on Monday/Tuesday
[17:38] <rickspencer3> ok, so everyone get on the Guaedec wiki today
[17:39] <rickspencer3> if you are like chrisccoulson, and are *thinking* about going, feel free to ping me or seb128 to discuss
[17:39] <rickspencer3> next item is the sprint
[17:39] <rickspencer3> please book travel if you haven't already
[17:39] <kenvandine> done :)
[17:39] <rickspencer3> and start thinking about good goals for the sprint
[17:39] <rickspencer3> also, add yourself to the sprint wiki
[17:40] <rickspencer3> the sprint is July 19th - 23rd
[17:40] <rickspencer3> this will be here before we know it!
[17:40] <rickspencer3> ok
[17:40] <rickspencer3> kenvandine, partner update?
[17:40] <kenvandine> sure
[17:41] <kenvandine> U1 has slowly been trickling out weekly releases...
[17:41] <kenvandine> this week will include the update rb plugin for the music store, with gwibber and url sharing
[17:42] <kenvandine> for DX
[17:42] <kenvandine> indicator-network is in universe, please test if you can
[17:42] <kenvandine> https://wiki.ubuntu.com/ConnMan
[17:42] <kenvandine> for instructions... you don't need the ppa on maverick
[17:42] <kenvandine> indicator-sound has landed with the player controls
[17:42] <kenvandine> lots of good stuff to test :)
[17:43] <kenvandine> appmenu hasn't been added to une by default yet
[17:43] <kenvandine> pending bug fixes
[17:43] <kenvandine> i am hoping it gets added soon
[17:43] <kenvandine> that is all i have
[17:43] <rickspencer3> no app menue in A2?
[17:43] <didrocks> (not sure it will do it for alpha2, will be discussed next release)
[17:43] <seb128> rickspencer3, I'm inclined to say no right now
[17:43] <rickspencer3> ok
[17:44] <seb128> rickspencer3, we can discuss that later on if you want
[17:44] <rickspencer3> seb128, it's your call
[17:44] <rickspencer3> if you say it's not ready, it's not ready
[17:44] <seb128> ok, so not decided
[17:44] <rickspencer3> thanks kenvandine
[17:44] <rickspencer3> no Riddell
[17:44] <Riddell> no me?
[17:44] <seb128> but it they don't start fixing their issue rsn it will not be in alpha2...
[17:45] <rickspencer3> hi Riddell
[17:45] <rickspencer3> :)
[17:45] <rickspencer3> I didn't see your update on the wiki
[17:45] <rickspencer3> go ahead Riddell
[17:45] <Riddell> never got a reminder e-mail :)
[17:45] <Riddell> (possibly the fault of my e-mail)
[17:45] <Riddell>  - new kubuntu council voted in, me, ScottK, neversfelde
[17:45] <Riddell>  - I've promoted a metric tonne of packages to main, still waiting on MIRs but asac said just to do it now
[17:45] <Riddell>  - packagekit got updated to 0.6
[17:45] <Riddell>  - plasma-mobile is in the archive, a new variant should be along soon, "tech preview"
[17:46] <rickspencer3> Riddell, fault of the emailer
[17:46] <rickspencer3> ^suitably ambiguous
[17:46] <Riddell> also debian import freeze this week, I did a run of new-source and I got the sync script fixed so I'm going over the backlog of syncs
[17:47] <rickspencer3> thanks Riddell
[17:47] <rickspencer3> didrocks, anything to add for UNE update?
[17:47] <didrocks> yeah
[17:47] <didrocks>  * Normal release this week, as well in maverick than in lucid UNE ppa, mostly bugfixes
[17:47] <didrocks>  * Coming soon (next release), places with file (and zeitgeist) and applications places. Also workspaces switch handling!
[17:47] <didrocks>  * No bug report in transitionning from lucid (UNE) -> maverick, and lucid (unity ppa) -> maverick: some people tried, good news!
[17:47] <didrocks>  * So, maybe some uploads next Thursday at the beginning of the freeze for alpha2 (depending on when the freeze will begin) to get UNE in shape for alpha3 (MIR for new components + NEWing)
[17:48] <rickspencer3> No bug report in transitionning from lucid (UNE) -> maverick
[17:48] <rickspencer3> wow, that's quite surprising
[17:48] <rickspencer3> nice job
[17:49] <didrocks> well, it's been well tested ;)
[17:49] <rickspencer3> wow, software-center status seems really detailed!
[17:49] <seb128> didrocks, worked nicely there, great work!
[17:49] <rickspencer3> tremolux, I know there's been lots of good progress there
[17:49] <rickspencer3> any highlights to call out?
[17:49] <didrocks> seb128: thanks ;) we'll se if A2 users will have the same experience :)
[17:49] <tremolux> sure!
[17:49] <tremolux> New Apps:  We have an Application Review Board LP team and PPA set up now (https://launchpad.net/~app-review-board)
[17:49] <tremolux> and we've implemented a first-cut display of New Apps in the app-review-board PPA in software-center trunk
[17:49] <tremolux> Buy Something: Big news is that we are adding a Software Center Agent web service that will be the primary contact point for Software Center
[17:49] <tremolux> This new service will act as broker between the Payments API and Launchpad and represents a great improvement to our overall design
[17:49] <tremolux> UI Enhancements: good progress - PPA/channel support for installed items view implemented, single-pane dept screen in-progress
[17:51] <tremolux> (that's my summary)
[17:52] <seb128> rickspencer3, still there?
[17:52] <rickspencer3> so, maybe not everyone is aware that there is a change of plan here
[17:52] <seb128> ;-)
[17:52] <rickspencer3> :)
[17:52] <rickspencer3> this is on the server side
[17:52] <tremolux> yes
[17:52] <rickspencer3> it's really a better approach, at least I think it is
[17:52] <rickspencer3> but it rather resets the schedule for some items
[17:53] <seb128> Riddell, while you are at syncs can you add #590446 to the list?
[17:53] <rickspencer3> however, we maintain the goal of making "buy something" work end to end during the distro sprint
[17:53] <rickspencer3> seb128, I'm going to go into lurk mode now
[17:53] <tremolux> yes, that's still the target
[17:53] <rickspencer3> just ping me if you have any questions during release status or other business
[17:53] <seb128> ok
[17:54] <seb128> so we are approching alpha2 now
[17:54] <seb128> http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html
[17:54] <seb128> we are on track but we need to keep working as we do currently
[17:54] <seb128> the features should land by thursday this week
[17:55]  * ccheney sees his server items show up on desktop too, heh :)
[17:55] <seb128> then we have a bit less that a week for documentation, bug fixing, cleaning, etc
[17:55] <seb128> ccheney, right, that's because you are a member of the team
[17:55] <ccheney> ok
[17:56] <seb128> while we wrap alpha2 we need start building the alpha3 list
[17:56] <seb128> current status for alpha3 is http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-3.html
[17:56] <pitti> that has a very odd shape right now :)
[17:56] <seb128> the trend line and chart will be resetted after alpha2 is released so don't worry about it
[17:56] <seb128> pitti, ^ ;-)
[17:56] <pitti> it'll auto-reset after a2
[17:56] <seb128> right
[17:57] <seb128> so we need to make sure this list is on shape for next week
[17:57] <pitti> 95 WIs seems ambitious
[17:57] <seb128> so please review your items and clean things to have something you can deliver for alpha3
[17:57] <seb128> what pitti said
[17:57] <seb128> if we count the alpha2 items we did over 80 work items over that iteration
[17:58] <seb128> knowing that chrisccoulson was busy with firefox and didn't do much work items tasks
[17:58] <seb128> so I think 80 is around what we should have
[17:58] <pitti> hm, in lucid alpha-3 we got 100 done, so perhaps it's fine
[17:58] <seb128> if you have specs not on this list and should be let me know
[17:58] <tremolux> seb128: one issue for software-center is that, with the new Agent web service approach, the work items need to be revisited and updated
[17:58] <seb128> pitti, we had you in the team by then ;-)
[17:59]  * seb128 hugs pitti
[17:59] <pitti> (but that included stuff moved over to later milestones, too
[17:59] <pitti> seb128: heh *hug*
[17:59] <seb128> tremolux, that's fine, but can you try to do that by alpha2?
[17:59] <tremolux> seb128: yes
[17:59] <seb128> pitti, right, counting the DONE items for alpha2 we are around 80 items
[17:59] <seb128> tremolux, thanks
[18:00] <seb128> ok
[18:00] <seb128> that's about it, summary
[18:00] <tremolux> seb128: things are still somewhat in flux (the API specifically), but we should be able to make a good cut
[18:00] <seb128> - let's get alpĥa2 rocking
[18:00] <seb128> - get your alpha3 items in order for next week (ie before alpha2)
[18:00] <seb128> - let me know if some specs are not tracked and should or if you think we should do changes
[18:00] <seb128>  
[18:01] <seb128> tremolux, ok, we can still adjust later, we just want a rough idea for now
[18:01] <seb128> I think we need chromium to show up on this alpha3 list somehow
[18:01] <seb128> connmann as well
[18:01] <seb128> so we will still tweak over the week
[18:01] <pitti> uh, yes
[18:01] <seb128> chrisccoulson, sorry that will likely be some extra tasks for you...
[18:01] <pitti> if we are really going with connman, then rather sooner than later
[18:02] <chrisccoulson> heh :)
[18:02] <seb128> pitti, we are blocked on dx for now
[18:02] <pitti> for it will cause a hell of a lot of regressiosn
[18:02] <seb128> pitti, their indicator is not ready to be shipped yet
[18:02] <pitti> seb128: can't we use the upstream applet for now?
[18:02] <didrocks> pitti: we discussed at UDS and first agreed on A2 for that reason, but what seb128 said
[18:02] <seb128> but it's on their a3 roadmap
[18:02] <pitti> so that we can already test the dbus backend?
[18:02] <seb128> pitti, there is no upstream applet I think
[18:02] <pitti> how does meego and frieds use it then?
[18:03] <pitti> "friends"
[18:03] <didrocks> it's their own ui
[18:03] <didrocks> integration in meego "desktop interface"
[18:03] <didrocks> for other like maemo, I don't know
[18:03] <seb128> pitti, the indicator should be in a shipable state in the next weeks, it will be less work to get that ready than to adapt what others are doing around connmann
[18:03] <kenvandine> it works pretty well now...
[18:04] <seb128> pitti, ie the indicator is in universe now
[18:04] <kenvandine> but lacks a way to tweak it
[18:04] <kenvandine> so if you have problems, it is hard to save yourself
[18:04] <pitti> I'm mostly concerned about the lack of pppoe, vpn, and testing with 3G
[18:04] <seb128> pitti, so we can start doing opt-in testing
[18:04] <seb128> ie people who want to test can install it
[18:04] <pitti> I see
[18:04] <seb128> pitti, right, we are a bit late on schedule and know it
[18:05] <seb128> we will do a call for testing soon
[18:05] <seb128> and it will be in UNE before alpha3
[18:05] <pitti> alpha-3 sounds fine
[18:05] <pitti> I'd just hate to see it slip to beta
[18:05] <seb128> it will not
[18:05] <pitti> since we'll have a hard time pulling it out again after beta
[18:05] <seb128> if it miss alpha3 we will likely go to fallback plan to keep n-m
[18:05] <pitti> sounds like a plan
[18:05] <seb128> but we will not miss alpha3 I think
[18:05]  * pitti STFU and let seb128 continue his great work
[18:05] <seb128> or some people will get in trouble ;-)
[18:06] <seb128> pitti, thanks for your comment, much appreciate
[18:06] <seb128> always good to have feedback ;-)
[18:06] <seb128> and so everybody is updated on the topic
[18:06] <seb128> ok
[18:06] <seb128> other comments, questions?
[18:07] <seb128> seems not
[18:07] <seb128> rickspencer3, still around? wanting to add something or should we wrap now?
[18:07] <rickspencer3> no thanks
[18:07] <seb128> thanks
[18:07] <rickspencer3> I'll read backscroll
[18:07] <didrocks> thanks everyone
[18:07] <Riddell> seb128: I did that sync
[18:07] <ArneGoetje> thanks
[18:07] <tremolux> thanks!  good day everybody
[18:07] <seb128> and don't forget to update wikis for sprint and GUADEC
[18:07] <pitti> thanks everyone
[18:07] <seb128> and work items for a2 and a3!
[18:08] <seb128> Riddell, thanks
[18:08] <seb128> Riddell, it was on the alpha2 list so checking
[18:08] <Riddell> https://merges.ubuntu.com/main.html is worryingly long if anyone is short of things to do
[18:08] <jcastro> didrocks: can we discuss banshee/UNE/hal?
[18:09] <didrocks> jcastro: sure, can we in 25 minutes? I should go to some errands right now
[18:09] <didrocks> oh no need for errands, praise to my gf :)
[18:09] <jcastro> hah ok
[18:10] <didrocks> jcastro: so, what's going on dude?
[18:10] <jcastro> ok so I asked lamalex to kind of explain it
[18:10] <jcastro> because there's stuff in like 3 different places
[18:10] <lamalex> i can wait 25 minutes though
[18:10] <lamalex> didrocks: just ping me when you're back
[18:10] <didrocks> right, there is the iphone stuff, the udev backend and the rest of things :)
[18:10] <didrocks> lamalex: no no, it's ok finally :)
[18:11] <lamalex> oh ok
[18:11] <didrocks> I will hopefully have something to eat tonight, don't worry :-)
[18:11] <lamalex> :P
[18:11] <didrocks> lamalex: so, apparently, your work will be reviewed this week-end, right?
[18:12] <didrocks> (what aaron told)
[18:12] <lamalex> didrocks: I hope so, I talked to alan today and he hopes to have his stuff merge ready into mine by tomorrow
[18:12] <lamalex> aaron hasn't spoken to me, but if he says he plans on reviewing it this weekend then yeah
[18:12] <didrocks> lamalex: oh, so merging the iphone branch with yours? already?
[18:12] <lamalex> tomorrow
[18:12] <didrocks> sweet :-)
[18:13] <lamalex> and then aaron will review that (I assume)
[18:13] <didrocks> it was in the email you should have received
[18:13] <lamalex> ah, yeah
[18:13] <didrocks> lamalex: can you poke him once merged?
[18:13] <lamalex> sure
[18:13]  * lamalex really wants to see banshee in une :P
[18:14] <didrocks> so, as soon as aaron gave a +1, I'll try to import that in our banshee package
[18:14] <didrocks> so that we can have testers :)
[18:14] <didrocks> lamalex: heh, so do I
[18:14] <lamalex> sweet
[18:14] <seb128> didrocks, convince them to roll a tarball ;-)
[18:14] <didrocks> lamalex: FYI, I have some interface changes for UNE
[18:14] <didrocks> seb128: will try :-)
[18:14] <lamalex> didrocks: wrt banshee?
[18:14] <didrocks> lamalex: I just have one blocker and as I'm neither a mono hacker nor a banshee one, I have some hard time to get it done :-)
[18:15] <didrocks> lamalex: I've tweaked the netbook interface to get it fit well into UNE
[18:15] <didrocks> like switch back and forth between interfaces, just showing one at a time, and so on
[18:15] <lamalex> ive never actually seen the meego interface
[18:15] <didrocks> the remaining thing from my perspective is the status bar
[18:16] <lamalex> i lost the ac cord to my netbook..
[18:16] <didrocks> lamalex: it's really good, I've done not a lot for get it working in a good way
[18:16] <lamalex> awesome! i wonder if i could build/run it on my desktop
[18:16] <didrocks> so, for the last item, I hope to find a banshee hacker to help me, but no hurry in that :-)
[18:17] <didrocks> lamalex: it's just --enable-meego in configure
[18:17] <lamalex> cool beans, ill check it ouy
[18:17] <didrocks> lamalex: but I think you will want my tweak, I'll publish them this week as soon as I have some time
[18:18] <lamalex> i added this channel to my autojoin so i should be in here, ping me when youve got a patch i can test out
[18:18] <didrocks> lamalex: sweet, I will (sounds like a friday task: breaking banshee :-))
[18:19] <didrocks> lamalex: thanks a lot and do not hesitate to ping me as well as the hal-free merging process goes on
[18:19] <lamalex> I'll keep you in the loop
[18:20] <didrocks> thanks lamalex, and jcastro
[18:20] <didrocks> and good work on removing HAL from banshee, not an easy task
[18:20] <lamalex> thanks
[18:21] <jcastro> didrocks: are you shipping it with a2?
[18:22] <didrocks> jcastro: it won't make it, it should be MIRed before Thursday and integrated :-)
[18:22] <didrocks> jcastro: but if things keeps moving on on that speed, I think it can be in an early daily image post A2
[18:22] <jcastro> ok so we have time to break things then, whew
[18:22] <didrocks> right ;)
[18:23] <jcastro> didrocks: yeah something like "hardware support is totally broken, here's how to help"
[18:23] <didrocks> jcastro: I'm sure you can help for community testing for this?
[18:23] <jcastro> that's my plan!
[18:23]  * lamalex will blog about it as well
[18:26] <didrocks> jcastro, lamalex: let's rock banshee post alpha2 then! and keep us in touch :-)
[18:28] <lamalex> wow the meego interface is sweet
[18:29] <jcastro> I dude
[18:29] <jcastro> lamalex: I mean, I know dude, it's nice.
[18:41] <geser> rodrigo_: your PPU upload rights just got fixed
[18:43] <om26er> kenvandine, there?
[18:46] <om26er> bug 531835 was fixed for maverick but people often complain at #ubuntu and also #empathy guys face people too with the small font. can this be SRUed ?
[18:46] <ubot2> Launchpad bug 531835 in empathy (Ubuntu) (and 3 other projects) "Fonts are very small (affects: 13) (heat: 74)" [Low,Invalid] https://launchpad.net/bugs/531835
[18:47] <rodrigo_> geser, yeah, cjwatson did it, thanks
[18:47] <rodrigo_> kenvandine, are you uploading the rb-u1 plugin new release?
[19:07] <kenvandine> rodrigo_, hey... i can if it is ready
[19:07] <kenvandine> rodrigo_, or you can if you have upload rights for it
[19:08] <kenvandine> seb128, want to rethink an SRU for bug 531835 ?
[19:08] <ubot2> Launchpad bug 531835 in empathy (Ubuntu) (and 3 other projects) "Fonts are very small (affects: 13) (heat: 74)" [Low,Invalid] https://launchpad.net/bugs/531835
[19:08] <rodrigo_> kenvandine, don't know if it's ready, just read the backlog of the meeting and saw you mention it
[19:08] <rodrigo_> kenvandine, did aquarius tell you anything about it?
[19:08] <kenvandine> rodrigo_, ah... not that i know if... josh told me it would this week
[19:08] <kenvandine> it had been blocked on the server rollout
[19:08] <kenvandine> but the server side is done now
[19:08] <rodrigo_> right, I was waiting on that also
[19:08] <rodrigo_> ah, done?
[19:08] <kenvandine> rodrigo_, so it needs a release, etc
[19:09] <kenvandine> josh said it was
[19:09] <rodrigo_> I'll check with aquarius and then I can do the release
[19:09] <rodrigo_> and upload
[19:09] <kenvandine> rodrigo_, great
[19:09] <kenvandine> thx
[19:10] <kenvandine> om26er, checking with seb128
[19:13] <om26er> kenvandine, thanks
[19:13] <jcastro> htorque: around?
[19:15] <htorque> jcastro: yes
[19:15] <jcastro> htorque: in hindsight I think my bug filing method for bugs is kind of wrong.
[19:16] <jcastro> htorque: how do you feel about just doing "also affects" and adding each app to the master bug?
[19:17] <htorque> jcastro: well, i guess it would be easier to follow which applications are affected by the master bug
[19:18] <htorque> jcastro: right now i'd have to open all the duplicates to check if the problem is fixed
[19:19] <jcastro> htorque: indeed
[19:20] <jcastro> htorque: let's not make more work, how about we just leave them how they are but if you notice new apps just add them under also affects.
[19:20] <jcastro> and then it'll be my job to communicate that to bratsche and ted
[19:20] <htorque> jcastro: sounds good
[19:20] <jcastro> thanks for your help so far, you've been great!
[19:21] <htorque> much time thanks to the boring world cup :P
[19:21] <bratsche> Which issue are you guys talking about?
[19:27] <seb128> kenvandine, om26er: would that have any visual impact on users who run the standard config?
[19:27] <seb128> kenvandine, om26er: ie if some user install lucid and upgrade would that result in a visual change?
[19:27] <kenvandine> seb128, slight... it would make their chats use the same font as other applications
[19:28] <kenvandine> seb128, the bug heat is getting up there...
[19:28] <seb128> kenvandine, "there" being?
[19:28] <seb128> kenvandine, I think I'm subscribed to this bug report and didn't see any comment recently
[19:29] <kenvandine> 74 i think
[19:30] <kenvandine> 98
[19:30] <kenvandine> it would be a visual change
[19:30] <kenvandine> but it does make it more consistent with other apps and honor the users settings
[19:30]  * kenvandine doesn't have strong opinions either way
[19:31] <seb128> I don't have one either
[19:31] <seb128> om26er's screenshot seems fine to me
[19:31] <seb128> ie the fonts on http://launchpadlibrarian.net/40145608/Screenshot.png are nice
[19:32] <om26er> seb128, I find them hard to read
[19:32] <kenvandine> yeah... but if you change your font settings to something very different... it won't honor them
[19:32] <seb128> om26er, well then it's a matter of taste
[19:32] <kenvandine> om26er, i think it looks nice too :)
[19:32] <kenvandine> but yeah, taste
[19:33] <om26er> no problem on my side but people come with complaints. I've seen them
[19:33] <kenvandine> i can see if you change your font to something you really prefer... or bump the size up it is annoying that your chats don't honor that
[19:33] <seb128> kenvandine, where did you get the 98 count? the bug has 13 users having the issue
[19:33] <kenvandine> if you mouse over the bug heat in LP
[19:34] <kenvandine> it says 98
[19:34]  * kenvandine doesn't know how heat is calculated
[19:34] <seb128> right, heat is buggy anyway
[19:34] <kenvandine> but that number has gone up ... not sure why
[19:34] <seb128> I've noticed some bugs with some hundred heat and no duplicate or comment and with 1 user having the issue
[19:35] <seb128> let's not discuss that though
[19:35] <kenvandine> i think what is in lucid isn't terrible... but the theme change is very minor and it really just stops forcing a value
[19:35] <seb128> is there any way we could still have a correct default and let user change settings?
[19:35] <kenvandine> zdra just committed a fix for empathy so it uses the document font instead of app font
[19:35] <kenvandine> which was my complaint
[19:35] <kenvandine> no...
[19:35] <seb128> right, I was going to point that
[19:36] <kenvandine> but that goes along with the theme change
[19:36] <seb128> ok
[19:36] <seb128> let's get didrocks' current empathy sru go to updates
[19:36] <kenvandine> right now if we don't force a value it uses application font settings instead of document font
[19:36] <seb128> then we can do the 2.30.2 with that empathy change
[19:36] <kenvandine> ok
[19:36] <kenvandine> cool
[19:36] <seb128> then we can backport the theme change
[19:36] <kenvandine> om26er, ^^
[19:36] <om26er> seb128, cool :)
[19:37] <seb128> btw we need user testing for that empathy sru and some others
[19:37] <om26er> kenvandine, seb128 thanks alot guys. time to sleep ;)
[19:37] <seb128> so if you still have a lucid box can you try if the update works for you and add a comment saying that the update doesn't break things?
[19:37] <seb128> pedro_, ^
[19:37] <kenvandine> om26er, thx for the awesome bug hunting!
[19:38] <kenvandine> whoops
[19:38] <seb128> pedro_, we need some sru testing if you can help
[19:38] <seb128> pedro_, I've another round of 2.30.2 updates waiting for reviews but we need some of the current one to be tested as well
[19:38] <pedro_> seb128, I'm on it , doing evolution-rss atm and then i'm going for empathy
[19:38] <seb128> pedro_, thanks
[19:39] <pedro_> you're welcome
[20:22] <asac> i cant open gwibber through the messaging indicator anymore ;)
[20:22] <asac> in maverick
[20:22] <asac> is that button the "broadcast button" ?
[20:24] <asac> kenvandine: ^^
[20:24] <kenvandine> asac, it is
[20:24] <kenvandine> look at the log, ~/.cache/gwibber/gwibber.log
[20:25] <asac> kk
[20:25] <asac> kenvandine: everytime i click there i get:
[20:25] <asac> 2010-06-22 21:22:28,543 - Gwibber GNOME Client - INFO - Running from the system path
[20:25] <asac> 2010-06-22 21:24:50,693 - Gwibber GNOME Client - INFO - Running from the system path
[20:25] <asac> not much
[20:26] <kenvandine> humm
[20:26] <kenvandine> that looks like it is working..
[20:26] <asac> the same happens if i click on it in application menu
[20:26] <asac> let me check
[20:26] <kenvandine> run it from the command line
[20:26] <asac> only the service is running
[20:26] <asac> ps -eaf | grep gwibber
[20:26] <asac> asac      2512     1  0 00:47 ?        00:00:07 /usr/bin/python /usr/bin/gwibber-service
[20:26] <asac> asac     28142 16999  0 21:26 pts/7    00:00:00 grep gwibber
[20:26] <asac> so its not hidden on some worksapce at least ;)
[20:27] <kenvandine> hehe
[20:27] <kenvandine> yeah
[20:27] <asac> ah in xsession-errors i have something:
[20:27] <asac> kenvandine: here we go: http://paste.ubuntu.com/453545/
[20:28] <asac> couch doesnt like me ;)
[20:28] <kenvandine> indeed
[20:28] <kenvandine> did this just start happening?
[20:28] <asac> it started today
[20:28] <asac> though i upgraded to maverick last night ;)
[20:29] <asac> but i µblogged about the successful upgrade iirc
[20:29]  * asac checks ;)
[20:29] <kenvandine> killall gwibber-service beam.smp desktopcouch-service
[20:29] <kenvandine> and try again
[20:29] <asac> kenvandine: http://identi.ca/notice/37390754
[20:29] <asac> so seems its not new, but at least it opened after i tried a few times ("which probably means: took long")
[20:30] <kenvandine> that traceback means couchdb is running, but desktopcouch can't access it
[20:30] <asac> kk
[20:30] <asac> beam.smp(1375): Operation not permitted
[20:30] <asac> so thats not run as my user it seems
[20:30] <kenvandine> humm
[20:30] <kenvandine> weird
[20:30] <asac> couchdb   1375  1374  0 00:45 ?        00:02:03 /usr/lib/erlang/erts-5.7.4/bin/beam.smp -Bd -K true -- -root /usr/lib/erlang -progname erl -- -home /var/lib/couchdb -- -noshell -noinput -sasl errlog_type error -couch_ini /etc/couchdb/default.ini /etc/couchdb/local.ini /etc/couchdb/default.ini /etc/couchdb/local.ini -s couch -pidfile /var/run/couchdb/couchdb.pid -heart
[20:31] <asac> kenvandine: i remember that we had something like that in the past ;)
[20:31] <asac> anyway, now it seems to start
[20:31] <kenvandine> that is the system couchdb
[20:31] <kenvandine> so you have the server installed
[20:32] <kenvandine> you shouldn't have couchdb installed, just couchdb-bin
[20:32] <kenvandine> unless you need the server :)
[20:32] <kenvandine> humm
[20:32] <kenvandine> have you suspended?
[20:32] <asac> no ;)
[20:32] <asac> my laptop is currently a desktop as it has no battery ;)
[20:32] <kenvandine> hehe
[20:32] <kenvandine> mine is almost there
[20:32] <kenvandine> 32% capacity
[20:32] <kenvandine> gotta get a new one before the sprint
[20:32] <asac> at least it weights 70% less now ;)
[20:32] <kenvandine> hehe
[20:33] <asac> yeah i have to get a battery too (not a new one as i dont have any battery;))
[20:47] <pitti> good night everyone
[20:53] <didrocks> good night pitti
[21:29] <rickspencer3> hi lamalex
[21:29] <lamalex> ha, hi
[21:51] <rickspencer3> lamalex, I guess you know packaging for Ubuntu pretty well?
[21:51] <lamalex> yeah, a fair amount
[21:51] <lamalex> I had to do a bunch at jolicloud