/srv/irclogs.ubuntu.com/2009/06/16/#ubuntu-desktop.txt

robert_ancellTheMuso: I agree, not my thing really00:00
TheMusoOk. How does one officially claim a package, since I am new to the team in terms of process?00:00
robert_ancellTheMuso: There is not process at the moment.  Just open a bug for the update, then make the changes00:01
seb128there is no "official claiming"00:01
seb128we tend to know who do upgrades usually and let things continue this way00:02
seb128so feel free to do the update00:02
TheMusoOk I'll take care of it then.00:03
robert_ancellsoc1: but the patch is simpler, see debian/gconf-defaults e.g. in totem00:03
soc1ah thanks, ok00:05
soc1robert_ancell: mhh ok, totem-common.gconf-defaults ...00:29
soc1but i guess i need to edit the scheme ... because i don't want to change a particular panel, but every panel which will ever be generated00:29
robert_ancellsoc1: Don't you want to set the default value of the gconf key? So all users who have not chosen a preference will get the ones you want00:31
robert_ancellsoc1: setting gconf-defaults will modify the schema defaults as it is installed00:32
soc1ah ok00:38
soc1thanks00:38
=== rickspencer3 is now known as rickspencer3-afk
soc1 /schemas/apps/panel/global/panel_show_delay 0 should do it, right?00:40
TheMusoWhats the usual procedure for updating the autoconf stuff when configure.ac is patched? Is it a matter of installing gnome-common, and running autogen.sh, and turning the resulting autoconf file changes into a patch?00:47
TheMusorobert_ancell: ^^ are you able to answer my query, given what you've done so far? This is what I would normally do, but I am wondering whether the desktop team has a different procedure.00:51
robert_ancellTheMuso: Seb showed me to run "autoreconf" and if that doesn't work run "gnome-autogen.sh".  But either is fine as long as it builds00:52
robert_ancellsoc1: Yes00:52
TheMusorobert_ancell: Ok that helps, thanks.00:53
=== asac_ is now known as asac
pittiGood morning07:02
didrockshey robert_ancell!07:28
didrocks(congrats for releasing gcalctool :D)07:28
pittihey didrocks07:29
pittirobert_ancell: good morning07:29
robert_ancellpitti: hey, up early!07:29
pittirobert_ancell: not really, 8:30 here07:29
robert_ancelldidrocks: It was really broken too.  I'm just glad I got it together enough to make a working release!07:30
robert_ancellpitti: as I said, early :O)07:30
pittiI'm already here for half an hour :)07:30
didrockshi pitti ;)07:30
didrocksrobert_ancell: pitti is watching you ^^07:30
robert_ancelldidrocks: I was wondering who installed the webcam in the corner of my office...07:31
didrocksrobert_ancell: :)07:31
didrocksrobert_ancell: did you update/worked on brasero (and gnome-games?)07:31
robert_ancelldidrocks: not yet, been working on compiz and plan to do some packaging now.  Feel free to do any you want...07:32
didrocksok, will begin with brasero. Then, gnome-games if I have some time07:33
* didrocks needs to take a bzr backport as I can't pull from my intrepid server because of repostiroy format...07:36
Amaranthseb128 is going to kill me08:04
AmaranthI'm going through paper cut bugs and most of the ones that don't have a package assigned seem to be for either nautilus, gtk+2.0, or gnome-control-center :P08:05
Amaranththe ux and design teams are getting spammed too :P08:08
didrocksI'm doing cheese :)08:18
didrocksrobert_ancell: 2.27.2-0ubuntu2 has never been released (you didn't ask for sponsorship). I include it with the new version and upload to universe08:21
didrocksrobert_ancell: btw in changelog: "Fix enviornments typo" <- this is collector :)08:21
robert_ancelldidrocks: collector?08:22
didrocksrobert_ancell: at first glance, I was thinking your wrongly typoed "environment" in changelog but indeed, you was just quoting the typo :)08:24
robert_ancelldidrocks: :)08:25
robert_ancelldidrocks: I'm trying to update the autoreconf patch for evince but running autoreconf is making it huge! how did you make your patch so small?08:30
seb128hello everybody08:30
robert_ancellseb128: hi seb08:30
seb128robert_ancell, evince only requires autoconf08:31
robert_ancellseb128: how do you know that?08:31
seb128because only the configure.ac changed08:31
pittihey seb128, bonjour08:31
seb128you need autoreconf when you have changes to makefile.aml for example08:31
seb128hello pitti08:31
robert_ancellseb128: ah, i see08:31
seb128configure update -> autoconf08:31
seb128that's what we do for most of the launchpad integration changes08:32
robert_ancella lot of my patches will be too big...08:32
pittiIANAAG, but doesn't that sometimes also require aclocal?08:32
seb128pitti, dunno, I'm running autoconf only for years and it's working08:32
pittiokay08:32
seb128pitti, could be technically wrong but that does the job08:32
pittiwell, it should complain/fail if it wants aclocal, anyway08:32
seb128well usually launchpad integration changes are "launchpad-integration" added to a pkg-config line08:33
pittirobert_ancell: just make sure to rm -r autom4te.cache/, then it should be okay08:33
seb128so it's nothing to do with aclocal08:33
robert_ancellpitti: What is in the cache? I delete that out of the resultant patch file08:33
pittirobert_ancell: you can do that as well, I just find it easier to rm before I create the patch08:34
robert_ancellsure08:34
pittirobert_ancell: it speeds up subsequent auto* runs, but these are huge, and by and large just junk08:34
* robert_ancell doesn't believe there is such a thing as an autoconf guru. Autoconf is where skynet will come from08:34
seb128what is in the cache? cache informations, nothing useful for the package to build08:34
pittirobert_ancell++08:35
pittimake hazard08:35
seb128Keybuk is the closer of an autotools guru we have around08:35
didrockshey seb128!08:40
seb128lut didrocks08:40
* seb128 sponsors gcalctool08:42
didrocksoh brasero is really well integrated with nautilus now08:43
didrocksseb128: and you didn't sponsored gtkhtml3.14? /me is sad ;)08:43
seb128didrocks, it's in junk, I only sponsor things on proper components ;-)08:43
didrocksseb128: :p08:44
seb128any reason you let it in junk?08:44
seb128you apparently registered the product08:44
didrocksseb128: yes, just forgot to push it again :)08:44
didrocksdoing it now08:44
seb128joke aside if we push it to the ubuntu-desktop bzr would be better to use the right product no?08:44
seb128thanks08:44
pittiseb128: it even has to08:44
pittithere's no +junk for teams, just for individuals08:45
seb128pitti, there is08:45
pittioh, I was told there isn't08:45
pittimaybe they changed that recently08:45
seb128pitti, I push versions to ubuntu-desktop/+junk/versions yesterday08:45
* pitti STFU08:45
seb128I push*ed* versions08:45
seb128and some people looked at it so apparently that worked08:45
robert_ancellupdating file-roller...08:46
* seb128 reviews gcalctool, gtkhtml, file-roller08:47
robert_ancellseb128: no-one has done file-roller afaik, I'm about to start08:47
seb128ah ok08:48
seb128I though you were uploading it for review08:48
robert_ancellseb128: do you use bzr for file-roller? it has a bzr link but it doesn't to clone08:49
seb128I think I planned too by launchpad sucks08:49
robert_ancellwant to clone08:49
chrisccoulsongood morning everyone08:50
seb128there is no "file-roller" product08:50
seb128the product is named "fileroller"08:50
chrisccoulsonwould anyone object if i took the gnome-terminal and vte updates?08:50
seb128so I'm not sure if I pushed to "fileroller" and just delayed to get the product renamed and forgot08:50
robert_ancellseb128: ok, i'll have a look08:50
seb128chrisccoulson, hey, not at all, they are yours08:50
seb128robert_ancell, thanks08:50
chrisccoulsonseb128 - thanks08:50
chrisccoulsoni notice gnome-screensaver is out of date too, but vaguely remember you discussing an issue with that last cycle. is that the case, or is it ok to update too?08:51
seb128there is 2.26 in bzr08:52
seb128we still didn't resolve this "screen will not unlock after upgrade"08:52
didrocksyes, I will update it an see if the issue still exists...08:52
seb128but apparently nobody is going to work on that until we got bitten08:52
seb128so I'm leaning toward uploading now08:52
chrisccoulsoni thought it was something like that. i'll try and take a look at that when i get the chance if the issue still exists08:53
seb128didrocks, would be nice to do the 2.27 update ;-)08:53
didrocksseb128: ok. I'm finishing brasero, uploading cheese and then work on this one :)08:53
didrocksbrasero done08:56
didrockstesting cheese08:56
seb128gcalctool uploaded08:56
seb128reviewing gtkhtml08:56
didrocksit seems that #ubuntu-destkop is owned by bots :)08:56
seb128lol08:57
robert_ancellI've requested fileroller to be renamed to file-roller09:02
seb128reviewing evince09:03
seb128robert_ancell, thanks09:03
seb128brb09:04
=== crevette__ is now known as crevette
didrockscheese uploaded, working on gnome-screensaver09:17
* seb128 reviews cheese09:17
didrocksseb128: hum, cheese is in universe09:18
seb128didrocks, have you looked at the typo fix sponsoring request for cheese?09:18
didrocksseb128: yes, I have included it in this update09:18
seb128ok, feel free to upload then09:18
seb128since it's in universe and you can do that ;-)09:18
didrocksthat's what I have done already. I must confess ^^09:19
seb128excellent!09:19
didrocksthat's a way to see if I have still universe access :)09:19
seb128soon archive reorganisation09:19
didrocksfor permission, at the end of the release, isn't?09:20
seb128during the cycle was my understanding09:20
seb128but I might be wrong I didn't follow the details09:20
didrocksyes, near the end of the cycle IIRC for step 109:21
seb128ok, I just noted that it was for this cycle09:22
seb128I don't care too much since I've upload rights everywhere09:22
didrocksof course :)09:22
seb128but it will be good for your guys, you will be able to upload your desktop upgrades ;-)09:22
seb128robert_ancell, put gnome-games on your todolist for tomorrow if you didn't yet, maybe open a bug to "register" it ;-)09:23
didrocksyes :-) I saw some people still asks for core-dev, not sure if I should in some monthes (maybe even after archive reorg), if I still upload some server packages... well, will see :)09:23
robert_ancelldidrocks: were you going to do gnome-games? If not I'll do it tomorrow09:24
didrocksrobert_ancell: I had this in my plan. But as there is gnome-screensaver now, I'm delaying it :-) Feel free to do it ;)09:25
robert_ancelldidrocks: that may take some time, ok I claim it then09:25
robert_ancellseb128: do you know how debian/file-roller.mime was generated?  I need to add some more entries09:27
seb128robert_ancell, I would say "by hand"09:28
robert_ancellseb128: :)09:28
seb128just copy the current lines and replace the mimetype and command09:29
robert_ancellseb128: I'm trying to work out if they have an executable to test for09:30
=== cjwatson_ is now known as cjwatson
didrocksseb128: the issue is still present09:44
didrocks(for gnome-screensaver)09:44
seb128didrocks, not surprised ...09:44
didrockswe never know :-) Well, no good traces to debug the issue :/09:45
didrocksseb128: do you think it worthes to dedicate some time to fix it this week-end?09:51
didrocksor wait for upstream or upload it...09:51
seb128didrocks, I would say "upload"09:51
seb128nobody is going to work on it until it's annoying enough09:52
didrocksseb128: ok, I'm finishing the package so... will see user's returns.09:52
=== pitti is now known as pitti_
robert_ancellI'm loving http://people.ubuntu.com/~seb128/versions.html, so much easier to see where we are behind!10:02
chrisccoulsonlol @ bug 38771510:06
ubottuLaunchpad bug 387715 in gnome-games "Crying icon in mines too sad " [Undecided,New] https://launchpad.net/bugs/38771510:06
chrisccoulsonsome bug reports are quite entertaining10:06
james_wheh10:06
crevette:)10:06
didrocksseiflotfy1: gnome-screensaver is ready, though (and there is a bug with lp inline editor if you click on update description then :))10:07
didrockshey james_w, crevette ;)10:07
seiflotfy1uhm didrocks wrong person?10:07
james_whey didrocks10:07
crevettehey didrocks10:07
didrocksseiflotfy1: sorry, yes, it was intented to seb128, autocompletion rules ^^10:07
robert_ancellbye all10:11
crevettedid someon experienced some black flash on the display recently, I seen such flashes while on battery10:16
sochi10:19
socabout https://bugs.launchpad.net/hundredpapercuts/+bug/38751810:20
ubottuLaunchpad bug 387518 in gnome-panel "The auto-hide default settings of the gnome-panel are cumbersome, making the panel look sluggish and uncomfortable" [Undecided,New]10:20
soci found the values i want to change in both panel-global.schemas.in (where they are marked deprecated) and in panel-toplevel.c (as #defines)10:26
socwheere is the right place to change it now?10:26
didrocksseb128: (between two flickerings :)) gnome-screensaver is ready, though (and there is a bug with lp inline editor if you click on update description then :))10:35
seb128re10:35
seb128didrocks: should be back stable now, got some karmic and wireless issues10:35
didrocksseb128: hum, you told some days ago that karmic was giving you a hard time? Do you think I must upgrade at this point or wait a little bit?10:36
seb128not so sure10:36
seb128I'm not quite happy about the intel driver on my laptop10:36
seb128but my ati desktop works correctly10:36
didrocksseb128: ok... I have a nvidia one. Might worth a try...10:37
seb128well it's not too bad10:37
seb128it's just that when you walk away and come back on intel your screen might not turn on again until reboot10:38
maxbmy i915 seems happy10:38
pitti_seb128: the most recent kernel enabled KMS on radeon, does that work for you?10:38
seb128and that after some hours xorg and compiz eat some gigabytes or ram10:38
seb128of ram rather10:38
didrocksseb128: hum, that doesn't sound good :/10:38
seb128I expect those to be intel issues though10:39
seb128my desktop has no such issues10:39
didrocksok. I will try to have some time to upgrade my laptop10:39
seb128didrocks: I guess you tested gnome-screensaver? ;-)10:49
didrocksseb128: screen locking and screensaver launch yes (without hw acceleration)10:52
didrocksI'm uploading hamster-applet before lunch10:55
seb128ok good10:55
seb128I'm uploading gnome-screensaver ;-)10:55
didrocksthanks seb128 :-)10:55
rodrigo_so, are there step by step instructions on how to submit new packages/new versions of existing packages?10:56
rodrigo_I've tried using dput on my PPA and had some problems10:56
rodrigo_about missing files, which are supposed to be in the tarball and files I dput'ed10:57
seb128how did you build the package you wanted to upload?10:58
seb128basically go to the source10:58
seb128and run "debuild -S -sa"10:58
seb128what error do you get? what version did you use?10:59
rodrigo_yeah, did that, even built it locally fine, but then dput'ed it, and there are errors always: https://launchpad.net/~rodrigo-moya/+archive/ppa10:59
seb128ok11:00
seb128so the upload is not the issue11:00
seb128but it doesn't build?11:00
* seb128 looks at the build log11:00
crevettedo you have a debian/ folder before doing the debuild ?11:01
rodrigo_yes11:01
seb128urg11:01
rodrigo_it builds fine locally, as I said11:01
rodrigo_and then dput my-ppa ..source.changes11:01
seb128rodrigo_: that is a hackish package11:02
seb128lecon one, you need an orig.tar.gz11:02
crevetterodrigo_, what is the content of the diff.gz ?11:02
seb128ie the upstream tarball named tomboy_0.15.1.orig.tar.gz11:02
seb128so it will put the debian changes in the diff.gz11:02
rodrigo_seb128: ok11:02
seb128and you can see easily what you changed11:02
LaneyNOOOOOOOOOOOO11:02
seb128Laney: ?11:03
* Laney dives in front of the bullet11:03
LaneyI mean, if someone's doing Tomboy, don't11:03
rodrigo_seb128: I got the tomboy sources via apt-get source, is that the correct way, or should I use something else?11:03
rodrigo_Laney: why?11:03
Laneybecause I already did it11:03
Laneyand it's waiting to be uploaded to experimental11:03
seb128rodrigo_: that's the correct way11:03
rodrigo_Laney: I need the very latest, even will do git snapshots11:03
Laney(there is a bug that I assigned to myself)11:04
rodrigo_Laney: what version did you package?11:04
Laney0.15.111:04
rodrigo_Laney: ah, ok11:04
Laneywe got some sexy space savings too11:04
Laneythanks to meebey11:04
seb128Laney: rodrigo is doing work on tomboy and that's a learning exercise too11:04
rodrigo_seb128: so for submitting packages for karmic, what's the process?11:04
Laneywell whatever11:04
Laneybut I was going to sync it soon11:04
crevetteLaney, in that case rodrigo_ is targetting  jaunty apparently11:05
rodrigo_Laney: I plan to package git snapshots, so unless you really want to do it, please leave tomboy to me11:05
Laneyyou want to do them for karmic?11:05
rodrigo_(once I get this dput thing to work, of course :)11:05
Laneyor some ppa?11:05
rodrigo_crevette: I'0m just testing on jaunty, but will do for karmic also11:05
seb128rodrigo_: there is no debian directory in your tarball11:06
rodrigo_seb128: so, any step-by-step instructions?11:06
seb128rodrigo_: wget https://edge.launchpad.net/~rodrigo-moya/+archive/ppa/+files/tomboy_0.15.1-0~ppa4.dsc https://edge.launchpad.net/~rodrigo-moya/+archive/ppa/+files/tomboy_0.15.1-0~ppa4.tar.gz11:06
seb128dpkg-source -x *.dsc11:06
seb128look to the directory11:06
seb128so upgrade in a nutshell11:06
seb128 11:06
rodrigo_hmm, ok, so having the ..orig,tar,gz will fix it?11:06
seb128apt-get source tomboy11:07
seb128wget http://download.gnome.org/sources/tomboy/0.15/tomboy-0.15.2.tar.gz11:07
seb128mv tomboy-0.15.2.tar.gz tomboy_0.15.2.orig.tar.gz11:07
seb128(or cd tomboy-ubuntu version; uupdate ../tomboy-0.15.2.tar.gz)11:07
seb128tar xzf tomboy_0.15.2.orig.tar.gz11:07
seb128cp -R tomboy-ubuntu/debian tomboy-0.15.211:07
seb128cd tomboy-0.15.211:07
seb128debuild11:07
seb128ups11:07
seb128dch -v 0.15.2-0ubuntu1~rodrigo11:08
seb128before the debuild11:08
seb128you might also need to update some patches or build-depends11:08
seb128but that's the basic11:08
rodrigo_yeah, I know that part :)11:08
rodrigo_ok, great, thanks a lot :)11:08
seb128if you don't have the orig.tar.gz it will create a debian native package11:08
seb128ie all in a tarball11:09
seb128you want an upstream tarball and a diff.gz with the ubuntu changes11:09
rodrigo_I'll try with tomboy 0.15.2, so Laney, please leave that to me11:09
seb128so make sure you have the upstream tarball correctly named11:09
rodrigo_that's what dch does, right?11:09
seb128dunno what you did in your case, the debian directory seems to be a symlink11:09
Laneyrodrigo_: There are some good fixes in Debian git that you probably want11:09
rodrigo_yeah, right, it is11:09
seb128that's not due to the orig.tar.gz11:09
Laneyimage symlinking and such like11:09
Laneysaves about 3M iirc11:10
rodrigo_seb128: I was confused about where to put the sources/untar them11:10
rodrigo_seb128: and so when it builds and works correctly in my PPA, how do I submit it for karmic?11:10
seb128Laney: cdbs in ubuntu does that automagically if tomboy is using cdbs11:10
seb128rodrigo_: open a bug and subscribe ubuntu-main-sponsors11:10
seb128add the diff.gz to the bug or a bzr url to your packaging11:11
rodrigo_ok11:11
rodrigo_and for new packages, the same?11:11
rodrigo_packages not existing in karmic, I mean11:11
seb128ask on #ubuntu-motu for those maybe11:11
Laneyseb128: how big is it installed currently?11:11
rodrigo_seb128: ok, great, things are clearer now :)11:11
seb128I would tend to say to do the same but they are a review system named REVU11:11
Laneyhe also used pngquant to crush some images too11:12
seb128Laney: Installed-Size: 1282011:12
seb128Size: 363027411:12
Laneyhttp://packages.debian.org/changelogs/pool/main/t/tomboy/current/changelog11:12
Laneygiven, that is against 0.1411:12
seb128cool11:12
rodrigo_and last question (for now :) ), is there any way of knowing who is packaging what?11:13
rodrigo_that is, I don't want to step on Laney's toes if he's doing 0.15.1, for instance11:13
LaneyI set the bug to "In Progress" on LP11:13
rodrigo_ubuntu-desktop bugs, I guess?11:13
seb128rodrigo_: open a bug saying you work on the update and use the bug for sponsoring when you are ready11:14
Laneybug 38110111:14
ubottuLaunchpad bug 381101 in tomboy "New upstream version 0.15.1" [Wishlist,In progress] https://launchpad.net/bugs/38110111:14
rodrigo_seb128: ok, cool11:14
huatsmorning everyone !11:16
seb128lut huats11:18
huatshey seb128 !11:18
huatshow are you ?11:18
seb128good, you?11:19
huatsbusy I can imagine with 2.27.311:19
huats:)11:19
huatsgood too11:19
huatsso if you have anything to do, I am your men :)11:19
seb128that's ok, we have a great team and there is a reasonable number of tarballs11:19
huatsok11:19
seb128huats: nothing to do right now but I will ping you if somebody comes ;-)11:20
huatsok, let's do it :)11:20
huatsI am around11:20
huats:)11:20
didrocksseb128: I imagine epiphany tarball, is epiphany-webkit12:01
seb128yes12:01
seb128and it's on sync with debian so don't touch ;-)12:01
didrocksoki :-)12:02
seb128pitti is back ;-)12:08
pittimeh, my server is back up (they repaired the VM host), but its networking is still broken12:08
seb128lunch time, bbl12:08
didrocksseb128: have a good lunch12:08
seb128thanks, you too!12:08
didrockspitti: so bad :/ That's why I prefer to be self-hosted (appart when you have a power breakage during UDS and you can't access your server ^^): when something bad happens, it's my fault :)12:10
pittithey are usually very reliable12:10
pittimuch more than I could ever do at home12:10
* pitti sent a support ticket12:10
sochi13:03
socseb128: https://bugs.launchpad.net/hundredpapercuts/+bug/387518 any idea how to process with that? i already attached a patch to the upstream bugzilla and i'm hoping they pick that up ...13:04
ubottuLaunchpad bug 387518 in gnome-panel "The auto-hide default settings of the gnome-panel are cumbersome, making the panel look sluggish and uncomfortable" [Wishlist,Triaged]13:04
seb128Hi soc13:04
seb128wait for them to reply13:04
seb128I think that's a duplicate too13:04
seb128that has been discussed some months ago on the lists too I think13:05
socah ok ...13:05
seb128soc: you can try pinging vuntz when he's around, he work on gnome-panel for GNOME13:07
=== cjwatson_ is now known as cjwatson
didrocksseb128: can I take gnome-desktop?13:19
seb128didrocks: if you do it quickly yes13:19
seb128didrocks: gnome-settings-daemon is broken because it needs new APIs which are in this version13:20
seb128quickly = during the afternoon13:20
didrocksseb128: ok. I can do it during the afternoon, I think. The longer is the API breakage check :)13:20
seb128;-)13:21
socseb128: ah ok thanks13:23
socvuntz: are you here?13:24
pittiyay13:39
seb128pitti: server back?13:40
pittiyep13:40
didrocksseb128: I have to regenerate relibtoolize. So, that comes to my question for gnome-python-desktop, what is relibtoolize and how to generate it ? (it's seems to generate Makefile.in, like autoconf...)13:42
seb128run autoreconf13:42
didrocksseb128: but in previous patch, we don't touch to Makefile.am. So, what's the use?13:44
seb128looking13:45
seb128didrocks: it's to avoid a rpath issue on amd64 apparently, I don't know enough about autotools to be sure what commands need to be ran and in which order13:50
seb128you need at least autoconf and alocal I think13:50
seb128it's easier to just run autoreconf13:50
pittiif you start using several commands, you should really just use autoreconf IMHO, to avoid breakage13:50
seb128but feel free to investigate an another way to do that13:50
seb128pitti: that's what I do but didrocks likes to understand what needs to be done theorically ;-)13:50
pitti(autoreconf -i, in particular)13:50
didrockspitti & seb128 : I will try autoreconf first to run them in the right orders. Thanks :)13:51
pittididrocks: you want to _understand_ autotools?13:51
didrocksseb128: you begin to understand mean :)13:51
didrockspitti: I tried... I began a little13:51
* pitti draws a cross and mutters some exorcism spell13:51
didrocksand see that's a mess ;)13:51
didrocksahah13:51
didrocksseb128: s/mean/me13:51
pittiif you want to understand what your build system is doing, write Makefiles manually13:52
pitti:)13:52
pitti(well, actually I'm half-serious about it)13:52
didrockspitti: will think about it... really! :)13:53
* didrocks is already far far away ;)13:53
socvuntz: *ping*13:53
crevettesoc, vuntz will reply to you, don't need to ping him several times14:00
Ampelbeinhi there. can i do the eog update?14:01
seb128Ampelbein: hey, yes sure14:03
asacawe: already running under full steam or still getting coffee et al;)?14:09
* pitti blinks -- "firefox wifi scanner"?14:15
soccrevette: ok14:19
rickspencer3pitti: seb128: kenvandine: Riddell: bryce: asac: I forgot to send the reminder mail for the team meeting and to set up the meeting wiki page14:21
rickspencer3:(14:21
pittihey rickspencer314:21
kenvandineno worries14:22
kenvandinegood morning rickspencer314:22
pittirickspencer3: reports were trickling in anyway14:22
seb128rickspencer3: hi, you still have some hours for that ;-)14:22
rickspencer3heh14:22
asacgood morning14:22
RiddellI always need a ping on irc to remember the meeting anyway :)14:22
aweasac: hey... getting cofffee.  let myself signed in last nite while doing kernel builds.  ;)14:26
awes/let/left/14:27
asacawe: thats good. ;)14:27
didrocksseb128: gnome-desktop is ready for you :) (had some issues with my pbuilder, which is why it takes longer than planned)14:55
seb128didrocks: ok thanks14:55
hggdhpitti, ping re. apport-retrace & package hooks14:57
seb128hey hggdh, you should ask your question directly ;-)14:58
hggdhheh14:58
seb128didrocks: you forgot to update the shlibs version14:59
seb128didrocks: when new apis are added the shlibs needs to be updated14:59
hggdhso there it goes: pitti, we are working on anonymising the stacktraces of Evolution (and others). Is there a way to have a package hook called from apport-retrace on the backoffice?14:59
didrocksseb128: I was thinking dh_shlibdeps was doing it14:59
seb128didrocks: look to the rules, DEB_DH_MAKESHLIBS_ARGS_libgnome-desktop-2-11 += -V 'libgnome-desktop-2-11 (>= 1:2.25.90)'15:00
seb128hum there is also still a libgnome-desktop-2-7.install in bzr15:00
Mark__Ttedg: http://goodies.xfce.org/projects/panel-plugins/xfce4-indicator-plugin15:02
seb128didrocks: I'm not sure to understand your comment15:02
didrocksseb128: I was thinking that dh_makeshlibs was generating shlibs file and the dh_shlibdeps was reading it15:03
pittithere we go, "pending approval" specs down to 015:03
tedgMark__T: Cool.  Why does it have a dep on indicator-applet and not something like libindicate?  (or is that a bin packaging vs. source package thing)15:03
pittihey hggdh15:03
seb128didrocks: there is no programmatic way for a build to know if symbols changed and when out of using the new .symbols format15:03
pittihggdh: apport doesn't have a feature like this right now15:04
rickspencer3pitti: do you want specs done and the burn down charts running at the start of Thursday, or end of day Thursday?15:04
* rickspencer3 is preparing meeting agenda15:04
pittihggdh: if you need this, can you please create a bug report with the detailled intended behaviour, and we discuss it there? (please subscribe "pitti")15:04
hggdhpitti, will do, thanks15:04
pittirickspencer3: I'm not picky about the exact time15:04
pittirickspencer3: but half of the specs are still in drafting, so some effort is in order15:05
rickspencer3let's say the burn down chart officially starts Friday15:05
pittiadmittedly I sent 2/3 of them back to drafting15:05
rickspencer3so specs done, work items pulled out eod Thursday15:05
pittirickspencer3: Friday> fine for me15:05
rickspencer3(if they aren't *quite* ready to be "accepted" I'll look the other way, so long as the work is well enough defined for the burndown)15:06
rickspencer3sound okay?15:06
pittirickspencer3: *nod*, work items defined is sufficient for the burndown chart15:07
pittibut still, all the specs should be drafted by Thursday as well15:07
rickspencer3pitti: can you paste me a link to the burndown chart again :/?15:15
rickspencer3when you get moment? (want it for the meeting page)15:16
pittihttp://piware.de/tmp/desktopteam-burndown-karmic.png15:17
pittirickspencer3:15:17
pitti^15:17
rickspencer3tx15:18
cjhow's karmic coming?  should I upgrade? :)15:21
* cj pokes eeejay15:21
cjhow you been man?15:21
didrockspitti: so, do you think that the ubuntu-project template for quickly shouldn't have launchpad binding?15:24
pittididrocks: you certainly do need LP for PPAs and for your user name15:25
pittididrocks: but I'm not convinced that it should register projects15:25
didrockspitti: ok, so, when first releasing, we would just ask the user to give his/her lp project name?15:26
didrockspitti: because when you first use LP, you have a lot to learn. That's why project creation would be an help (but only on release, not on project creation)15:27
rickspencer3pitti: what if you want to back up your project?15:28
rickspencer3quickly save?15:28
pittirickspencer3: ~username/+junk/project ?15:28
pittithat's per-user namespace at least15:28
pittididrocks: on release> right, makes sense15:28
didrockspitti: maybe it was not clear enough in the spec that it was only on release. I thought I detailed that, talking about "dummy project"15:29
pittididrocks: it was clear15:29
rickspencer3didrocks: are you going to be around in two hours? I was going to bring up the idea of regular quickly discussion time in our team meeting15:29
pittididrocks: but still, once hundreds of people are using this, we'll get a flood of poorly described LP project, and I doubt that these are meant for that15:30
didrocksrickspencer3: in two hours, yes, no problem :)15:30
didrockspitti: yes, that's risky and that's why it's just a proposal. It's somehow handy... but the flood can be a bad counter-part15:31
didrocksok, let's talk in a couple of hours, so :)15:31
pittididrocks: I think we should start without remote bzr, or perhaps with +junk15:32
didrockspitti: yes, it's maybe wiser15:32
* didrocks comments out his launchpad project creation code :)15:33
seb128lool: there? do you know about the 003_gdk.pc_privates change in gtk?15:34
vuntzsoc: pong15:46
loolseb128: I guess15:49
seb128lool: what is it useful for? ;-)15:50
loolTo reduce linked libraries IIRC15:50
seb128which ones?15:52
seb128and why don't we have a bug upstream about that?15:52
seb128brb15:52
loolseb128: It was introduced by Josselin with:15:53
lool  * 003_gdk.pc_privates.patch: generate correct Requires.private for15:53
lool    gdk-2.0.pc containing all necessary dependencies for static linking.15:53
loolAs you can see, it splits GDK_PACKAGES in GDK_PACKAGES and @GDK_PRIVATE_PACKAGES@15:54
loolSo that only directly needed libs are listed in Requires:, and all libs are listed in Requires.private: (used for static linking)15:54
rodrigo_seb128: at UDS there were discussions on patching g-about-me for gwibber accounts, do you know who's working on it?15:55
loolI don't know whether it's sent upstream15:55
seb128rodrigo_: no idea, ask to kenvandine15:55
kenvandinerodrigo_: me15:55
loolI know there's controversy about Requires.private upstream; it's somewhat justified, pkg-config upstream should be trying to clarify the situation, but there's no active upstream anymore15:55
kenvandinerodrigo_: haven't talked to upstream yet15:55
kenvandinerodrigo_: opinions?15:56
seb128lool: ok, I fail to update that to 2.17.2 configure changes since I don't understand the logic, could you have a look?15:56
rodrigo_kenvandine: I am upstream, so talk to me :)15:56
kenvandinehehe15:56
kenvandineplanned to15:56
rodrigo_kenvandine: well, I think it's a good idea to have a central place for accounts, so yeah15:56
loolseb128: I have a meeting in a couple of minutes, but I could have a look afterwards15:56
kenvandineeveryone in the session agreed about-me was likely the best place15:56
rodrigo_kenvandine: yes, seems so, specially to make it useful, since right now it's mostly useless15:57
seb128lool: thanks15:57
kenvandinerodrigo_: so i was thinking adding a "Social networks" tab, and only display that if gwibber was there15:57
kenvandinerodrigo_: the design team also plans to look at that UI15:57
kenvandineand make suggestions15:57
rodrigo_kenvandine: I'd like, in the long term, to have any kind of accounts (mail, google, etc)15:57
kenvandinerodrigo_: that would be very cool15:57
rodrigo_kenvandine: have you started working on it?15:57
kenvandinenope15:57
kenvandinerodrigo_: it would be GREAT if you did it :)15:58
rodrigo_kenvandine: ah, yes, I guess I can, dobey is also looking at something similar15:58
kenvandinerodrigo_: gwibber's config is being split out into a dbus service15:58
kenvandineso there will be an API to configure it15:58
rodrigo_ah, cool15:58
rodrigo_kenvandine: can't it just read a gconf key set up by g-about-me?15:59
kenvandinein fact, i think he has finished that15:59
kenvandineperhaps15:59
rodrigo_kenvandine: ok then, will be back to you soon, as soon as I finish a couple of things I need to finish15:59
kenvandinesure16:00
kenvandinerodrigo_: thx!16:00
rodrigo_kenvandine: and another question, I've been told to add a couple of blueprints for new packages needed for u1 for karmic, so where should I create those blueprints?16:00
kenvandinehttp://blueprints.launchpad.net16:02
dobeyhola16:02
kenvandineyo dobey16:02
* dobey wonders what he should look at16:02
kenvandinedobey: you worry about the u1 stuff we need for now :)16:03
kenvandinebut we were talking about gnome-about-me/gwibber16:03
rodrigo_dobey: scroll back my conversation with kenvandine16:03
kenvandinerodrigo_ was volunteering you for work ;-D16:03
rodrigo_:D16:03
kenvandinefun work of course16:04
rodrigo_kenvandine: what project should I set for the blueprint? ubuntu?16:04
kenvandinedepends on what you are doing16:04
kenvandinemost likely yes16:04
rodrigo_it's for new packages for karmic16:05
dobeyoh16:06
dobeyso the gnome-about-me ui is really complicated (probably because it's just the evolution address book contact editor UI, with an additional button to change the password)16:07
dobeyhrmm16:07
rodrigo_yes, that's why it's mostly useless16:07
dobeyyeah16:07
rodrigo_only changing the password is the only thing that makes it useful16:07
crevetterodrigo_, no it can enroll your fingerprint16:09
crevette+also16:09
rodrigo_right, that's new also16:09
crevetteit needs fprintd which is not package in ubuntu16:09
dobeythat's just a different metric for 'password' :)16:09
rodrigo_Laney: where can I get your tomboy 0.15.1 submission?16:24
rodrigo_Laney: the source package, that is16:24
Laneyrodrigo_: I updated it to 0.15.2 earlier actually16:26
Laneyrodrigo_: It's in the git repository that you'll find linked from the PTS page16:26
Laneybranches master-devel and upstream-devel specifically16:26
=== jdo_ is now known as jdobrien
Riddellrickspencer3: what time is the meeting these days?16:32
rickspencer3Riddell: it's in 58 minutes16:32
Riddellok16:33
seb128didrocks: gnome-desktop uploaded and fixes xrandr thanks16:36
didrocksseb128: y/w :)16:36
seb128didrocks: we are good on updates now ;-)16:36
didrocksseb128: yes, this time, GNOME people don't release enough tarball to beat us! :)16:37
seb128hehehe ;-)16:38
didrockseven if they try with libsoup just right now! (taking it, btw ;))16:39
didrocksseb128: oh, we are in sync with debian. So, I don't touch it :)16:40
seb128;-)16:40
pittihttps://merges.ubuntu.com/main.html indeed shows a couple of desktop packages with -0ubuntu1 vs. -1, so maybe we can sync even some more16:40
crevette didrocks libsoup 2.27.2 comiiiing16:41
seb128in most case we have diff due to launchpad integration though16:41
crevette:)16:41
didrockscrevette: you're lagguing :)16:41
crevettewe know you can't refrain you to package it16:41
didrocksit was a mistake, I was looking at the wrong package, we are not in sync with debian on libsoup2.4-1. So, doing it :)16:43
pittiseb128: I meant libraries, like libwnck or pygtksourceview16:44
seb128ah right16:44
seb128the first one has probably special changes for compiz but gtksourceview should be syncable16:44
Laneyrodrigo_: Did you manage to get it?16:46
rodrigo_Laney: I'm busy with other stuff, so will look for it later, so if you give me an URL that would make it easier :)16:49
Laneyeasily done16:49
Laneygit clone git://git.debian.org/pkg-cli-apps/packages/tomboy.git16:49
Laneygit branch master-devel origin/master-devel16:49
Laneygit branch upstream-devel origin/upstream-devel16:49
Laneygit checkout master-devel16:49
Laneygit-buildpackage -S16:49
rodrigo_well, just the git clone command is enough, but thanks :)16:50
Laneymight need a pristine-tar in there somewhere16:50
didrocksseb128: do we use the "libsoup" lp product or create a libsoup2{,.4} one?16:56
pittididrocks: libsoup16:59
didrockspitti: ok, thanks :)16:59
pittididrocks: if we are ever concerned with libsoup3, 2 and 3 are series of that product17:00
didrockspitti: ok, but we don't specify the serie in our bzr branch, just the product, isn't it?17:00
pittididrocks: right17:01
didrockspitti: thanks for the confirmation :)17:01
pittididrocks: well, you can specify it in the branch name, of course17:01
didrockspitti: something like ~ubuntu-desktop/libsoup/libsoup2/ubuntu, for instance?17:02
socvuntz: sorry, now i'm here!17:02
didrocks(as LP can now handle more than "3 parts" for branches)17:02
pittididrocks: ~u-desktop/libsoup/ubuntu-libsoup217:02
pittididrocks: no, what you mean are package branches17:03
pittididrocks: project branches are unchanged (~owner/project/branchname)17:03
pittididrocks: package branches are ~owner/ubuntu/karmic/package/branchname17:03
pittibut we shouldn't use them for our packaging-only branches for now17:03
didrockspitti: oh, ok. didn't know there was a difference. ok, let's use /ubuntu atm, we will see if we have to rename later17:03
pittididrocks: right, sounds like a plan17:04
didrockspitti: right17:04
* pitti yays at his first successful run of PYTHONPATH=. gtk/apport-gtk --symptom camera17:07
bryce\o/17:07
pittihey bryce, how are you?17:08
seb128didrocks: libsoup should work17:10
brycepitti: doing good17:12
rickspencer3desktop team meeting in 15 minutes17:15
rickspencer3pitti: very cool!17:15
* pitti invokes "apport-gtk --symptom my-day-only-has-24-hours" and hopes for some solution17:16
didrocks:)17:17
didrockspitti: share the solution if you fond one, please :)17:17
didrockss/fond/find/17:17
pittirickspencer3: today we got some more work items, I re-ran the collector (see http://piware.de/tmp/desktopteam-burndown-karmic.png)17:18
rickspencer3huh17:19
pittirickspencer3: it seems to have confused pychart utterly, though, wrt. the y scale17:19
rickspencer3I noticed that17:19
rickspencer3I wonder what happend?17:19
rickspencer3in any case, the chart is still readable17:19
rickspencer3I have to say, the png's produced on your computer are less than beautiful17:20
pittiI know, I'd prefer svg17:20
rickspencer3I think it supports svg17:20
rickspencer3does it not?17:20
pittihttp://piware.de/tmp/desktopteam-burndown-karmic.svg17:20
pittirickspencer3: it does, but it's ugly as wel17:21
pittil17:21
rickspencer3lol17:21
pittiperhaps that's just firefox, though17:21
rickspencer3what's wrong with it ;) ?17:21
pittirickspencer3: (not sure if you are serious); does it look ok for you?17:22
rickspencer3pitti: I was joking, it looks very oddly assembled to me17:22
pittirickspencer3: do PNGs look better on your computer?17:23
rickspencer3I'll try debugging it later17:23
rickspencer3hold on17:23
rickspencer3pitti: I'm not sure, actually17:23
* pitti wonders where the --make-it-look-good option is17:24
rickspencer3I wonder why the scale is so out of whack17:24
rickspencer3one thing I can do is make the text and the line thickness a little bigger17:24
rickspencer3that should be simple formatting options17:24
rickspencer3pitti: are you passing size parameters to the script?17:25
pittino, I don't; I thought it'd infer it automatically17:25
pittirickspencer3: btw, I just pulled again, I'm still at rev7 (no hashbang)17:25
rickspencer3in terms of length and width of the chart, I made up some more or less aribtrary defaults17:25
rickspencer3pitti: the only change I made was adding the shebang17:26
rickspencer3pitti: perhaps you can send me your data in a csv file and I can try to debug why the scale is off?17:26
pittirickspencer3: http://piware.de/tmp/desktop-workitems.db17:27
pittirickspencer3: that's the actual real db17:27
rickspencer3so I have to query it with sql-lite?17:27
* rickspencer3 downloaded data17:27
pittirickspencer3: I added a title now17:28
pittirickspencer3: should I use --height as a workaround, or does that just scale the entire image?17:28
loolseb128: I have a new version of the patch17:28
rickspencer3height is just the height of the chart, doesn't talk to the scale17:28
loolCurrent gdk-2.0.pc:17:28
pittioops, yes17:28
loolRequires: gdk-pixbuf-2.0 pango pangocairo gio-2.017:28
loolRequires.private: fontconfig x11 xext xrender xinerama xi xrandr xcursor xfixes xcomposite xdamage cairo-xlib17:28
loolNew gdk-2.0.pc:17:28
loolRequires: gdk-pixbuf-2.0 pango pangocairo gio-2.017:29
loolRequires.private: fontconfig x11 xext xrender xinerama xrandr xcursor xfixes xcomposite xdamage cairo-xlib17:29
loolThis is with x11 target17:29
geserdoes gnome-display-properties work for somebody after yesterdays/todays updates in karmic?17:29
rickspencer3oops, time for the meeting17:29
rickspencer3in 1 min.17:29
seb128geser: yes after install libgnome-desktop-2-11 2.2717:29
seb128installing17:30
loolCurrent gdk-directfb-2.0.pc:17:30
loolRequires: gdk-pixbuf-2.0 pango pangocairo gio-2.0.17:30
loolRequires.private:.17:30
* rickspencer3 taps gavel17:30
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-06-1617:30
loolNew gdk-directfb-2.0.pc:17:30
rickspencer3asac: may I edit the wiki page?17:30
loolRequires: gdk-pixbuf-2.0 pango pangocairo gio-2.017:30
loolRequires.private: fontconfig cairo-directfb17:30
loolSo there'sa difference here17:30
rickspencer3ArneGoetje: asac bryce kenvandine pitti Riddell tkamppeter seb12817:31
rickspencer3ready?17:31
pittio/17:31
Riddellhi17:31
kenvandinehere17:32
asachi17:32
seb128sorry for that17:32
seb128I'm there17:32
bryceheya17:32
* asac will finish activity report in wiki after meeting then17:32
seb128I was testing the gtk upgrade ;-)17:32
rickspencer3asac: thanks17:32
asac(sorry)17:32
ArneGoetjehere17:32
rickspencer3asac: no apology necessary17:32
rickspencer3may I edit it now?17:32
ccheneyhi17:32
* rickspencer3 answers own question17:33
rickspencer3ccheney: hi!17:33
rickspencer3I was looking for calc :P17:33
tkamppeterhi17:33
ccheneyrickspencer3: ah yea i changed my nick so xchat alerts could be useful :)17:33
rickspencer3hi Till ( tkamppeter )17:33
rickspencer3ccheney: thanks!17:33
rickspencer3let's go17:33
ccheneyeg every reference to OOo calc in xchat alerted me, heh17:34
kenvandinehehe17:34
rickspencer3please note that I changed the meeting template17:34
rickspencer3I'm going to strive to provide a status summary to the world based on this meeting17:34
rickspencer3in terms of actions from last meeting, the only one is regarding bug assignement, and I would like to save that until a discussion near the end of the meeting17:35
rickspencer3so please review the wiki for the status of action items from last week17:35
rickspencer3so, Feature Definition Freeze17:35
rickspencer3pitti: any comments?17:36
pittiwell, my current review queue is zero, and you should all have mail with my whimsical comments17:36
pittisome of them are back to drafting and need some fine-tuning17:36
kenvandinepitti: humm... you should have my social from the start in your queue again17:36
pittikenvandine: no, it's not17:37
asacpitti: wifi is in your queue again ;)17:37
kenvandineoh... humm17:37
pittiasac: right17:37
pittiso, please try to get them at least into the first review round by Thursday17:37
* kenvandine didn't see a mail17:37
pittithere are some specs which didn't go to review once yet17:37
pittialso, please add work items to your blueprints by Thursday, so that we can start making http://piware.de/tmp/desktopteam-burndown-karmic.png actually useful17:38
pittisorry for its bad look, will tune by next week17:38
rickspencer3my expectation that the burndown chart generated on Friday morning will be useful for tracking17:39
rickspencer3so that gives you until eod Thursday to identify work items in your blue prints17:39
pittiso if you are ignoring blueprint mail and sent a spec to "pending approval", please check the status of your's on https://blueprints.launchpad.net/people/+me/+specs?role=drafter17:39
* rickspencer3 whip cracking noises17:39
rickspencer3:)17:39
pittifrom what I saw in the specs so far, Karmic will be a killer release!17:39
rickspencer3yeah!17:40
rickspencer3pitti: it sounds like you need:17:40
pittiso,17:40
rickspencer3(go ahead, sorry) :P17:40
pittiTODO: add work items by Thursday17:40
pittiTODO: finish spec drafting by THursday and set them to "pending approval"17:40
pitti[done]17:40
rickspencer3ok17:41
rickspencer3I would add that the specs should have gone through at least one good round of review by Thursday17:41
rickspencer3moving on ...17:41
pitti(mind that the original deadline was today..)17:42
rickspencer3right17:42
rickspencer3kenvandine ?17:42
rickspencer3partner status?17:42
kenvandineah17:42
kenvandinemy turn :)17:42
rickspencer3(thanks pitti :) )17:42
kenvandineI'll start with online services17:43
kenvandinehttps://wiki.ubuntu.com/UbuntuOne/DesktopIntegration/Status17:43
kenvandinethis is a wiki page listing features planned for ubuntuone in karmic17:43
kenvandinewith acceptance criteria, still a WIP17:43
rickspencer3these are tests that you are running?17:43
kenvandinethis should help us track how things are shaping up before feature freeze17:44
kenvandineyes17:44
kenvandinei expect OLS QA will run them as well17:44
kenvandinebut i will track it for us17:44
kenvandineubuntuone-client and it's deps are being prepared to go into main now as well17:45
kenvandinewell universe then MIRs for main17:45
kenvandinehopefully that will go smoothly17:45
pittinice17:45
kenvandineI want to start tracking the DX team work in a similar fashion17:45
pittikenvandine: how many of them have automatic tests? (especially for the sync daemon)17:45
kenvandinethey are doing 2 week iterations17:45
kenvandinepitti: they have unit tests17:45
kenvandinebut no functional tests that are automatic17:46
pittikenvandine: are there tests for 2 sync daemons talking to each other?17:46
pittiokay17:46
kenvandinethat feature isn't done yet :)17:46
rickspencer3pitti: is that important, should it be added to the acceptance criteria?17:46
pittiit seems to me that this shouldn't be too hard to set up with some shell scripts17:46
kenvandineif it is planned by karmic, it should17:46
kenvandinepitti: sort of...17:47
kenvandinethere are a few gotchas...17:47
kenvandinelike the keyring... etc17:47
pittirickspencer3: well, it'd certainly help to run the tests automatically on a daily basis and spot regressions that way17:47
pittikenvandine: yeah, the sandboxing certainly needs some work17:47
rickspencer3pitti: that makes sense, but I was referring to the 2 sync daemon scenario17:47
kenvandinei was thinking VMs17:47
pittikenvandine: not saying that it's easy, just that it would be great to have17:47
kenvandine:)17:47
kenvandinepitti: agreed17:48
rickspencer3well ... the first step of automation is often to define the tests17:48
kenvandinei will check to see if they have committed to the peer syncing by karmic17:48
pittikenvandine: I thought peer syncing was the first and major goal?17:48
kenvandinelast i heard it was something they wanted, but no timeline17:48
kenvandinepitti: not sure about that... i will confirm17:48
pittiIOW, if we take away file sharing, there's not much left, is there?17:49
rickspencer3ACTION kenvandine to define priority and timing of peer syncing, add to acceptance tests if necessary17:49
kenvandinepitti: well file sharing is there... but not peer to peer17:49
rickspencer3aah17:49
kenvandinelocal network stuff17:49
kenvandinepitti: that is what you are talking about right?17:49
pittikenvandine: right, thanks17:50
kenvandinei will confirm, but i don't think that was super high17:50
kenvandinethey want more features and the API done17:50
kenvandinemore services17:50
kenvandineafaik17:50
pittiso a test script would just use the real cloud17:50
kenvandineyes17:50
pittiwhich is still useful, the test suite could drive the web ui to check for success17:51
kenvandineok, DX team now... we are hoping to get them to use the burn downs17:51
kenvandinebut that is still in the works17:51
pittikenvandine: how's the general bug situation with u1, getting better?17:51
kenvandinebetter17:51
kenvandinegetting quieter :)17:52
kenvandinei plan to align the integration points for both the DX and OLS teams so they don't both hit us at the same time17:52
kenvandinedefine milestones based on that schedule17:52
kenvandineso hopefully we don't have both teams beating on my door on the same day to get stuff done17:53
kenvandinemore to come on that soon17:53
kenvandineone thing for us to think about right now, is fusa/gdm17:53
rickspencer3kenvandine: what is blocking the DXE team from using burndown charts? Can we help?17:53
kenvandinethey are working on the fusa changes for gdm now, and should have something in a ppa for us soon17:53
rickspencer3oh17:53
kenvandinerickspencer3: nothing as far as i know17:54
kenvandinejust doing it :)17:54
rickspencer3do we need to get new GDM into karmic asap for them?17:54
kenvandineno17:54
kenvandinewe need them to align, land the fusa changes at the same time17:54
rickspencer3ACTION: rickspencer3 to ask davidbarth if the DXE team needs help setting up burndown charts17:54
pittiwell, we need to get gdm-new working at all17:54
pittiand if it does, move it to karmic as well17:54
pittis/if/once/17:54
kenvandinepitti: it almost works :)17:54
rickspencer3this sounds like an unmet dependency17:55
kenvandinebut yes, it needs work still17:55
pittiindependently of the DX work we need to get it in ASAP17:55
rickspencer3the new GDM is triggering the FUSA work, right?17:55
kenvandineyes17:55
pittisince a lot of other things (artwork, boot speed, etc.) depend on this17:55
kenvandineit works well enough for them to do what they are doing17:55
kenvandinepitti: agreed17:55
kenvandineseb128: have you looked at that lately?17:55
seb128kenvandine: no17:56
kenvandineted should have fusa changes (proof of concept) code done the end of this week17:56
kenvandinewhich can be built into the ppa17:56
seb128good17:56
kenvandineand hopefully the end of the next 2 week iteration be ready for karmic17:56
kenvandineso we should plan to have gdm ready the same time17:56
rickspencer3seb128: will that align for you?17:57
kenvandinei installed it in a VM with karmic and it worked after a reboot, restarting the service didn't do it17:57
kenvandinebut it fails like ever 3 boots :/17:57
kenvandinewhich is weird17:57
seb128rickspencer3: yes, the new gdm is mostly ready, I still have an upgrade issue to debug but it's almost good to upload17:57
kenvandinei think both ted and kwwii is running it on jaunty17:57
seb128it's in the ubuntu-desktop karmic ppa now17:57
rickspencer3seb128: ack ... and thanks17:58
kenvandinei think that is all i have right now17:58
rickspencer3thanks kenvandine17:58
rickspencer3Riddell: Kubuntu?17:58
RiddellKubuntu Status17:58
RiddellAll specs approved17:58
RiddellWork items from specs are tracked here https://wiki.kubuntu.org/Kubuntu/Todo/Karmic17:58
RiddellKDE 4.3 Beta 2 is in and working well17:59
RiddellMain inclusion reviews needed for arora, kopete-facebook, qjson, enca17:59
RiddellBig win of the week is elite Kubuntu developer Roman Shtylman had his OpenOffice KDE 4 patches merged http://lists.freedesktop.org/archives/ooo-build/2009-June/000036.html  http://shtylman.com/stuff/oo/oo_new.png17:59
RiddellBig win two, elite Kubuntu developer Yuriy has made an Oxygen icons theme for OpenOffice  http://yktech.us/temp/oo-ox.png17:59
RiddellSome community handling needing done in one of our local team IRC rooms, am investigating it along with IRC council17:59
RiddellKubuntu-DE will be joining KDE and Amarok for a stall at Linux Tag next week17:59
RiddellElite Kubuntu developer rgreening is making good progress on the KDE port of USB Creator http://imagebin.ca/view/5E5mIe.html17:59
RiddellKDE apps Help->Report Bug now uses Apport and reports to Launchpad, hopefully our beastie triagers can forward upstream the ones which belong there17:59
Riddellend report :)17:59
rickspencer3Riddell: what's "community handling"?18:00
pittiRiddell: OOo KDE4> !!!18:00
Riddellrickspencer3: guy incharge of channel is removing admin rights any lying about it, I need to work out the right way to get him replaced18:01
rickspencer3also I have the urge to point burndown.py at your todo list :)18:01
rickspencer3too bad18:01
rickspencer3thanks for handling that18:01
Riddellccheney: do you have any time to look at the open office oxygen stuff?18:01
rickspencer3a good example of your steady leadership of the community and product18:02
Riddellrickspencer3: I put the work items: in the spec whiteboards too, although it would be nicer not to have to update two places18:02
ccheneyRiddell: not really until next week I used up my time already this week yesterday18:02
rickspencer3action: rickspencer3 to investigate slurping work item status from Kubuntu todo list18:02
ccheneyRiddell: it should be fairly straightforward (i hope) may take an hour or so to do due to patching the OOo source, etc18:02
Riddellccheney: next week is good.  but let me know if it won't happen for ages and I can try and look at it (although it'll take me longer than it would you presumably)18:02
rickspencer3don't forget that ccheney is only with us 20% time :)18:03
pittiRiddell: if every table line is one WI, I'm happy to teach workitems.py about parsing this one18:03
Riddellpitti: yes it is18:03
rickspencer3pitti: that might be good, because it would also create another option for people to track work items18:03
rickspencer3like other teams might want to copy Kubuntu, and the tools would be right there18:03
pittiseems straightforward then18:03
pittimake it an action item for me then18:04
rickspencer3ACTION: pitti to slurp work item status from Kubuntu todo list18:04
rickspencer3thanks Riddell18:04
Riddellpoke MIR team about those MIRs :)18:04
rickspencer3Riddell: may I suggest that you go ahead and look at that OOo stuff if you have the time, based on ccheney's limited bandwidth for us this release?18:04
rickspencer3ACTION: MIR team to consider themselves poked regarding Kubuntu MIRs18:05
rickspencer3:)18:05
asacRiddell: feel free to assign me a few18:05
Riddellwill do18:05
ccheneyRiddell: i can point out what you need to do to make it work18:05
rickspencer3Riddell: good job, Kubuntu seems off to another great start18:06
Riddellccheney: that would be useful18:06
rickspencer3move on?18:06
rickspencer3What was the outcome of the discussion on assigned bugs?18:06
seb128we all seem to agree on how to use assignment18:07
pittiit was by and large violent agreement18:07
kenvandine:)18:07
rickspencer3raging agreement works for me18:07
rickspencer3so does anyone need help *unassigning* bugs18:07
rickspencer3asac: >18:07
rickspencer3?18:07
pitti(that seems to be a very individual problem to me FWIW)18:08
rickspencer3ok18:08
rickspencer3it seems like if someone has a lot to unassign, it could be rather tedious18:08
rickspencer3so perhaps some teammates could lighten the load18:09
asacrickspencer3: atm i going through assignedbugs a bit day-by-day. we will see if i need help when i am done with the first round18:09
pittirickspencer3: I wouldn't want other people to mess with my bugs TBH18:09
rickspencer3pitti: ok18:09
rickspencer3thanks pitti and asac18:09
rickspencer3moving on ...18:09
rickspencer3here's a discussion topic ...18:10
rickspencer3Is there a single or small set of indicators that could communicate our status wrt to incoming and resolving bugs?18:10
pittiwe have those on a global ubuntu level from the QA team18:10
rickspencer3pitti: right18:10
pittisplitting it by team seems hard without actually triaging them all18:10
rickspencer3which are your referring to though?18:10
rickspencer3on launchpad?18:11
pittirickspencer3: resolving bugs should be possible18:11
bryceone approach could be to have a procmail script or whatever watching the incoming bug mail flow18:11
pittiwe could ask the QA team to do something like http://qa.ubuntu.com/reports/bug-fixing/jaunty-fixes-report.html for karmic, and split by team18:11
bryceboth NEW bugs, and bugs closed as invalid/fixed/etc. are marked in a machine readable way18:11
pittithat would work if we define a fixed subset of pacakges to be "ours"18:12
rickspencer3bryce: hmm18:12
pittibryce: QA team parses -changes@ for that list18:12
rickspencer3what I would like to see is a report on bugs on the product, not necessarily on the team members18:12
brycepitti: yeah same idea basically18:12
rickspencer3pitti: right, is the lack of that list the lynch pin in this whole thing?18:12
pittirickspencer3: list of desktop-ish packages?18:12
pittirickspencer3: well, we could derive it from the seeds18:13
rickspencer3pitti: yes18:13
rickspencer3ok18:13
pitti"desktop" seed minus platform seed18:13
rickspencer3pitti: would you have time to work on this with me this week or next?18:14
pittithat wouldn't handle bugs which are assigned to the wrong package (of which there are a lot)18:14
rickspencer3(and whoever wants to help)?18:14
rickspencer3hmmm18:14
rickspencer3do you think that noise would invalidate the reading>18:14
rickspencer3?18:14
pittirickspencer3: if it's urgent, yes; I have some other urgent tasks to do, though18:14
rickspencer3not urgent, but important18:14
pittirickspencer3: not invalidate, we should just allow a 20% error margin :)18:14
rickspencer3ok18:14
pittibut I don't know germinate very well myself18:15
pittiso we need to consult cjwatson anyway18:15
rickspencer3I think we should put this to bed for this week and focus on feature definition, but I'll bring it up again next week18:15
rickspencer3perhaps not in the meeting though18:15
rickspencer3anyone else, thoughts?18:15
pittibryce: you have X bug stats as well, don't you?18:15
asacwhat kind of metric are we trying to get here? all incoming bugs vs. all fixed bugs? that sounds like a game we cannot win18:16
pittiasac: fixing them all shouldn't be the goal18:16
brycepitti: yes that's right18:16
pittibryce: you have a fixed list of packages? or you simply count the ones you're a package contact for, and thus receive mail anyway?18:16
asacpitti: i dont say that fixing all is the goal. just want to understand what the goal is18:16
rickspencer3asac: what I want is a measure that provides us a sense of the overall current quality, as well as a leading indicator regarding the quality when we ship18:17
pittiasac: hm, incoming bug rate isn't very good for that18:17
pittierm, rickspencer3 ^18:17
cjhow do I tell Jaunty that it's running on a laptop instead of a desktop?  I want it to know to do the power-saving, lid-closing fu18:17
asaci dont think that bugs are a good measure of quality18:17
rickspencer3pitti: interesting that you say that, why not?18:17
pittiI daresay that jaunty's quality is far better than edgy's, and yet we get more bugs18:17
seb128well, measuring how much of those bugs are read is somewhat a good metric18:17
asacat least not _all_ bugs18:17
pittibecause bugs primarily correlate with #users, not #problems18:17
asacwe need to narrow those down to bugs we accepted to be something that should be in a metric like this18:18
bryceasac: for X I've found it useful to understand my rate of incoming vs. rate of closed and how they compare, because if the former is too much higher than the latter, or if there is a sharp change in rate, it serves as a signal something's wrong18:18
rickspencer3seb128: not sure what you mean18:18
rickspencer3bryce: good point, it's the incoming *rate* that you measure18:18
rickspencer3like by what percentage is the list growing18:18
pittibut for the rate to be useful, you need it on a per-package level?18:19
asacbryce: so you look for serious regressions through statistics ;)? thats a good idea, but it doesnt serve the goal to understand overall quality imo.18:19
pitti(and I believe we already have that)18:19
brycepitti: right, we take care to ensure ubuntu-x-swat is the package contact for all packages we consider to belong to X, so I can auto-snarf my package list from https://bugs.edge.launchpad.net/~ubuntu-x-swat/+packagebugs18:19
seb128rickspencer3: I mean that we should not aim at triaging all the bugs in a proper way but we should at least look at most of the bugs to pick up real issues and do metric on those18:20
asacrickspencer3: problem is that growth probably is related to growth in userbase ... which we dont really know any details on18:20
bryceasac: yeah I would definitely agree #bugs is a measure of popularity, not quality18:20
rickspencer3but that seems easy to understand18:21
pittifor spotting regressions, I liked the "3-day subscription after upload" better, I think18:21
rickspencer3the goal is not to provide a perfect measure, but a sense of the overall quality and trajectory18:21
brycequality is a bit harder to quantify...  one idea I've had is now that I'm tagging symptoms on bugs, to compare proportions of bugs with serious symptoms to ones with less serious ones.  If the proportions change, that is meaningful, separate from the overall quantity18:22
rickspencer3and I think measuring rate of growth attenuates the growing user base noise as well18:22
seb128well, we want a way to mark real issues we picked18:22
pittirickspencer3: hm, I still think that the scaling by users and hardware far outweighs the change of "quality" in the sense of how many bugs we fix and introduce18:22
seb128and measure how good we are doing on those18:22
rickspencer3seb128: I agree18:22
rickspencer3perhaps measuring *confirmed* bugs would be better than *new*18:23
seb128I tend to measure desktop quality by number of milestoned bugs18:23
pittimeasuring #regressions would be useful, though18:23
rickspencer3I know it's *hard* to quantify, but that doesn't mean we should shy away from it18:23
brycerickspencer3: agreed18:23
rickspencer3incoming regressions would be a good measure18:23
seb128ie when we managed to scatch most of the milestoned desktop bugs that's a good sign18:23
rickspencer3hmm18:23
rickspencer3incoming milestoned bugs, interesting thought18:24
rickspencer3and easy to query for18:24
asacyes. please lets not try to do course grained overall stats. QA team should do those if they theink its important18:24
asacrather look at things that get pushed on our plate, like milestones, team assignments18:24
asacetc.18:24
pittiwe could perhaps get some graphs on http://qa.ubuntu.com/reports/regression/regression_tracker.html18:24
rickspencer3asac: hmmm18:24
seb128I tend to use milestones as a todo for the cycle, ie milestone all the desktop bugs I would like to get fixed for karmic18:24
seb128and watch this list18:24
rickspencer3not sure I agree18:24
rickspencer3again, I am interested in understanding the *product* not just the team workload18:25
rickspencer3asac: ^^18:25
asacrickspencer3: what product in particular?18:25
asacdesktop-cd?18:25
seb128well then we need a standard way to mark that a bug affect the product quality18:25
rickspencer3bryce: do you think incoming versus resolved regressions would provide a meaningful indicator?18:25
asacor ubuntu18:25
seb128and to track the list of those issues18:25
bryceasac: Ubuntu I gather18:25
rickspencer3asac: desktop-cd more or less18:25
pittiI'm just not sure whether it makes sense to do some "desktop" subset here18:25
rickspencer3pitti: not "desktop team" if that's what you mean18:26
seb128pitti: well that's the issues our team has to work on?18:26
rickspencer3but I think "server" and "unr" are probably seperable18:26
asaci still have the feeling its a Qa team topic18:26
brycerickspencer3: incoming vs. resolved would be a meaningful indicator.  (For X, most bugs would classify as 'regressions')18:26
pittibut foundations/kernel are affecting us as well18:26
pittiQA team topic> *nod*, at least we should include them in the discsussion18:26
asacof course we can provide suggestions and ideas and request certain things.18:27
seb128I think it's good to know where we stand18:27
ccheneyOOo is on target to surpass evolution as the most upstream bugs by karmic release, it seems latelely almost all of the bugs filed are legitimate though maybe not of high enough importance to fully triage (?)18:27
* ccheney isn't clear on what level of bug triage he should be doing (outside of the 20% issue at present)18:28
brycerickspencer3: I'm a big believer that "you can't boil everything down to a single metric, without it risking being gamed".  I suggest gathering several different metrics, see what's useful, and use them to calibrate or correlate.  If quality is going up, then several different metrics should all show the same thing.18:28
brycealso, once you have a tool to gather/graph/etc. one metric, you can adapt and reuse the tool for another metric without too much trouble.18:28
rickspencer3I propose that close down this discussion now ...18:28
pitticcheney: if you watch out for major regressions, that should be enough IMHO18:29
bryceoh, sorry18:29
rickspencer3but I feel that I can make some good progress in thinking about it given this feedback18:29
* ccheney takes it offline18:29
rickspencer3bryce: that wasn't directed at you18:29
rickspencer3keep going, I'm sorry, I sensed it was drawing to a close (obviously wrong)18:29
rickspencer3now it's all socially awkward18:30
rickspencer3way to ruin the party rickspencer318:30
rickspencer3:P18:30
seb128lol18:30
brycerickspencer3: only last point, is I suggest using metrics only for our own education, not for measuring our individual performance, else we'll end up gaming it.18:30
asaci think we all need to think a bit and maybe do some after meeting discussions on this. its really a complex task to find metrics for quality ;)18:30
rickspencer3bryce: obsolutely18:31
rickspencer3very well put18:31
rickspencer3asac: agreed18:31
pittior even define what we understand as "quality"18:31
asacright18:31
rickspencer3bryce: even if we don't game it, it just wouldn't be meaningful18:31
seb128pitti: well, "quality" is pretty clear, it define how well user will react to the new version18:32
rickspencer3hey all18:32
brycedon't forget we can also look *outside* launchpad for measurable indicators of quality18:32
rickspencer3bryce: ?18:32
seb128the topic seems controversial for some reason18:32
seb128but it seems something clearly defined to me18:33
pittiseb128: hm, "how well user reacts" is not really quantifyable either :)18:33
rickspencer3I'd like to give tkamppeter a moment to give us an update on printing18:33
tkamppeterFor the printing all looks nice. After getting a lot of complaints caused by the bad PostScript which the Ghostscript-based pdftops filter has produced, I fixed the upstream bugs in Poppler and switched back to Poppler. This fixed everything.18:33
rickspencer3tkamppeter: this is in Jaunty?18:34
tkamppeterI have also considered this as a Jaunty SRU and discussed it by e-mail. I will prepare the SRU in the next days.18:34
rickspencer3ok18:35
rickspencer3last topic, I'll just make it an announcement so that you can all go enjoy your dinners and all ...18:35
tkamppeterI get only positive answers and if someone still complained his problem was something else.18:35
rickspencer3I've been pestering people about quickly in an ad hoc manner ...18:35
pitti*nod*, I'm confident enough now to have this SRUed18:36
pittirickspencer3: (JFYI, I also have two topics, one of which was in my mail)18:36
rickspencer3pitti: ok18:36
tkamppeterpitti, do you mean me?18:36
rickspencer3tkamppeter: thanks for the update18:36
rickspencer3moving on to a quick announce, then to pitti for two items18:37
pittitkamppeter: right, I meant we should do this as a jaunty SRU and let it sit in -proposed for two weeks or so18:37
rickspencer3I'll set up a regularly time for discussing quickly, if any one is interested, let me know (I'll move this to the mail list)18:37
rickspencer3phew18:37
rickspencer3pitti18:37
rickspencer3?18:37
pittiso, thing 1:18:37
pittihttps://merges.ubuntu.com/main.html18:37
didrocks(rickspencer3: before / after the spec approval? sorry pitti)18:38
pittiplease have a look at which packages still need to be merged18:38
pittiand tell me if you need help with your merges18:38
pittitkamppeter: ^ you have a fair bunch as well18:38
* asac notes ifupdown18:38
pittithing 2:18:38
pittilast week I reviewed the telepathy/empathy MIR bugs18:39
pittithey are all okay now, except for bug 38467718:39
ubottuLaunchpad bug 384677 in telepathy-gabble "telepathy-gabble main inclusion" [Undecided,Incomplete] https://launchpad.net/bugs/38467718:39
pittiit says "will maintain itself", but if we want to make empathy real in karmic, this needs some dedicated maintainership18:39
pittiaudio/video are horribly broken, and it's very crashy18:40
pittiso I wanted to ask whether someone can adopt this -- kenvandine/seb128/robert_ancell?18:40
seb128pitti: we have cassidy and Zdra from upstream around18:40
seb128and there is a bug day planned for empathy already18:41
seb128pedro is looking at those bugs18:41
kenvandineyup18:41
seb128and debian get the new versions18:41
pittiah, so we should feel encouraged to file bugs like mad then?18:41
kenvandinepitti: yes18:41
seb128what else do you want to get added?18:41
kenvandineplease :)18:41
pittiokay, good18:41
pittithanks, fine for me18:41
seb128ok good18:41
kenvandinegreat18:41
pittithen I propose we'll switch over karmic this week18:41
rickspencer3!18:41
kenvandine:-D18:41
kenvandinewoot18:41
seb128I will look at those bugs every now and then as I'm doing for pidgin18:41
asacgreat18:42
pitti[done]18:42
seb128but I don't have the bandwith to take over extra components ;-)18:42
asacso pidgin off CD?18:42
kenvandinei am trying to get my MI patch merged upstream18:42
asac;)18:42
kenvandineplan to finish their requirements by tomorrow18:42
pittiasac: ish; libpurple sucks in pidgin-data, which needs to be fixed18:42
kenvandineasac: yup18:42
ccheneyis there a way to pull history (logs) from pidgin into empathy?18:42
pittiwastes 1 MB CD space18:42
asacpitti: yeah saw that bug.18:42
jcastroccheney: I am looking into that (would be nice)18:42
ccheneyjcastro: ok18:42
kenvandineccheney: not yet... but i think jorge was going to file a bug18:42
awepitti:18:43
asac(rather discussion fwiw)18:43
pittirickspencer3: back to you18:43
rickspencer3pitti: thanks18:43
rickspencer3sorry, I didn't see your mail, or I would have put your items earlier in the agenda18:43
pittirickspencer3: please note down merges as action item18:43
rickspencer3my had18:43
rickspencer3any other business?18:44
seb128I just want to point http://people.ubuntu.com/~seb128/versions.html18:44
pittinote that merges need to be finished by June 25th18:44
seb128it's working now but not regularly updated yet18:44
seb128code on ~ubuntu-desktop/+junk/versions18:44
pitticool18:44
rickspencer3ACTION: tkamppeter to review merges18:44
pittiseb128: now we need a "sync" and a "do merge" button :)18:44
rickspencer3ACTION: asac to review ifupdown merge18:44
pittirickspencer3: s/tkamppeter/everyone/18:45
seb128pitti: right, coming next18:45
seb128patches are welcome ;-)18:45
ccheneyi'm uploading a new OOo later today that will have rosetta enabled for export, then later OOo-l10n using rosetta data once i verify it works on that side as well18:45
pittiseb128: sync-source.py -a -f -F, let's go home18:45
seb128hehe18:46
rickspencer3ACTION: Everyone to review merges and ask for help if needed18:46
seb128action: getting dinner? ;-)18:46
rickspencer3ACTION seb128 to fix dinner18:46
pittimmmm dinner18:46
* rickspencer3 taps gavel18:47
kenvandinehehe18:47
rickspencer3thanks all!18:47
brycethanks18:47
pittithanks everyone18:47
seb128thanks rickspencer318:47
awesee ya18:47
ArneGoetjethanks18:47
ccheneythanks18:47
asacthx18:47
brycerickspencer3: btw, upstream has changed how ctrl-alt-backspace works again.  :-P18:47
rickspencer3bryce: lol18:47
pittibryce: !18:47
rickspencer3what does it do now?18:47
brycenow it's configurable18:47
jcastrohah18:47
jcastroawesome18:47
pittibryce: wasn't it configurable before, too?18:47
bryceer, configurable during runtime18:47
tkamppeterthanks.18:48
rickspencer3thanks tkamppeter18:48
pittibryce: ctrl+alt+backspace changes the setting? :-)18:48
jcastrois it alt-sysrq-k-ctrl-alt-backspace? That would be so great.18:48
rickspencer3lol18:48
brycejcastro: :-)18:48
rickspencer3didrocks: still around?18:48
didrocksrickspencer3: of course :)18:48
rickspencer3kenvandine: quickly?18:48
kenvandine?18:48
rickspencer3I was thinking that we should start a quickly mailing list, and perhaps set a regular discussion time18:49
rickspencer3thoughts?18:49
kenvandineyes!18:49
didrocksyes, it will be lot easier!18:49
rickspencer3lool: ^^^18:49
kenvandinepitti: i really hope the gwibber spec is good now :)18:49
pittiNB that launchpad projects support MLs now18:49
rickspencer3pitti: sweet18:49
rickspencer3pitti: interested?18:49
jcastrorickspencer3: appply for a list now and I can approve it18:49
rickspencer3jcastro: I'll try, hold on18:50
kenvandineoh know... jcastro has that kind of power?18:50
kenvandines/know/no18:50
jcastro\o/18:50
rickspencer3jcastro: done18:50
rickspencer3jcastro: thanks18:50
rickspencer3didrocks: kenvandine: shall we use that list to discuss a regular time?18:51
kenvandinegreat first post :)18:51
rickspencer3sweet18:51
rickspencer3enough said18:51
* kenvandine wonders why his laptop is dog slow suddenlhy18:51
rickspencer3jcastro: why aren't you on the quickly team?18:51
didrocksrickspencer3: on fundamentals idea, yes (like, do we want quickly to creat project), but a regular meeting is great too :)18:51
rickspencer3kenvandine: because one of your torrent trackers just picked up like 10 seeders?18:52
jcastrorickspencer3: dunno, I will apply. (list done)18:52
kenvandineoh... of course.. .pidgin is making my box swap18:52
kenvandinehehe18:52
rickspencer3ok18:52
rickspencer3great!18:52
kenvandinepidgin with like 30 channels on irc... not so good18:52
rickspencer3thanks didrocks, sorry you hung around for nothing :(18:53
didrocksjcastro: approved18:53
didrocksrickspencer3: no pb. I think I will try to follow desktop team meeting when I have the time :)18:53
rickspencer3didrocks: that would be great18:54
didrocksrickspencer3: will you answer to pitti's concern on the spec?18:54
didrocksI have not a clear idea on everything (like project creation/interaction between quickly and launchpad we want), to be honest :)18:54
* kenvandine had to reboot to get the load down :/19:02
pmatulisis it possible to configure the Panel (add icons) and have that config applied to all system users?19:25
chrisccoulsonpmautils - i think thats difficult if users already changed their panel config19:26
chrisccoulsonbecause they will have custom gconf settings19:26
chrisccoulsoni might be wrong though.19:26
didrockschrisccoulson: you can set some of them as mandatory19:27
didrocksso, user can't override your configuration19:27
ccheneykenvandine: i ended up using bip with xchat and irssi, xchat just for alerts and irssi for actual irc usage19:28
chrisccoulsonit depends what you're trying to achieve really. if you just want to change the default config and have that flow through to existing users, then i think its pretty difficult19:28
ccheneykenvandine: it seems to work much better than attempting to use pidgin for real irc19:28
didrockspmatulis: http://library.gnome.org/admin/system-admin-guide/stable/ is your friend :)19:28
ccheneykenvandine: real irc imho being more than 1-2 channels19:28
didrockschrisccoulson: yes, for existing user, I don't know how it handles if you change afterwards19:28
kenvandineccheney: agreed19:29
kenvandinepidgin is killing me19:29
chrisccoulsondidrocks - there are some hacks in our gnome-panel package for handling things like that, eg FUSA migration and indicator-applet migration19:29
chrisccoulsonwhich reminds me - i must finish this gnome-panel package this evening19:29
didrockschrisccoulson: :)19:29
ccheneykenvandine: note that if you do end up using bip with xchat and irssi you may want to get the new bip from karmic as it has a bugfix for that usecase19:29
ccheneykenvandine: otherwise it prepends weird + and - signs before everyones comments19:30
pmatulischrisccoulson: this is in the context of a locked down environment19:30
chrisccoulsonah, ok - then what didrocks suggested will be most interesting to you19:30
pmatulischrisccoulson: i want to force those icons on all users19:31
pmatulisand then lock the panel19:31
pmatulisi've gone through that resource, but there is nothing that forces the panel "config" on all users, it's always user-based to my understanding19:32
pmatulisyou can force the panel to be locked for everyone however19:32
pmatulisunless i try to alter the *default* config19:34
didrockspmatulis: did you have a look at that, for locking and setting system-wide: http://library.gnome.org/users/gconf-editor/stable/defaults-mandatory.html.en?19:37
pmatulisdidrocks: yes, but not in the context of trying to alter the default panel config19:38
pmatulisdidrocks: would you happen to know which key provides that?19:39
didrockspmatulis: I never tried that, but you tell that if you change an icon place on the panel, the gconf key differs, and you can't put it as mandatory (so locked?)19:39
pmatulisnot sure i follow19:40
didrockspmatulis: IIRC, when you change something on the pannel, some gconf key are created/changed19:41
pmatulisyes19:41
didrocksso, if you change them system-wide, in /etc/gnome19:41
didrocksand then put them as mandatory to avoid people changing them in their ~19:42
didrocksyou should get what you want19:42
pmatulisright19:44
pmatulisnow i'm trying to hunt down what needs to be changed19:44
pmatulisit's not a single key, keys have to be removed and other added19:45
pmatulisexample: /apps/panel/default_setup/objects/email_launcher19:45
pittikenvandine: so you want to keep tightly integrating gwibber accounts into gnome-about-me?19:51
kenvandinei think so, and there is some unrelated talk about adding things like gmail setup to about me19:55
kenvandineseems to be the most natural fit19:55
kenvandinethe goal is to disconnect the "being social" from using gwibber19:56
pittikenvandine: well, the integration could be much more loose by just adding a "Configure social networks..." button there, which starts gwibber's wizard19:56
kenvandinelike fusa will interacte with it19:56
kenvandineetc19:56
pittikenvandine: did you talk to g-c-c upstream about this?19:56
kenvandinepitti: yeah, but that feels a little disconnected19:56
pittithis will be a pretty heavy patch19:56
kenvandineyes19:56
kenvandinerodrigo_  might even do the work... or dobey19:56
kenvandine:)19:57
pittiokay19:57
pittigood, approved then19:58
pittigood night everyone20:00
pittiI might do some hacking tonight, but off IRC20:00
=== rickspencer3 is now known as rickspencer3-afk
didrockspitti: good night!20:04
kenvandine:)20:06
kenvandinegood night pitti, thx20:06
ccheneyi am having trouble with jaunty on my desktop system whenever i try to go to a window titlebar (i think that is the correct term?) it turns the cursor into a hand instead of an arrow20:14
ccheneyand i can't drag windows around20:14
ccheneyanyone seen an issue like that before?20:15
ccheneyit seems i can sometimes cause it to show as a insert cursor, but it won't show up as an arrow regardless20:15
ccheneyit thinking i have a stuck key wouldn't cause that would it?20:16
* ccheney isn't sure how to debug this issue20:16
kenvandineccheney: no clue20:16
* ccheney wonders wtf is wrong with his desktop system, its pretty much unusable with whatever is going on20:25
ccheneyi'm pretty sure a stuck key couldn't cause this problem20:25
ccheneybryce: ping20:26
ccheneywhatever is happening also isn't consistent i logged out and back in and its working for the moment, but it seems to keep recurring20:27
bryceccheney: yep?20:35
ccheneybryce: have you heard any reports about mouse getting stuck in weird state20:35
brycenot like you've described exactly20:35
ccheneybryce: on jaunty for some reason my mouse seems to get stuck thinking it is in eg text selection mode from gnome-terminal, etc20:36
bryceccheney: have you ruled out that it's the window manager? if you use compiz, try metacity; if not then vice versa20:36
ccheneyi'm using metacity, it doesn't happen every time and i'm not doing anything special so i am not sure what is causing it20:36
bryceccheney: can you identify when that started happening, and pin it to a particular update in /var/log/dpkg.log?20:37
ccheneynot really sure how to track down what actually is causing it20:37
ccheneyit started happening a month or so ago, i may just need to reinstall jaunty and try to track it down that way20:37
ccheneyi don't use my desktop machine directly that much, mostly through ssh so i don't know more specific than that :-\20:37
bryceccheney: video driver?20:38
ccheneynv20:38
brycehmm20:38
bryceccheney: single-head or dual-head?20:38
ccheneybryce: single-head20:39
brycehmm, ok so that rules out most of my guesses :-)20:39
ccheneyi seem to see it most often when moving around gnome-terminal window it normally goes from the text selection to hyperlink hand to arrow depending on what you hover over, but it seems to get stuck at times and then even going entirely out of the gnome-terminal area doesn't help restore it to normal behavior20:40
brycewell, the way this stuff works is that the client applications request cursor state changes through libx11 (usually via a gtk lib wrapper), which puts in the request to the xserver20:43
ccheneyso when leaving a window metacity should be telling it to change (i guess?)20:44
brycethere's a particular chunk of code in the xserver which handles cursors, separate from most of the other code (which is why when X freezes the mouse cursor still moves)20:44
bryceccheney: yeah either the window manager or the client application make the requests20:44
ccheneybryce: ok20:45
bryceit's conceivable it's a gnome-terminal bug.  from what you describe it sounds like it might be trying to do something special with it20:46
ccheneyok20:46
bryceanother option is gtk, if it affects multiple gnome apps20:46
ccheneyyea20:46
=== ember_ is now known as ember
bryceunfortunately on -nv I doubt compiz will be an option, but if it is, that could help identify whether it's a window manager issue or not.  But maybe just experimenting with gnome-terminal and other apps would be easier.20:47
brycee.g., like try running xterm or a different terminal program for a while20:48
ccheneyi could try running nvidia to see if the issue goes away from the xserver side i suppose20:49
bryceif you want to get really hard core, there are some x protocol trace tools (xtrace, xmon, xscope) which will tell you exactly what protocol commands are going through20:49
ccheneyok20:49
brycebut probably not useful until after you can reliably reproduce it20:49
ccheneyyea20:49
bryceanother angle would be to test older versions (like you said, reinstall jaunty, and upgrade piece by piece)20:50
bryceI'd probably take a good look at the gnome-terminal changelog to see if they added/modified any cursor-related code recently, in which case that'd become quite suspicious20:50
ccheneyok20:50
ccheneyhmm the last entry i see in changelog for gnome-terminal is mar 19, which was quite a while before even jaunty release20:51
bryceanyway, let me know how it goes; I could probably throw a lot more ideas on how to debug it further, esp. if it starts looking like it really is an X bug20:51
ccheneyhmm are we not getting the gnome .1 release in jaunty this time?20:53
chrisccoulsonccheney - i think the .1 release of gnome-terminal was considered for SRU but rejected, as the changes didn't meet SRU requirements21:08
ccheneyoh21:08
chrisccoulson2.26.1 changes the behaviour of the state saving code for example21:08
ccheneyok21:08
ccheneyhmm yea after looking on lp in the past it seems the .1 release came out early enough to go in the official releast (without updates)21:09
chrisccoulsoni think it was released in the two weeks prior to release, so everything was pretty much frozen21:10
ccheneyok21:11
=== ember_ is now known as ember
rodrigo_kenvandine: around?22:27
kenvandinerodrigo_: yup22:28
kenvandinerodrigo_: what's up?22:28
rodrigo_kenvandine: I added the 2 blueprints I told you about: https://blueprints.launchpad.net/ubuntu/+spec/couchdb-glib-package-for-karmic and https://blueprints.launchpad.net/ubuntu/+spec/evolution-couchdb-package-for-karmic , could you review them please?22:29
kenvandinesure!22:29
rodrigo_thanks :)22:29
kenvandineis tomorrow morning ok?22:29
kenvandinei might get to it tonight22:29
kenvandinebut can't promise :)22:29
kenvandineoh... you need the wiki pages too22:30
kenvandine:)22:30
kenvandine                                  Set the URL for this specification22:30
kenvandinecreate a wiki page with the actually implementation spec22:30
kenvandinehttps://wiki.ubuntu.com/DesktopTeam/Specs/Karmic/SymptomBasedBugReporting22:32
kenvandineas an example22:32
kenvandinehttps://blueprints.launchpad.net/ubuntu/+spec/desktop-karmic-symptom-based-bug-reporting22:32
kenvandinerodrigo_: ^^22:32
rodrigo_kenvandine: yes, will do that, and morning is ok :)22:33
kenvandineok22:33
kenvandinethx22:33
ftahm, libgtk2.0-dev broken22:40
fta /usr/lib/pkgconfig/gdk-2.0.pc not totally substituted22:40
fta$ pkg-config --cflags --libs gtk+-2.022:40
ftaPackage @GDK_PRIVATE_PACKAGES@ was not found in the pkg-config search path.22:40
ftaPerhaps you should add the directory containing `@GDK_PRIVATE_PACKAGES@.pc'22:40
fta...22:40
asaclool: ^^22:47
asachmm. seems seb did the upload22:48
=== ember_ is now known as ember
rodrigo_kenvandine: ok, done an initial version, will review it tomorrow morning, so review it whenever you want23:04
=== rickspencer3-afk is now known as rickspencer3

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!