[00:00] <charlie-tca> logs should be at http://irclogs.ubuntu.com
[02:20] <kenvandine> jasoncwarner, i just uploaded the latest snapshot of overlay-scrollbars to the ppa so you don't need to add the unity daily builds ppa
[02:20] <kenvandine> https://launchpad.net/~ayatana-scrollbar-team/+archive/release
[02:21] <kenvandine> it is much better than the version from last week :)
[02:21] <jasoncwarner> ah, thanks!
[02:21] <jasoncwarner> kenvandine: I installed the deb...will I be able to upgrade ok?
[02:21] <kenvandine> yeah
[02:21] <kenvandine> then you have basically the same thing
[02:21] <kenvandine> and you have the ppa enabled, so you'll get upgrades
[02:22] <kenvandine> this way everyone that had played with it will get all the fixes
[02:22] <kenvandine> jasoncwarner, what do you think?
[02:22] <jasoncwarner> I did..I disabled it when I got the deb link from you...but will renable now
[02:22] <kenvandine> not the unity daily builds ppa
[02:22] <kenvandine> but do enable the ppa:ayatana-scrollbar-team/release
[02:22] <TheMuso> RAOF: Any ideas why the nux unity support test succeeds, even though I am running nouveau without experimental 3D installed?
[02:22] <jasoncwarner> kenvandine: no, just hte ppa:ayatana-scrollbar-team/release....I'll enable that
[02:23] <jasoncwarner> yeah
[02:23] <kenvandine> good, done run the crack daily builds :)
[02:23] <jasoncwarner> kenvandine: so far so good, honestly. Not too many issues with me using it.
[02:23] <kenvandine> unless you want to bleed
[02:23] <kenvandine> yeah
[04:40] <robert_ancell> pitti, ping
[04:42] <robert_ancell> pitti, you had a 60 hour lock on the gnome-control-center branch, I hope that wasn't intentional 'cause I broke it...
[04:43] <kenvandine> robert_ancell, i have seen that on a couple branches, i think LP is a little disgruntled :)
[04:44] <robert_ancell> kenvandine, heh, naughty LP!
[04:48] <RAOF> Sponsor trawl time!  Who'd like to upload a re-enabled IA32 assembler version of mesa?
[04:51] <robert_ancell> RAOF, ah, I can I guess?
[04:51] <RAOF> Ta.
[04:52] <RAOF> http://cooperteam.net/Packages
[04:52] <robert_ancell> RAOF, mesa 7.10.1-0ubuntu3?
[04:53] <RAOF> Yup.  You can leave the rest of the X world for one of the X guys ;)
[04:53] <robert_ancell> RAOF, you guys should really use some sort of packaging branch...
[04:53] <RAOF> We do.
[04:53] <RAOF> Would you like a link to there instead?
[04:54] <robert_ancell> RAOF, yes please
[04:55] <RAOF> git://git.debian.org/git/pkg-xorg/lib/mesa on the ubuntu branch.
[04:56] <robert_ancell> oh, so debcheckout wasn't lying then :)
[04:56] <RAOF> Nope :)
[04:56] <RAOF> Although there's no way to encode the branch in the vcs format field, sadly.
[04:56] <robert_ancell> RAOF, ok, uploaded.  If anyone asks, it wasn't me who did it :)
[04:57] <RAOF> Heh.
[04:58] <RAOF> My lips are sealed!
[05:01] <TheMuso> robert_ancell: Unfortunately its not hard to find out who uploaded it.
[05:01] <TheMuso> Or should I say fortunately...
[05:02] <robert_ancell> TheMuso, stupid signing :)
[05:02] <TheMuso> heh
[07:01] <didrocks> good morning
[07:37] <pitti> good morning
[07:38] <didrocks> hey pitti
[07:38] <pitti> hey didrocks
[07:38] <didrocks> thanks for the dh7 langpack work :)
[07:38] <pitti> didrocks: took a while, as I added tests for each and everything
[07:38] <pitti> but now dh-translations is working
[07:39] <didrocks> oh nice, testsuite for the win \o/
[07:39] <pitti> I just need to add a dh sequencer now, package it, and test it
[07:39] <dpm> good morning all
[07:39] <pitti> didrocks: yeah, I've been bitten too hard with that stuff in the past
[07:39] <pitti> hey dpm
[07:39] <pitti> dpm: maverick langpack export arrived last evening, I built the packs overnight
[07:39] <dpm> hey pitti, yeah, I saw that the full export happened in the end.
[07:39] <pitti> I'll give them a quick test this morning, and upload
[07:40] <dpm> cool
[07:40] <didrocks> hey dpm
[07:41] <dpm> heya didrocks, how's it going?
[07:41] <didrocks> pitti: you will add a --with langpack?
[07:41] <didrocks> or something like that
[07:41] <pitti> yes
[07:41] <didrocks> dpm: I'm fine, thanks! you?
[07:41] <dpm> very well, thanks, slowly waking up :)
[07:48] <dpm> pitti, before uploading, and if it's not much of a hassle, may I ask you to rebuild the maverick language-pack-ca-base including the additional ca-valencia.xpi file I added to po2xpi? I pinged chrisccoulson about it, but it seems he hadn't had the chance to merge it yet. Once merged langpack-o-matic should pick it up automatically, although I'm not sure how it should be told that both the ca.xpi and ca-valencia.xpi files belong to the 'ca' language pa
[07:48] <dpm> ck
[07:49] <pitti> dpm: ah, that's missing; I can just add it by hand for now, but I need to fix it in the code as well; would you mind filing a bug against langpack-o-matic about it and assign to me?
[07:49] <dpm> pitti, sure, thanks!
[07:50] <pitti> dpm: where can I get ca-valencia.xpi for now?
[07:50] <chrisccoulson> i'm just merging that now btw ;)
[07:50] <pitti> ah
[07:50] <pitti> chrisccoulson: oh, good morning! early for you
[07:50] <dpm> cool, thanks chrisccoulson! (and good morning :)
[07:50] <chrisccoulson> hi! yeah, it's pretty early for me ;)
[07:50] <didrocks> hey chrisccoulson
[07:50] <chrisccoulson> hi didrocks
[07:51] <chrisccoulson> how are you?
[07:57] <didrocks> I'm fine, thanks, you? :)
[08:01] <dpm> pitti, ok, bug 736676 - let me know if you need more info
[08:01] <ubot2> Launchpad bug 736676 in langpack-o-matic "Add ca-valencia.xpi to the same language pack ca.xpi is in" [Undecided,New] https://launchpad.net/bugs/736676
[08:02] <pitti> dpm: looks fine, thanks
[08:06] <rodrigo_> morning
[08:10] <dpm> good morning rodrigo_
[08:11] <rodrigo_> hi dpm
[08:13] <pitti> hey rodrigo_
[08:14] <rodrigo_> hello pitti
[08:22] <dpm> thanks for the merge chrisccoulson
[08:45] <pitti> meh - the import failed early due to a LP oops
[08:49] <pitti> dpm: hah, langpack-o-matic already handles the -valencia pack properly (just had to update the test suite as it didn't previously expected a second xpi)
[08:50] <pitti> dpm: as I had to restart the maverick import anyway due to the LP oops, they'll be included
[08:50] <dpm> pitti, awesome, thanks, langpack-o-matic ftw!
[08:54] <chrisccoulson> pitti - have you seen this? http://people.mozilla.com/~sayrer/2011/temp/process.html ;)
[08:54] <chrisccoulson> i guess we'll need to be able to roll language packs quite quickly ;)
[08:56] <pitti> chrisccoulson: even faster release process?
[08:56] <chrisccoulson> pitti - yeah. it's pretty similar to that of chromium
[08:59] <chrisccoulson> kklimonda, i got mongodb built btw, but it fails the test-suite quite spectacularly
[09:00] <chrisccoulson> like, foo.x = 17; return foo.x gives NaN
[10:19] <Sweetshark> pitti: could you give me a hint again were I find the patches generated by merge-o-matic?
[10:19] <pitti> hey Sweetshark
[10:20] <pitti> Sweetshark: http://patches.ubuntu.com/
[10:29] <Sweetshark> pitti: the hyphen patch looks good, could you sync that?
[10:29]  * Sweetshark looks at the openoffice.org-dictionaries and openthesaurus packages
[10:29] <pitti> Sweetshark: you looked at https://merges.ubuntu.com/h/hyphen/hyphen_2.7.1-3ubuntu1.patch vs. https://merges.ubuntu.com/h/hyphen/hyphen_2.7.1-4.patch ?
[10:30] <pitti> Sweetshark: the automatic merge https://merges.ubuntu.com/h/hyphen/hyphen_2.7.1-4ubuntu1.patch still has the extra language-support recommends, though
[10:31] <pitti> i. e. this needs a merge, not a sync
[10:33] <Sweetshark> pitti: ugh, yes. I meant the merge looks good for hyphen. Do I need to repeat the merge? I would end up just as the automatic one did.
[10:33] <pitti> Sweetshark: it's rather trivial indeed, you just need to update the changelog (remaining differences/uploader)
[10:34] <seb128> pitti, reading your discussion with fta, why do we prevent report of abort crashes to start?
[10:34] <pitti> seb128: we have always done so
[10:34] <pitti> seb128: since maverick or so we do report the ones with an AssertionMessage, though
[10:34] <seb128> pitti, right but it seems wrong
[10:35] <pitti> back then you (or other folks) complained about getting too many useless reports about sigabrt, because they didn't tell you the actual assertion message
[10:35] <seb128> we got discussions several times a week with annoyed users that get "a crash but apport telling them it can't report it" where we need to explain them how to use gdb to get a stacktrace anyway so we have a clue what's going on
[10:36] <pitti> for sigabrt?
[10:36] <seb128> pitti, well I changed my mind, I think having to deal with confused users is work over what cleaned extra bugs is ;-)
[10:36] <seb128> cleaning
[10:36] <pitti> okay :) no big deal to report these again
[10:36] <seb128> pitti, not sure, I think usually the message say "it's an assert without error message set"
[10:37] <pitti> added to my todo then
[10:37] <seb128> pitti, but since it's a crash and we want to know what's going on we usually go and explain them how to use gdb...
[10:37] <seb128> pitti, thanks
[10:37] <pitti> would still like to finish dh_translations first, though
[10:37] <seb128> pitti, oh about that
[10:37] <seb128> pitti, did you notice http://packages.qa.debian.org/g/gnome-pkg-tools/news/20110227T161722Z.html
[10:37] <seb128> ?
[10:38] <seb128> pitti, debian got some dh7 --gnome work done recently
[10:38] <pitti> * Add --with gnome debhelper sequencer (Closes: #578494).
[10:38] <pitti> nice
[10:38] <seb128> pitti, I forgot to comment on the lp bug about that
[10:38] <pitti> that's by and large bug 595008
[10:38] <ubot2> Launchpad bug 595008 in gnome-pkg-tools "should port the GNOME cdbs custom rules to dh7" [Wishlist,Triaged] https://launchpad.net/bugs/595008
[10:38] <seb128> pitti, your comment from yesterday made me remember about it
[10:38] <seb128> pitti, yeah, that's why I mention it now ;-)
[10:38] <pitti> niice
[10:40] <pitti> seb128: should we merge that for natty?
[10:41] <pitti> seb128: so I guess we should make --with gnome imply --with translations (i. e. add dh_translations to the gnome sequencer)
[10:42] <seb128> pitti, sure
[10:43] <seb128> pitti, yes, similar to cdbs, --gnome should do the magic for Ubuntu things
[10:43] <pitti> I just converted jockey from cdbs to dh and dh_translations
[10:43] <pitti> now mostly equivalent, the only thing that we are missing is the symlinking of identical doc files
[10:43] <seb128> ok
[10:44] <seb128> pitti, just curious do you win anything from using dh? or that was just a testcase for the new dh?
[10:44] <pitti> seb128: mostly for a real-life test case; I have automatic test cases in pkgbinarymangler, but I'm paranoid :)
[10:44] <pitti> seb128: I won't upload the new jockey right now
[10:44] <pitti> seb128: the win is mostly that it's much faster to build
[10:45] <pitti> but I won't start mass-converting packages for now, at least not before we get the doc symlinking back
[10:47] <pitti> seb128: I now test it with aptdaemon (bug 690270)
[10:47] <ubot2> Launchpad bug 690270 in aptdaemon "Translated String (zh_TW) Not Showed within aptdaemon" [Medium,In progress] https://launchpad.net/bugs/690270
[10:47] <seb128> pitti, thanks ;-)
[10:48] <seb128> btw why is cdbs slower to build?
[10:49] <pitti> seb128: because it calls all the dh_* for each single package individually
[10:49] <pitti> dh calls them just once, and they work on all packages then
[10:50] <seb128> right
[11:08] <seb128> mvo, bug #724735
[11:08] <ubot2> Launchpad bug 724735 in aptdaemon "aptd crashed with UnicodeDecodeError in _set_status_details(): 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128)" [Medium,Triaged] https://launchpad.net/bugs/724735
[11:09] <seb128> mvo, seems a frequent user issues and it has a patch to review
[11:10] <mvo> thanks seb128! I have a look
[11:12] <seb128> mvo, #635893 seems a frequent issue as well
[11:15] <jibel> mvo, hi
[11:15] <mvo> hey jibel
[11:15] <jibel> mvo, s-c is not in a good mood this morning: bug 736716
[11:15] <ubot2> Launchpad bug 736716 in software-center "software-center crashed with TypeError in _check_members(): Collection contains member of invalid type <type 'list'>. Expected <class 'zeitgeist.datamodel.Event'>" [High,Triaged] https://launchpad.net/bugs/736716
[11:16] <mvo> jibel: yeah, fixed in bzr :)
[11:16] <jibel> mvo, wow, thanks!
[11:17] <seb128> mvo, is #626798 really a crash or just apport noise?
[11:18] <rodrigo_> seb128, oh, saw your comment last night about https://bugzilla.gnome.org/show_bug.cgi?id=644560 but it was late, so the answer is: the fix is not that easy, so looking into a correct fix for it
[11:18] <ubot2> Gnome bug 644560 in Gal "Can't set an account password" [Normal,Needinfo]
[11:18] <seb128> rodrigo_, ok, I was just pointing it in case you just forgot to add it
[11:18] <seb128> rodrigo_, thanks
[11:19] <rodrigo_> seb128, yeah, I should have added another comment after I discussed it with upstream
[11:19] <mvo> seb128: that is caused by policykit having a short timeout I think
[11:19] <seb128> rodrigo_, if you discussed it with upstream that's fine ;-)
[11:19] <rodrigo_> seb128, the issue is that it needs to be hidden when editing an existing account, and displayed when creating a new account
[11:22] <seb128> rodrigo_, ok
[11:27] <seb128> rodrigo_, btw any news about the gdm, g-s-d race?
[11:28] <rodrigo_> seb128, I'm mostly done in pinpointing where the problem is, seems so far it's in gnome-session
[11:29] <seb128> rodrigo_, do you know if someone is going to work on actually fixing it?
[11:29] <rodrigo_> seb128, I discussed it with vuntz the other day, so either him or me will fix it, once I know where the problem is
[11:30] <seb128> vuntz, hey
[11:30] <seb128> rodrigo_, ok, let me check with vuntz, I just want to avoid duplicating work
[11:31] <rodrigo_> seb128, ok
[11:31] <rodrigo_> vuntz, it's about https://bugzilla.gnome.org/show_bug.cgi?id=634988
[11:31] <ubot2> Gnome bug 634988 in general "my computer is too fast" [Normal,New]
[11:32]  * pitti is now satisfied with dh_translations and uploads
[11:37] <pitti> dpm: are you running maverick ATM?
[11:37] <pitti> dpm: would you mind trying the -ca langpack which just finished building? (I checked that it has teh ca-valencia ffox plugin)
[11:39] <pitti> dpm: and the -es one as well, perhaps? (for the search plugins)
[11:42] <dpm> pitti, I'm running natty, and I don't have access to a maverick machine. I'll try to install an iso on a virtual machine and test
[11:42] <pitti> dpm: you can install them in the live system, too
[11:43] <pitti> dpm: I'll test the German ones
[11:43] <dpm> pitti, yeah, but it will take me the same amount of time, as I have to download the ISO
[11:43] <pitti> oh
[11:47] <dpm> or do we have any cloud machine where we could test?
[11:47] <pitti> not that I know of
[11:47] <dpm> jibel? ^
[11:48] <dpm> or jibel_ :)
[11:50] <jibel> hi dpm , I don't know any cloud system where we can test but I can help with testing in a VM, I must have a few maverick somewhere
[11:51] <dpm> jibel, cool, thanks, wait though, I'm talking with kim0, our community cloud expert, he might be able to help with that
[11:51] <jibel> dpm, okay, just ping me if you want me to test something
[11:51]  * jibel is back to nVidia testing 
[11:52] <dpm> cool, thanks :)
[11:53] <pitti> seb128: if you have a second, would you mind binNEWing dh-translations?
[12:02] <pitti> dpm: http://people.canonical.com/~pitti/tmp/lp/ has the .debs
[12:06] <dpm> pitti, ok, thanks
[12:15] <seb128> pitti, ok
[12:19] <pitti> dpm: the German one works well for me
[12:20] <pitti> dpm: so I guess I'll wait with the upload until your OK?
[12:20] <pitti> I'd just like to give this a little extra testing, as the underlying langpack-o-matic machinery is still very new
[12:21] <dpm> pitti, if you don't want to block on me, you can upload the others - I can test 'ca' and 'es' (I found a maverick ISO I'm installing on a VM right now)
[12:22] <pitti> dpm: it can wait another hour, that's fine
[12:22] <dpm> pitti, ok, let's talk again in ~1h
[12:25] <seb128> pitti, new-ed
[13:12] <pitti> seb128: merci
[13:21] <seb128> pitti, yw
[13:26]  * popey tickles kenvandine with bug 736848
[13:27] <kenvandine> no bot to give us a url?
[13:28]  * kenvandine does it the old school way
[13:29] <kenvandine> not finding that bug
[13:29] <kenvandine> popey, ^^
[13:29] <popey> private
[13:30] <popey> https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/736848
[13:30] <ubot2> popey: Error: <Bugtracker.plugin.Launchpad instance at 0x993484c> bug 736848 not found
[13:30] <popey> wut
[13:30] <popey> i copy/pasted that from the url in lp
[13:30] <kenvandine> very weird
[13:30] <kenvandine> can you subscribe me?
[13:30] <popey> sure
[13:31] <popey> done
[13:57]  * pochu waves :)
[13:58] <pochu> didrocks: so, looks like https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/687732 regressed
[13:58] <ubot2> Launchpad bug 687732 in compiz "gtk.Label <a href> link-activate signal broken with compiz in natty" [High,Fix released]
[13:58] <pochu> didrocks: the testcase fails in natty here
[13:58] <didrocks> pochu: hey hey
[13:58] <didrocks> oh?
[13:58] <pochu> GtkLabels with links don't work
[13:58] <didrocks> i'm just discussing compiz bug right now :)
[13:58] <didrocks> bugs*
[13:58] <didrocks> so, perfect timing!
[13:58] <pochu> :)
[13:59] <pochu> that affects empathy, e.g. the facebook new account dialog
[13:59] <pochu> possibly more places
[13:59] <didrocks> pochu: sure, it's a high priority :)
[13:59] <pochu> so I'd appreciate if you can include that bug in your discussions ;)
[13:59] <didrocks> thanks for the head's up :)
[13:59] <pochu> neat, thank you!
[13:59] <didrocks> pochu: doing right now on #compiz-dev
[13:59] <pochu> let me know if you discover something
[14:00] <didrocks> pochu: sure, can you update the status please?
[14:00] <dpm> pitti, the 'ca' and 'es' language packs look fine except for one thing: the yelp front page is in English - this might have to do with that bug kyleN worked on a while ago? (bug 451673)
[14:00] <didrocks> (on the bug)
[14:00] <ubot2> Launchpad bug 451673 in yelp "Untranslated Yelp main page (Ubuntu Help Center)" [High,Confirmed] https://launchpad.net/bugs/451673
[14:00] <didrocks> pochu: with version and such…
[14:00] <pitti> dpm: is that a regression from the maverick final langpacks?
[14:00] <pochu> didrocks: of course
[14:01] <didrocks> thanks :)
[14:01] <pitti> dpm: I hate this bug; I think I attempted to fix it at least three times now :/
[14:01] <dpm> pitti, I'm actually not sure if it's a regression. I can't remember if the bug was fixed before release or not
[14:01] <seb128> didrocks, pochu: I can't confirm there
[14:02] <didrocks> just tried as well
[14:02] <didrocks> can't confirm
[14:02] <pochu> hrmm, weird
[14:02] <didrocks> (on gedit)
[14:02] <pochu> have you tried the test case?
[14:02] <pochu> I have natty uptodate as of two minutes ago
[14:02] <pitti> dpm: booting maverick live in Spanish to check
[14:02] <dpm> ok
[14:03] <smspillaz> pochu: poke
[14:03] <smspillaz> pochu: you said links were weird ?
[14:03] <seb128> pochu, I just tried the testcase example
[14:03] <smspillaz> does this happen right after you change viewports or all the time ?
[14:03] <seb128> pochu, works here
[14:03] <pochu> smspillaz: apparently all the time, but it seems seb128 and didrocks can't reproduce it :/
[14:03] <smspillaz> pochu: so what, clicking on links doesn't work ?
[14:04] <pochu> smspillaz: in links on GtkLabels, yes
[14:04] <smspillaz> pochu: hrm
[14:04] <pochu> GtkLinkButtons are ok
[14:04] <smspillaz> pochu: fire up xev
[14:04] <pitti> dpm: system -> about Ubuntu is in Spanish, but pressing F1 on the desktop background ("Ubuntu Help Center") is in English
[14:04] <smspillaz> pochu: click anywhere in xev
[14:04] <smspillaz> it should only give 2 events
[14:04] <smspillaz> ButtonPress and ButtonRelease
[14:04] <pitti> dpm: that is, the topic list on the left is Spanish, but the main text is English
[14:04] <smspillaz> is that right ?
[14:05] <pochu> smspillaz: yes, I get two events when I click
[14:05] <pochu> smspillaz: ButtonPress and ButtonRelease
[14:05] <smspillaz> pochu: right ok
[14:05] <smspillaz> hrm
[14:05] <smspillaz> do the links only not work sometimes or is it all the time
[14:05] <smspillaz> because if you are getting just ButtonPress and ButtonRelease then compiz isn't doing anything silly
[14:05] <smspillaz> (no interference with the app)
[14:06] <dpm> pitti, yeah, that's exactly what I saw on the latest langpacks too, so as bad as it might be, it does not seem to be a regression. However, IIRC kyleN fixed it for the Chinese langpacks for the OEM build, so releasing new Chinese langpacks might mean a regression on the field for his build
[14:06] <pochu> smspillaz: sometimes they work, e.g. if I click on other links (like a GtkLinkButton), they start to work on the GtkLabels
[14:06] <smspillaz> right
[14:06] <smspillaz> does it happen with metacity ?
[14:06] <pitti> dpm: I guess we can leave that to the -proposed testing then?
[14:06] <pochu> smspillaz: just tried again, the first time in xev I didn't get ButtonPress and ButtonRelease
[14:07] <pitti> dpm: I'm uploading the lot now; let's see what sticks
[14:07] <smspillaz> pochu: well, the first time you click, you will get a bit more
[14:07] <smspillaz> because of click to focus
[14:07] <smspillaz> but after that
[14:07] <smspillaz> it should work fine
[14:07] <smspillaz> speaking of which
[14:07] <smspillaz> pochu: have you got anything like sticky windows, or click to focus not enabled or something weird like that?
[14:07] <pochu> smspillaz: hmm, it seems it doesn't work inside the black square
[14:08] <dpm> pitti, yeah, I guess so. We can then decide if it's possible to fix it, or if the zh_* langpacks can be patched, or if we just don't upload them to -updates
[14:08] <pochu> smspillaz: no, this is pretty much an stock Ubuntu natty
[14:08] <smspillaz> inside the black square you'll get a bit more
[14:08] <pitti> dpm: or perhaps they actually work :)
[14:08] <pochu> smspillaz: but I don't get ButtonPress inside the black square
[14:08] <dpm> pitti, yeah, that'd be my favourite option :)
[14:08] <pochu> smspillaz: I get KeymapNotify, ButtonRelease and LeaveNotify inside the square
[14:08] <smspillaz> hrm
[14:08] <smspillaz> or maybe you shouldn't get a bit more
[14:08] <smspillaz> *switches to metacity
[14:09] <pochu> ah no I get ButtonPress too
[14:09] <pochu> my bad
[14:09] <pochu> so I get ButtonPress, EnterNotify, KeymapNotify, ButtonRelease, LeaveNotify
[14:09] <smspillaz> right
[14:09] <smspillaz> same with metacity
[14:10] <smspillaz> hrm
[14:10] <smspillaz> and the links don't work unless you click on a button
[14:10] <smspillaz> pochu: what happens if you switch to metacity ... I wonder if this is a gtk+ issue
[14:10] <pochu> something like that, yeah
[14:12] <pochu> smspillaz: seems to work from metacity
[14:12] <pochu> smspillaz: actually the test case doesn't
[14:12] <pochu> this is quite weird
[14:13] <smspillaz> pochu: I vote bug in gtk+
[14:14] <smspillaz> since when I was initially dealing with this problem, it was indeed gtk+ being buggy
[14:14] <smspillaz> (not checking the event->xfocus.mode)
[14:14] <smspillaz> but I had to work around it in compiz anyways
[14:16] <pochu> smspillaz: well it's weird that it works in metacity but not in compiz then, isn't it?
[14:22] <pochu> well scratch that, as I said it also seems to fail on metacity
[14:28] <vuntz> rodrigo_: hey
[14:28] <vuntz> rodrigo_: I'm not working on the g-s-d issue on login, no
[14:29] <vuntz> rodrigo_: and I'll obviously gladily accept help here :-)
[14:30] <rodrigo_> vuntz, ok, I've been looking a bit at it, so will keep going
[14:31] <seb128> hey vuntz
[14:31] <seb128> vuntz, so I guess you will not work on that in the next 2 weeks?
[14:32] <vuntz> seb128: no, I won't
[14:32] <seb128> vuntz, ok thanks
[14:33] <seb128> vuntz, it's a bit of a visible issue and since new computers don't get slower increasing numbers of users hit it
[14:33] <vuntz> right
[14:33] <seb128> vuntz, well, we will work on in for natty and send a patch back if we get one
[14:34] <rodrigo_> I will keep looking for a fixç
[14:34] <rodrigo_> fix
[14:34] <vuntz> if someone sends me a computer fast enough to reproduce, I can possibly find time, though ;-)
[14:34] <rodrigo_> hehe
[14:34] <bcurtiswx> does anyone here use pithos, and get the gstreamer error?
[14:36] <pitti> Sweetshark: sorry, dropped the ball on that -- do you want me to merge hyphen?
[14:38] <seb128> vuntz, I can send you a sleep (1) shell command :p
[14:38] <seb128> vuntz, it might be possible to hack on with some tweaking, but don't bother
[14:39] <Sweetshark> pitti: if you could give it a fast merge, please do. LO currently needs me a bit too, because we are mergeing ~80 milestones from OOo into master (including the new buildsystem)
[14:39] <seb128> vuntz, we should just make desrt fix it since he has been reporting the bug he obviously has a computer which triggers it ;-)
[14:39] <pitti> Sweetshark: ack, doing
[14:42] <Sweetshark> pitti: thanks a lot!
[14:42] <pitti> Sweetshark: kein Problem :) (uploaded)
[14:48] <pochu> smspillaz: meh, apparently I was doing something weird, it works now
[14:48] <pochu> smspillaz: sorry for the noise
[14:48] <seb128> pochu, can you close the bug again then?
[14:48] <seb128> (didn't check if you did)
[14:49] <pochu> seb128: I already did :)
[14:49] <seb128> thanks
[15:01] <chrisccoulson> kklimonda, mongodb test failures down to 5 \o/
[15:01] <kklimonda> chrisccoulson: you are incredible. :)
[15:02] <chrisccoulson> heh
[15:19] <seb128> bah
[15:20] <seb128> pitti, did you already see apport chroot updates raise and assertionerror on the apt-get clean command?
[15:21] <pitti> seb128: doesn't ring a bell here; what does it say?
[15:21] <seb128> apport-chroot", line 110, in upgrade_chroot
[15:21] <seb128>     assert chroot.run(['apt-get', 'clean']) == 0
[15:21] <seb128> AssertionError
[15:21] <seb128> pitti, it's the amd64 retracer log
[15:22] <seb128> I've removed the lock just to see
[15:22]  * pitti blames multiarch
[15:22] <seb128> pitti, random guess you you think it might be due to it?
[15:23] <pitti> yes, it's a totally unfounded random guess
[15:23] <pitti> but it's the one thing happening now that is very intrusive
[15:25] <seb128> bah, failed again
[15:25] <seb128> let me log in and see manually
[15:43] <seb128> pitti,
[15:43] <seb128> # apt-get clean
[15:43] <seb128> apt-get: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by apt-get)
[15:43] <seb128> apt-get: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by /tmp/tmprHOceK/usr/lib/libapt-pkg.so.4.10)
[15:43] <pitti> seb128: argh, chroots have a botched apt-get?
[15:43] <seb128> mvo, ^ did you see such errors before?
[15:43] <seb128> pitti, they don't yet since the update fails on the broke apt-get clean
[15:43] <pitti> ah, good
[15:44] <seb128> so the tarballs didn't get updated
[15:44] <seb128> but it I do an upgrade I get that
[15:44] <seb128> I will exit 1
[15:44] <mvo> seb128: woah, where does this one come from?
[15:45] <seb128> mvo, retracers, apport-chroot
[15:45] <seb128> it happens after upgrading libstdc++6 today
[15:45] <mvo> seb128: I don't think I have seen that, what chroot in particular?
[15:45] <mvo> oh
[15:45] <seb128> let's move to #ubuntu-devel, it's a slangasek thing
[15:46] <mvo> did he break it?!?
[15:49] <seb128> mvo, he did the recent update, but I think it's a fakechroot issue
[15:49] <seb128> pitti, let's switch back here maybe
[15:50] <seb128> pitti, so you say to dchroot -q -c lucid  -> dchroot -q -c natty ?
[15:50] <pitti> seb128: yes; but I suppose that's not up to date
[15:50] <seb128> let me try that
[15:50] <pitti> seb128: we can do sudo apt-get install package, but I don't think dist-upgrde
[15:50] <seb128> pitti, do we need to?
[15:50] <pitti> well, we could probably just install libc6 and friends manually
[15:51] <pitti> seb128: I guess so, we need the latest multiarch stuff there
[15:51] <seb128> pitti, seems not
[15:52] <seb128> pitti, dist-upgrading the fakechroot environment works and doesn't lead to a broken apt-get
[15:52] <pitti> ooh
[15:52] <pitti> cool
[15:52] <seb128> pitti, but will the < natty retracing work in a natty chroot?
[15:52] <pitti> seb128: so far I kept lucid as long as that works, as it's stable
[15:52] <seb128> like the lucid etc
[15:53] <pitti> seb128: it should, but certainly worth testing
[15:53] <seb128> let me try
[15:53] <seb128> $ aptt update
[15:53] <seb128> E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
[15:53] <pitti> seb128: we only had to switch in hardy
[15:53] <seb128> pitti, doesn't work
[15:53] <pitti> seb128: sudo
[15:53] <pitti> seb128: we have sudo privs for "apt-get install"
[15:53] <seb128> pitti, I'm in the apport-chroot login lucid.tar.gz
[15:53] <pitti> ah
[15:54] <seb128> I guess it's one of the apt changes
[15:54] <pitti> but strange, why would this suddenly give a permission error
[15:54] <seb128> hum
[15:54] <seb128> sorry
[15:54] <seb128> pitti, my fault
[15:55] <seb128> pitti, in fact "apport-chroot login lucid.tar.gz" just returns
[15:55] <seb128> it doesn't let me in
[15:55] <seb128> it exit 0 though
[15:55] <seb128> weird
[15:55] <pitti> I guess that answers "does it work for lucid :/
[15:55] <seb128> seems to work with maverick
[15:56] <seb128> pitti, should I comment lucid and switch the cronjob to natty for now?
[15:56] <seb128> having natty crashes retracers seems higher priority than lucid
[15:56] <pitti> I agree
[15:56] <pitti> seb128: please do
[15:56] <seb128> ok, doing
[15:56] <seb128> thanks
[15:56] <pitti> seb128: i. e. comment it in the chrootmap
[15:56] <seb128> right
[15:56] <pitti> merci beaucoup
[15:56] <seb128> de rien
[15:57] <seb128> I will try to run the lucid ones manually every week or so until we sort that
[15:57] <seb128> it's just a matter to editing the chrootmap the other way around and changing the -c target
[15:58] <pitti> seb128: for hardy I copied the entire directory and cronjob
[15:58] <pitti> and just let them run once a day
[15:58] <seb128> we could do that as well
[16:04] <seb128> pitti, btw is there any known apport breakage that makes apport dialog have a "%s" rather than the software name?
[16:04] <seb128> pitti, that's for crashes
[16:05] <pitti> seb128: not known to me -- where is that exactly?
[16:06] <seb128> pitti, works now, I will keep watching for it
[16:08] <seb128> I got an apport auto opening while I was doing other things and the "Sorry, <software> crashed> ..." usual dialog opened by with a bold "%s" rather than the actual "Sorry software crashed" string
[16:08] <seb128> I'm wondering if it failed to get the name or something
[16:09] <seb128> oh, it's indicator-datetime
[16:10] <seb128> pitti, http://people.canonical.com/~seb128/dialog.png
[16:10] <seb128> pitti, could be a broken translation, let me check
[16:14] <seb128> pitti, I can't spot anything wrong the translation
[16:16] <pitti> bryceh: I implemented support for a DuplicateSignature: field in apport now; https://bugs.staging.launchpad.net/ubuntu/+source/libatasmart/+bug/733894 is a test
[16:16] <ubot2> Launchpad bug 733894 in qbittorrent "torrent constantly paused" [Undecided,Fix released]
[16:16] <pitti> bryceh: i. e. that automatically got a need-duplicate-check tag (so the retracer will process it), and DuplicateSignature field
[16:16] <pitti> bryceh: here /usr/share/apport/package-hooks/libatasmart4.py just set report['DuplicateSignature'] = 'Code42Red'
[16:17] <pitti> bryceh: so xorg hook could do something like "XorgGPUFreeze:<topmost GPU instruction>:<registerwhatnot>..."
[16:17] <seb128> pitti, nice!
[16:18] <pitti> seb128: this allows us to implement auto-duplication much more easily in hooks, for package install failures or GPU freezes
[16:19] <seb128> pitti, do you know what english string should be used in the dialog in the screenshot?
[16:19] <pitti> seb128: will check in a minute, sorry
[16:19] <seb128> pitti, no hurry, so for keeping highlighting your IRC ;-)
[16:21] <pitti> seb128: how did you trigger this?
[16:21] <pitti> seb128: it gets it from self.w('label_heading').get_label(), i. e. from the GtkBuilder file
[16:21] <seb128> pitti, adding a gcalendar in evo with a random user@gmail.com and not entering a password to make indicator-datetime crash
[16:22] <seb128> the crash is bug #724856
[16:22] <pitti> seb128: the default string of the label is &lt;span weight="bold" size="larger"&gt;%s&lt;/span&gt;
[16:22] <pitti> which is pretty much what you see
[16:22] <pitti> so it seems in this case the label test isn't being set
[16:22] <pitti> >>> 'a%sb' % None
[16:22] <pitti> 'aNoneb'
[16:22] <pitti> ok, so it's not a failure to detect the name
[16:22] <pitti> it's not called at all
[16:23] <pitti> hm, but I fail to see where, I guess I need to reproduce this
[16:23] <pitti> seb128: killall -SEGV will do :)
[16:23] <seb128> pitti, no it doesn't
[16:24] <seb128> dunno why
[16:24] <pitti> seb128: btw, the datetime indicator works fine again
[16:24] <pitti> I see my evo appointments again, thanks ted
[16:25] <seb128> pitti, ok you are righty
[16:25] <seb128> kill -11 $(pidof indicator-datetime-service)
[16:25] <seb128> on a working indicator-datetime is doing the same
[16:25] <seb128> it doesn't on indicator-session-service
[16:26] <seb128> so it's something it doesn't like about indicator-datetime
[16:27] <pitti> seb128: ah, can reproduce
[16:28] <seb128> pitti, btw just ran into bug #729223 when searching in apport bugs for this one
[16:28] <ubot2> Launchpad bug 729223 in apport "notifying users of assertion failures is confusing" [Undecided,Confirmed] https://launchpad.net/bugs/729223
[16:28] <pitti> seb128: ah, I can close that then
[16:28] <seb128> pitti, which is basically what I was saying about assertions earlier today, if you want to use the bug to track the "enable assertionr eport"
[16:29] <seb128> pitti, bug #730569, got duplicates 2 days ago it might still be an issue
[16:29] <ubot2> Launchpad bug 730569 in apport "apport-gtk crashed with RuntimeError in /usr/lib/pymodules/python2.7/gi/overrides/Gtk.py: Gtk couldn't be initialized" [Undecided,New] https://launchpad.net/bugs/730569
[16:29] <pitti> seb128: 729223> done, thanks
[16:30] <seb128> bug #730569 I meant
[16:30] <seb128> pitti, sorry I will stop bumping bugs references there ;-)
[16:30] <seb128> I didn't find one about the %s title
[16:30] <pitti> seb128: that's fine -- trying to keep up :)
[16:31] <pitti> seb128: opened in a tab, will get to that
[16:34] <pitti> seb128: %s -> it does work in apport-cli, so I guess it's gtk specific
[16:35] <pitti> seb128: ah, got it
[16:35] <pitti> seb128: it's called "Time & Date", which the label tries to interpret as an entity
[16:36] <seb128> oh
[16:36] <seb128> that makes sense
[16:36] <pitti> one replace('&', '&amp;') later, it works
[16:36] <seb128> ;-)
[16:36] <pitti> I'm sure that there is a quote_html kind of thingy somewhere
[16:37] <seb128> pitti, you should perhaps use g_markup_escape_text
[16:37] <pitti> that's what I was looking for, thanks
[16:37] <seb128> yw
[16:38] <fta> unescape in xml.sax.saxutils too
[16:38] <pitti> works fine
[16:39] <fta> or, the opposite
[16:41] <chrisccoulson> kklimonda, 4 failures now. i might have to abandon this soon, and do more important work ;)
[16:44] <chrisccoulson> note to self - don't let daughter in the room now she knows that my mouse moves things on the screen
[16:46] <sense> How actively is the GNOME 3 PPA maintained? It seems that a number of the packages there need to be rebuilt against the new libgtk-3-0, they currently require the uninstallable libgtk3.0-0.
[16:48] <pitti> seb128: hm, no real idea about the "gtk could not be inited" crash :/
[16:49] <pitti> seb128: it's easy to make it not crash, of course
[16:49] <seb128> pitti, no worry, in fact I confused 2 tabs, I though in was a required_version error still there
[16:49] <pitti> but that would just paper over the problem
[16:49] <seb128> pitti, seems fine to ignore, my bet is that those are crashes on session closing
[16:49] <pitti> seb128: oh, did you still see those?
[16:49] <pitti> ah, could be
[16:50] <pitti> seb128: so perhaps it should just die silently then
[16:50] <seb128> pitti, no, I had a tab open with a bug about those but it's incomplete and got no need duplicates
[16:50] <seb128> new
[16:50] <pitti> after all, crashes will be shown again in the next session then
[16:50] <seb128> right
[16:50] <seb128> pitti, so it's all ok
[16:50] <seb128> pitti, retracers seem unhappy
[16:51] <seb128> pitti, they are both retracing a bug for over half an hour, strace show they do things but it should take a minute to retrace a bug, not half an hour
[16:51] <pitti> erk
[16:51] <seb128> retracing #736547 failed with status: 99
[16:51] <seb128> transient error reported; halting
[16:51] <seb128> ok, they stopped in fact
[16:52] <seb128> let me ran one by hand
[16:55] <seb128> pitti, ok, makes sense now
[16:55] <seb128> The authorization page:
[16:55] <seb128>  (https://launchpad.net/+authorize-token?oauth_token=...
[16:55] <seb128> should be opening in your browser. Use your browser to authorize
[16:55] <seb128> this program to access Launchpad on your behalf.
[16:55] <seb128> wth?
[16:55] <pitti> seb128: forgot --auth?
[16:55] <seb128> pitti, no, it's the cron command
[16:55] <pitti> hm, did we get a new launchpadlib yesterday or so?
[16:55] <seb128> well I copied, paster the cron command without >> log
[16:56] <seb128> no
[16:56] <seb128> pitti, but I switched to natty chroots
[16:56] <seb128> we need to update the token there I guess
[16:56] <seb128> hum
[16:56] <seb128> the user dir should be the same though...
[16:56] <pitti> it should work fine
[16:56] <pitti> we have used that token for a year or so
[16:56] <pitti> also in the natty fakechroots with natty's launchpadlib
[16:57] <seb128> dunno what's going on there
[16:57] <pitti> I'll have a look
[16:58] <seb128> pitti, thanks
[16:58] <pitti> hmm
[16:58] <pitti> why do we have ".lpcookie" as well as "launchpad-credentials"
[16:58] <pitti> they are identical
[16:59] <seb128> it's likely me again when I tried to fix the error that you fixed by cleaning the cache
[16:59] <seb128> I though the name was wrong
[16:59] <seb128> so I did a cp from one to the other just to be sure
[17:01] <pitti> seb128: I just try to refresh it with the new per-computer thingy that LP does these days
[17:01] <seb128> pitti, ok thanks
[17:01] <seb128> pitti, do you want me to run the command again?
[17:02] <pitti> seb128: hang on, not done yet
[17:04] <pitti> seb128: actually no, if I do apport-retrace --auth /tmp/auth 123 -s it works just fine
[17:04] <DBO> #ubuntu-touch
[17:04] <DBO> oops
[17:04] <pitti> seb128: hm, it works well here
[17:05] <pitti> ah, no
[17:05] <pitti> WTF
[17:05] <pitti> seb128: the outside crash-digger works, manual chroot login works, but once the crash-digger starts retracing in chroot it failsl
[17:07] <pitti> impressive unity changelog!
[17:12] <seb128> pitti, you scared didrocks away by saying that it seems ;-)
[17:15] <seb128> pitti, indeed nice list, and seems didrocks was right to spend some time scripting the changelog generation from the launchpad milestoned bugs list
[17:16] <seb128> would be quite some work to write that manually
[17:16] <pitti> absolutely
[17:16] <seb128> pitti, but there are going your chances to catch up on bug closing count ;-)
[17:16] <pitti> no chance on that :)
[17:37] <fta> after each reboot or logout/login, i get a empty desktop. compiz is dead, and the crash file doesn't have the core. just sig11 and a procmap
[17:51] <pitti> seb128: ok, it's not due to lplib, it's some change in fakechroot which stopped working under natty apparently
[17:52] <seb128> pitti, :-(
[17:52] <pitti> seb128: I added a print open(options.auth_file).read() to apport-retrace
[17:52] <seb128> I hate when that happens
[17:52] <pitti> IOError: [Errno 2] No such file or directory: '/tmp/tmpn0xQgF/tmp/auth'
[17:52] <pitti> seb128: I need to leave for today, I'm afraid I'll need to continue tomorrow
[17:52] <pitti> I just don't get why it does work in an interactive chroot
[17:52] <pitti> ah, hang on
[17:52] <pitti> ---- apport-retrace auth file:  /tmp/tmpn0xQgF/tmp/auth
[17:53] <pitti> that's supposed to be /tmp/auth
[17:53] <pitti> I actually might have an idea about it
[17:53] <pitti> but -> tomorrow, sorry
[17:54] <seb128> pitti, no hurry, have a good evening, see you!
[17:54] <seb128> I will go for sport soon as well
[17:54] <pitti> seb128: if you want, you can try reverting http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/natty/apport/ubuntu/revision/1749
[17:55] <pitti> seb128: (just in the local checkout; doesn't affect the install in the fakechroots)
[17:55]  * pitti waves, bye!
[17:57] <seb128> pitti, bye
[19:29] <Ampelbein> kklimonda: your latest update to transmission seems to have broken magnet-links again
[19:30] <kklimonda> Ampelbein: hmm..
[19:30] <kklimonda> Ampelbein: yes, it did
[19:30] <kklimonda> Ampelbein: I'll fix it now
[19:30] <Ampelbein> kklimonda: k, thanks. ;-)
[19:32] <kklimonda> I was trying to get a single Exec line that works for both 11.04 and 10.04
[19:32] <kklimonda> but it looks like it's not going to happen and I'm sad.. ;)
[19:36] <Ampelbein> hmm, no idea besides some hackish if-lsb-release-then-sed in debian/rules
[20:07]  * mterry has been working on eclipse so hard he doesn't feel well and is lying down
[20:09] <kenvandine> mterry, no fun :)
[20:13] <Martiini> how do I search specific repository ?? does this look right -  aptitude search '~S ~i (!~Alaunchpad  ~O"kernel")'
[20:23] <bcurtiswx> mterry, feel better :)
[20:51] <desrt> rodrigo_: ping
[20:53] <desrt> mterry: ping too
[20:54] <mterry> desrt, heyo?
[20:55] <desrt> mterry: i think gnome-power-manager needs a new upload in the gnome3 team ppa
[20:55] <desrt> the libindicator vendor patch needs to be removed
[20:55] <desrt> since it indirectly pulls in gtk2 (conflicting with gtk3 thus causing it to crash on startup)
[20:56] <mterry> desrt, ah, interesting.  why does it indirectly pull in gtk2?  I thought we had gtk3 versions of the appindicator stack
[20:56] <desrt> oh.  if you do then you just need to switch to that version, i guess
[20:57] <desrt> although i'm not totally sure it makes sense to have libappindicator when using gnome-shell?
[20:58]  * desrt is trying not to play politics too much :p
[20:59] <mterry> desrt, it shouldn't hurt, but if it does, I remember the plan of record at UDS being to dynamically switch between experiences, so that a pure GNOME experience could be offered?  But libappindicator does gracefully fallback to status icons
[20:59] <desrt> i think the plan was that we would have GNOME_ME_HARDER
[21:00] <desrt> but i guess that a user who installs the gnome3 ppa is indicating fairly clearly that they want 'upstream experience'
[21:01] <desrt> unless you guys see it as more of a staging ground for the gnome3 stuff you'll be landing next cycle
[21:01] <mterry> desrt, yar, but hopefully we'll be able to reuse the packaging for O
[21:01] <desrt> jinx :)
[21:02] <mterry> desrt, so you don't know of any particular issue with the indicator stuff besides pulling in gtk2?  I suspect that if we get it to build with the gtk3 stack, it should use its fully GNOME fallback
[21:02] <desrt> mterry: i have no complaints if it works
[21:02] <desrt> i can tell you that simply removing the vendor patch fixed it for me
[21:03] <mterry> k
[21:03] <desrt> (the error is that on startup you get the detected-gtk2-and-gtk3-in-same-process assertion)
[21:07] <desrt> gnome-screensaver is also broken due to some gsettings abuse
[21:09] <mterry> desrt, a patch to remove or a patch to add?
[21:09] <desrt> i don't know about that one
[21:09] <desrt> i'll look into it
[21:11] <desrt> i applied to the team
[21:12] <desrt> i think it's caused by you shipping old gsettings-desktop-schemas
[21:13] <desrt> an update there would probably fix it
[21:40] <chrisccoulson> oh, pants, there's going to be an RC2 for firefox
[21:40] <chrisccoulson> micahg^^ ;)
[21:53] <TheMuso> chrisccoulson: lol
[22:35] <chrisccoulson> kklimonda, 0 fails!
[22:35] <chrisccoulson> \o/
[22:35] <chrisccoulson> have you got anything to add before i upload it?
[22:35] <kklimonda> chrisccoulson: no :)
[22:36] <chrisccoulson> cool, i'll do that in a bit, or maybe in the morning
[22:36] <chrisccoulson> 4 failures were actually my fault. i broke an enumerator
[22:36] <chrisccoulson> which ended up being a pain to debug
[22:38] <chrisccoulson> i guess i should forward my patch upstream
[22:39] <kklimonda> chrisccoulson: we do have an older release, but it probably makes sense to forward it as the reference
[22:39] <kklimonda> (upstream has released 1.8 few days ago)
[22:47] <robert_ancell> desrt, You can see the GNOME3 packages that are out of date here: http://people.canonical.com/~platform/desktop/versions.html
[22:47] <robert_ancell> natty version / GNOME3 versions
[22:47] <desrt> hey!
[22:47] <desrt> i like that
[22:48] <robert_ancell> the light green section second from the bottom
[22:48] <desrt> is this vs. debian experimental?
[22:48] <robert_ancell> the only other thing is to have a look at debian, as they might have already done some of the GNOME3 packages
[22:48] <robert_ancell> yes
[22:49] <desrt> no gnome ppa section :)
[22:49] <desrt> er.  column, i mean
[22:49] <desrt> i guess that's not so hard, though :)
[22:50] <desrt> robert_ancell: this page impresses me
[22:50] <desrt> i didn't know that you guys made so much attempt to stay in sync with debian
[22:51] <robert_ancell> the gnome3 column is essentially the ubuntu column and the version after the /
[22:51] <robert_ancell> no, we hate all our upstreams according to the media!
[22:51] <desrt> hmm.
[22:51] <robert_ancell> I spend my day trying to make that page green
[22:54] <desrt> actually, the problem looks to be the opposite of what i thought
[22:54] <desrt> someone *removed* keys from gsettings-desktop-schemas
[22:55] <desrt> which is slightly distressing...
[23:00] <desrt> robert_ancell: so it occurs to me that it's canonical's official policy to have a lot of this page yellow?
[23:00] <robert_ancell> desrt, no, we want it to all be green
[23:01] <desrt> oh.  now i understand the slashes
[23:01] <desrt> you track multiple upstream branches
[23:01] <desrt> and variously follow them in main and in the team ppa
[23:04] <robert_ancell> yup
[23:05] <desrt> got a few minutes to waste on me?
[23:06] <desrt> NOTICE: 'gnome-screensaver' packaging is maintained in the 'Bzr' version control system
[23:22] <seb128> desrt, yellow is "current version but not merged on debian"
[23:22] <seb128> desrt, that increase after the initial merge period
[23:23] <seb128> desrt, btw there is quite some hate around on your "gsettings abort on missing schemas" ;-)
[23:23] <desrt> i guess for bzr-maintained packaging i'm supposed to do the normal thing
[23:24] <desrt> then copy the debian directory back to the bzr folder and 'push' or whatever
[23:24] <desrt> se	ya... i know.  i'm quite close to capitulating :)
[23:24] <seb128> desrt, we got quite some crashers because gsettings-desktop-schemas did renaming
[23:25] <seb128> it's somewhat ridiculous because that's thing you don't especially care about but you get no desktop
[23:25] <desrt> seb128: i think gsettings-desktop-schemas should develop an API policy
[23:25] <desrt> like API staility guaranteed during stable release series
[23:25] <seb128> still your desktop shouldn't crash because the background schemas got renamed
[23:25] <desrt> same as we do for libraries...
[23:26] <desrt> well
[23:26] <desrt> we often see the desktop crashing because some idiot removed g_application_get_type() or something
[23:26] <desrt> :)
[23:27] <seb128> lol
[23:28] <seb128> desrt, bzr maintained package, you mean the desktop ones i.e debian dir only?
[23:28] <seb128> desrt, basically debcheckout source; cd source; bzr bd
[23:29]  * desrt plays with bzr builddeb
[23:29] <seb128> it will grab the tarball for you, unpack and build
[23:29] <seb128> bzr bd-do
[23:29] <seb128> to get in a environement when you can do changes, when you exit0 it will apply those to the vcs
[23:29] <seb128> like you can refresh patches this way
[23:33] <desrt> it seems that i have to do dch -i to tell it about the new version before it wants to fetch the updated tarball?
[23:39] <seb128> desrt, right