[01:23] <jasoncwarner> TheMuso RAOF robert_ancell : what are the chances we don't fly out this weekend? Anyone hear what the ash cloud is doing this weekend?
[01:24] <TheMuso> jasoncwarner: I have been thinking the same thing this morning.
[01:26] <jasoncwarner> TheMuso RAOF most flights out of Adelaide are cancelled this morning. Everything was good until yesterday....
[01:26] <TheMuso> Right, according to local papers here in Syd, all flights will be canceled out of Sydney this afternoon.
[01:29] <jasoncwarner> TheMuso: GAH! fingers crossed about dublin...
[01:32] <TheMuso> Yeah.
[01:32] <TheMuso> The best we can do is keep an eye on the news, and come the end of the week, to call our airlines and get info.
[01:33] <TheMuso> Thats what I've decided to do anyway.
[02:27] <bryceh> heh, sounds like a repeat of last time we were in dublin
[02:27] <bryceh> hopefully no one gets stuck in europe like last time
[02:29] <TheMuso> Dublin, or Brussles?
[02:30] <bryceh> TheMuso, oh wasn't it dublin when the volcano blew?  lts's and sprints seem to bleed together after a while
[03:03] <TheMuso> No, Brussles I believe.
[05:31] <pitti> Good morning
[06:11] <korben> goodmorning to all of u (here it's 8:11am)
[06:20] <TheMuso> Morning pitti.
[07:46] <didrocks> good morning
[07:47] <pitti> bonjour didrocks
[07:48] <didrocks> guten morgen pitti, how are you?
[07:48] <ricotz> good morning
[07:48] <pitti> didrocks: I'm great, thanks! how about you?
[07:48] <pitti> hey ricotz, how is it going?
[07:48] <ricotz> es geht ;)
[07:48] <didrocks> pitti: I'm fine, thanks :) Had to put my graphic card again in the hoven yesterday evening though ::
[07:48] <didrocks> :/
[07:48] <didrocks> hey ricotz
[07:48] <pitti> urgh
[07:48] <didrocks> but it fixed it again, so no complain for now
[07:48] <didrocks> :)
[07:49] <ricotz> i hope you are both fine
[07:49] <ricotz> didrocks, interesting, are often would this work ;)
[07:50] <didrocks> ricotz: we'll see, it's the second time right now. I put the same time than last time well it worked for 4 months. Let's see how it goes :)
[07:50] <pitti> I guess the Apollo folks had to do crazy things like these all the time..
[07:50] <didrocks> heh :)
[07:52] <ricotz> didrocks, i have a broken card which suddenly stopped working (an old 7900gtx) perhaps this could work here too if the problem is similar
[07:55] <didrocks> ricotz: what do you have as graphical effects? Apparently, the caracteristic are blue and white lines on screen (even from the first screen showing the constructor logo)
[07:57] <ricotz> didrocks, in this case it isnt "initializing"/"booting", it stopped working overnight
[07:58] <ricotz> i would think a broken lane might cause every symptom
[07:58] <didrocks> probably yeah
[08:00] <ricotz> didrocks, do you know if there are more ppa builders again soon? it is quite a queue already
[08:02] <didrocks> ricotz: I don't really know, I know that was planned at some point, but I'm not sure something happened. However distros one are free, so better to work on distro? ;) https://launchpad.net/builders
[08:04] <ricotz> didrocks, daily/test builds arent distro friendly ;)
[08:05] <didrocks> ricotz: right, what are you working one for daily build btw? :)
[08:05] <ricotz> this G_CONST_RETURN removal is blocking things a bit
[08:06] <ricotz> didrocks, gnome-shell and dependencies
[08:07] <didrocks> ricotz: oh, you are going on daily build now rather on . version?
[08:08] <ricotz> didrocks, not really daily, but git builds -- but i am doing this since gnome-shell 2.29
[08:09] <didrocks> oh ok
[08:18] <TheMuso> Morning didrocks.
[08:18] <TheMuso> didrocks: Maybe a new card is worth considering at this point. :)
[08:18] <didrocks> hey TheMuso
[08:18] <didrocks> TheMuso: yeah, the thing is my laptop hardware is quite old… and the card still expensive, so I want to push it as far as I can :)
[08:19] <didrocks> then, I'll certainly take a thinkpad :)
[08:26] <didrocks> RAOF: is it known that nvidia-current wants to run away on upgrade? (working fine now with the 3 kernel)
[08:30]  * TheMuso nods.
[08:31] <didrocks> TheMuso: FYI, I pushed the qt-at-spi with fixed LICENSE in our ubuntu-desktop ppa, just porting now the Qt and QML patches to fix instability issue to Qt
[08:31] <TheMuso> didrocks: Ok sweet.
[08:32] <didrocks> then, rebuilding Qt, crossing fingers and such :-)
[08:58] <pitti> aah, Radiance GTK theme \o/
[08:59] <seb128> hey desktopers
[08:59] <pitti> didrocks: as bug 799742 is currently making CD builds fail, would you have a minute to revie?
[08:59] <ubot2> Launchpad bug 799742 in gtk3-engines-unico "[MIR] gtk3-engines-unico" [High,New] https://launchpad.net/bugs/799742
[08:59] <pitti> bonjour seb128
[08:59] <didrocks> pitti: sure, looking
[08:59] <seb128> pitti, hey, thanks for the reminder ;-)
[08:59] <didrocks> hey seb128
[09:00] <pitti> seb128: just barely in time before you showed up :)
[09:00] <seb128> pitti, hum, do recommends make CD build fail? it was supposed to be a recommend
[09:00] <seb128> (the theme)
[09:00] <pitti> seb128: it's a depends of light-themes
[09:00] <pitti> same as murrine
[09:00] <pitti> for light-themes it makes sense, I think
[09:00] <pitti> it -> depends:
[09:00] <seb128> oh ok, I though ken said he would set it as a recommend until it's promoted
[09:00] <seb128> to avoid that sort of issue
[09:01] <seb128> well if didrocks can review it, it's better ;-)
[09:01] <didrocks> no worry, the MIR should be quick to review
[09:01] <didrocks> just pushing a candidate a11y Qt to our ppa first :)
[09:01] <pitti> once it's in main, I'll rebuild CDs
[09:01] <pitti> we haven't had an amd64 build in four days now, due to various component mismatches
[09:01] <didrocks> ken is making a very short… MIR :)
[09:09] <pitti> chrisccoulson: is the ubufox package in a bzr branch as well, or just lp:ubuntu/ubufox? in the latter case, want me to update it to current trunk, to get the home page customization fix into oneiric?
[09:10] <chrisccoulson> hi pitti
[09:10] <chrisccoulson> it's already in oneiric isn't it?
[09:10] <pitti> chrisccoulson: hey, how are you?
[09:10] <chrisccoulson> i'm sure i uploaded it last week ;)
[09:10] <chrisccoulson> i'm good thanks, how are you?
[09:10] <pitti> chrisccoulson: ooh, rad! thanks
[09:10] <pitti> I'm great
[09:10] <seb128> hey chrisccoulson
[09:10] <chrisccoulson> yeah, there we go - https://lists.ubuntu.com/archives/oneiric-changes/2011-June/003118.html
[09:11] <chrisccoulson> hi seb128, how are you?
[09:11] <seb128> I'm fine
[09:11] <pitti> chrisccoulson: I thought you only merged the branch yesterday, and I didn't see a new upload then
[09:11] <seb128> reading through http://status.ubuntu.com/ubuntu-oneiric/canonical-desktop-team-oneiric-alpha-2.html ;-)
[09:11] <pitti> chrisccoulson: seems the last one is from 4 days ago already
[09:11] <pitti> but it's in the changelog, so should be fine
[09:11] <seb128> pitti, I'm wondering if we should create work items for GNOME updates next cycle to avoid that "flat effect"
[09:11] <didrocks> hey chrisccoulson!
[09:11] <chrisccoulson> yeah, i think it's all there :)
[09:11] <chrisccoulson> hi didrocks
[09:12] <pitti> seb128: if many people are working on GNOME, i. e. it falls under the "do package updates" category, that's fine -- but not everyone is
[09:12] <pitti> creating WIs for package updates is a bit excessive IMHO - it just creates even more WIs to keep track of
[09:13] <pitti> but I won't stop you from creating them if you prefer
[09:13] <pitti> but I'm more worried about getting some non-packging development done as well
[09:13] <chrisccoulson> seb128, i was wondering the same for firefox updates too. ie, i already spent a big chunk of this cycle getting lucid and maverick ready for firefox 6, and none of that work had any WI's (which is why my progress appears to be a bit flat so far)
[09:13] <seb128> pitti, no, I was just saying that if having a flat period is an issue we could solve that by adding work items for normal work
[09:13] <pitti> and whether this is a time management issue, or GNOME 3 is buggier than we thought, or people have to work on other things, etc.
[09:14] <pitti> seb128: I don't mind flat periods at all
[09:14] <seb128> well I think we are getting lot of work done
[09:14] <seb128> it just doesn't relfect in count of work items
[09:14] <seb128> so maybe we are not good enough at listing all the things we have to do
[09:14] <pitti> my worries is that we still have some 85 open WIs for a2
[09:14] <pitti> if we had 15, and it would be flat for a week, I'd be entirely happy :)
[09:15] <pitti> e. g. LibO packaging is blocked on upstream releases, default-email-client seems stuck, software-center-ui seems blocked on design feedback, etc.
[09:15] <didrocks> override_dh_install:
[09:15] <didrocks>         dh_install --fail-missing
[09:15]  * didrocks hugs kenvandine :)
[09:16] <seb128> lol
[09:16] <pitti> and stuff like oneconf is probably just not getting manpower
[09:16] <didrocks> (even if it's not really necessary when you only have one package…)
[09:16] <didrocks> pitti: it's getting some work under cover (week-end mostly) :)
[09:16] <seb128> pitti, yeah, I'm reading though the list, some should probably be moved to later iterations
[09:17] <pitti> and http://people.canonical.com/~platform/workitems/oneiric/canonical-desktop-team-oneiric-alpha-2.html#didrocks is just scary -- didrocks, please clone yourself three times
[09:17]  * pitti hugs didrocks
[09:18]  * didrocks hugs pitti
[09:18]  * didrocks hugs pitti
[09:18]  * didrocks hugs pitti
[09:18] <didrocks> done \o/
[09:18] <seb128> didrocks, you can probably move the qa script and zg items to alpha3
[09:18]  * seb128 hugs didrocks pitti
[09:18] <pitti> didrocks2, didrocks3, didrocks4: welcome!
[09:18] <didrocks> pitti: i hope that with the Qt one, it will go down a lot today :)
[09:18] <pitti> cute!
[09:18] <didrocks> seb128: right, those can be moved
[09:18]  * didrocks hugs seb128 back
[09:18] <seb128> didrocks, isn't the cd space qt splitting done?
[09:19] <pitti> didrocks: do you think there are actually Qt modules left which we wouldn't need in a default install?
[09:19] <didrocks> seb128: I still waiting a last one item for it, but we can close the wi, it will be minor anyway
[09:19] <didrocks> pitti: just the -mysql one
[09:19] <didrocks> pitti: but I fear that Qt scripts depends heavily on it
[09:19] <didrocks> the other things are done, we only take the minimum
[09:20] <pitti> libqt4-sql-mysql + libqt4-sql are 120 kB
[09:20] <didrocks> so yeah, I'll close the WI for now as most if done, I'll keep -mysql somewhere in the etherpad
[09:20] <didrocks> so maybe not worth the effort
[09:20] <pitti> not worth spending significant effort (i. e. more than 15 mins) on it
[09:20] <didrocks> ok, it will be more when I looked at the headers
[09:20] <didrocks> so I'll close it!
[09:20] <pitti> yay
[09:21] <didrocks> with a little luck, I'll be able to close 4 WIs today
[09:22] <didrocks> the lightdm will proably wait for the sprint
[09:23]  * pitti hands a bucket of luck over to didrocks
[09:23] <seb128> pitti, mterry: I've dropped the deja-dup mir linking from the spec
[09:23] <seb128> it was counting 2 workitems for deja-dup and duplicity mirs which have already been approved
[09:23] <seb128> those are listed in the whiteboard as well anyway
[09:24] <pitti> for those cases I actually prefer keeping the bug and dropping the whiteboard item (then the WI will be done when the MIR gets processed)
[09:24] <pitti> but *shrug*, no biggie
[09:25] <seb128> pitti, well, the bugs are "in progress" so they show as todo where they got acked
[09:25] <pitti> seb128: oh, that means we can promote?
[09:25] <seb128> pitti, I think they are done but pending on having them seeded or something
[09:25] <seb128> pitti, no, there is a third one which has been bounced back to doko yesterday
[09:26] <pitti> ah, ok
[09:26] <seb128> but I think that should doable today if doko review it
[09:26] <seb128> it was just ubuntu-couch to use dh_python2
[09:26] <didrocks> ok, unico built. All is fine expect that COPYING is LGPL2.1+ and headers are LGPL2+, so technically, it's ok, just weird, I'll ask Cimi to fix it for the next release but won't block on that
[09:27] <seb128> mpt, hi, do you know when bug #588200 will have a design?
[09:27] <ubot2> Launchpad bug 588200 in system-config-printer "Replace standard printing applet with indicator" [High,Confirmed] https://launchpad.net/bugs/588200
[09:32] <didrocks> pitti: MIR done and promoted
[09:32] <pitti> didrocks: merci beaucoup
[09:32] <didrocks> avec plaisir :)
[09:32] <seb128> pitti, do you know why "topic-oneiric-xubuntu" shows up on our page?
[09:32] <didrocks> kenvandine: just look at the license comment on https://bugs.launchpad.net/ubuntu/+source/gtk3-engines-unico/+bug/799742 please when you will be there
[09:32] <ubot2> Ubuntu bug 799742 in gtk3-engines-unico "[MIR] gtk3-engines-unico" [High,Fix released]
[09:32] <pitti> didrocks: did you actually change-override.py it? if so, the bug can be closed
[09:33] <didrocks> pitti: it is closed, isn't it?
[09:33] <pitti> seb128: I don't know; I didn't set up the topics, that was kate; presumably becuase it's still desktop land (just not canonical desktop team)
[09:33] <seb128> pitti, ok
[09:33] <pitti> didrocks: "fix committed"
[09:33] <didrocks> pitti: you should reload :)
[09:33] <pitti> didrocks: ah, now; sorry for the noise :)
[09:33] <didrocks> no worry :)
[09:34] <seb128> pitti, ok, reviewing the WIs it's lot of small and side ones and email client still having lot of todos
[09:34] <didrocks> I fix committed until I change-override normally, but that's just me being picky in case I'm distracted during the promotion and jump on other things :)
[09:34] <seb128> it's all chrisccoulson fault :p
[09:34] <seb128> though a11y has quite some as well
[09:34] <pitti> and LibO
[09:34]  * pitti applauds didrocks' thorough transactional workflow
[09:34] <chrisccoulson> seb128, can i defer the blame to someone else? ;)
[09:35] <pitti> chrisccoulson: always!
[09:35] <chrisccoulson> like, ted. libindicate is being a pain, so it's all ted's fault!
[09:35] <didrocks> everytime it all comes down to ted, poor ted :-)
[09:35] <chrisccoulson> lol
[09:35] <seb128> pitti, right
[09:36] <chrisccoulson> i keep getting empty indicators in the messaging menu with thunderbird, and i can't figure out what's going on :/
[09:36] <seb128> chrisccoulson, that's also the indicator stack taking CD space righT? :p
[09:36] <pitti> chrisccoulson: is there a particular reason why /usr/lib/firefox-5.0/distribution/distribution.ini must have the version in it?
[09:36] <pitti> chrisccoulson: right now, we'd have to rebuild all customization packages with every firefox upgrade
[09:37] <chrisccoulson> pitti - "version=1.0"?
[09:37] <fta> chrisccoulson, same with liferea
[09:38] <chrisccoulson> fta - i can't figure out if i'm doing something wrong or if it's an indicator issue
[09:38] <chrisccoulson> and it doesn't help that the documentation is non-existant ;)
[09:38] <pitti> chrisccoulson: I mean, would it be possible to look in /usr/lib/firefox/ ?
[09:38] <chrisccoulson> pitti - oh, i see what you mean
[09:38] <chrisccoulson> hmmmm, we could symlink it i guess
[09:39] <pitti> chrisccoulson: or should I preemptively create symlinks to firefox-[6789].0?
[09:39] <chrisccoulson> pitti - there is also /etc/firefox/syspref.js now, which can be used for setting preferences
[09:39] <pitti> well, actually not symlinks -- opportunistic diversions rather
[09:39] <chrisccoulson> (if that helps)
[09:39] <zyga> hi
[09:40] <zyga> any xchat-gnome users around?
[09:40] <zyga> xchat-gnome segvfaults on startup since yesterday
[09:40] <zyga> I added ubuntu-desktop/ppa to my system
[09:41] <pitti> ooh
[09:41] <pitti> chrisccoulson: I thought that went away with 4.0
[09:41] <seif__> seb128, didrocks as usual feel free to assign bugs from zeitgeist to me
[09:41] <chrisccoulson> pitti - the global pref folder went away, but i added back a single pref file again
[09:42] <seb128> hey seif__
[09:42] <seif__> we ust worked out some big issues
[09:42] <seif__> such as memory
[09:42] <chrisccoulson> (it means that applications can't drop random preferences in there)
[09:42] <seif__> and still working more
[09:42] <didrocks> seif__: we have to discuss zg integration for while which aren't opened or just plugged usb key btw!
[09:42] <didrocks> s/while/files
[09:44] <pitti> chrisccoulson: well, WDYT is better -- using distribution.ini or syspref.js?
[09:44] <pitti> chrisccoulson: I could then ship /etc/firefox/pref/ubuntu-defaults-foo.js
[09:44] <pitti> at least that seems to exist for apturl and software-center now
[09:44] <pitti> chrisccoulson: hm, but that would only work for [Preferences], not for adding bookmarks
[09:44] <pitti> chrisccoulson: I need a [BookmarksToolbar]/[BookmarksMenu] category for that
[09:44] <pitti> chrisccoulson: unless we want to hack omni.jar's profile in the default package's postinst?
[09:45] <pitti> chrisccoulson: oh, hang on, these are not just preferences, it's actual javascript code? then I guess I could do pretty much anything there
[09:46] <chrisccoulson> pitti - yeah, distribution.ini would be better for that. i'd rather not do anything with omni.jar, as it's ordered in a particular way by the build system
[09:46] <chrisccoulson> pitti - the preference files are confusing. the parser doesn't actually understand javascript ;)
[09:46] <chrisccoulson> perhaps i should just install firefox in to /usr/lib/firefox?
[09:47] <chrisccoulson> that solves some of the current upgrade breakage too
[09:47] <pitti> chrisccoulson: ^ only if you give up on the firefox metapackage and the firefox-X.Y packages and just name them "firefox", I think
[09:48] <chrisccoulson> pitti - there are no firefox-X.Y packages anymore. there is a "firefox-trunk" package, but that installs in to /usr/lib/firefox-trunk-X.Y
[09:48] <pitti> chrisccoulson: ok, so no omni.jar hacking; if syspref.js can't add arbitrary stuff like bookmarks, then I guess it is distribution.ini
[09:48] <pitti> oh, right
[09:48] <pitti> chrisccoulson: then, not much point in versioned paths either?
[09:49] <chrisccoulson> i think the only reason we have a versioned path is because that is what "make install" gives you, but no other distro is actually using that path in their packages
[09:49] <chrisccoulson> we're the only people not using /usr/lib/firefox
[09:53] <pitti> is that hard to change?
[09:53] <chrisccoulson> pitti - i'll have a look at changing that. first of all, i need to look at packages sync'd from debian which install browser plugins in to /usr/lib/firefox/plugins though
[09:53] <chrisccoulson> i've always ignored those in the past because our firefox build ignores them :)
[09:53] <chrisccoulson> but i want to make sure we don't have anything in the archive installing stuff in to /usr/lib/firefox which shouldn't be there, before i change anything
[09:54] <chrisccoulson> pitti - eg, packages doing silly things like https://launchpad.net/ubuntu/+source/pcmanx-gtk2/0.3.9-2ubuntu3
[09:54] <chrisccoulson> (although, i already fixed that one)
[09:58] <didrocks> pitti: can I get extra kudos for Qt in the ubuntu-desktop ppa? seems that the build will start in 16 hours for i386
[09:59] <didrocks> 18 hours on amd64
[09:59] <chrisccoulson> didrocks, join the club! my daily builds are now every other day ;)
[10:00] <pitti> didrocks: you are being mozilla-dailied, it seems
[10:00] <didrocks> chrisccoulson: I'm sure you are the guilty one! :)
[10:00] <didrocks> yeah, this is the mozilla effect :)
[10:00] <pitti> didrocks: nudged
[10:02] <didrocks> pitti: Danke Schön
[10:02] <chrisccoulson> i uploaded these 22 hours ago - https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/thunderbird-aurora/+packages
[10:02] <chrisccoulson> and they're still waiting ;)
[10:02] <chrisccoulson> what happened to all the PPA builders?
[10:03] <pitti> we apparently have fewer
[10:03] <pitti> chrisccoulson: are these blocking you? I can bump their build score to make them jump the mozilla-daily queue
[10:04] <pitti> chrisccoulson: i386 built, though
[10:04] <pitti> daily maverick and lucid builds? that sounds a bit wasteful, though
[10:04] <chrisccoulson> pitti - i'm not too concerned about the daily builds. but i'm going to upload firefox 5 to the firefox-stable PPA in a bit, and that ones quite important as it's a security update for the current firefox-stable PPA users
[10:04] <pitti> chrisccoulson: that uses the ubuntu buildds, right?
[10:04] <chrisccoulson> pitti - no, that one doesn't (the ubuntu-mozilla-security PPA does though)
[10:05] <pitti> ah
[10:05] <pitti> chrisccoulson: well, let me know if you need that bumped then
[10:05] <chrisccoulson> eventually the firefox-stable PPA will go away, when all ubuntu releases are on the same version :)
[10:13] <didrocks> am I the only one with a regularly hidden cursor? (particularly in gedit)
[10:14] <rodrigo_> didrocks, I only see it sometimes in the terminal
[10:14] <pitti> in the terminal it's a feature, though
[10:14] <chrisccoulson> hmmm, thunderbird is telling me how much spam i have in the messaging indicator
[10:14] <rodrigo_> pitti, is it?
[10:14] <chrisccoulson> should probably fix that ;)
[10:14] <pitti> it should go away as soon as you start typing, and come back when you move the mouse
[10:14] <didrocks> rodrigo_: got that quite regularly
[10:15] <pitti> in the past we had a hack called "unclutter" (it's still in the archive), but now it seems to be part of X/GNOME/whatever (I didn't check)
[10:15] <rodrigo_> pitti, ah, right, but it just disappears completely sometimes, even when moving the mouse, and is back when the mouse is out the terminal window
[10:15] <pitti> well, I love it; when that is broken, the mouse constantly gets in the way
[10:15] <pitti> rodrigo_: ok, I don't get that
[10:15] <rodrigo_> but only happens once in a while
[10:16] <pitti> I have mouse in terminal; press a key -> pointer goes away; nudge the mouse -> comes back
[10:16] <pitti> same in gedit indeed, nice
[10:16] <pitti> doesn't work in firefox
[10:16] <pitti> so I suppose it's somewhere in gnome, not X
[10:21] <didrocks> pitti: ok, I know what's wrong regarding my workflow
[10:21] <fta> didrocks, i see it too sometimes, i can usually type, but i don't see the block or vline cursor (not the mouse pointer pitti is talking about), i usually have to give the focus to another app, and go back to the text field to solve this
[10:21] <didrocks> pitti: in gedit, press a key -> pointer goes away, use array keys to navigate, still not there until you move your mouse
[10:22] <didrocks> fta: moving the mouse should work from what I see, the issue is when you navigate with arrow keys
[10:22] <didrocks> s/array/arrow
[10:22] <fta> i do switch between workspaces with the keyboard, and i use the follow focus mode
[10:23] <seb128> pitti, I don't think there is an "unclutter" in GNOME
[10:23] <seb128> pitti, the cursor hidding when typing is done by some widgets like text entries, it's not new, but it doesn't work accross the board
[10:24] <pitti> seb128: ah, so the widgets do that themselves
[10:25] <kinouchou> hello seb128, didrocks and  fredp
[10:25] <seb128> lut kinouchou, ca va bien ?
[10:26] <didrocks> salut kinouchou
[10:27] <chrisccoulson> hmmm, i'm sure my thunderbird issue is really a ted bug. sometimes it works fine and sometimes i just get an empty line in the indicator (and a lozenge with no count in it)
[10:27] <seb128> chrisccoulson, don't spend too much time on bug fixing early in the cycle
[10:27] <seb128> chrisccoulson, dx might have fixed those issues for you before it's debugging time
[10:27] <chrisccoulson> seb128, yeah, but i'd like it to work :)
[10:28] <seb128> pitti, just for info I'm doing a manual run of the lucid retracers to clean the backlog of lucid bugs
[10:28] <pitti> seb128: oh, thanks; I tried yesterday, but the chroots are broken
[10:28] <pitti> seb128: I. e. you run that in the lucid dchroot?
[10:28] <seb128> pitti, the amd64 is running fine for me
[10:28] <seb128> pitti, yes
[10:29] <pitti> ah
[10:29] <pitti> lucid fakechroot in natty dchroot seems broken
[10:29] <seb128> right
[10:29] <kinouchou> yep seb128  and you?
[10:29] <seb128> pitti, that's why we commented the lucid lines in the map file
[10:29] <seb128> pitti, they need to run under lucid and we didn't want to duplicate the directories and the cron job
[10:30] <seb128> pitti, so I manually tweaked the map, run them by hand under lucid and will restore the natty map when i'm done
[10:30] <seb128> kinouchou, I'm great thanks!
[10:46] <pitti> chrisccoulson: do we have some patch in firefox which would force the default search engine to Google? I set browser.search.defaultenginename="Wikipedia", and that appears in about:config, but it's still google
[10:47] <chrisccoulson> pitti - that's also set in ubufox
[10:47] <pitti> and if I set browser.search.order.1 to Wikipedia as well, it starts with Yahoo..
[10:47] <pitti> chrisccoulson: I purged xul-ext-ubufox to rule that out
[10:48] <chrisccoulson> pitti - right, it's google by default in firefox too
[10:48] <chrisccoulson> but we can override them with browser.search.order.1 and browser.search.order.2 etc...
[10:48] <pitti> chrisccoulson: so the browser.search.defaultenginename doesn't actually work?
[10:48] <pitti> chrisccoulson: see above, I already tried that..
[10:48] <chrisccoulson> i don't think so
[10:49] <chrisccoulson> hmmm, that should work
[10:49] <pitti> could I set browser.search.selectedEngine?
[10:51] <chrisccoulson> we shouldn't set that by default, as i think that's meant to be purely a user pref which only exists if the user changed their search engine
[10:51] <pitti> that's what I tought
[10:51] <pitti> thought
[10:52] <chrisccoulson> pitti - did you just try changing the other prefs in about:config, or somewhere else?
[10:53] <pitti> chrisccoulson: in about:config, for testing
[10:53] <pitti> oh, fun
[10:54] <chrisccoulson> pitti - ah, in some cases that won't always work
[10:54] <pitti> browser.search.order.1 == Bing works
[10:54] <pitti> but == Wikipedia doesn't
[10:54] <pitti> ok, I'll set it in distribution.ini then and play around with that; thanks so far
[10:55] <pitti> browser.search.defaultenginename="Bing"
[10:55] <pitti> browser.search.order.1="Bing"
[10:55] <pitti> now it defaults to Amazon.de
[10:55] <chrisccoulson> pitti - for some prefs, firefox will explicitly read the default value (and ignore any user value), although i'm not sure if that's the case here
[10:55] <pitti> is that predictable in any way?
[10:55] <pitti> almost sounds like an off-by-one error in the indexing
[10:57] <pitti> no luck with "Wikipedia (de)" either, and /usr/lib/firefox-addons/searchplugins/de/bing.xml is also just "Bing" (no localized name)
[11:01] <pitti> chrisccoulson: ok, just setting browser.search.defaultenginename = "Wikipedia (de)" works here if I do it in about:config
[11:01] <pitti> but that only seems to work as a per-user key
[11:01] <pitti> not a system-wide key from distribution.ini
[11:02] <chrisccoulson> hmmm, i'm just trying to figure out how it works
[11:03] <pitti> purged firefox-locale-de, but no difference :/
[11:23] <chrisccoulson> pitti - i'm confused why browser.search.defaultenginename worked in about:config, but i can see why it doesn't work in distribution.ini
[11:23] <pitti> chrisccoulson: oh?
[11:23] <chrisccoulson> you're hitting the same issues i had when i tried to migrate our distro preferences in to distribution.ini, which are:
[11:23] <chrisccoulson> 1) The preferences are set after most things have started, and
[11:24] <chrisccoulson> 2) from Firefox POV, they're actually not default preferences, but they appear as user preferences
[11:24] <chrisccoulson> and firefox ignores the user value for defaultenginename
[11:24] <pitti> hm, I thought browser.search.selectedEngine was the per-user one
[11:24] <pitti> (setting that in distro.ini doesn't work either)
[11:25] <chrisccoulson> does it also not change the value in about:config, or is it just that it has no effect?
[11:25] <pitti> chrisccoulson: so since there doesn't seem to be any way to do that in distribution.ini, could we make ubufox change it?
[11:25] <chrisccoulson> if it's the latter, then you're hitting problem 1
[11:25] <pitti> chrisccoulson: about:config is correct wrt. distribution.ini, but doesn't have an effect
[11:26] <chrisccoulson> ok, that's problem 1, i that the pref is set after the search service has initialized :(
[11:26] <pitti> even setting browser.search.selectedEngine reflects in about:config, but doesn't have an effect
[11:26] <pitti> ah, how bad
[11:26] <chrisccoulson> that one is confusing
[11:27] <pitti> chrisccoulson: is that a bug or a feature? (the wrong order)
[11:28] <chrisccoulson> i'll need to think a bit more about this. overriding preferences seems to be very problematic at the moment (even from ubufox, as we get issues like bug 784542, which are a consequence of extensions being loaded after the pref service has already initialized)
[11:28] <ubot2> Launchpad bug 784542 in firefox "Firefox forgets middlemouse.contentLoadURL on every restart (dup-of: 548866)" [Undecided,Invalid] https://launchpad.net/bugs/784542
[11:28] <ubot2> Launchpad bug 548866 in firefox "forgets middlemouse.contentLoadURL on upgrade or browser restart" [Medium,In progress] https://launchpad.net/bugs/548866
[11:28] <chrisccoulson> brb, i need to restart. compiz is behaving like it's filled with glue
[11:28] <pitti> heh
[11:28] <pitti> chrisccoulson: so I'll leave that for now
[11:29] <pitti> it's not a blocker right now
[11:34] <chrisccoulson> oh, my battery is so going to die at the rally next week
[11:34] <chrisccoulson> 47.1% capacity yesterday, and 43.5% capacity today
[11:35] <chrisccoulson> i get the annoying g-p-m warning on every login now (your battery is about to die and the world is going to end)
[11:35] <chrisccoulson> i guess it's not helped by the fact that natty and oneiric use so much power :/
[11:36] <jasoncwarner_> chrisccoulson: but we are getting linux kernel 3, now with more power and better access to the internet?
[11:37] <chrisccoulson> i guess that because 3 > 2 then the new kernel will use 50% more power? ;)
[11:38] <chrisccoulson> i wonder if i can get hold of a new battery before the weekend :/
[11:38] <chrisccoulson> i get about 25 minutes on my laptop atm ;)
[11:39] <jasoncwarner_> chrisccoulson: that is awesome...it is effectively 25 minutes better than a desktop
[11:39] <jasoncwarner_> nice
[11:39] <chrisccoulson> lol
[11:39] <chrisccoulson> that's a good way to put a positive spin on things :)
[11:40] <pitti> chrisccoulson: no AC brick?
[11:40] <pitti> well, obviously you have one
[11:40] <chrisccoulson> pitti - yeah, i just have to stay connected to it permanently atm
[11:40] <pitti> I mean, at the rally
[11:40] <jasoncwarner_> chrisccoulson: Always look on the light side of life
[11:40] <jasoncwarner_> http://www.youtube.com/watch?v=WlBiLNN1NhQ
[11:41] <chrisccoulson> yeah, i might actually have to bring the AC brick i have connected to my docking station, as opposed to the more slimline charger
[11:41] <chrisccoulson> it's double the power ;)
[11:41] <chrisccoulson> jasoncwarner_, lol ;)
[11:42] <pitti> jasoncwarner_: I can't see that in Germany -- is it the Monty Python song in Life of Brian?
[11:42] <jasoncwarner_> yeah...
[11:43] <jasoncwarner_> pitti: you can't see it in germany? I thought only AU was held out of seeing interesting web clips....
[11:44] <chrisccoulson> hmmm, thunderbird seems to behave differently when i use chromebug. i may have to resort to logging some console messages instead to figure out why things aren't working :/
[11:45] <chrisccoulson> seb128, the good thing is that it shows an indicator also for non-Inbox messages :P
[11:45] <chrisccoulson> does evolution do that? ;)
[11:45] <chrisccoulson> :-)
[11:46] <didrocks> chrisccoulson: hum, how does this work when I have 30 folders like I do?
[11:47] <chrisccoulson> didrocks, the spec says we should only show 6 folders, which it currently ignores. i'm still working out how we should handle that
[11:47] <chrisccoulson> note, it only displays an indicator for mail folders which get a new message
[11:48] <pitti> chrisccoulson: do you want me to file a bug report for the non-working browser.search.defaultenginename, or is there one already?
[11:48] <chrisccoulson> i'll probably collapse them in to per-account indicators and combine the counts, or something like that
[11:48] <didrocks> chrisccoulson: right, but I don't want my indicator to turn blue for every new email received in -changes
[11:48] <pitti> chrisccoulson: if it's too hard to fix in ffox itself, we might put a workaround into ubufox? I don't mind making the package depend on ubufox if the user specifies a default search engine
[11:48] <chrisccoulson> pitti - does it not work if you set it in /etc/firefox/syspref.js either?
[11:49] <pitti> chrisccoulson: let me try
[11:49] <chrisccoulson> pitti - the issue is that overriding browser preferences from extensions in general seems to be a bit fragile, due to the fact that extensions don't exist when most of the browser starts
[11:49] <chrisccoulson> i think we're abusing the preference system a bit :)
[11:49] <pitti> hm, if "default search engine" isn't a preference, what is?
[11:51] <pitti> chrisccoulson: doesn't work in syspref.js either
[11:54] <chrisccoulson> hmmm, that sounds like a bug then. looking at the pref code, it looks for the default engine there first, and then falls back to search order if it doesn't contain a valid engine (or it contains a hidden engine)
[11:55] <chrisccoulson> s/pref code/search code/
[12:01] <pitti> chrisccoulson: I'll file it then
[12:10] <chrisccoulson> b'ah, damn you jsctypes!
[12:10] <chrisccoulson> i didn't realize when a C function returns a string, i need to actually convert it back to a jsval
[12:11] <chrisccoulson> aha, https://developer.mozilla.org/en/js-ctypes/js-ctypes_reference/CData#readString%28%29
[12:14] <chrisccoulson> wooh, t'works!
[12:18] <seb128> chrisccoulson, speaking of which I need to check, I noticed that evolution-indicator has a gconf key to watch only the inbox set to true by default
[12:18] <seb128> chrisccoulson, so it might do other boxes as well ;-)
[12:18] <chrisccoulson> heh
[12:18] <chrisccoulson> i can add a pref too :P
[12:18] <seb128> chrisccoulson, you better find CD space first :p
[12:20] <rodrigo_> seb128, oh, it just monitors the inbox, that explains why it didn't show correct data for me
[12:21] <seb128> rodrigo_, right
[12:21] <seb128> it's njpatel's fault
[12:21] <rodrigo_> :)
[12:21] <seb128> I changed the gconf key let's see how it goes
[12:21] <seb128> the description mentions "notifications", dunno if that applies to the indicator as well
[12:22] <chrisccoulson> what's the key?
[12:22] <seb128> chrisccoulson, /apps/evolution/eplugin/evolution_indicator/only_inbox
[12:22] <chrisccoulson> thanks
[12:22] <seb128> yw
[12:23] <seb128> ok, I could stop being lazy and grep the code :p
[12:24] <seb128> chrisccoulson, not sure how tb handle that but another thing I don't like is that it clears the counts when evolution is focussed
[12:25] <seb128> clearing the indicator color is fine but it should keep the counts to the unread ones
[12:25] <chrisccoulson> seb128, for thunderbird, it clears the counts when you select the folder and read an unread message (rather then focusing it)
[12:25] <chrisccoulson> clearing the count is part of the spec
[12:25] <didrocks> seb128: it works like that last time I checked
[12:26] <seb128> didrocks, "like that" being?
[12:26] <seb128> it keeps the count?
[12:26] <didrocks> seb128: if you don't check "only inbox", you will have the sum and notification of all folders
[12:26] <seb128> oh ok
[12:26] <didrocks> which I don't want, with -changes and other mailing list, I don't want to be spammed every 30s…
[12:26] <seb128> why is that not the default?
[12:26] <chrisccoulson> the count is meant to indicate the number of unread messages since you last viewed the mailbox
[12:26] <seb128> didrocks, the spec says it should do it up to 6 boxes
[12:26] <didrocks> seb128: the design on the wiki told to only check the inbox
[12:27] <seb128> didrocks, no, it says to display all the boxes up to 6
[12:27] <didrocks> I think it was 6 inboxes, aren't it?
[12:27] <chrisccoulson> yeah, i'm following what's on the wiki, rather than what evo does :)
[12:27] <didrocks> ok, anyway, it's all boxes, which is suboptimal anyway :)
[12:27] <chrisccoulson> we could probably add a "ignore messages with this header" for the -changes spam use-case
[12:28] <seb128> ideally you would opt in boxes you care about
[12:28] <seb128> but I guess we are in geek land
[12:28] <chrisccoulson> yeah
[12:28] <seb128> normal users have an inbox only ;-)
[12:28] <chrisccoulson> that's adding a lot of complexity too. i want to get the basics working first :)
[12:29] <seb128> didrocks, ok, that inbox_only preference is buggy
[12:29] <seb128> I just got a notification that I receive 2 new messages and the icon turned blue
[12:30] <didrocks> seb128: oh really? was working in last november IIRC
[12:30] <seb128> but there is no box which contains messages listed
[12:30] <seb128> it still list only my inbox in the indicator
[12:30] <didrocks> I remember to fix something in that area
[12:30] <didrocks> hum
[12:30] <seb128> well maybe I should restart the indicator ;-)
[12:30] <seb128> the unity icon has a count of "2" though which is right
[12:31] <didrocks> seb128: more possible that you have to restart the indicator
[12:31] <didrocks> more than possible*
[12:31] <seb128> ok
[12:32]  * didrocks just implemented oneconf sync and push to a mock infra (file-based, will be better for auto tests)
[12:33] <didrocks> hum, need to send dbus signal and bind that with my mainloop now
[12:38] <seb128> ok, lucid retracing backlog cleared, retracer back on natty, oneiric mode
[12:49] <didrocks> qt successfully built \o/ Let's see :)
[13:13] <lool> Hey folks
[13:13] <lool> I'm having some issues lately and wanted to discuss some solutions
[13:13] <didrocks> hey lool
[13:14] <chrisccoulson> hi lool
[13:14] <lool> First, ssh-agent isn't started anymore on desktop login; it seems /etc/lightdm/Xsession doesn't set OPTIONFILE like /etc/X11/Xsession does, and this breaks the scripts from /etc/X11/Xsession.d
[13:14] <lool> (hey didrocks, chrisccoulson!)
[13:15] <lool> The easy fix would be to set OPTIONFILE=/etc/X11/Xsession.options in /etc/lightdm/Xsession, but it doesn't feel quite right; I have to challenge why lightdm is not using /etc/X11/Xsession but its own?
[13:15] <didrocks> I know that robert wanted to check one by one each file sourced and only include them if really needed to reduce clutter (as there is no standard way as of today), so better to check this with him
[13:15] <lool> Xresources don't appear to be setup properly; I get reversed video in xterm, I suspect it's the same Xsession thing
[13:16] <didrocks> probably, there is a similar discussion about /etc/environment which isn't source as of today for the same reason
[13:16] <lool> The concept of /etc/X11/Xsession.d is that you drop a file there and it get picked up; it's a bit heavy because it's shell-ish, but ISTR that pitti had timed a login and it didn't seem that bad when compared to other session startup pigs (nautilus, compiz and gnome-panel back then)
[13:17] <lool> I don't really see how sourcing Xsession.d scripts one by one would work: they rely on stuff provided by /etc/X11/Xsession and we'd have to duplicate the whole interface
[13:18] <didrocks> lool: right, I know, and all our session systems (gconf path, compiz profile) are relying on that. it's still sourced because I showed that to robert, not source about /etc/X11/Xsession directly though
[13:18] <didrocks> s/source/sure
[13:18] <lool> I do sympathize with revisiting the whole Xsession.d approach, but less with a lightdm-specific solution
[13:18] <didrocks> lool: I think for those, it will be easier to directly speak with robert (maybe as a sprint goal? see which files needs to be sourced)
[13:19] <didrocks> agreed
[13:19] <lool> Note that Linaro is not coming to the rally; I am however coming for a couple of days
[13:19] <lool> (Wednesday - Friday)
[13:19] <lool> didrocks: Yeah, sorry for using you as a mirror to discuss the changes; I'll copy-paste the chat to Robert
[13:19] <didrocks> lool: can you write that somewhere so that it's on the agenda? (also the etherpad in /topic can be a nice place to write that down)
[13:23] <lool> davmor2: added to pad; thanks
[13:23] <lool> err s/davmor2/didrocks
[13:23] <lool> davmor2: sorry
[13:23] <didrocks> :)
[13:24] <rodrigo_> ok, lunch time, bbl
[13:24] <lool> (terminal being reversed makes it almost unreadable  :-)
[13:26] <lool> didrocks: Ok; now for a compiz one  :-)
[13:26] <pitti> lool: or, rather, I took the expensive bits out and change them from external programs to shell builtins :)
[13:27] <lool> didrocks: start xterm, and Ctrl-click on it to open an embedded menu
[13:27] <lool> pitti: ISTR that your conclusion was that we could keep it as it and still get decent login speed; but then maybe we hit the point where this isn't true anymore
[13:28] <pitti> right
[13:28] <pitti> lool: well, that was true with the Xsession.d scripts we had back then
[13:28] <lool> pitti: I feel Xsession.d duplicates other mechanisms we have and there is overlap betweem all the systems we want to support (GNOME, XDG, compiz, Xsession.d) but Xsession at least had the merit to try to be desktop agnostic; it does a bit too much to my taste, but I currently can't live without it
[13:28] <pitti> the ones shipped by x11-common are alright now
[13:28] <seb128> lut lool
[13:28] <lool> seb128: hey!
[13:29] <seb128> lool, do you know why gdm has its own Xsession script? ;-)
[13:29] <lool> pitti: You have to wonder whether it's right to run ssh-agent for instance
[13:29] <seb128> lool, I think robert_ancell didn't want to just copy old way to do things without understanding why they are done and if we could do better
[13:29] <pitti> lool: I don't see anything heavyweight in my Xsession.d/ right now; most scripts just set some extra variables and do some stating
[13:29] <lool> seb128: I think it's because they don't have a common one in all distros, so they just provide one
[13:30] <didrocks> lool: hum, you mean the xterm warning?
[13:30] <lool> didrocks: sorry, got interrupted; now move your mouse to highlight the entries
[13:30] <pitti> lool: ssh-agent was indeed one of the remaining nontrivial things, and we discussed it extensively back then; but we didn't find a better way to deal with it
[13:30] <lool> didrocks: some black (or white?) lines persist in the menu after highlight/dehighlight
[13:30] <didrocks> lool: Ctrl + click gave me a warning and no menu at all
[13:30] <pitti> lool: also, it takes way less than 0.1 seconds even on the slow Atom in the mini 10
[13:30] <seb128> lool, better to drop an email to robert_ancell or open bugs for things you have issues with
[13:30] <lool> didrocks: wow
[13:31] <didrocks> Warning: Cannot convert string "-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*" to type FontStruct
[13:31] <seb128> lool, I think he will bring back was is needed but he wanted to do it only after understanding the reason and trying to figure if we can do better
[13:31] <davmor2> lool: forgiven don't do it again ;)
[13:31] <didrocks> so I can't even got as far as you are :)
[13:31] <lool> pitti: there's also a gpg-agent, right?
[13:31] <seb128> gnome-keyring is the gpg agent nowadays
[13:31] <lool> there's also handling of user resources and xsession -- that's ok
[13:31] <pitti> lool: I think we eliminated that
[13:32] <lool> pitti: I have one running here, maybe I start it in some other way
[13:32] <pitti> lool: oh, it's in /etc/X11/Xsession.d/60seahorse-plugins, right
[13:33] <pitti> lool: we just don't install seahorse-plugins by default
[13:33] <seb128> pitti, that's deprecated
[13:33] <lool> there's also use-session-dbus
[13:33] <seb128> pitti, gnome-keyring3 does gpg
[13:33] <pitti> seb128: oh, nice
[13:33] <pitti> indeed, seems to be a no-op, and seahorse-plugins is empty
[13:33] <lool> pitti: I guess I'm looking at a relatively old system which I upgraded over the years
[13:34] <seb128> pitti, seems like you just have seahorse-plugins uninstalled and we don't clean the conffile as we should?
[13:35] <lool> didrocks: sounds like something sets a font which isn't available...
[13:35] <lool> didrocks: that's likely in your system-wide or user X resources
[13:35] <lool> You can try setting XTerm.VT100.faceName
[13:35] <seb128> pitti, do you want to review https://code.launchpad.net/~gunnarhj/language-selector/oneiric/+merge/64270
[13:35] <seb128> ?
[13:35] <seb128> pitti, it's a lightdm dmrc support for l-s
[13:37] <didrocks> lool: I will shortly, I put what you told in a note. Will be an easy way to see if there is missing destructor events
[13:37] <lool> Now another small one I wanted to mention: some packages don't appear to have followed transitions: rhythmbox-ubuntuone-music-store seems uninstallable for some weeks now; indicator-applet seems to rely on old libpanel-applet -- I guess that's just a NBS rebuild away; I've pushed it to my PPA to see
[13:38] <lool> didrocks: Thanks; I would have liked someone to reproduce before I file a bug; I could try downgrading xterm to see if it's a recent regression, but history was relatively hard against compiz in the last months  ;-)
[13:39] <pitti> lool: rhythmbox-ubuntuone-music-store needs porting to GTK3 and GI, so I added a breaks to RB 3
[13:39] <seb128> lool, right, the music store is having an issue that they try to support 2 players on different gtk versions :p
[13:39] <didrocks> lool: right, but compiz didn't change a lot since natty this time, but it can be guilty of course ;)
[13:39] <lool> pitti: is this on the plate of the U1 team?
[13:39] <lool> seb128: ah I see what you mean
[13:39] <pitti> that'd be my gut feeling, yes
[13:39] <seb128> lool, indicator-applet is not "just a NBS", gnome-panel switched to gtk3 so the indicator stack needs to be ported to GTK3
[13:39] <lool> They want to support backports but can't backport gtk+ to e.g. lucid
[13:39] <lool> gtk+-3.0 that is
[13:40] <seb128> lool, it's ongoing work and should land before the end of the rally, but it's far from being trivial work
[13:40] <lool> Ok; I understand why these were held up for so long now
[13:40] <seb128> lool, we need to dual build every lib for gtk2 and gtk3 and then port and dual build every indicator
[13:40] <seb128> lool, unity is still on gtk2 as well, the next upload will be gtk3
[13:40] <seb128> lool, it's coming together, just took some work ;-)
[13:41] <seb128> lool, since you can't load gtk2 and gtk3 from a same process it's making those transition so fun game ;-)
[13:42] <pitti> do we really need dual builds?
[13:42] <seb128> yes
[13:42] <seb128> xfce is on gtk2
[13:42] <pitti> do we still need to support GTK2 indicators in oneiric?
[13:42] <pitti> oh
[13:44] <lool> seb128: Yeah, I undestand  :-/
[13:44] <seb128> pitti, did you see my language-selector ping? or should I rather ask mvo about those? not sure who is maintaining l-s nowadays
[13:44] <seb128> pitti, https://code.launchpad.net/~gilir/language-selector/lubuntu-integration/+merge/64917 as well, seems trivial but I'm not sure how the pkg list works there
[13:45] <lool> xfce > ouch
[13:45] <lool> do they have a gtk3 plan?
[13:45] <pitti> seb128: no, I didn't see your ping; I still don't see it, was it here?
[13:45] <seb128> pitti, 14:35 "<seb128> pitti, do you want to review https://code.launchpad.net/~gunnarhj/language-selector/oneiric/+merge/64270 "
[13:45] <seb128> " pitti, it's a lightdm dmrc support for l-s"
[13:45] <lool> Ok; last minor cut is some icon issues on the lightdm greeter; the top right corner has two broken icons when I remove gnome-icon-theme-full
[13:45] <charlie-tca> xfce plan is to use gtk2 through Xfc3 4.10, which is due in January
[13:45] <pitti> seb128: l-s is a shared thing these days between GunnarHj, mvo, and me
[13:46] <mvo> seb128: I'm fine doing work on it, however answers first I guess :)
[13:46] <seb128> lool, bug #796793
[13:46] <ubot2> Launchpad bug 796793 in lightdm "accessibilty and shutdown menu are missing icons" [Medium,Triaged] https://launchpad.net/bugs/796793
[13:46] <pitti> seb128: I can have a look
[13:46] <lool> thanks
[13:46] <seb128> charlie-tca, so next cycle for the lts you will be on gtk3 right?
[13:47] <seb128> hey mvo ;-) deal with pitti I guess ;-)
[13:47] <seb128> pitti, mvo: not sure if the lubuntu request on https://code.launchpad.net/~gilir/language-selector/lubuntu-integration/+merge/64917 would make l-s install chromium though?
[13:47] <seb128> or is it smart to just install the translations matching what you have installed?
[13:47] <pitti> seb128: no, it won't -- it's magic!
[13:47] <pitti> seb128: in particular, this says:
[13:48] <pitti> tr::chromium-browser:chromium-browser-l10n
[13:48] <seb128> I guess it checks for the first package to install the second?
[13:48] <charlie-tca> no, it looks like gtk2 for 12.04
[13:48] <seb128> charlie-tca, no way
[13:48] <pitti> "If the package chromium-browser is installed, then install chromium-browser-l10n-LANG"
[13:48] <pitti> seb128: correct
[13:48] <seb128> pitti, great ;-)
[13:48] <charlie-tca> seb128: that is the current plan for xfce
[13:48] <seb128> charlie-tca, well you better figure a way to do without anything from Ubuntu then I guess, we will not keep dual build for indicators etc in the lts
[13:48] <pitti> seb128: that's a lot more flexible and dynamic than our old static language-support-* stuff, which required everything to be in main, and was only really useful for packages in the standard install
[13:49] <charlie-tca> They are looking at january 2013 to go to GTK3
[13:49] <seb128> pitti, indeed, seems great ;-)
[13:49] <seb128> 2 years to port to gtk3? doh :-(
[13:49] <charlie-tca> seb128: Thanks for the heads up. I have hopes they will go to gtk3 earlier
[13:50] <seb128> lool, speaking about the lightdm greater, it's really an hello world greater to allow log in ;-)
[13:52] <seb128> bah bug #800136
[13:52] <ubot2> Launchpad bug 800136 in gnome-control-center "Minimized panel in thumbnail screen is a gnome-shell panel " [Wishlist,Triaged] https://launchpad.net/bugs/800136
[13:52] <pitti> seb128, mvo: merged, uploading now
[13:52] <seb128> pitti, \o/
[13:53] <mvo> thanks!
[13:54] <seb128> pitti, did you merge gunnar's lightdm one as well?
[13:55] <pitti> no, seems I missed that from IRC, too
[13:55] <lool> seb128: Sure
[13:55] <seb128> pitti, hum, do you filter me out? I copied it again after you said you missed the first ping
[13:55] <seb128> pitti, 14:35 and 14:15 in the channel
[13:55] <seb128> ups
[13:55] <seb128> 14:15
[13:55] <seb128> 14:45
[13:55] <seb128> can't type!
[13:55] <pitti> ah, seems I thought you just repeated gilir's one
[13:56] <seb128> no, that was the first ping you missed ;-)
[13:56] <seb128> https://code.launchpad.net/~gunnarhj/language-selector/oneiric/+merge/64270
[13:57] <pitti> seb128: doing
[13:57] <seb128> thanks
[13:57] <seb128> mvo, https://code.launchpad.net/~evfool/synaptic/fix791135/+merge/63092
[13:57] <seb128> mvo, can you review that one?
[13:57] <seb128> mvo, https://code.launchpad.net/~evfool/synaptic/fix206555/+merge/63100 as well
[13:57] <seb128> mvo, https://code.launchpad.net/~evfool/synaptic/fix157574/+merge/63104
[13:58] <seb128> mvo, sorry, cleaning the sponsoring list a bit ;-)
[13:58] <mvo> seb128: sure thing!
[13:58] <seb128> mvo, danke!
[13:58] <pitti> seb128: are you piloting today?
[13:58] <seb128> pitti, I was yesterday it seems but I missed it so I will pilot this afternoon in exchange
[13:59] <seb128> so "yes" ;-)
[13:59] <mvo> seb128: autopliot, eh?
[14:10] <seb128> bigon, hi, do you think you could update json-glib in debian? tedg did the update in https://code.launchpad.net/~ted/ubuntu/oneiric/json-glib/0.13.4/+merge/65263 but I would prefer staying in sync if we can
[14:10] <seb128> (0.13.2 to 0.13.4)
[14:41] <didrocks> orca seems to tell that it's happy with Qt a11y :)
[14:41] <didrocks> for people waiting to test: install qt and qt-at-spi from the ubuntu-desktop ppa
[14:41] <didrocks> then, by default, a11y isn't activated
[14:42] <didrocks> if you want to activate it: export QT_ACCESSIBILITY=1
[14:42] <didrocks> (should make some application a little bit more crashy, but it's acceptable for now)
[14:46] <lool> Turns out that the xterm reverse video issue was a separate one
[14:46] <lool> reported LP #800193 and LP #800192, first has a patch
[14:46] <ubot2> Launchpad bug 800193 in lightdm "Bogus handling of Xresources dir" [Undecided,New] https://launchpad.net/bugs/800193
[14:46] <ubot2> Launchpad bug 800192 in lightdm "Sources Xsession.d but doesn't setup required env vars" [Undecided,New] https://launchpad.net/bugs/800192
[14:46] <lool> second has a workaround
[14:48] <RAOF> didrocks: Yes, it's known that upgrades will want to remove nvidia-current ATM.  nvidia-current needs to be updated to handle the multiarch mesa, so it'll be broken until that happens.  I've sent a patch to tseliot; it should be soon.
[14:48] <didrocks> RAOF: nice to know! ;) how come you are not sleeping btw? ;)
[14:48] <seb128> mvo, should bug #798882 be acked?
[14:48] <ubot2> Launchpad bug 798882 in gdebi "Sync gdebi_0.8~exp2 (main) from Debian experimental (main)" [Wishlist,New] https://launchpad.net/bugs/798882
[14:49] <mvo> seb128: probably, let me double check
[14:51] <RAOF> didrocks: I'm not as far in the future as normal; I'm in Perth at the moment :)
[14:52] <didrocks> RAOF: oh ok :-)
[14:53] <seb128> be careful, you might land in an european tz soon if you keep it this way!
[14:54] <RAOF> Heh.  I'll be in one in 5 days anway!
[14:57] <ogra_> hmm, is bug 798546 g-p-m or libindicator ?
[14:57] <ubot2> Launchpad bug 798546 in gnome-power-manager "No Battery state indicator in Unity Panel " [Undecided,Confirmed] https://launchpad.net/bugs/798546
[15:00] <bigon> seb128: I'ill have a look
[15:00] <seb128> bigon, thanks
[15:03] <seb128> ogra_, likely gpm, pitti mention it, not worth debugging though both gpm and the status icon are going away this cycle
[15:03] <seb128> hum, mention -> mentionned
[15:03] <ogra_> uhm, but i will still see my battery charge thats left if on battery, right ?
[15:04] <chrisccoulson> ogra_, you will have to guess it
[15:04] <chrisccoulson> ;)
[15:04] <seb128> ogra_, don't you get blinking leds on armel when the battery runs empty?
[15:04] <seb128> ;-)
[15:05] <chrisccoulson> heh
[15:05] <ogra_> seb128, well, i tend to adjust stuff like brightness etc based on the time left shown in the power statistics
[15:05] <chrisccoulson> actually, why do you need that? isn't battery life on armel infinite?
[15:05] <seb128> joke aside they are moving the service code to gnome-settings-daemon and dropping the status icon
[15:05] <seb128> the indicator will become a proper indicator rather than a gpm patch then
[15:06] <ogra_> right, so visually not much will change then
[15:06] <seb128> so you will get an indicator and g-s-d doing the notification, key handling, etc
[15:06] <seb128> no, but with some luck less bugs
[15:06] <seb128> new code, cleaning, etc
[15:06] <ogra_> chrisccoulson, my ac100 eats between 4 and 5W which means a difference of 2h runtime
[15:07] <seb128> nessita, hey
[15:07] <seb128> nessita, how are you?
[15:07] <seb128> nessita, mvo: was there anything blocking https://code.launchpad.net/~mvo/ubuntu-sso-client/dh_python2/+merge/64154 from just being uploaded?
[15:07] <nessita> hey seb128! my power supplier is very unstable today, apparently
[15:07] <ogra_> so adjusting power properties while checking the wattage really helps if i need longer battery time
[15:08] <ogra_> chrisccoulson, btw, on your intel laptop your CPU alone eats 5W
[15:08] <nessita> seb128: hum, I need to review that, let me do it asap
[15:08] <chrisccoulson> ogra_, mine probably eats more than that!
[15:08] <seb128> nessita, ok, thanks
[15:08] <ogra_> heh
[15:08] <chrisccoulson> battery life for me is closer to 2 minutes than 2 hours, literally ;)
[15:08] <seb128> nessita, no hurry, I'm just patch piloting and it's in the review queue
[15:08]  * highvoltage switched to SSD last week and got a whole extra hour \o/
[15:09] <ogra_> and speedier disk accesses ;)
[15:09] <highvoltage> for sure
[15:09] <dobey> i wish 1.8" SSDs weren't so expensive
[15:10] <didrocks> can anyone try the ubuntu-ppa with the new qt and tell me if they can still launch qmlviewer for instance?
[15:10] <didrocks> (or unity-2d-panel)
[15:12] <seb128> didrocks, you can't?
[15:12] <seb128> didrocks, can do in a bit if nobody else does before ;-)
[15:13] <didrocks> seb128: it's not working, seems to block on an unix socket read
[15:13] <didrocks> seb128: thanks
[15:13] <didrocks> seb128: first, please ensure it works for you before an upgrade :)
[15:13] <seb128> ok
[15:14] <didrocks> not sure if it's a local issue, it seems to block everytime on the same socket
[15:16] <seb128> didrocks, is i.e mumble blocking as well?
[15:16] <didrocks> I tried to launch small Qt example, didn't try mumble, one sec
[15:16] <didrocks> hum, mumble is blocking now, yeah
[15:17] <didrocks> always on the same socket
[15:17] <didrocks> on the read operation from this socket: connect(14, {sa_family=AF_FILE<EMAIL_ADDRESS>22) = 0
[15:18] <seb128> didrocks, is there a binary I should get from the ppa or just upgrade?
[15:18] <seb128> didrocks, when you say ubuntu-ppa it's ubuntu-desktop ppa?
[15:18] <didrocks> seb128: just upgrade if you don't want to test accessibility, just the new qt with some accessibility add on
[15:18] <didrocks> seb128: yeah, ubuntu-desktop/ppa
[15:18] <seb128> ok
[15:18] <didrocks> hum, it seems it's my current session which is screwed
[15:19] <didrocks> can't launch a new instance of gedit
[15:19] <seb128> ok
[15:19] <nessita> seb128: the branch makes sense to me, though I'm not very familiar with dh_python2 so I'm not sure if there is any specific there that needs to be corrected
[15:20] <didrocks> hey nessita
[15:20] <nessita> hey didrocks!
[15:20] <seb128> nessita, don't worry about that it's likely fine, I just wanted to check with you before uploading your package
[15:20] <seb128> brb
[15:37] <bigon> seb128: I've uploaded json-glib
[15:37] <seb128> re
[15:37] <seb128> bigon, thanks!
[15:38] <bigon> mmmh gir pkg should be renamed gir1.2-json-1.0 instead of gir1.2-json-glib-1.0
[15:42] <didrocks> re
[15:42] <didrocks> hum, seems that the reboot made everything working well
[15:43] <seb128> didrocks, so local issue ;-)
[15:43] <seb128> chrisccoulson, could you review, sponsor https://bugs.launchpad.net/ubuntu/+source/tuxguitar/+bug/797887 ?
[15:44] <ubot2> Ubuntu bug 797887 in tuxguitar "Please merge tuxguitar 1.2-8 (universe) from debian unstable" [Undecided,Confirmed]
[15:44] <didrocks> seb128: yeah, kind of scary to have ICE blocking like that…
[15:44] <seb128> chrisccoulson, I'm not sure to understand why we need the 03-no-mozilla.patch, should that be sent to debian?
[15:44] <chrisccoulson> seb128, we need that because we switched off mozilla support in swt-gtk
[15:45] <seb128> hum ok, the changelog was not clear about that ;-)
[15:48] <tseliot> RAOF, didrocks: my code for nvidia is ready, I'd like to do the same for fglrx and then upload
[15:49] <didrocks> tseliot: excellent, thanks a lot :)
[15:49] <tseliot> :)
[15:56] <hrw> hello
[15:56] <hrw> can someone help me with bug 793580?
[15:56] <ubot2> Launchpad bug 793580 in evolution "no way to set fixed-width font for reading emails" [Undecided,Incomplete] https://launchpad.net/bugs/793580
[15:58] <seb128> hrw, hi, try #evolution on irc.gnome.org?
[16:00] <hrw> seb128: thx
[16:00] <hrw> 17:00 [gnome] -!- ERROR Closing Link<EMAIL_ADDRESS>(No more connections allowed in your connection class)
[16:00] <hrw> 17:00 [gnome] -!- Irssi: Connection lost to irc.gnome.org
[16:00] <hrw> ;(
[16:01] <cyphermox> hrw: my guess is your messages are being displayed as HTML, not plain text. Plain text will show monospace correctly.
[16:01] <seb128> hrw, try irc.gimp.org
[16:01] <hrw> connected
[16:01] <hrw> cyphermox: evo is set to display plain text
[16:02] <hrw> cyphermox: and even for text/plain mails sans font is used
[16:03] <cyphermox> ok
[16:26] <pitti> jasoncwarner, Sweetshark, bryceh, chrisccoulson, didrocks, tremolux, Riddell, kenvandine, cyphermox, mterry, rodrigo_, seb128, tkamppeter, pedro_: meeting reminder in 4 minutes
[16:26] <cyphermox> o/
[16:26] <rodrigo_> pitti, getting ready :)
[16:27] <didrocks> hey
[16:27] <tremolux> hey!
[16:27]  * pedro_ waves
[16:28] <tremolux> hrm, can't seem to log into the wiki to post my update  :/
[16:28] <didrocks> tremolux: took a lot of time for me
[16:28] <didrocks> ubuntu sso seems to lag
[16:28] <tremolux> didrocks: yeahp
[16:29]  * kenvandine waves
[16:30] <pitti> several people had wiki problems since the upgrade
[16:30] <pitti> so, meeting time
[16:30] <pitti> jasoncwarner, Sweetshark, bryceh, chrisccoulson, didrocks, tremolux, Riddell, kenvandine, cyphermox, mterry, rodrigo_, seb128, tkamppeter, pedro_: meeting starts
[16:30] <rodrigo_> o/
[16:30] <mterry> heyo
[16:30] <pitti> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-06-21
[16:30] <chrisccoulson> hi!
[16:31] <seb128> hey
[16:32] <pitti> FYI, the burndown charts still have the wrong alpha-2 milestone end; they shoudl fix themselves over midnight UTC
[16:32] <pitti> so let's dive right in with kenvandine
[16:32] <kenvandine> ok
[16:32] <pitti> kenvandine: still fighting wiki-wars? :0
[16:32] <pitti> :)
[16:32] <kenvandine> sort of...
[16:32] <kenvandine> :)
[16:32] <kenvandine> was in a meeting
[16:32] <kenvandine> starting with U1
[16:33] <kenvandine> they are going to make sure the sso fix breaking U1 in oneiric gets uploaded today
[16:33] <kenvandine> and the ppa/release stuff we talked about last week...
[16:33] <kenvandine> they will have something written up this week and make sure everyone is happy with it
[16:34] <rodrigo_> kenvandine, do you have any update about desktopcouch brokenness in oneiric being fixed?
[16:34] <kenvandine> i guess chipaca mentioned it in the release meeting last week, not sure what he had to say
[16:34] <kenvandine> rodrigo_, i don't... didn't know it was broken
[16:34] <kenvandine> rodrigo_, poing me to the bug and i'll make sure they are looking at it
[16:34] <kenvandine> s/poing/point
[16:34] <rodrigo_> kenvandine, I knew on Friday, will check with rye later, not sure if there was a bug
[16:34] <kenvandine> ok
[16:35] <kenvandine> that is all i have for U1, and nothing really new for DX... besides a do over with tedg
[16:35] <pitti> kenvandine: I followed up about the PPA issue, but no answer from U1 team yet
[16:35] <kenvandine> he upgraded to oneiric and is doing releases now
[16:35] <pitti> tedg: thanks for running oneiric!
[16:35] <kenvandine> pitti, they have committed to having something documented for everyone to review this week
[16:36] <tedg> pitti, Heh
[16:36] <kenvandine> i got the first release from him just before the meeting, going through the whole stack
[16:36] <kenvandine> oh, and the theme is uploaded now
[16:36] <mterry> anything we need to do to use it?
[16:36] <kenvandine> light-themes now includes Ambiance and Radiance gtk3 themes
[16:36] <kenvandine> you need gtk3-engines-unico
[16:36] <pitti> didrocks was kind enough to MIR it, so it's in today's images (I rebuilt them after they failed this morning)
[16:36] <kenvandine> which is pending a MIR
[16:36] <kenvandine> woot
[16:36] <pitti> but it isn't set as the default theme yet
[16:36] <mterry> kenvandine, but I mean to turn it on
[16:37] <mterry> ah
[16:37] <pitti> that still seems to be adwaita
[16:37] <didrocks> kenvandine: I had some comments on it, please make sure to read it and follow up with Cimi
[16:37] <kenvandine> will do
[16:37] <pitti> or is that because I have gnome-themes-standard installed?
[16:37] <kenvandine> no idea... perhaps
[16:37] <pitti> will purge and re-test
[16:37] <kenvandine> thx
[16:37] <kenvandine> i'll test on a live iso too
[16:37] <kenvandine> pitti, so do the isos have it now?
[16:37] <seb128> mterry, turn it on in dconf-editor ;-)
[16:38] <pitti> kenvandine: http://cdimage.ubuntu.com/daily-live/20110621/ should have them
[16:38] <kenvandine> awesome
[16:38] <kenvandine> thx
[16:38] <pitti> ah, I used gnome-tweak-tool to enable Radiance
[16:38] <kenvandine> that is all i have
[16:38] <pitti> that worked
[16:38] <mterry> seb128, I looked, the key I thought it would be (/desktop/gnome/interface/gtk-theme) already said Ambiance
[16:39] <pitti> kenvandine: thanks; mind to add that to the wiki, too?
[16:39] <tkamppeter> hi
[16:39] <kenvandine> pitti, i will
[16:39] <seb128> mterry, you want org.gnome.desktop.interface gtk-theme
[16:39] <seb128> mterry, i.e dconf, not gconf
[16:40] <seb128> kenvandine is supposed to update ubuntu-artwork to move the gconf-default to a gsettings-override but he didn't do it yet ;-)
[16:40] <pitti> kenvandine: thank you!
[16:40] <mterry> seb128, sure, that's what I'm looking at.  But dconf has paths too, and the path for the org.gnome.desktop schema is /desktop/gnome
[16:40] <kenvandine> seb128, indeed :)
[16:40] <pitti> didrocks already sent the report to the wiki; great job on Qt a11y!
[16:40] <didrocks> thanks :)
[16:40] <pitti> looking forward to see GTK3 unity, too
[16:40] <didrocks> testers needed!
[16:40] <pitti> didrocks: anything to discuss?
[16:40] <mterry> whatever, can deal with this after meeting
[16:40] <didrocks> nothing in addition to what I wrote :)
[16:40] <seb128> right
[16:41] <pitti> didrocks: apt-get dist-upgrade should be everyone's morning/evening gymnastics
[16:41] <didrocks> pitti: it's in the ppa right now
[16:41] <didrocks> not oneiric
[16:41] <didrocks> just waiting to ensure that we have no regression
[16:42] <didrocks> the backport is approximatly 100 commits
[16:42] <didrocks> so quite intrusive :)
[16:42] <didrocks> I'll let it staging for 2/3 days before pushing in oneiric
[16:42] <pitti> didrocks: will upstream backport that as well, or just to 4.8, and we keep the backport ourselves?
[16:42] <pitti> didrocks: 4.8 is not possible/adequate for oneiric?
[16:43] <didrocks> pitti: upstream helped us to backport 4.8 to 4.7, but there is no official support. However, they told me they wanted to help us as far as they can
[16:43] <didrocks> pitti: it's more horrible than that, it's a 4.8 branch with some 5.0 features that we stripped together
[16:44] <didrocks> pitti: 4.8 has still an unkown release date, and talking with them at the summit about our feature freeze calendar, they confirmed that it's safer to plan on 4.7
[16:44] <didrocks> (4.7.4 should be out soon)
[16:44] <pitti> ack
[16:44] <pitti> I'm just a little worried because they wouldn't include the a11y patches in their QA for point releases
[16:45] <pitti> that sounds like a non-negligible source of problems/regressions?
[16:45] <didrocks> pitti: no, that's the downside, however, right now, the accessibility code is only activated under certain condition (env var, but soon, the dbus activation), so we should be safe for integrating regression on non accessibility side
[16:45] <pitti> didrocks: in general, does Qt come with a comprehensive test  suite, or does upstream have a separate secret/manual procedure for this?
[16:45] <didrocks> but yeah, with accessibility enabled, we can have some problems/regressions, hence this early test
[16:46] <didrocks> pitti: they have a very extensive test suite. However, they don't ship it in the tarball
[16:46] <pitti> ah, but in git? i. e. we have access to it?
[16:46] <didrocks> I need to rediscuss about that with them, I found nobody to explain why
[16:46] <didrocks> yeah
[16:46] <didrocks> in git
[16:46] <pitti> well, that's good enough
[16:46] <pitti> thanks!
[16:46] <didrocks> yw :)
[16:47] <pitti> wiki vs. tremolux still 1:0?
[16:47] <tremolux> pitti: haha, yes
[16:47] <tremolux> I can summarize and post it after tho, sound good?
[16:47] <pitti> tremolux: any news from the UX s-c design review?
[16:47] <pitti> tremolux: go ahead
[16:47] <tremolux> k
[16:47] <tremolux>  * Software Center 4.1.6 released, UI enhancements and bug fixes
[16:47] <tremolux>  * New Natty and Maverick SRUs currently in verification
[16:47] <tremolux>  * Software Center 5.0 redesign by UX team continues, more user testing this week and delivery of final design to come next week at rally
[16:47] <tremolux>  * And finally...great progress on GTK3 port by Matthew McGowan  \o/
[16:48] <pitti> wohoo!
[16:48] <rodrigo_> :)
[16:48] <tremolux> pitti: knew you'd like that  :D
[16:48] <tremolux> about the user testing, yes, they have completed the first round and a second round begins today (or has begun I expect)
[16:48] <pitti> tremolux: I'm curious, how does "progress" look like?
[16:48] <pitti> given that you probably can't even start the program until it's like 80% ported?
[16:49] <tremolux> like, it works! but not totally pretty as a lot of the custom code has been removed for now
[16:49] <tremolux> until we get the new design it doesn't make sense to go much farther I think
[16:49] <pitti> ah, so you just dropped all gtk2-ish imports, and disable parts of it
[16:49] <pitti> TBH I hadn't expected it to go that well
[16:49] <tremolux> it's Matt McGowan's work, he rocks
[16:50] <pitti> haven't heard a single OMGGTKBUG cry about this yet
[16:50] <didrocks> (just a note that I talk to mpt to ensure they consider OneConf in the redesign, so it would be more work, but won't block the inclusion by default)
[16:51] <tremolux> didrocks: ah, excellent!
[16:51] <pitti> thanks tremolux; great progress!
[16:51] <tremolux> thx pitti
[16:52] <pitti> also, thanks everyone for doing some WI cleanup
[16:52] <pitti> http://status.ubuntu.com/ubuntu-oneiric/canonical-desktop-team-oneiric-alpha-2.html already looks better today
[16:52] <chrisccoulson> i need to do some WI cleaning soon ;)
[16:52] <pitti> desktop-o-default-email-client still wins by far in terms of WI
[16:53] <pitti> chrisccoulson: I guess there's quite a lot of upstream/m_conley work involved there? or is all of that on your plate?
[16:53] <chrisccoulson> i guess i'm going to be very busy at the rally next week
[16:53] <pitti> desktop-o-software-center-ui seems blocked on the UX feedback
[16:53] <pitti> I asked jasoncwarner_ to cover desktop-o-accessibility-ubiquity in the Eastern edition
[16:54] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-quickly
[16:54] <pitti> mterry, didrocks: this is still blocked on the new LP features (sinzui's 4 WIs for alpha-2); do you happen to know the status of this?
[16:54] <chrisccoulson> pitti - i guess for the default-email one that there might be a bit of shifting around. i'm busy on the messaging menu work atm, as mike already has a lot on his plate
[16:54] <mterry> pitti, no.  I assume it's still not done
[16:55] <chrisccoulson> but those are a3 milestoned, and i'd really like to land them before a2
[16:55] <didrocks> pitti: didn't have the time to track it done, it's been blocked for 3 cycles now
[16:55] <pitti> mterry: so I'll just re-target these to a3, beta1, etc. until it's done, and postpone the spec accordingly?
[16:55] <mterry> pitti, sure, on it
[16:55] <mterry> pitti, oh, you're on it I mean
[16:55] <pitti> mterry: (no action necessary right now)
[16:55] <pitti> chrisccoulson: yeah, I think at beta-1 is too late, it's after FF
[16:56] <pitti> didrocks, mterry: well, there are still a bunch of non-blocked WIs, but I guess these are just a manpower issue
[16:56] <mterry> yes
[16:56] <pitti> but it's low priority, so deliberately a target of opportunity
[16:56] <didrocks> right
[16:56] <pitti> so no harm there when we have to postpone, except your pride :/
[16:57]  * mterry has carefully cultivated a lack of pride for such instances
[16:57] <pitti> kenvandine: how is the new gwibber coming along?
[16:57] <kenvandine> very nicely!
[16:57] <kenvandine> almost ready to upload
[16:58] <pitti> yay
[16:58] <pitti> kenvandine: any blockers due to new gtk/python etc?
[16:58] <kenvandine> nope
[16:58] <kenvandine> it's vala :)
[16:58] <pitti> the current GTK 3.1.6 performance problem is quite a sucker
[16:59] <kenvandine> yeah, not affecting gwibber
[16:59] <pitti> lucky you :)
[16:59] <pitti> ok, great
[16:59] <seb128> pitti, where do you notice it?
[16:59] <pitti> Sweetshark: are we still blocked on LibO 3.4.0/3.4.1 to actually release?
[16:59] <kenvandine> empathy
[16:59] <kenvandine> is the only place i have seen it
[16:59] <seb128> oh, I'm using pidgin ;-)
[17:00] <seb128> would explain
[17:00] <pitti> seb128: empathy is unusable, but I've also seen long Evolution hangs
[17:00] <mterry> i've seen problems in control center too (at least on deja-dup)
[17:00] <kenvandine> oh... maybe that is why evo has been sucking this week
[17:00] <pitti> kenvandine: try downgrading to 3.1.4 and compare
[17:00] <seb128> mterry, right, I ran into it there
[17:00] <kenvandine> pitti, i did for empathy
[17:00] <pitti> Company knows about it, and said it's being worked on
[17:00] <pitti> but no fix yet in upstream trunk
[17:01] <kenvandine> yeah, i am following the bug
[17:01] <Sweetshark> pitti: 3.4.0 still has some packaging issues: ~5 patches need rebasing, and most importantly we need an update for the service registration foo
[17:01] <pitti> so in general, if anyone sees long GNOMEish program hangs in oneiric, it's probably that
[17:01] <Sweetshark> pitti: http://wiki.services.openoffice.org/wiki/Passive_Component_Registration
[17:01] <pitti> Sweetshark: oh, we modified that? or do you mean "we" as in Debian as well?
[17:01] <rodrigo_> no hangs here, but some slowness seen in the last few days, indeed
[17:02] <Sweetshark> pitti: we as in debian aswell
[17:02] <pitti> ah
[17:02] <pitti> Sweetshark: ok, it's not an alpha-2 blocker I think, we can easily move it to a3
[17:02] <pitti> if it gets later than that (after FF), then we need to reconsider staying at 3.3, but let's do that discussion if/when we need it
[17:03] <pitti> does anyone have any other topic? blockers? discussions? announcements?
[17:04] <Sweetshark> pitti: I digged through the source today and got the theory straight, _rene_ might give the implementation a try tonight. hopefully theory will match up with relality.
[17:04] <micahg> Firefox 5 should be going out to natty today
[17:04] <Sweetshark> s/relality/reality/
[17:04] <pitti> Sweetshark: high hopes :)
[17:04] <seb128> small note, http://pad.ubuntu-uk.org/oneiric-desktop has gconf and gtk2 rdepends on the CD lists
[17:04] <pitti> micahg: ah, right; thanks for the additional l10 testing
[17:04] <seb128> if anyone is interested in those
[17:04] <seb128> I've started adding bug references as well
[17:05] <tremolux> I wanted to thank pedro_ for his awesome work on the desktop bug summary page, super-helpful for us for s-c bugs!
[17:05] <pitti> seb128: oh, I thought libgnome2-0 and friends are gone with dropping tomboy
[17:05] <seb128> I will tag the bugs as well
[17:05] <seb128> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gnome3-gtk3
[17:05] <seb128> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gnome3-gsettings
[17:05] <seb128> pitti, they are, gconf and gtk2 not yet though
[17:05] <seb128> pitti, which is the ones I mentioned today ;-)
[17:05] <pitti> yeah
[17:06] <seb128> I cleaned the libgnomevfs list
[17:06] <seb128> it's basically kept it by libreoffice and firefox
[17:06] <seb128> their -gnome still use gnome-vfs and gio
[17:06] <pitti> hm; nobody really tests gnomevfs any more
[17:06] <chrisccoulson> yeah, i'll need to distro-patch gnomevfs out of firefox
[17:07] <pedro_> tremolux, you're welcome! :-)
[17:07] <Sweetshark> pitti: btw that might also make postinst hooks superflous that patch around the services.rdb after install, which is icky and errorprone. Instead we will just have multiple service.rdbs.
[17:07]  * tremolux hugs pedro_
[17:07] <chrisccoulson> seb128, could you report a bug and assign it to me, so it doesn't fall off my radar?
[17:07]  * pedro_ hugs tremolux back
[17:07] <chrisccoulson> or just keep pinging me on IRC ;)
[17:07] <pitti> Sweetshark: and those are then just static XML files, instead of "real" databases?
[17:07] <Sweetshark> pitti: right
[17:07] <pitti> nice
[17:08] <seb128> chrisccoulson, ok
[17:08] <seb128> chrisccoulson, ping
[17:08] <seb128> chrisccoulson, ping
[17:08] <seb128> chrisccoulson, ping
[17:08] <chrisccoulson> lol
[17:08] <seb128> chrisccoulson, let me know when I can stop :p
[17:08] <chrisccoulson> seb128, careful, i might do that back to you and then change my IRC name
[17:08] <chrisccoulson> so you get a stuck indicator ;)
[17:09] <seb128> that bug should get a CVE or something ;-)
[17:09] <chrisccoulson> lol
[17:09] <chrisccoulson> yeah, it's basically a DoS
[17:09] <pitti> aaanyway
[17:09] <pitti> sounds like the meeting is over :)
[17:09] <chrisccoulson> don't tell mdeslaur
[17:09] <pitti> thanks everyone! looking forward to seeing all of you next week
[17:09] <micahg> chrisccoulson: I hit that bug the other day :-/
[17:09] <rodrigo_> yeah!
[17:09] <pitti> at the beer drinking rally (this is Dublin after all..)
[17:09] <tremolux> thanks everybody!
[17:09] <chrisccoulson> micahg, yeah, it's a total PITA ;)
[17:09] <pedro_> thanks!
[17:10] <chrisccoulson> pitti - i'm looking forward to some guinness!
[17:10] <fta> pitti, just saw "chromium-browser-l10n-LANG" mentioned above, what's about it? is it needed?
[17:10] <pitti> fta: it's just chromium-browser-l10n, sorry
[17:10] <pitti> fta: latest language-selector will now auto-install it if you have chromium installed
[17:11] <fta> oh, good
[17:11] <seb128> pitti, thanks
[17:11] <fta> pitti, thanks
[17:13] <pitti> chrisccoulson: NACK for guiness!
[17:14] <kenvandine> :)
[17:14] <kenvandine> looking forward to the guiness!
[17:14] <mdeslaur> chrisccoulson, seb128: huh? CVE for what?
[17:14]  * mdeslaur has got enough CVEs as it is...
[17:15] <seb128> mdeslaur, xchat-gnome's indicator being stupid with nicknames changes
[17:15]  * pitti chuckles how you can make the security team jump up and down
[17:15] <chrisccoulson> heh
[17:15] <pitti> mdeslaur: *hug*
[17:15] <seb128> it doesn't clear the highlight if the contact changes nickname before you read the message
[17:15] <chrisccoulson> mdeslaur, messaging indicator DoS ;)
[17:15] <chrisccoulson> you have to restart the indicator service don't you?
[17:16] <seb128> mdeslaur, so you have no way to clear the indicator blue color out of waiting for the contact to get the old nick back or restarting your IRC client ;-)
[17:16] <chrisccoulson> mdeslaur, do you use xchat-gnome?
[17:16] <chrisccoulson> do you want me to demonstrate ;)
[17:16] <mdeslaur> oh, ffs, you guys are nuts :)
[17:16] <chrisccoulson> lol
[17:17] <chrisccoulson> and this one isn't even my fault, for a change
[17:17] <pitti> I already imagine the USN: "A remote attacker could exploit this so that the message envelope has the wrong color"
[17:17] <chrisccoulson> lol
[17:17] <mdeslaur> hehe
[17:19] <kenvandine> seb128, i'll make that slightly better soonish...
[17:20] <Sweetshark> chrisccoulson: I had a great case of message indicator DoS once: I logged in my corp. account X-Chat account for the first time after having the account for quite some time (was using a webfrontend before). It was connected with some internal twitter service. And every tweet since the dawn of time caused an indicator popup. Those are not implemented with performance in mind to much. But the kicker was:
[17:21] <Sweetshark> This was on a remote session on a SunRay. That hugged the net and the CPU for ~15 minutes ...
[17:21] <chrisccoulson> lol
[17:21] <chrisccoulson> yeah, that could be handled a little better too ;)
[17:23] <Sweetshark> I gues that was the only time in history that xchat stole the cpu from gcc on that rather bigiron shared developer machine.
[17:43] <pitti> rodrigo__: I responded to your language-cleanup spec comment, thanks!
[17:49] <cjwatson> any problem with me uploading libappindicator?
[17:49] <pitti> oh, ken is offline
[17:49] <pitti> mterry, seb128: ^ do you know?
[17:49] <cjwatson>   * Call dh_python2 from binary-fixup rather than binary-predeb, so that
[17:49] <cjwatson>     generated maintainer script snippets actually end up in the package.
[17:49] <cjwatson>   * Remove unused libmono-dev build-dependency (for Mono 2.10 transition).
[17:50] <seb128> cjwatson, not at all, go for it
[17:50] <seb128> cjwatson, thanks for the fixes ;-)
[17:50] <cjwatson> thanks.  I think libindicate needs much the same
[17:51] <seb128> cjwatson, feel free to upload it as well if you want or let it to us if you prefer we can do it
[17:52] <cjwatson> I might as well just do it all now, it's part of this remove-pyc-files-from-squashfs project
[17:52] <seb128> ok
[17:53] <cjwatson> looks like ecryptfs-utils has a similar problem, but that isn't your problem :-)
[17:54] <seb128> it's not indeed ;-)
[18:21] <pitti> chrisccoulson: I finally got around to filing bug 800304
[18:21] <ubot2> Launchpad bug 800304 in firefox "browser.search.defaultenginename does not work from distribution.ini" [Undecided,New] https://launchpad.net/bugs/800304
[18:26] <pitti> good night everyone!
[18:32] <seb128> 'night pitti
[18:41] <fta> chrisccoulson, http://code.google.com/p/chromium/issues/detail?id=86715  last comment, any idea?
[18:44] <chrisccoulson> the trace definitely looks like it's just the menubar fetching properties for menuitems
[18:44] <chrisccoulson> not sure why that would hang though, unless there are a lot of menu items
[19:14] <fta> chrisccoulson, maybe a giant bookmark
[19:24] <fta> who's doing this appmenu?
[19:24] <fta> tedg, any idea? http://code.google.com/p/chromium/issues/detail?id=86715
[19:32] <seb128> pedro_, hola!!! ;-)
[19:32] <seb128> pedro_, how are you?
[19:32] <tedg> fta, Are you getting that?  Seems get be an error with g_value_init()?  Not sure how that could happen.
[19:34] <pedro_> seb128, hey! good and you?
[19:34] <seb128> pedro_, I'm great thanks!
[19:34] <tedg> jcastro, Do you know who's doing work on the appmenu stuff for Chrome?
[19:34] <seb128> pedro_, your bugs summary rocks dude ;-)
[19:34] <seb128> pedro_, just wanted to tell you ;-)
[19:35] <pedro_> seb128, thanks! glad you like it :-)
[19:35] <pedro_> seb128, i'm doing some others i'll show you those at the rally ;-)
[19:35] <seb128> pedro_, ;-)
[19:36] <seb128> pedro_, I'm trying to think to a way to build list of "small bugs that we should fix this cycle to look better"
[19:36] <seb128> pedro_, those are not really ranked in duplicates or comments or anything
[19:36] <seb128> pedro_, I'm pondering between tags, or assigning to desktop-bugs or ...
[19:37] <seb128> pedro_, well I milestone them for oneiric as start ;-)
[19:37] <pedro_> seb128, probably we can start adding tags + a milestone and build a list with those
[19:37] <pedro_> the bad thing about tags though is that everybody can add those, but we can play for a bit and see how it goes
[19:37] <seb128> pedro_, I think I will think a bit this week and ask everybody what they think next week in a roundtable
[19:37] <pedro_> seb128, sounds good :-)
[19:38] <seb128> pedro_, think about it this week if you want and see if you can figure some better way ;-)
[19:38] <seb128> pedro_, if not we will just sort if over a beer next week ;-)
[19:38] <pedro_> seb128, oh yeah Guinness FTW :-)
[19:38] <seb128> not sure about the guinness but I will get some beer don't worry ;-)
[19:41] <fta> tedg, i'm not seing this, but as i am the chromium maintainer for ubuntu, they ping me when there's a problem with ubuntu
[19:44] <tedg> fta, Ah, okay.  I'm guessing with a retrace we might get a better stack.
[19:44] <tedg> fta, It seems odd the one in the bug.
[22:46] <achiang> is there a way to actually run a foo.desktop file? xdg-open wants to open it in gedit


[20:56] <Unit193> Hmmm, perhaps it'd be good to remove the 'next meeting' header: https://wiki.ubuntu.com/TennesseeTeam ?
[20:57] <average_guy> :D That would be the most that has happened in here in quite some time Unit193
[20:58] <Unit193> average_guy: Howdy.
[20:59] <average_guy> hey Unit193, I've started testing iso's
[20:59] <average_guy> fun times
[20:59] <Unit193> Nice, think I've seen your name pop up a few times in -quality.  Mainbuntu or a flavor?
[20:59] <Unit193> Heh, indeed.
[21:00]  * Unit193 likes creating ISOs. :P
[21:01] <average_guy> I have been doing a little of everything, but it is becoming more and more apparent that I should pick 1 or 2 and do those more thoroughly
[21:02] <wrst> I would change that if ubuntu one would ever log me in...
[21:02] <average_guy> am watching the tracker to see whats gets tested the least
[21:02] <average_guy> hi wrst
[21:02] <Unit193> wrst: Haha!  Good luck editing the wiki.  :P
[21:03] <Unit193> Can't you still install/remove without?
[21:03] <wrst> oh I know
[21:04] <wrst> Unit193: I don't know but last time I used it the login process worked about this smoothely
[21:04] <Unit193> USC always gets purged too fast for me to open it. :D
[21:05] <Unit193> Synaptic still has uses (package origins), but apt/apt-get/apt-cache are still my favored methods.
[21:05] <wrst> well its a terrible implementation of a good way to do things
[21:05] <wrst> well I'm an arch user so yeah ... I like command line installing of stuff so I know whats going on
[21:05] <Unit193> And, you know I live in the mad house, so have to see what's going on. :P
[21:06] <Unit193> Running systemd 214 on trusty, not really supported so much and packages with only an upstart job kind of fail a little.
[21:08] <Unit193> wrst: I'd update it for you, but the wiki isn't liking me any better, sorry.
[21:08] <wrst> ha ha
[21:08] <wrst> yeah its a pain it seems
[21:08] <Unit193> I got logged in, but it stalled after that.


[03:56] <guiverc> i've made some comments on the zdnet ubuntu kylin article.. I've not used it so I don't know, but version doesn't match lunar & it mentions packages not found in seed (see comments)
[03:57]  * guiverc says OUCH ... just noted the time...
[03:59] <Bashing-om> guiverc: Looking :D


[00:22] <smkellat> Blog post: http://coyote.works/posts/SiteRebuild20191030/
[00:22] <jenni> [ Updated The Company Site ] - https://bit.ly/2WwTeVw


[00:17] <Odd_Bloke> Hah.
[10:15] <meena> so, i didn't realize we have no fallback when blkid doesn't work in ds-identify, so here's a bug: https://bugs.launchpad.net/cloud-init/+bug/1901174
[14:32] <minimal> Can anyone help with a issue related to testcases? I'm working on a PR and have written a testcase for it but getting the weird situation where the RHEL sysconfig output appears to be JSON rather than plain text and so doesn't match the expected output
[14:49] <meena> it's not json, it's the object
[14:58] <meena> minimal, it means you're comparing a serialised version of thing with an unserialised one
[15:13] <minimal> meena: I've just using the pre-existing functions in test_net.py that compare expected output with actual output
[15:28] <minimal> I think I'm just getting confused by the failure output and its actually worked as intended
[15:32] <minimal> I'm still a bit confused about the testing layout in test_net.py - I expected to be able to define an "input" network config v2 YAML and the expected ENI, Netplan, and sysconfig for it in one place and have all outputs tested in on go but now I realise there are separate classes for testing each of these output formats
[15:32] <minimal> so seems I need to write separate testcases for each of the output types
[15:38] <rharper> minimal: yes, for a new scenario in test_net.py,  you have an input, which is ingested into internal network_state; and then for each distro/renderer, there's an expected output;  so it sounds like you're on the right track;   alternatively you might chat with Odd_Bloke to see if there are suggestions on switching to a pytest parametrized style which could significantly improve how those tests get written;
[15:42] <minimal> rharper: what's confused me is that in test_net.py there's "dhcpv6_stateless" which contains expected_eni, expected_netplan, expected_sysconfig_opensuse, and expected_sysconfig_rhel which I copied/pasted (as well as the function test_dhcpv6_stateless_config that uses it) as a basic for my new testcase but when I ran tox only expected_sysconfig_rhel appears to be tested - none of the other outputs are checks so why are they defined/present.
[15:43] <rharper> minimal: a diff would help; but test inputs/outputs data are reused in differnt test Classes in that file
[15:43] <rharper> test_net.py is a *beast* and it's easy to not see where all of the call sites are due to the repeated pattern of the classes
[15:44] <minimal> yeah, I'm finding it hard to figure out how it works when its 5000+ lines long
[15:47] <rharper> minimal: exactly =?
[15:47] <rharper> =/
[15:48] <minimal> seems I need to put the function for ENI in class TestEniRoundTrip, not in class TestEniNetRendering as I was doing.....doh!
[15:48] <rharper> a small refactor could take the defined configs and put them in tests/data/test_net_configs.py;  and then each of the classes in test_net, could be test_net_classname.py and import what they needed from data/test_net_configs.py
[15:50] <minimal> certainly seems like refactoring is badly needed. I'm trying to do the right thing and create a testcase for functionality that's been broken for how knows how long as its not currently tested.
[15:50] <minimal> time to reach for some headache tablets........... ;-)
[15:51] <rharper> heh
[16:16] <Odd_Bloke> Yeah, I think those tests have been structured well in that the test data and testing code _are_ separate, but that approach still leads to a lot of boilerplate in "vanilla" Python unit testing (which I agree parameterisation could address).  Even "just" a refactor to split them into separate files as suggested would help a great deal, I think.
[16:24] <minimal> have figured it out now for eni and netplan so now need to make changes to sysconfig.py before I can test that
[16:26] <minimal> Odd_Bloke: ideally it would be nice to have a generic test function that then behind the scenes calls one-or-more or all of the specific output functions
[16:27] <minimal> so for "dhcp" for example the test_dhcp function would call test_netplan_dhcp, test_eni_dhcp etc but the test_dhcp would have an arg to let you select some of the outputs if you did'nt want them all called
[16:47] <Odd_Bloke> minimal: Are you familiar with pytest parameterisation (https://docs.pytest.org/en/stable/parametrize.html)?  It allows you to programmatically generate multiple instances of the same test with different inputs: I think this would map onto the current dicts we already have pretty well.
[16:52] <Odd_Bloke> So instead of (e.g.) TestNetplanRoundTrip having to have a bunch of copy/pasted definitions, we would instead define a single test method which is parameterised with `yaml` and `expected_netplan` from each of the dicts.  (Something like `@pytest.mark.parametrize("yaml,expected_netplan", [(entry["yaml"], entry["expected_netplan"]) for entry in NETWORK_CONFIGS.values()])`.)
[16:53] <Odd_Bloke> So anything new added to NETWORK_CONFIGS will automatically be picked up by those tests (and we lose a lot of boilerplate code too).
[17:00] <minimal> Odd_Bloke: nor familiar with that but it sounds good. For each test you'd need to be able to define which of multiple inputs to each test (netconfig v1, v2, eni?) and which (or all) of the outputs
[17:08] <Odd_Bloke> minimal: I think you'd define a separate test for each of the dict keys: different renderers have different setup requirements for testing.
[17:10] <Odd_Bloke> And then (and now, for that matter) you can run only the Netplan tests with: pytest -k TestNetplanRoundTrip tests/unittests/test_net.py
[17:11] <minimal> Odd_Bloke: BTW what's your view on Mina's comments on PR 623?
[17:12] <Odd_Bloke> (Due to our pytest support matrix (our tests need to run on the version of pytest in Ubuntu 16.04), I don't think we can mark up each of the cases to be able to select quite as specifically as "the 'small' configuration on netplan".  Given that _all_ the test_net tests currently run in ~2s, I don't think that's too painful.)
[17:17] <smoser> warning, stupid question
[17:17] <smoser> meena: do you use systemd on freebsd ?
[17:21] <smoser> someone have time to review https://github.com/canonical/cloud-init/pull/622
[17:29] <meena> smoser, nope, we can't we don't have cgroups on freebsd
[17:29] <meena> https://www.freebsdnews.com/2018/08/21/benno-rice-the-tragedy-of-systemd-bsdcan-2018/ good talk on why freebsd could really use something like systemd
[17:30] <meena> we also don't have the probably easier to port Solaris contracts, which are roughly the same concept
[17:37] <Odd_Bloke> minimal: Have replied on #623. :)
[17:39] <minimal> Odd_Bloke: Thanks, will be glad to put that PR to bed :-)
[17:42] <smoser> meena: so why do you care about ds-identify ?
[17:42] <meena> smoser: because it's what guesses which cloud you're on, and on FreeBSD, it's ca 95% wrong.
[18:15] <meena> how the heck do i get the first "word" in a $line in bash? $line[0] does not cut it
[18:19] <meena> is bash the worst programming language?
[18:26] <meena> oh, never mind, this isn't bash, this is sh.
[18:28] <minimal> cut -f1 ?
[18:30] <meena> minimal: that'd be 3 cut calls
[18:30] <minimal> efficiency isn't shell's selling point :-)
[18:31] <meena> i thought efficiency was the point of ds-identify
[18:31] <meena> nothing else uses cut in that code
[18:31] <meena> i'm already using awk to normalise an output
[18:32] <meena> nothing else does that either!
[18:32] <meena> there's one call to grep
[18:32] <meena> no sed
[18:38] <meena> smoser: ping
[18:38] <smoser> meena: 2 minutes ?
[18:39] <smoser> (i have to go, in < 2 minutes . return in 40)
[18:41] <smoser> sorry. out.
[18:43] <meena> s'okay
[19:19] <smoser> meena: back
[19:24] <meena> smoser: https://github.com/canonical/cloud-init/pull/625
[19:25] <meena> i'm surprised you can do so much with ds-identify without shelling out…
[19:25] <meena> what i'm not surprised about is how the result looks (ugly, af)
[19:25] <smoser> i've written way to much shell in my life.
[19:32] <meena> smoser: examples of what the lines look like are in https://bugs.launchpad.net/cloud-init/+bug/1901174
[19:37] <meena> smoser: i don't understand this: "also... maybe we consider trying to render different versions ? freebsd and linux ?"
[19:51] <smoser> we could have a ds-identify on linux that only contained linux
[19:51] <smoser> and one for freebsd that only contained freebsd
[19:52] <smoser> was what i was suggesting.
[19:52] <smoser> and "render" one file ds-identify based on which platform was being installed for
[19:55] <meena> smoser: i'll leave this to more advanced developers of cloud-init
[19:56] <smoser> what you're doing is probably ok.
[19:56] <meena> yeah, i don't get blkid not found errors any more ;)
[19:56] <smoser> but i dont want more confusing code to read (than it already is) or slower runtimee
[19:57] <meena> i've now resolved two of your review complaints, https://github.com/canonical/cloud-init/pull/625
[20:10] <meena> so, i have 3 pull requests in the race right now, and all of them are going to break me because of tests.