[00:13]  * TheMuso hasn't upgraded, so not experiencing it.
[00:13] <TheMuso> RAOF: Do you use pulse much/listen to audio much in maverick?
[00:14] <RAOF> A certain amount.
[00:14] <RAOF> I still haven't got around to setting up my stereo system after moving, so I don't yet do the more fancy stream-over-wifi that I did in Sydney.
[00:17] <RAOF> Apart from volume being muted each time I start my session, everything seems to be working.
[00:26] <TheMuso> RAOF: Oh thank you. thats what I was goign to ask about.
[00:26] <TheMuso> RAOF: I get that too, and I have a theory about that, which I am not sure how to test.
[00:26] <RAOF> What's the theory?
[00:27] <TheMuso> RAOF: But I can tell you if you were to kill pulse running as your user before you restarted, your data would be saved and your next session would have sound.
[00:27] <TheMuso> Basically, when you restart, pulse gets a SIGINT/SIGTERM, and starts to save its data, but it gets hit with a SIGKILL before it finishes what it needs to do.
[00:27] <TheMuso> This is not an ALSA problem, and as I siad, if you kill pulse before restarting, the data is saved properly.
[00:28] <TheMuso> gah typing
[00:29] <RAOF> Heh.  Took me a couple of passes to spot the mistake :)
[00:29] <RAOF> Would you like me to confirm that behaviour for you?
[00:30] <TheMuso> RAOF: If you don't mind. Firstly confirm that you kill pulse and your volume data is saved properly first I think
[00:30] <TheMuso> RAOF: I have a bug number, let me dig it up.
[00:31] <RAOF> I'll do it when I restart for updates.
[00:31] <TheMuso> ok cool thanks.
[00:32] <TheMuso> RAOF: bug 592016
[00:32] <ubot2> Launchpad bug 592016 in pulseaudio (Ubuntu) "[Maverick] Sound is always muted on startup; unmuting makes the volume at lowest level (affects: 11) (dups: 1) (heat: 104)" [Undecided,Confirmed] https://launchpad.net/bugs/592016
[00:47] <TheMuso> Hrm no nvidia driver updates yet, so I have to either wait, or switch back to Nouveau.
[00:48] <RAOF> tselliot was working on an upload last night; it looked like he'd got all his ducks in a row, but it hasn't been uploaded yet.
[00:51] <TheMuso> np
[01:04]  * RAOF looks forward to blowing away this btrfs and replacing it with ext4 tonight, so that updates don't kill performance for quite so long.
[01:04] <TheMuso> heh
[01:09] <chrisccoulson> i'm seriously disappointed. i updated my laptop today, and despite the warnings, X still works!
[01:09] <chrisccoulson> i was expecting it to break!
[01:14] <RAOF> chrisccoulson: You waited too long.  If you'd done it 24 hours earlier there would have been a period when apt-get would want to remove xorg, ubuntu-desktop, that sort of thing :)
[01:15] <chrisccoulson> RAOF - ah, i shouldn't have waited then ;)
[01:15]  * micahg feels better for not upgrading till after X 1.9 transition :)
[01:31] <TheMuso> Where does one's personal gstetings data get stored, i.e in which subdir of the home dir?
[01:37] <TheMuso> gsettings even
[01:38] <lifeless> .config ?
[01:40] <TheMuso> Looked there, but nothing looks obviously gsettings-ish.
[01:41] <RAOF> Do we have anything that's using gsettings?  Presumably the answer is yes.
[01:42] <RAOF> My guess would be ~/.config/dconf
[01:42] <TheMuso> empathy does
[01:42] <RAOF> That certainly contains a binary blob called “user”
[01:44] <TheMuso> RAOF: nothing there with that name. I just changed some settings in empathy and closed it.
[01:54] <RAOF> TheMuso: Any idea why I appear to have two separate pulseaudio processes running?
[01:54] <TheMuso> RAOF: One for gdm?
[01:54] <RAOF> I'm not running gdm.
[01:54] <RAOF> Both are running as my user.
[01:54] <TheMuso> whaa
[01:54] <TheMuso> No idea.
[01:55] <TheMuso> RAOF: how are you checking?
[01:55] <RAOF> htop.
[01:55] <RAOF> There are two separate pulseaudio processes, with distinct PIDs and distinct nice values.
[01:56] <TheMuso> Are they both pulseaudio, or is one pulseaudio-gconf-helper?
[01:56] <TheMuso> i.e I have one pulseaudio, and run gconf-helper which is part of pulse.
[01:56] <TheMuso> Oh and seems gsettings is currently usig the memory backend.
[01:56] <Chipaca> has there been a regression that would make gnome keyring throw ioerrors again?
[01:57] <Chipaca> we're seeing that and are wondering about it :(
[01:57] <Chipaca> nessita: I know! let's switch to kwallet
[01:58] <RAOF> No, they're both listed as /usr/bin/pulseaudio --start --log-target=syslog
[01:58] <TheMuso> RAOF: no idea then.
[01:59] <RAOF> It could well be an artefact of the way I've worked around not being able to login via gdm.
[01:59] <TheMuso> possibly.
[02:05] <Sarvatt> RAOF: press H
[02:05] <RAOF> Sarvatt: To make gdm work?
[02:06] <Sarvatt> to make it hide the other pulseaudio thread :)
[02:07] <RAOF> Oh, no.  It's not a separate thread.
[02:08] <RAOF> (I can see the two separate threads of one of the processes separately)
[02:08] <Sarvatt> TheMuso: the nvidia-current thats going in maverick is in https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates it requires adding Option "IgnoreABI" "True" to the serverflags section in xorg.conf though to work with xserver 1.9 :(
[02:09] <Sarvatt> but at least it works!
[02:10] <TheMuso> Yay. Failed upgrade due to libgirepository breakage/override issues.
[02:10]  * TheMuso updates his mirror
[02:11] <Sarvatt> its fixed on any mirror? been broken all day here
[02:11] <RAOF> Yeah, still broken here.
[02:12] <RAOF> Well, unless it got fixed in the hour between me starting the update and the update actually finishing.
[02:12] <Sarvatt> slightly less here now than before, only wants to remove epiphany-browser gnome-games libgirepository1.0-0 libseed0 lightsoff seed swell-foop
[02:13] <Sarvatt> it was epiphany-browser gnome-games libgirepository1.0-0 libmutter-private0 libseed0 lightsoff mutter netbook-launcher seed swell-foop ubuntu-netbook unity before
[02:13] <TheMuso> heh
[02:17] <RAOF> Oh, it didn't try to remove unity for me.
[02:17] <Sarvatt> guessing that was just because of mutter
[02:17]  * ajmitch didn't have any problems after upgrading python-gobject
[02:18] <ajmitch> but it's not like I have much installed beyond the default desktop packages
[02:18] <Sarvatt> python-gobject wants to remove all of that too
[02:19] <ajmitch> perhaps a few other things depend on libgirepository1.0-0, as it was removed & replaced with libgirepository1.0-1 for me
[02:19] <RAOF> Alright.  Let's play “kill pulseaudio before restarting”
[02:19] <TheMuso> Yeah. My problem is that both those packages own the same file, but obviously there is no conflicts/replaces etc to resolve that.
[02:19] <TheMuso> Or is there...
[02:20] <ajmitch> there's an exact match on 0.9.3-0ubuntu1
[02:20] <TheMuso> Hrm there is conflicts/replaces.
[02:20] <ajmitch> so if you had an earlier libgirepository1.0-0 installed, it won't conflict/replace
[02:21] <TheMuso> Right
[02:21] <TheMuso> That may be it
[02:21] <ajmitch> most likely, should be an easy fix
[02:22] <ajmitch> and then the others (mutter, epiphany-browser) get to be rebuilt, yay
[04:31] <TheMuso> Is it known that dconf and dconf editor from dconf-tools crash horribly?
[05:10] <robert_ancell> TheMuso, dconf problems?
[05:38] <ajmitch> robert_ancell: to fix up gir-repository, is it as simple as changing the 1.0 references to 1.1 in the .gir files?
[05:38] <ajmitch> it's somewhat broken
[05:53] <TheMuso> robert_ancell: Trying to have a play with dconf/dconf-editor from dconf-tools and they crash. Not a biggy atm, just wanted a peak.
[06:16] <robert_ancell> ajmitch, yes, I've uploaded that change
[06:16] <robert_ancell> TheMuso, they work for me, are you fully upgraded?
[06:16] <robert_ancell> ajmitch, (the same change was made in gir-repository git)
[06:24] <TheMuso> robert_ancell: Should be, as I said its no real bother atm.
[06:25] <robert_ancell> TheMuso, that's weird though.  what sort of errors are you getting?
[06:25] <robert_ancell> TheMuso, if you run gcalctool, change the mode, and then restart does the mode stay the same?
[06:26] <TheMuso> robert_ancell: I am talking about the dconf and dconf-editor binaries from gconf-tools.
[06:26] <TheMuso> s/gconf-tools/dconf-tools/
[06:27] <robert_ancell> TheMuso, yes, is dconf working otherwise?
[06:28] <TheMuso> robert_ancell: Yes, empathy seems to be fine with it.
[07:01] <ajmitch> robert_ancell: sorry for bothering, I'm obviously too slow :)
[07:02] <robert_ancell> ajmitch, np
[07:02] <robert_ancell> :)
[07:38] <didrocks> good morning
[08:10] <robert_ancell> didrocks, hey
[08:10] <didrocks> hey robert_ancell :)
[08:10] <robert_ancell> didrocks,  is mutter working well for you now? sorry about that
[08:11] <didrocks> robert_ancell: can't test right now. I think it should. I'll have a proper test later. no worry ;)
[08:12] <robert_ancell> didrocks, If I don't see seb128 before he starts, can you remind him to look at the libgirepository package he made - the two versions contain the same files
[08:12] <didrocks> robert_ancell: sure, I will
[08:24] <didrocks> RAOF: I see that a lot of people are complaining about the new X server and nvidia proprietary driver, known issue?
[08:25] <RAOF> didrocks: Yeah; tselliot's got a new nvidia proprietary driver (at some advanced stage of) ready, which works against the new X server.
[08:25] <didrocks> RAOF: there is no Break: against the old one? (the one not compatible with the new X server?)
[08:26] <didrocks> RAOF: or are all people not reading the "partial upgrgade" thing?
[08:26] <RAOF> The old one should be Depend-ing on something that the new X server doesn't provide.
[08:27] <RAOF> We've been propagating  some changes in the way Debian handles the dependencies, the goal of which is to make it easier for apt to upgrade in situations where there's a valid solution.
[08:28] <didrocks> RAOF: hum, I can upgrade my X server there without any nvidia update… So, the provides: doesn't seem to work :/
[08:28] <RAOF> It used to offer the “solution” of removing all of X more frequently than it should be.
[08:28] <didrocks> yes, but if I can upgrade normally and break my machine there… ;)
[08:29] <didrocks> can I check something to see what's not going well and why it doesn't wait for the new driver?
[08:30] <RAOF> It would appear to be a packaging bug in nvidia-current.
[08:31] <didrocks> is it linked to Provides: xserver-xorg-video-7 ?
[08:31] <RAOF> It *should* be Depend-ing on _something_ X related :) (preferably xserver-xorg-video-abi-8.0)
[08:31] <didrocks> ok, I see no such depends :)
[08:32] <didrocks> can you see that with tseliot? It's too late for now but for next time :)
[08:32] <didrocks> I can't blame the user on the French forum for not reading the "partial upgrade" this time ;)
[08:32] <didrocks> I just can say "it's an unstable release, do not rely on it" ;)
[08:32] <didrocks> (and ok, I'm waiting before upgrading!)
[08:33] <RAOF> You should be able to add "Option" "IgnoreABI" "true" to xorg.conf to make the nvidia driver work.
[08:34] <RAOF> (At least, that's my understanding)
[08:34] <didrocks> RAOF: yeah, people get that workaround on the forum
[08:34] <didrocks> so, it should work
[08:34] <didrocks> but I can wait :)
[08:35] <didrocks> Do you want to break your graphical output? [Y/n]
[08:35] <RAOF> Looks like fglrx is also a little messed up.
[08:36] <RAOF> Depends: libxext6 (>= 0)
[08:36] <RAOF> Hah.
[08:36] <didrocks> hum :-)
[08:36] <RAOF> That's a pretty easy dependency to satisfy :)
[08:38] <didrocks> you never know… Did someone try foo -2.24? ;)
[08:39] <didrocks> that can be… an interesting experience!
[08:40] <RAOF> :)
[08:59] <seb128> hey
[09:00] <didrocks> salut seb128
[09:00] <seb128> lut didrocks
[09:00] <seb128> en forme?
[09:00] <didrocks> ça va ;) OOo a planté à cause d'un symbol file pas à jour, donc je reprends le build ce matin avec dpkg-buildpackage -nc, ordi toujours à plat :) mais ça va! et toi?
[09:01] <seb128> lol
[09:01] <seb128> ca va
[09:02] <seb128> worked a bit late for those gir rebuilds
[09:02] <seb128> did that fix unity or not?
[09:03] <didrocks> seb128: well, as I'm still in build mode, I can't easily switch sessions :/ I have to take my scratchbox to make some tests today
[09:03] <seb128> didrocks, don't bother I will upgrade now to see how it goes
[09:04] <robert_ancell> seb128, hey
[09:04] <didrocks> seb128: thanks :)
[09:04] <seb128> robert_ancell, hello mr broke everything so the european guys have something to do during their day ;-)
[09:04] <robert_ancell> seb128, :)
[09:05] <robert_ancell> seb128, the package renaming you did broke upgrades, not sure what to do about that
[09:05] <seb128> robert_ancell, did it? how?
[09:06] <robert_ancell> seb128, because both versions contain the same files
[09:06] <seb128> well I used a conflicts,replaces
[09:06] <robert_ancell> seb128, weird, I upgraded my mini and it borked installing the -1 version
[09:06] <seb128> but it should conflict only with your buggy build
[09:07] <seb128> not with 0.6
[09:07] <seb128> since the soname changed
[09:07] <robert_ancell> the mini didn't have my build on it
[09:07] <seb128> what file conflicted?
[09:07] <seb128> the sonames changed from .0 to .1
[09:07] <robert_ancell> /usr/lib/libgirepository-1.0.so.1.0.0
[09:07] <seb128> there should be no file conflict
[09:07] <seb128> you didn't have 0.9.3-0ubuntu1?
[09:08] <robert_ancell> no
[09:09] <robert_ancell> keep an eye out for it anyway
[09:09] <seb128> robert_ancell, ok, weird, it was libgirepository-1.0.so.0.0.0 in 0.6
[09:09] <seb128> can you check in /var/log/dpkg.log
[09:09] <seb128> what version was upgraded to what
[09:09] <seb128> ie grep libgir /var/log/dpkg.log
[09:09] <robert_ancell> ok
[09:10] <robert_ancell> booting it now..
[09:10] <seb128> thanks
[09:11] <robert_ancell> 0.6.14-1ubuntu1
[09:12] <seb128> hum, ok
[09:12] <robert_ancell> ajmitch had a similar problem - not sure if he got the buggy version first though
[09:12] <seb128> I will check
[09:13] <seb128> I might just conflicts on the previous version
[09:13] <seb128> you are right
[09:14] <seb128> the libeverything and the marshallingtest were already using .1
[09:14] <seb128> doh
[09:14] <robert_ancell> they like to make our lives hard! :)
[09:14] <ajmitch> hm?
[09:14] <ajmitch> oh, the conflicts/replaces
[09:14] <seb128> robert_ancell, I will take the debian change
[09:14] <lifeless> breaks plox
[09:14] <lifeless> :)
[09:14] <seb128>    * Install Everything-1.0 and GIMarshallingTests-1.0 typelib in new
[09:14] <seb128>      gir1.0-everything-1.0 package (Closes: #550478)
[09:15] <seb128> robert_ancell, ^ that will avoid the issue
[09:15] <robert_ancell> seb128, heh, that Everything file likes to cause us problems - we spent ages trying to decide where it lived
[09:16] <seb128> I meant to backport the debian change when they did it
[09:16] <seb128> that would have avoided the conflict
[09:17] <robert_ancell> seb128, oh, I was thinking - we're really screwed when gi does upgrades - all t he packages I looked at that install gir files have gir-1.0 hardcoded into them.  So they better be happy with the current filenames.
[09:17] <robert_ancell> s/filenames/binary format/
[09:18] <geser> looks like there is no need to file a bug about the libgirepository1.0-1 install issue
[09:18] <seb128> you people should use update-manager :p
[09:18] <seb128> it overwrite conflicts
[09:19] <seb128> robert_ancell, that's maybe why the directory didn't change with the abi version?
[09:19] <robert_ancell> seb128, yes, because it is the individual packages that choose the install location.  We might need to dh magic if they change it in the future
[09:19] <robert_ancell> gtg, see you guys tomorrow
[09:19] <robert_ancell> to use some dh magic
[09:20] <mvo> kiwinote: good morning! I just checked your deb-files branch, nice fixes. but it appears there is a test failing when I run test_database.py. - please re-merge and double check, but tests should be fixed
[09:20] <mvo> now
[09:20] <seb128> robert_ancell, have fun, see you tomorow
[09:24] <kiwinote> mvo: hi
[09:24] <kiwinote> mvo: is the test that is failing the self.assertEqual(len(db), 6) one?
[09:25] <mvo> kiwinote: I had the one about "expensive gem" failing
[09:26] <mvo> kiwinote: state was "NOT_FOUND" when it should be "NEEDS_PURCHASE"
[09:33] <kiwinote> mvo: thanks, the rest looks fine
[09:34] <mvo> kiwinote: so you have a new failure? or what do you mean with "the rest" ?
[09:34] <kiwinote> mvo: sorry, I meant that I had tested all the changes
[09:37] <mvo> kiwinote: ok :) thanks!
[09:59] <seb128> hey chrisccoulson
[09:59] <seb128> how are you?
[09:59] <chrisccoulson> hi seb128, i'm good thanks. how are you?
[10:00] <seb128> I'm fine thank you
[10:03] <ronoc> seb128: did an upgrade this morning and now my login screen is pretty unresponsive
[10:03] <ronoc> did you hear of any problems
[10:03] <seb128> ronoc, like no user listed?
[10:03] <seb128> ronoc, or...?
[10:03] <ronoc> seb128: it basically show the name of the machine, doesn't get to listing users
[10:04] <ronoc> the mouse works but i have to hard reset
[10:04] <seb128> known issue
[10:04] <seb128> seems to be a race
[10:04] <seb128> you can switch to a vt and sudo restart gdm
[10:04] <seb128> bug #614810
[10:04] <ubot2> Launchpad bug 614810 in gdm (Ubuntu) (and 1 other project) "gdm displays no user at startup in Ubuntu Maverick (affects: 5) (dups: 1) (heat: 34)" [Medium,Triaged] https://launchpad.net/bugs/614810
[10:05] <seb128> ronoc, it doesn't happen every time
[10:05] <ronoc> seb128: for me it is
[10:05] <ronoc> seb128: I found a crash report for _usr_bin_do-release-upgrade
[10:05] <seb128> ronoc, that's a different bug
[10:06] <seb128> ronoc, did you try restarting gdm?
[10:06] <ronoc> will try now
[10:06] <ronoc> bbiab
[10:15] <kiwinote> mvo: sometime during the merges we started getting get_software > app_name > cat_name instead of get_s > cat_name > app_name. There is a fix for this in my branch.
[10:16] <chrisccoulson> heh, i'll actually be at UDS quite early this time, rather than turning up late on sunday evening
[10:20] <mvo> kiwinote: thanks!
[10:28] <alf__> ronoc, seb128: i solved this issue by fixing the permissions of /lib/dbus-1.0/dbus-daemon-launch-helper
[10:29] <alf__> -rwsr-xr-- 1 root messagebus 47536 2010-08-09 18:28 /lib/dbus-1.0/dbus-daemon-launch-helper
[10:29] <seb128> what issue?
[10:30] <alf__> the no user on gdm
[10:32] <bilalakhtar> Anyone free over here?
[10:32] <bilalakhtar> I need to get an empathy bug fix in
[10:32] <cassidy> which bug?
[10:33] <bilalakhtar> cassidy: Yeah, Hi
[10:33] <bilalakhtar> cassidy:  A regression bug due to the freenode default network one
[10:33] <bilalakhtar> cassidy: I know you commented on the bugzilla bug
[10:33] <cassidy> ah ok this one
[10:33] <ronoc> seb128: still no joy
[10:34] <bilalakhtar> cassidy: bug #615081
[10:34] <ubot2> Launchpad bug 615081 in empathy (Ubuntu) "log in button is not enabled when adding IRC account (affects: 1) (heat: 8)" [Medium,In progress] https://launchpad.net/bugs/615081
[10:34] <bilalakhtar> I have the fix ^^
[10:34] <alf__> ronoc: what are the permissions of /lib/dbus-1.0/dbus-daemon-launch-helper ?
[10:35] <cassidy> bilalakhtar, could you submit it upstream please?
[10:35] <bilalakhtar> cassidy: ok
[10:35] <cassidy> that's not an Ubuntu specific issue so there is no reason to fix it in Ubuntu rather than upstream
[10:36] <bilalakhtar> cassidy: Since it is caused due to the freenode bugfix.
[10:36] <ronoc> alf__: -rwxr-xr-x
[10:36] <bilalakhtar> cassidy: ok, doing
[10:36] <ronoc> alf__ for root
[10:36] <ronoc> group and owner
[10:36] <bilalakhtar> cassidy: Have you accepted the DEFAULT_IRC_NETWORK patch?
[10:36] <alf__> ronoc: they should be -rwsr-xr-- 1 root messagebus 47536 2010-08-09 18:28 /lib/dbus-1.0/dbus-daemon-launch-helper
[10:36] <seb128> alf__, are you sure?
[10:37] <ronoc> alf__: have you experienced the problem I am having
[10:37] <seb128> alf__, the issue started after a gdm update where dbus didn't change in months, it's a gdm race
[10:37] <cassidy> bilalakhtar, yeah I merged it this morning
[10:37] <bilalakhtar> cassidy: Thanks a lot!
[10:37] <cassidy> thanks for the patch :)
[10:37] <cassidy> but I used gimpnet as default instead of freenode
[10:38] <ronoc> basically get to gdm, but the login window is not displayed, the screen right before login is displayed
[10:38] <cassidy> that still easier for you, you just have to patch one line
[10:38] <bilalakhtar> cassidy: Yes, I expected you to use GIMPnet, since that is preferred by GNOME
[10:38] <ronoc> where the name of the machine is displayed with the computer large icon
[10:38] <alf__> seb128, ronoc: that fixed the problem for me, perhaps it is seperate to the race condition
[10:38] <seb128> alf__, you though it fixed it
[10:38] <seb128> alf__, you just maybe got lucky on next try
[10:39] <ronoc> seb128: I can reproduce this every time
[10:39] <ronoc> haven't been able to log in for an hour
[10:39] <seb128> ronoc, you are the very first to not have it racy
[10:39] <seb128> ronoc, install xdm or use startx or enable autologin
[10:39] <ronoc> lucky me
[10:40] <ronoc> okay will try that
[10:40] <bilalakhtar> seb128: Are you free to sponsor a rhythmbox regression?
[10:40] <seb128> bilalakhtar, not now but I will do some sponsoring today and it's on my list
[10:40] <ronoc> seb128: i did notice a broken packages problem with gir and python
[10:40] <ronoc> seb128: would this have anything to do with it ?
[10:40] <alf__> seb128: perhaps, although in /var/log/syslog i got complaints about "setuid helper has wrong permissions"
[10:41] <seb128> ronoc, that should be sorted in the next hour
[10:41] <ronoc> grand
[10:41] <ronoc> bbiab
[10:42] <bilalakhtar> cassidy: Shall submit later today
[10:43] <seb128> alf__, weird, I don't get that permission issue there
[10:45] <alf__> seb128: are your permissions -rwsr-xr-- 1 root messagebus ?
[10:47] <seb128> yes
[10:48] <alf__> seb128: for me (and apparently ronoc) it was -rwxr-xr-x root root
[10:48] <seb128> weird
[10:48] <seb128> did that start recently?
[10:49] <alf__> seb128: I just noticed it today after a dist upgrade
[10:51] <seb128> I merged the new dbus with debian this week but that should affect that
[10:51] <seb128> it's still fine on my machines and there was nothing about permissions in the debian dir diff
[10:51] <seb128> anyway the "no user listed" started with the gdm update before dbus changed
[10:52] <seb128> so it's a different issue
[10:52] <alf__> seb128: yes, it seems so
[10:52] <mpt> mvo, good morning, how are you going with integrating Ubuntu Single Sign-On?
[10:53] <mvo> mpt: you mean how its going? or what the plan is?
[10:53] <mpt> mvo, both :-) I know about <https://wiki.ubuntu.com/TheGreatUbuntuSingleSignOnClientsMergeOf2010>
[10:54] <mvo> mpt: I played with the ubuntu-sso-client trunk yesterday, but it was not working for me, probably because of me not installing it properly
[10:55] <mvo> mpt: it looks straightforward though
[10:59] <seb128> ronoc, still no luck?
[11:00] <ronoc> seb128: no joy still, couldn't install xdm because the repo is broken with the gir stuff, startx fails because x is running already, when I kill x it automatically restarts bringing me to the unresponsive screen
[11:00] <ronoc> my only option is to return to the vt
[11:00] <seb128> ronoc, well you can sudo stop gdm
[11:00] <seb128> ronoc, or startx -- :1
[11:01] <alf__> ronoc: did you try changing permissions and rebooting?
[11:01] <ronoc> I didn't alf__
[11:01] <ronoc> just because i would rather not change permissions down /lib, but if it comes to it I will try it
[11:01] <alf__> ronoc: you should :)
[11:02] <alf__> ronoc: they are incorrect
[11:02] <seb128> do you guys are your lib dir on a different partition or something?
[11:02] <ronoc> nope
[11:02] <alf__> no
[11:02] <seb128> it still doesn't make sense to me
[11:03] <seb128> the dbus.postinst set the permission
[11:03] <mpt> mvo, the reason I'm asking is that I'm wondering about the case of reinstalling purchases. When that brings up the dialog, the dialog should allow *only* sign-in, not registration, because registration is a dead-end for that feature.
[11:03] <seb128> ronoc, alf__: can you run
[11:03] <seb128> dpkg-statoverride --list /lib/dbus-1.0/dbus-daemon-launch-helper
[11:04] <ronoc> seb128: will need to boot back into the maverick
[11:05] <alf__> seb128: I get no output
[11:05] <seb128> alf__, can you sh -x /var/lib/dpkg/info/dbus.postinst configure
[11:05] <mvo> mpt: good point
[11:05] <seb128> alf__, and tru to figure why it doesn't change the permission for you?
[11:06] <mvo> mpt: when this was discussed with and471 I pointed out to jonlea that for our use-case the login dialog would almost always be visibile (re-install)
[11:07] <mvo> mpt: iirc the ubuntu-sso one has a strong focus on registration
[11:08] <mpt> mvo, yeah, and that's fine if USC is remembering (or telling gnome-keyring to remember) the sign-in details, because 90% of the time you'll still want only registration. But, we still need the sign-in-only case.
[11:08] <mvo> mpt: I think its the right thing to have only one and doing it via dbus etc is the right way of doing it. but time is short, FF is very close
[11:08] <mvo> mpt: well, in USC we will never need registration currently as the agent is not capable (currently, there is a open bug about it) to get pre-exisiting credentials
[11:09] <mvo> mpt: you always have to login in the webkit view currently to purchase
[11:09] <ronoc> seb128: going to try again now
[11:09] <mpt> mvo, is that being fixed for Maverick?
[11:09] <mvo> mpt: but yeah, once that is fixed/added the 90% figure works for USC as wlel
[11:09] <mvo> mpt: I hope, we can bring it up in the next meeting
[11:09] <mpt> mvo, does it make sense to have a flag in the API that says "show only the sign-in choice, not registration, please"? Then the SSO team can implement it later
[11:10] <mvo> I think it does
[11:10] <mpt> ok
[11:10] <mpt> I'll discuss that with Chipaca and nessita
[11:10] <mvo> but we need to coordindate with them, I assuem they are under pressure as well
[11:10] <mvo> thans
[11:10] <mvo> thanks
[11:10] <mpt> yeah
[11:12] <mpt> mvo, which of (1) apturl replacement, (2) gdebi replacement, (3) devildante's add-ons work, are on track for merging?
[11:12] <mpt> and (4) the OneConf stuff
[11:12] <alf__> seb128: sudo sh -x /var/lib/dpkg/info/dbus.postinst configure seems to run fine :S
[11:13] <seb128> alf__, does it change the permissions for the helper?
[11:13] <alf__> seb128: yes
[11:13] <seb128> alf__, dpkg -l dbus | grep dbus?
[11:13] <mvo> mpt: (1) and (2) are the same branch
[11:13] <mvo> mpt: oneconf is done
[11:13] <alf__> seb128: 1.2.24-3ubuntu1
[11:13] <seb128> alf__, it's rather the state I'm interested in
[11:14] <seb128> ie is ie "ii"
[11:14] <seb128> or iU
[11:14] <mvo> mpt: its a plugin AFAIK didrocks does not need more from usc
[11:14] <seb128> or what?
[11:14] <alf__> seb128: iU
[11:14] <seb128> alf__, ah!
[11:14] <seb128> alf__, that's your issue then
[11:14] <seb128> alf__, sudo apt-get -f install
[11:15] <seb128> alf__, dbus is not configured, your upgrade probably broke
[11:15] <didrocks> mvo: mpt: all is ok for oneconf, it's already in the archive, apart from the issue of syncing which is out of oneconf scope, should be ready
[11:16] <didrocks> mvo: just that I will need a unregistering() function on USC side (if you uncheck the box "show other inventory"), so that it's taken into account without restarting USC, but I can do that (after my holidays, but before beta)
[11:16] <mpt> didrocks, cool. nzmm_ is working right now on a categorized list view for "Installed Software", and once he's got it done, you can reuse it for "items that aren't on this computer"/"other items"
[11:16] <mvo> didrocks: ok, that sounds like a bugfix
[11:17] <didrocks> mpt: excellent!
[11:17] <didrocks> mvo: right, that's why I'm not pushing too hard on that right now. I would prefer syncing working first :)
[11:17] <mvo> didrocks: yep :)
[11:18] <didrocks> mvo: I just have a bug in the view for non app, which seems to be set to True even if I excplitely set "False" to the model. Don't have the time right now to have a deeper look
[11:20] <mvo> mpt: addons and deb-files are under review, I want them in, but I don't want to de-stablize too much
[11:20] <mpt> mvo, deb-files being kiwinote's work, or something else?
[11:20] <mvo> didrocks: if you have a test-case I can have a look
[11:20] <mvo> mpt: kiwinote work
[11:20] <mpt> ok
[11:21]  * mpt keeps forgetting that OneConf is a plug-in
[11:21] <didrocks> mvo: I'll setup a mini view with it, just not that week (and on holidays then) :) Still, it's a bugfix IMHO
[11:21] <didrocks> mvo: btw, I think you saw my dummy branch for featured app?
[11:22] <mvo> didrocks: yeah, will merge it today
[11:22] <didrocks> mvo: thanks ;)
[11:25] <mvo> seb128: ara just pointed me to http://pastebin.ubuntu.com/476371/  - that is known, right?
[11:26] <seb128> mvo, yes
[11:26] <seb128> dpkg --force-overwrite -i /var/cache/apt/archives/libgirepository1.0-1_0.9.3-0ubuntu2_i386.deb
[11:28] <alf__> seb128: libgirepository1.0 is what broke my upgrade, too. Thanks!
[11:28] <seb128> np
[11:30] <ara> seb128, thanks!
[11:30] <seb128> np
[11:30] <seb128> I didn't notice because I upgraded yesterday and gor 0.9.3-0ubuntu1
[11:30] <seb128> got
[11:30] <seb128> it's only an issue if you skipped that version
[11:48] <seb128> ok, fix uploaded
[11:50]  * seb128 hugs mvo
[11:50] <seb128> update-manager is made of awesome
[11:50] <seb128> that's why I didn't notice the upgrade bug, it just turned the ovewrite to a warning
[12:00] <devildante> seb128: seconded :)
[12:47] <asac> mvo: debconf: delaying package configuration, since apt-utils is not installed ... is that a problem in general? or does that usually yield good/default configs?
[12:48] <Chipaca> mvo: hi
[12:49] <mvo> asac: that should be ok iirc, but colin will know for sure
[12:49] <asac> k
[12:50] <mvo> Chipaca: hi, I played with the dbus stuff but not with much success. but I create a quick-n-diry package thta might be the problem
[12:51] <Chipaca> mvo: not sure I followed the whole conversation there, but, I'm not sure why you'd need to support registration in your app for the u-sso-c to work for registering you. Or do you mean server-side?
[12:53] <mvo> Chipaca: that part is problably best to be explained by mpt
[12:53] <mvo> Chipaca: I couldn't bring up a dialog, but that may well be a bug on my side
[12:58] <nessita> mvo: wanna share what you did? I can review
[12:58] <nessita> (hi all!)
[12:58] <seb128> hey nessita
[13:00] <mpt> Chipaca, here's the issue: <https://wiki.ubuntu.com/SoftwareCenter?action=AttachFile&do=get&target=previous-purchases-authorize.jpg>
[13:01] <nessita> hi seb128, any idea why since yesterday's updates nvidia driver stopped working? (As in (EE) Failed to load module "nvidia" (loader failed, 7) (EE) No drivers available.)
[13:02] <seb128> nessita, I guess it's due to the xorg 1.9 transition
[13:02] <seb128> hey pedro_
[13:02] <Chipaca> mpt: I should pull you into the desktop+ sprint, and beg for freeze exceptions
[13:02] <pedro_> bonjour seb128
[13:02] <Chipaca> mpt: in fact, I could do that. Would you be able to come?
[13:02] <mpt> Chipaca, when and where is the sprint?
[13:02] <chrisccoulson> messita: <sebner> RAOF: lol, thx for the info :) I'm already using maverick, was just wondering if I can install the xserver upgrades :)
 You can, and it'll break nvidia unless you add IgnoreABI.
[13:03] <chrisccoulson> from #ubuntu-devel
[13:03] <Chipaca> mpt: Córdoba, Argentina, the week from the 23rd to the 28th
[13:03] <nessita> chrisccoulson: thanks!
[13:03] <chrisccoulson> yw
[13:03] <seb128> chrisccoulson, btw did you investigate the gdm issue yesterday?
[13:04] <chrisccoulson> seb128 - not yet, i've got sidetracked now trying to unbreak mozilla dailies ;)
[13:04] <chrisccoulson> thanks mozilla :(
[13:04] <seb128> the mozilla world seems facinating
[13:05] <chrisccoulson> yeah, the dailies are very broken now ;)
[13:06] <asac> some recent update broke emacs here :( ... (emacs:27923): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed
[13:06] <asac> and it becomes unresponsive quick :/
[13:13]  * Chipaca didn't mean to crash mpt. Could somebody power-cycle?
[13:14] <mpt> Chipaca, sorry, in a design discussion with Stuart. I could do 23rd to 26th
[13:14] <mvo> nessita, Chipaca: I have it working now, I guess the only issue is what mpt outlined. currently our main use-case is "I just reinstalled my computer and want to get my purchased apps"
[13:15] <mvo> nessita: it like really straightforward to integrate, nice work
[13:16] <mvo> its probably as simple as having a "optimize_ui_for_users_with_accounts" and just switching the main login window vs the new-user window
[13:18] <Chipaca> mpt: do you think it would be a good use of your time and health? (keep in mind it's a long trip) (while you ponder that, I'm asking for the FEs)
[13:18] <Chipaca> not for, *about* the FEs
[13:19] <nessita> mvo: :-)
[13:19] <nessita> mvo: a few details: reset password is not functional from the UI yet, it will very very soon
[13:20] <nessita> mvo: also, error handling from the server is a bit rough yet, we have a critical bug for that. You can look at https://bugs.launchpad.net/ubuntu-sso-client for details
[13:21] <mpt> Chipaca, it depends how much engineering time you would be devoting to sign-on + registration as opposed to other things. I'm used to long flights, and I have a holiday straight afterwards anyway (that's why I can't do the 27th/28th).
[13:25] <mpt> Chipaca, I do think it would be a good use of my time.
[13:50] <Zdra> seb128, funny thing: libglib recommand libdconf0, which depends on glib... so the build bot installs glib to compile glib...
[13:51] <Zdra> which breaks our ppa where we uploaded a broken glib
[13:52] <Zdra> :p
[13:52] <seb128> Zdra, recommends should be be used for build
[13:52] <seb128> Zdra, recommends should not be used for build
[13:52] <seb128> weird
[13:52] <Zdra> http://launchpadlibrarian.net/53429640/buildlog_ubuntu-lucid-i386.glib2.0_2.25.13-1ubuntu1~ppa10.04+1_CHROOTWAIT.txt.gz
[13:52] <Zdra> our broken glib segfault when installing the package
[13:53] <Zdra> but to build the new glib with the fix, it wants to install glib which segfault
[13:53] <Zdra> => we are f*cked
[13:53] <seb128> glib is in the builder installed package list
[13:53] <seb128> it's not coming from dconf
[13:53] <seb128> it gets upgraded before build
[13:54] <Zdra> ah
[13:54] <seb128> Zdra, delete the buggy glib from the ppa
[13:54] <seb128> so it doesn't get updated before build
[13:54] <seb128> then retry the new one
[13:54] <Zdra> Hm, ok
[13:54] <Zdra> so that's not a buildbot/package issue
[13:55] <Zdra> it is normal to need glib to build glib :p
[13:55] <seb128> no
[13:55] <seb128> it's just that glib is in the base system
[13:55] <seb128> so it's installed on the builders
[13:55] <Zdra> seb128, thx :)
[13:56] <seb128> yw
[13:59] <bilalakhtar> Anyone here ready to sponsor a rhythmbox fix ?
[14:06] <kenvandine> seb128, are the introspection issues settled down now?
[14:06]  * kenvandine wonders if it is a good time to do an update :)
[14:07] <seb128> kenvandine, they should yes
[14:07] <seb128> kenvandine, hey ;-)
[14:07] <kenvandine> :)
[14:07]  * kenvandine tries
[14:07] <kenvandine> hey... good afternoon :-D
[14:07] <seb128> chrisccoulson, micahg: could you update https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-mozilla-team-discussion and move the alpha3 work items remaining to beta?
[14:09] <chrisccoulson> seb128 - yeah, sure
[14:09] <didrocks> good morning kenvandine
[14:09] <kenvandine> hey didrocks!
[14:09]  * kenvandine is looking forward to getting back to using unity 
[14:09] <kenvandine> hehe
[14:09] <chrisccoulson> seb128 - do i just move the ones that are still TODO, or do i need to move the POSTPONED items too?
[14:10] <didrocks> kenvandine: keep me posted :)
[14:10] <seb128> chrisccoulson, just the TODO
[14:20]  * kiwinote congratulates mvo with the 1000th revision of s-c!
[14:20] <mvo> kiwinote: :)
[14:20] <kiwinote> and all others of course ;)
[14:21] <seb128> chrisccoulson, can you do me a summary of what you plan to work on until beta? do you have coming holidays btw?
[14:21] <bilalakhtar> Anyone here ready to sponsor a rhythmbox fix ?
[14:21] <bilalakhtar> oops
[14:21] <bilalakhtar> sorry for that
[14:21] <bilalakhtar> I should have waited
[14:22] <seb128> you have been asking 3 times today
[14:22] <bilalakhtar> yup
[14:22] <seb128> could you stop asking again and again?
[14:22] <mvo> kiwinote: yeah, s-c has a amazing bunch of people behind it
[14:22]  * bilalakhtar congratulates mvo for the 1000th revision of s-c
[14:22] <seb128> the reply didn't change since the first time you asked earlier
[14:22] <bilalakhtar> seb128: I apologized
[14:23] <bilalakhtar> so
[14:23] <mvo> thanks bilalakhtar
[14:23] <seb128> mvo, congrats for fixing update-manager download indications ;-)
[14:23] <bilalakhtar> and my revision is only 0.1 % of the 1000 revisions
[14:23] <mpt> Congrats mvo on r1000 :-)
[14:24] <seb128> today is mvo celebration day! ;-)
[14:24] <didrocks> mvo: seb128: no more supersonic download speed rate? I'm sad :)
[14:24] <didrocks> congrats mvo btw ;)
[14:24] <mpt> mvo, sorry for the silly question, but do you need to keep a standalone .deb saved if you want to uninstall the software later? Or does the relevant information get copied somewhere else on installation?
[14:24] <seb128> didrocks, yeah, I was a bit disappointed as well, I though mvo would just fix the compression to have to download less than a bit as indicated
[14:25] <didrocks> seb128: +1, quite disappointed :-)
[14:25] <devildante> mvo, good job! :)
[14:25]  * didrocks hugs mvo
[14:26] <bilalakhtar> mvo fixed the 'unknown time remaining' problem?
[14:26] <seb128> no, the one which made "1kb download estimated" be displayed all the time since the recent python-apt changes
[14:26] <cyphermox> mpt, assuming you didn't 'apt-get clean', downloaded debs may be in /var/cache/apt/archives
[14:28] <mpt> So, that's a "sometimes", then
[14:28] <mpt> thanks cyphermox
[14:29] <cyphermox> mpt, yeah "should", unless you did apt-get clean, or deleted them, or that it's a package installed during installation (in which case it presumably wasn't downloaded)
[14:29] <chrisccoulson> seb128 - sure
[14:29] <chrisccoulson> (i have no holidays planned btw)
[14:29] <cyphermox> mpt, I just download NM from the archive before working on it, in case... since re-downloading it when it's very broken is hard :)
[14:30] <seb128> chrisccoulson, ok
[14:33] <mvo> mpt: no worries, we don't need to keep the deb to uninstall it, all the info is part of the packaging system
[14:33] <mvo> thanks seb128, didrocks and bilalakhtar :)
[14:34] <bilalakhtar> mvo: You are welcome, being the great s-c developer!
[14:38] <seb128> didrocks, kenvandine: unity is fixed there
[14:39] <didrocks> seb128: great! thanks for confirming
[14:39] <seb128> np
[14:40] <seb128> slomo, hey
[14:40] <seb128> slomo, do you know if bug #610600 is a known issue?
[14:40] <ubot2> Launchpad bug 610600 in cheese (Ubuntu Maverick) (and 3 other projects) "Serious video performance regression in cheese (2.28.1->2.30.1) (affects: 1) (heat: 12)" [High,Confirmed] https://launchpad.net/bugs/610600
[14:41] <seb128> slomo, seems it's a gstreamer issue since a gst-launch has similar performance issues
[14:53] <slomo> seb128: might be fixed with latest good release
[14:53] <seb128> slomo, the one you uploaded today to debian?
[14:53] <slomo> seb128: v4l2src had a bug since many release, that made it prefer color format conversion over the native format of the camera
[14:53] <slomo> yes
[14:53] <seb128> slomo, ok thanks
[14:59] <didrocks> mvo: thanks for the merge btw :)
[15:01] <mvo> didrocks: my pleasure
[15:02] <mpt> kiwinote, what happens currently when you open a .deb but one of your repositories has a newer version of a package with the same name?
[15:02] <ayan> seb128: there is a patch upstream for lp bug 548652.
[15:02] <ubot2> Launchpad bug 548652 in fedora (and 4 other projects) "menu mouse-scrolling broken, when themes enable gtk-auto-mnemonics (affects: 40) (dups: 8) (heat: 220)" [Unknown,Unknown] https://launchpad.net/bugs/548652
[15:02] <kiwinote> mpt: you should get a warning in the pkgstatusbar
[15:02] <seb128> ayan, upstream said the patch as not correct though?
[15:02] <rodrigo_> seb128, are all gir-* packages rebuilt now?
[15:03] <seb128> rodrigo_, not sure all are but all the useful should be
[15:03] <seb128> rodrigo_, you should be able to retry builds on launchpad for things which failed to build
[15:03] <Riddell> yes, in kde's svn as part of kdesdkglib.GError: Icon 'emblem-system' not present in theme"  what am I likely to need to install to have that fixed?
[15:03] <rodrigo_> seb128, ok, so my package that failed won't get rebuilt until I do another submission?
[15:03] <rodrigo_> seb128, ah, ok
[15:03] <ayan> really?  hmph.  okay.
[15:03] <kiwinote> mpt: the warning text is a bit long (ie makes the bar expand), so it may be good to tweak the text
[15:03] <Riddell> cor, pasted two things in one somehow
[15:03] <Riddell> "glib.GError: Icon 'emblem-system' not present in theme"  what am I likely to need to install to have that fixed?
[15:03] <seb128> ayan, you should subscribe to bugs you are interested in to get new comments
[15:04] <seb128> rodrigo_, which one is it?
[15:04] <rodrigo_> seb128, https://launchpad.net/ubuntu/+source/ubuntuone-client/1.3.7-0ubuntu1
[15:04] <seb128> rodrigo_, do you have accept to the "retry" buttons?
[15:04] <seb128> rodrigo_, ie on https://edge.launchpad.net/ubuntu/+source/ubuntuone-client/1.3.7-0ubuntu1/+build/1912998
[15:04] <seb128> do you have "Retry this build"
[15:04] <rodrigo_> seb128, no, don't see it, where should it be?
[15:05] <rodrigo_> ah, yes, I see it
[15:05] <seb128> rodrigo_, under the build status
[15:05] <seb128> rodrigo_, you need to do it for every architecture which failed to build
[15:05] <rodrigo_> yeah
[15:05] <seb128> rodrigo_, or you can use "ubuntu-build"
[15:06] <rodrigo_> oh, cool
[15:06] <mpt> kiwinote, but if you install the standalone version, will it stick, or will Update Manager (or whatever) try to update it to the repository version later?
[15:07] <kiwinote> mpt: the update-manager will update it later, I presume
[15:08] <mpt> hrmmm
[15:12] <mpt> Is there a use case for wanting to keep with the old version? I suppose if the new version was horribly broken...
[15:13] <kiwinote> mpt: if the newer version is installed, we don't support downgrading to an older deb file afaik
[15:14] <kiwinote> mpt: installing the older deb file only works if the newer version isn't installed
[15:15] <mvo> downgrades are a fragile operation, there is no gurantee that they work (most of the time they will though)
[15:17] <slomo> seb128: btw, i'll upload the -bad pre-release soon... are you going to sync the 3 new pre-releases?
[15:17] <slomo> seb128: or merge or whatever
[15:18] <seb128> slomo, when are the next stable versions going to be out?
[15:20] <slomo> the plan is end of this week
[15:22] <rodrigo_> seb128, ok, seems they are building ok now, thanks!
[15:22] <seb128> rodrigo_, you're welcome, sorry for the trouble
[15:22] <rodrigo_> seb128, np
[15:22] <Chipaca> seb128: hi. Do you have a minute?
[15:22] <seb128> slomo, ok, I will probably update things in main and ping motus for universe ones
[15:22] <seb128> Chipaca, hey, sure
[15:23] <Chipaca> seb128: I'm not sure how aware you are, but we've gotten a ubuntu-sso-client that offers a dbus service that the ubuntu software centre can (and is, i think) using
[15:23] <Chipaca> seb128: this all came together in the last week
[15:23] <Chipaca> seb128: and there are some rough edges, especially when used from the USC
[15:24] <kenvandine> hey tedg
[15:24] <slomo> seb128: good, you should probably talk to the farsight people to push them a bit to get the few farsight plugins moved from gst-plugins-bad to -good ;)
[15:24] <Chipaca> seb128: so, I'd like to have mpt and a couple of my devs sprint for three days week after next
[15:24] <rodrigo_> seb128, sparc still failing (cannot determune gcc system), I shouldn't care about it, right?
[15:24] <seb128> slomo, I talked to tester at GUADEC
[15:24] <tedg> Good morning kenvandine
[15:24] <kenvandine> is there a sane way to handle building something that needs gir for dbusmenu on both lucid and maverick?
[15:24] <Chipaca> seb128: however, that will almost certainly result in things that are not strictly bugs
[15:24] <mvo> (its not used yet by s-c, but we want to use it)
[15:24] <seb128> slomo, he said he would need to write quite some testcases for that and it might take a while
[15:25] <Chipaca> seb128: would you be ok with FFEs for that? does that seem like a reasonable use of them?
[15:25] <kenvandine> Dbusmenu-Glib-0.2.gir vs DbusmenuGlib-0.2.gir
[15:25] <kenvandine> tedg,  ^^
[15:25] <seb128> kenvandine, -> ayatana
[15:25] <kenvandine> ok
[15:25] <seb128> thanks ;-)
[15:25] <tedg> kenvandine, Oh, I don't know. The issue is that the first one doesn't really get the namespaces right. :(
[15:25] <seb128> trying to have ayatana active a bit
[15:26] <seb128> and this channel has several running discussions ;-)
[15:27] <mpt> hi glatzor
[15:27] <rodrigo_> yeah, everyone talking to seb128 at the same time :)
[15:29] <seb128> lol
[15:29] <didrocks> rodrigo_: testing context switching of his new CPU :)
[15:29] <rodrigo_> :D
[15:30] <mvo> hey glatzor
[15:30] <rodrigo_> we need a seb128's clone, or 2
[15:30] <mvo> seb63
[15:30] <mvo> seb64 even
[15:30] <rodrigo_> :)
[15:31] <seb128> mvo, ok, I'm not sure to understand where we stand
[15:31] <seb128> is s-c using sso now
[15:31] <seb128> does it need it this cycle or can you do without it?
[15:31] <mvo> seb128: ok, that status quo is: s-c is using sso, but with its own implementation
[15:31] <mvo> seb128: of the login dialog, no design-team approved design, but working
[15:32] <mvo> seb128: the ubuntuone folks have a new way of doing it, gnomekeyring integration, dbus, fancy (design team approved) dialog
[15:32] <mvo> seb128: but its currently aimed toward the "I want to register" use-case
[15:32] <mvo> seb128: and we need (at least for one of our uses) the "I want to login" use-case
[15:33] <mvo> seb128: that is the background
[15:33] <mvo> Chipaca: anything to add from your side :) ?
[15:35] <seb128> mvo, what would switching to the new thing win you?
[15:36] <seb128> you would need the new "I want to login" use-case to be addressed?
[15:36] <seb128> which the current sso version doesn't?
[15:36] <mvo> it does adress it, but not very well
[15:36] <seb128> ie that's what that sprint discussion is about? adding a mode for that?
[15:36] <mpt> seb128, the win would be consistency between USC and Ubuntu One, and no longer needing that code in USC (so shorter code and shorter spec)
[15:36] <seb128> is not very well better or not that what you have now?
[15:37] <mvo> it would buy us a nicer UI, the same UI for both login cases (ubuntuone and s-c) and a cleaner design code-wise (dbus backend etc)
[15:37] <seb128> mpt, that will happen next cycle for sure
[15:37] <seb128> mvo, ^
[15:37] <mpt> of course
[15:37] <seb128> mvo, ok, so what are the drawbacks of upgrading today?
[15:37] <seb128> upgrading -> switching
[15:38] <mvo> its designed very much for new-registers
[15:38] <mvo> so we will not loose anything, its just not as good as it could be
[15:39] <micahg> seb128: I was going to try to get the gjs merge in today, I was wondering if I should carry fwd robert_ancell's gobject_introspection patch
[15:39] <mvo> I don't mind that much either way, if we don't use it now we use it in N
[15:39] <mpt> seb128, switching today results in Chipaca requesting a small FFe in two weeks
[15:39] <mpt> and also sends me to Argentina (probably)
[15:40] <seb128> micahg, if it's still revelant I guess yes
[15:40] <seb128> mpt, mvo, Chipaca: what would the new feature be?
[15:40] <mpt> seb128, the "Please show only the sign-in stuff, not the register stuff" mode for the SSO dialog.
[15:41] <seb128> so a new dialog basically
[15:41] <seb128> or just a show, hide for one widget on the current dialog?
[15:41] <seb128> or...?
[15:41] <seb128> does that implies new backend code as well?
[15:41] <mpt> Something on that continuum.
[15:41] <seb128> new dbus interfaces?
[15:41] <Chipaca> the current dialog has a button at the bottom that takes you to what we want to be the next dialog
[15:42] <LucidFox> seb128> From the looks of it, the issue with the webkit thing is that JSCore-1.0 thing set not only the repository version to 1.1, but also the JSCore version
[15:42] <Chipaca> i.e. the "oh i already have an account skip this" button
[15:42] <mpt> The new/changed dbus interface could go in today and just be ignored, I think (though I'm not an expert on that)
[15:42] <Chipaca> yes, but the rest of the change would still need a ffe
[15:42] <LucidFox> because of that, we get FTBFS in packages depending on webkit gir now
[15:43] <Chipaca> right?
[15:43] <seb128> Chipaca, I still have an hard time figure what would be the coming change
[15:43] <seb128> would that be a new dialog? new code?
[15:44] <seb128> or just a gtk_widget_show call for a widget in the current one?
[15:44] <Chipaca> just a gtk_widget_show, or some variation of that, i think? mpt?
[15:45] <mpt> I don't know, I'm sorry, I haven't designed it yet
[15:45] <mpt> It would take a few hours to sketch the alternatives and choose the best one
[15:45] <seb128> seems it's not only a label change
[15:45] <Chipaca> right, but, functionally the dialog already exists
[15:45] <seb128> why would mpt need to traval the world for a trivial change
[15:46] <kenvandine> so just a new look and exposing it?
[15:46] <mpt> well, if you put it like that... :-P
[15:46] <kenvandine> :)
[15:47] <seb128> I've difficulties to see why the change can't land this week if it's trivial
[15:47] <kenvandine> not really new functionality
[15:47] <seb128> why do you need a sprint and 2 weeks delay
[15:47] <Chipaca> it's not trivial. I'm arguing that if we get the dbus change, it might just be ui + a gtk_widget_show or somesuch
[15:47] <seb128> "just be ui"
[15:47] <seb128> so a new dialog?
[15:48] <Chipaca> seb128: because my team has been rushing to get this far and I need them to slow down for a few days or they'll burn out
[15:49] <Chipaca> seb128: do you have ubuntu-sso-client installed?
[15:49] <Chipaca> I can explain this easier by pointing you at it
[15:49] <nessita> Chipaca: current ubuntu-sso-client is way old
[15:49] <nessita> Chipaca: just FYI
[15:49] <seb128> Chipaca, yes
[15:50] <Chipaca> nessita: oh. Hm. seb128: could you pull lp:ubuntu-sso-client then?
[15:50] <Chipaca> nessita: that should work, right?
[15:51] <Chipaca> seb128: then, killall ubuntu-sso-client; PYTHONPATH=. bin/ubuntu-sso-client, and PYTHONPATH=. bin/ubuntu-sso-client-gui
[15:51] <Chipaca> from memory
[15:51] <mvo> PYTHONPATH=. bin/ubuntu-sso-login and then the dbus call
[15:51] <Chipaca> :)
[15:51] <nessita> nessita: yes sir, I can also provide a temp (working) package
[15:51] <seb128> nessita, stop talking to yourself
[15:52] <Chipaca> seb128: remember when I said "they'll burn out"? :)
[15:52] <mvo> heh! working too hard ;)
[15:52] <nessita> seb128: you have no idea how useless I am today :-)
[15:52] <nessita> seb128: but I make you laugh, oulalá!
[15:53] <mpt> mvo, glatzor: On a completely separate topic, you might have noticed from <https://wiki.ubuntu.com/SoftwareUpdateHandling#expanded> that I'd like update-manager to start showing the same icons, titles, and summaries (from app-install-data etc) for things as Ubuntu Software Center does. So maybe (for Maverick+1?) the code for determining that info should move out of software-center into its own library.
[15:54] <mpt> oh, bad timing
[15:54] <Chipaca> seb128: so, what we want is, on the one hand to have the gui start on the page you go to when you click the "already have an account?" button at the bottom of the dialog
[15:54] <mvo> mpt: library makes sense
[15:55] <Chipaca> seb128: on the other, make the whole thing as awesome as it can be. This last thing would fit within the "ui changes only" label (anything not-ui-only would be deferred)
[16:07] <seb128> LucidFox, sorry I completely forgot about what you were saying with all the pings there
[16:07] <seb128> LucidFox, dunno about that webkit issue you are talking about
[16:10] <LucidFox> Moment
[16:12] <LucidFox> seb128> bug #616387
[16:12] <ubot2> Launchpad bug 616387 in webkit (Ubuntu) "1.2.3-1ubuntu1: JSCore version incorrectly set to 1.1 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/616387
[16:14] <Chipaca> mvo: you got a minute (again)?
[16:14] <mvo> Chipaca: yes, I might be a bit slow responding but yes
[16:15] <seb128> LucidFox, do you have a fix for it?
[16:16] <seb128> LucidFox, seems you do, thanks
[16:16] <seb128> LucidFox, sponsoring that
[16:16] <Chipaca> mvo: alecu, he's adding a dbus login-only call *right now*. nessita will be doing the gtk work to make the login page be the default for that call, after lunch
[16:17] <mvo> Chipaca: ok
[16:17] <Chipaca> mvo: these people are fusing their hands solid as we talk. Did I mention they TDD? THey rock.
[16:18] <Chipaca> mvo: so... the new call will be almost identical to the old one, but be called login_ instead of register_or_login_
[16:18] <Chipaca> mvo: we'll work with mpt within the constraints of the feature freeze to get the dialog as good as it can be for M
[16:18] <Chipaca> mvo: that is, if the devs have hands
[16:19] <Chipaca> mvo: can you integrate that as soon as it's on trunk, so we all make it in before the fruz?
[16:22] <seb128> mvo, ok, so I still have difficulties to appreciate the scope of the change you will need in 2 weeks
[16:22] <seb128> ups
[16:22] <seb128> Chipaca, ^
[16:22] <seb128> but that seems rather tweaks
[16:23] <seb128> the fact that you need to wait for a sprint and get a designer there makes me nervous though
[16:23] <seb128> it doesn't fit with the easy change
[16:23] <seb128> so I can't really tell you whether that exception will be approved or not
[16:24] <mvo> Chipaca: I have a lot on my plate, but I will do my very best
[16:27] <rodrigo_> hmm, what's the lp url for tomboy branch, lp:~ubuntu-desktop/tomboy seems to be failing
[16:29] <rodrigo_> ah, missing /ubuntu
[16:30] <rodrigo_> hmm, no, that's wrong, it has the 1.2.x version, while maverick has 1.3.x
[16:30] <rodrigo_> seb128, ^^ ?
[16:31] <rodrigo_> sorry to ping you again :)
[16:32] <seb128> rodrigo_, I guess Laney didn't update the vcs while doing the update
[16:32] <rodrigo_> ah
[16:33] <rodrigo_> seb128, can you update it? I'm going to submit a patch to the existing package
[16:33] <seb128> rodrigo_, ok
[16:33] <rodrigo_> seb128, thanks
[16:34] <Laney> rodrigo_: what's the update?
[16:34] <Laney> seb128: I can't update the branch
[16:34] <rodrigo_> Laney, https://bugs.edge.launchpad.net/ubuntu/+source/tomboy/+bug/615876
[16:34] <ubot2> Ubuntu bug 615876 in tomboy (Ubuntu) "Add Ubuntu One note to Tomboy fresh install (affects: 1) (heat: 8)" [Wishlist,Triaged]
[16:35] <rodrigo_> Laney, and after that, a patch to have U1 as a separate syncing mechanism from 'Tomboy Web'
[16:35] <rodrigo_> Laney, but that needs still a bit of polish
[16:35] <Laney> ok cool
[16:35] <seb128> Laney, why not?
[16:35] <Laney> you should talk with ajmitch about u1 in debian btw
[16:35] <Laney> seb128: I'm not in the desktop team on LP
[16:36] <seb128> Laney, if you have upload rights you are in a team which is a subteam of it
[16:36] <seb128> Laney, no?
[16:36] <Laney> cli-mono uploaders team
[16:36] <Laney> it's not a subteam of desktop
[16:36] <seb128> oh ok
[16:36] <seb128> can you push to a junk or somewhere and do a merge request?
[16:36] <Laney> yeah will do next time
[16:38] <Chipaca> Laney: we've talked, and I've forwarded his concerns I think.
[16:38] <Laney> Chipaca: I'm not familiar with the issues, I just know that he was working on it
[16:40] <Chipaca> Laney: there are legal/political roadblocks. I'm sure we'll get through, around, over or past them :)
[16:40] <Laney> cool
[16:41] <Laney> I saw the trademark thread on -legal
[16:44] <seb128> Chipaca, rodrigo_: is the new note translatable and how?
[16:46] <rodrigo_> seb128, the notes are added in the code, using Catalog.GetString (gettext c# equivalent), so they should show up as translatable strings in the package
[16:46] <rodrigo_> seb128, not sure how to go with translating it though
[16:46] <rodrigo_> does the ubuntu translations team translate this kind of things?
[16:46] <rodrigo_> (strings added in patches to the package)
[16:49] <rodrigo_> seb128, http://pastebin.ubuntu.com/476498/
[16:49] <seb128> rodrigo_, ok, gettext means langpacks
[16:49] <seb128> rodrigo_, so great ;-)
[16:50] <rodrigo_> ah, ok
[16:50] <seb128> no static html copy in the source
[16:50] <rodrigo_> seb128, so, can you please update the package branch so that I can submit it then?
[16:51] <seb128> rodrigo_, I'm on it
[16:52] <rodrigo_> seb128, ok, thanks again :)
[16:52] <seb128> sorry the day is busy crazier every hour
[16:52] <rodrigo_> yeah, sorry for giving you more work :(
[16:52] <seb128> don't worry
[16:53] <seb128> rodrigo_, ok, done
[16:53] <rodrigo_> cool
[16:57] <rodrigo_> Laney, 1.3.1-1ubuntu1b1 <- version number for the last package, so my upgrade would be 1.3.1-2ubuntub1?
[16:58] <Laney> rodrigo_: ubuntu2 rather
[16:58] <rodrigo_> Laney, and what does the b1 stand for?
[16:58] <Laney> pitti did a rebuild
[16:59] <rodrigo_> Laney, ah, so my upgrade is 1.3.1-1ubuntu2 then?
[16:59] <rodrigo_> without the b1?
[16:59] <Laney> yep
[16:59] <rodrigo_> ok
[17:12] <rodrigo_> kenvandine, seb128: merge this when you have time, please -> https://code.edge.launchpad.net/~rodrigo-moya/ubuntu/maverick/tomboy/add-u1-note/+merge/32348
[17:12] <rodrigo_> package just submitted
[17:18] <seb128> kenvandine, rodrigo_: doing it
[17:25] <didrocks> seb128: (when you have minute, do not rush on that), do you have a comment/stopper on bug #615874 or should I go on with dpm and prepare the wiki page? (trying to get that ready tomorrow morning with testing if I can)
[17:25] <ubot2> Launchpad bug 615874 in evolution (Ubuntu) "Add Ubuntu One email to Evolution fresh install (affects: 1) (heat: 8)" [Wishlist,New] https://launchpad.net/bugs/615874
[17:27] <glatzor> hey mpt  and mvo!
[17:28] <davidbarth> Riddell: hey jonathan, it seems that konversation is missing entries in its desktop file to register with the messaging menu: is that a known bug or a recent change?
[17:28] <seb128> didrocks, I would rather have them to make some efforts to figure a way that would work with langpacks
[17:29] <didrocks> seb128: should I write that on the bug report and tell them to work on that or do you want to do it?
[17:29] <seb128> didrocks, I did comment earlier on the bug saying that
[17:29] <seb128> see comment #1
[17:30] <didrocks> yeah, saw that
[17:30] <seb128> I still don't think it's pratical
[17:30] <seb128> I would know how much they want that in
[17:31] <seb128> to weight the cost
[17:31] <seb128> it's a trade efforts win
[17:31] <didrocks> right, I agree with you
[17:37] <Riddell> davidbarth: why does it need entries in the desktop file?
[17:39] <didrocks> wow, my two builds in a ppa was stopped or dropped (the machine crashed?) and get rescheduled to another one :/
[17:41] <davidbarth> Riddell: hmm, actually not sure it had some in lucid, sorry; but the msg menu integration seems broken atm and agateau just went on a leave for the end of the week... ;)
[17:44] <davidbarth> Riddell: but clearly there is a regression here, i'll file a bug for agateau when he comes back; thanks
[17:46] <Riddell> davidbarth: hmm, the last upload removed the patch
[17:46] <Riddell> a bad merge
[17:47] <Riddell> mm yes, messy
[17:48] <davidbarth> Riddell: ah, ok, i've opened https://bugs.launchpad.net/ayatana-ubuntu/+bug/616422 to track that
[17:48] <ubot2> Ubuntu bug 616422 in ayatana-ubuntu "[regression] konversation not registered in the gnome msging menu (affects: 1) (heat: 6)" [High,New]
[17:48] <davidbarth> Riddell: can i reassign it to you then?
[17:51] <Riddell> davidbarth: yes do
[17:51] <Riddell> "jr"
[17:57] <Riddell> davidbarth: fix uploaded, sorry about that
[18:09] <nessita> seb128: ping
[18:09] <seb128> nessita, pong
[18:09] <nessita> seb128: I'm building the package for the ubuntu-sso-client (v0.98), and I'm getting these warnings https://pastebin.canonical.com/35748/ Should I try to fix them or they are... "known", let's say
[18:11] <davidbarth> Riddell: awesome! thanks for the quick turnaround on this one
[18:11] <nessita> seb128: and for the binary I also get dpkg-deb: warning: 'debian/ubuntu-sso-client/DEBIAN/control' contains user-defined field 'Python-Version'
[18:14] <seb128> nessita, you can ignore the maintainer ones
[18:14] <seb128> nessita, you might want to add a debian/source/format
[18:16] <seb128> nessita, do you have a "Python-Version" in your control?
[18:16] <seb128> it's usually XS-Python-Version or XB-
[18:25] <nessita> seb128: yes, there is a Python-Versio that was added by python-mkdebian
[18:26] <seb128> didrocks, mvo: ^ do you know about that?
[18:26] <seb128> I've never used python-mkdebian and I don't do lot of python packaging
[18:26] <seb128> I though it was XB-Python-Version or XS-Python-Version though
[18:26] <didrocks> yes, it's on purpose for python-support
[18:27] <didrocks> let me check, there is something without XB- or XS- IIRC
[18:28] <didrocks> nessita: nessita what do you have in debian/control? you should have XS-Python-Version which is in the source: section and XB- which is in the binary one (the XB- is stripped at build time then)
[18:29] <nessita> didrocks: you're right, this is what I have
[18:29] <nessita> https://pastebin.canonical.com/35749/
[18:31] <nessita> didrocks: I guess debuild is complaining for no reason?
[18:31] <didrocks> nessita: sure, and yeah, I have this warning too, however we comply to the python packaging policy (http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html). I didn't look too much about that warning TBH :)
[18:31] <didrocks> (yes seb128, you read it, for once I'm in the "I don't care so much about a warning" mode ;))
[18:32] <didrocks> nessita: I would blame the "no serious reason" at least, most of packages are like that :)
[18:35] <mvo> alecu: hi, I'm playing with trunk currently and get this traceback on clicking "cancel" http://paste.ubuntu.com/476530/
[18:35] <seb128> didrocks, you need holidays!
[18:36] <didrocks> seb128: if you say so… /quit :p
[18:36] <seb128> didrocks, ;-)
[18:36] <didrocks> :)
[18:36] <chrisccoulson> heh, "Facebook appears modifying in firefox.." is a really helpful and informative long bug description
[18:38] <LucidFox> Any ideas why, after a recent update, the Nautilus desktop background is hidden behind flat white most of the time?
[18:42] <seb128> no
[18:43] <seb128> I would blame the xorg updates
[18:47] <LucidFox> Hmm, is it just me or does someone else have this problem? It occurs with both nvidia and nouveau, no idea which package to file it against
[18:47] <vish> LucidFox: #ubuntu-x ?
[18:49] <nessita> didrocks: thanks!
[18:49] <didrocks> nessita: yw  :)
[18:50] <vish> didrocks: hi , any chance of Bug #578585 being fixed soon? i'v been trying to get unity working , but all i get is a white background.. and not able to do anything.:(
[18:50] <ubot2> Launchpad bug 578585 in unity (Ubuntu) (and 2 other projects) "Existing systray causes unity to crash (gnome panel conflict): Unity keeps reloading on my system and get white background... (affects: 21) (dups: 2) (heat: 121)" [Medium,Triaged] https://launchpad.net/bugs/578585
[18:50] <mvo> Chipaca, nessita: support for the sso login is commited to trunk (with the login_or_register api, the other one is not yet available in trunk afaics)
[18:51] <didrocks> vish: we don't know how to fix it in a proper way… did you try my comment about removing saved session?
[18:51] <nessita> mvo: the ologin only is entering trunk in a few minutes
[18:52] <vish> didrocks: yeah , i tried it i think once.. let me try again.. :)
[18:52] <didrocks> vish: ensure to remove the saved session in the capplet too… or you will save or session when unlogging :)
[18:53] <vish> ah , thanks , will uncheck that too
[18:53] <mvo> nessita: no rush, changing that is trivial
[18:59] <alecu> mvo, good catch. I'll take a look
[19:02] <mvo> alecu: np, thanks for working on it :)
[19:04] <mvo> nessita: the transient for xid change has not landed yet, right? I have it open behind s-c currently (not a big deal, just wanted to double check)
[19:05] <nessita> mvo: it has landed
[19:05] <nessita> mvo: yesterday, actually
[19:05] <nessita> mvo: you can check the log messages
[19:06] <nessita> mvo: can you please paste the output of ~/.cache/sso/oauth-login.log?
[19:07] <didrocks> ok, time to enjoy some dinner and evening! Have a good day/night everyone!
[19:09] <vish> aw , just missed him :(
[19:09] <vish> :)
[19:14] <mvo> nessita: lalala, my mistake (but its late here ;). transient_for xid works fine
[19:14] <nessita> mvo: ahahahahaah :-)
[19:14]  * nessita breaths
[19:20] <nessita> seb128: I proposed for merging the new package for ubuntu-sso-client upstream version 0.98: https://code.launchpad.net/~nataliabidart/ubuntu-sso-client/ubuntu-sso-client-0.98/+merge/32362
[19:23] <nessita> mvo: new Dbus API for only login landed on trunk
[19:28] <mvo> nessita: just saw it, does it hvae the coresponding UI yet too?
[19:29] <nessita> mvo: yes
[19:29] <nessita> mvo: you can roughly test it with:
[19:30] <nessita> killall ubuntu-sso-login; PYTHONPATH=. bin/ubuntu-sso-login & PYTHONPATH=. bin/ubuntu-sso-login-gui --logi
[19:30] <nessita> oops
[19:30] <nessita> an 'n' was missing, correct sentence is:
[19:30] <nessita> killall ubuntu-sso-login; PYTHONPATH=. bin/ubuntu-sso-login & PYTHONPATH=. bin/ubuntu-sso-login-gui --login
[19:35] <mvo> nessita: sweet, works fine, updates s-c trunk to use it
[19:35] <nessita> mvo: :-)
[19:36] <seb128> re
[19:36] <seb128> nessita, you want that uploaded to maverick then?
[19:37] <nessita> seb128: yes please! and I'd be even more grateful if you can enumerate what steps I should follow to achieve that.
[19:38] <nessita> seb128: is the merge proposal enough? shall I need to file a bug or similar?
[19:38] <nessita> shall I file*
[19:38] <seb128> nessita, what you did is fine, I'm sponsoring it now
[19:38] <nessita> seb128: thank you
[21:40] <mvo> devildante: I commented on the addons branch, all in all very nice
[21:40] <mvo> devildante: but some smallish issues, sorry for that
[21:41] <mvo> devildante: I also pushed a branch with some tweaks, please re-merge that
[21:41] <devildante> mvo: okay, thanks :)
[21:44] <mvo> devildante: the design stuff is probably more something for mpt, best is to talk to him tomrrow about it I think
[21:44] <devildante> mvo: okay
[21:45] <mvo> resolving the conflicts is going to be a bit of work, I'm sorry for that, but the deb-files branch was the last big branch to land (other than addons)
[21:47] <devildante> mvo: np
[21:56] <seb128> dobey, there?
[21:58] <devildante> mvo: could you elaborate on this: "- I would love to avoid the extra addons_install, addons_remove to each of the action methods in aptdaemon (as install()/remove() is really a apply() now for complex changes)
[21:58] <devildante> "
[22:00] <dobey> seb128: hey
[22:01] <mvo> devildante: its more a feeling, but I would like to use apply() instead of install when its becoming a complex operation with install and remove at the same time. does that make sense?
[22:01] <seb128> dobey, hello
[22:01] <seb128> dobey, what do you mean by "Is there any reason these separate files aren't pulled into the separate locale packages along with the rest of the translations"?
[22:02] <devildante> mvo: is there an apply() function in aptdaemon?
[22:02] <mvo> devildante: aptd.py iirc does not have one yet, but the daemon itself has a commit_packages
[22:03] <devildante> mvo: meh, that's what I was using
[22:03] <dobey> seb128: i see all of the translated default Inbox files installed on my system. they don't seem to be installed from the translations package, like the .mo files normally are on ubuntu
[22:03] <mvo> devildante: right, that is fine
[22:04] <mvo> devildante: I mean, it feels odd to call aptd.install("foo", addon_remove="bar"), instead the stuff in the detailsview should IMO call a apply() function with "to_add, to_remove"
[22:05] <seb128> dobey, right, that's the issue
[22:05] <seb128> dobey, they come with the tarball
[22:05] <seb128> dobey, having upstream handling translations with git commit is ok
[22:05] <seb128> dobey, having us handling translations with packages uploads is not
[22:06] <dobey> seb128: i don't understand why this is any different than other translations
[22:07] <seb128> dobey, other translations? gettext ones?
[22:07] <mvo> devildante: its not a big deal, I will try to outline something in the branch tomororw, I'm a bit tired now (but feel free to come up with your own solution/ideas)
[22:07] <seb128> dobey, the gettext templates are imported into rosetta, can be translated there and are exported in langpacks
[22:08] <seb128> dobey, they don't require any upload of the source to update translations
[22:08] <dobey> seb128: yes. why are these files not also pulled out to be translated there?
[22:08] <seb128> because we don't have a way to handle random files in langpacks
[22:08] <seb128> we just handle normal /usr/share/locale gettext files
[22:08] <seb128> rosetta knows only about po files
[22:09] <dobey> ok. well we can't easily change how evolution 'translates' the default Inbox file
[22:09] <seb128> it has no way to import or allow translators to translate that text
[22:10] <seb128> dobey, right, which means that change will have a maintainance cost
[22:10] <seb128> I'm not sure the win is worth the cost
[22:10] <dobey> every change does, yes.
[22:11] <dobey> i don't know, but that file hasn't changed in years
[22:11] <dobey> the default Inbox file
[22:11] <dobey> and i think novell/suse even patches it in their own packages
[22:12] <seb128> they probably don't care about having it translated
[22:12] <dobey> i just made the debdiff because joshua said it needed to be a patch, and it's easy to do for that
[22:13] <dobey> i think they ship patches for the translated ones too. if they still ship it patched anyway
[22:13] <seb128> the thing is that we would need to collect translations by some way
[22:13] <seb128> and to update the patch and do an upload every time a translation team wants to change something
[22:13] <dobey> fixing evolution to suck less re: translations is going to be a much larger project though
[22:14] <seb128> right
[22:14] <dobey> seb128: i'm not partial one way or the other about it. i was just trying to help by making the debdiff. if it's too much burden, feel free to discuss that with mattgriffin/cparrino/johnlea and come to a conclusion about what we can and can't do there :)
[22:14] <seb128> I was rather suggesting finding another way to promote u1
[22:15] <dobey> seb128: yeah, that's fine by me, but i'm not the person to make that decision. i'm not even working on the client stuff for maverick. just made a quick debdiff for the karma :)
[22:16] <kenvandine> dobey, anything for karma :)
[22:16]  * kenvandine ducks
[22:16] <dobey> hehe
[22:16] <dobey> kenvandine: it's what ghandi would do
[22:20] <bratsche> Anyone on #dx right now by any chance?  Is ted or agateau around?
[22:21] <dobey> yes, and no
[22:21] <bratsche> Thanks.
[22:22] <dobey> no, neither of them seem to be on that is :)
[22:22] <bratsche> Right, that's what I thought you meant. :)
[22:22] <bratsche> Thanks.
[22:23] <seb128> bratsche, I thinks agateau is on holidays
[22:24] <bratsche> Ah, okay.
[22:24] <seb128> bratsche, ted was around until a bit less than an hour ago, he might come back ;-)
[22:24] <bratsche> Cool.