[01:03] <robert_ancell> TheMuso, can you sponsor libgweather from bzr?
[01:04] <TheMuso> robert_ancell: sure thing
[01:16] <TheMuso> robert_ancell: I don't seem to have /usr/share/cdbs/1/class/python-autotools.mk on my system, and installing libgweather's build dependencies doesn't grab it either. Do you know what package its from?
[01:22] <robert_ancell> TheMuso, Mavericks cdbs
[01:23] <TheMuso> oh ok
[01:23] <robert_ancell> makes the debian packages _so much better_ but yeah, can't build them on Lucid
[01:23]  * TheMuso uses a chroot then.
[01:34] <robert_ancell> RAOF, bryceh: How fast can you get an xserver to start on boot?
[01:35] <RAOF> robert_ancell: You mean - what service dependencies does the xserver have?
[01:36] <bryceh> robert_ancell, depends on hardware
[01:36] <robert_ancell> both dependencies and what the state is now - i.e. is lucid booting x as fast as it can?
[01:37] <bryceh> robert_ancell, if you mean "is there anything we can change in xserver to make the xserver portion of the boot faster", I think we pretty much squeezed everything out of it we knew to do
[01:38] <bryceh> robert_ancell, however if you mean "Are there other things in the boot process that could get us to a working X session faster"... maybe, I'm not sure there though.
[01:38] <RAOF> You could start X sooner in the boot if you didn't have to start it from gdm.  I'm not sure how useful that would be, though.
[01:38] <robert_ancell> bryceh, so how long does it take to start on a cut down system, e.g. a dell mini
[01:39] <robert_ancell> I'm asking because I've been working on a new display manager which is as fast as possible.  I was wondering how fast you could get X running so then you could run an X app as the boot splash
[01:39] <bryceh> robert_ancell, xserver itself takes a second or two on a dell mini with ssd (exact time varies boot to boot, but seb128 and scott had some detailed numbers as proof)
[01:39] <bryceh> robert_ancell, if you use xdm and boot into a non-gnome X session using the -vesa driver, you can get things up and running in about a second
[01:40] <bryceh> maybe less
[01:40] <robert_ancell> nice, that would be fast enough.  run a static image on the fb before that
[01:41] <bryceh> robert_ancell, also there is a timing patch floating around for xserver (check the debian/patches/ dir, I think it may be just commented out)
[01:41] <bryceh> robert_ancell, if you are able to use fbdev, that may give equivalent performance as vesa
[01:42] <robert_ancell> I'd want to use the same drivers as the desktop would run on, so you don't have to reload anything later in the boot
[01:42] <bryceh> ah gotcha
[01:43] <bryceh> ok, was going to mention some other "well if you can lock down the hardware, then you can drop..."
[01:43] <RAOF> bryceh, robert_ancell: The upstream server now timestamps its logs, as of 1.8.
[01:44] <bryceh> RAOF, know if that patch is backported to lucid?  (and if it's better than the one we were toying with last release?)
[01:44] <RAOF> I certainly haven't backported it to Lucid.  I'm not sure if it's been backported to 1.7
[01:45] <bryceh> mm
[01:46] <bryceh> anyway, I had gone through the timing data myself and didn't spot any obvious optimizations we could do, so might not be worth the trouble, but patches are available if xserver boot seems slow
[01:47] <bryceh> robert_ancell, these days a lot of the goopy stuff amenable to optimization (like edid probing) is done in the kernel side via kms
[01:47] <robert_ancell> ok
[01:48] <bryceh> edid caching is a big win, and that's a kernel thingee
[01:48] <Sarvatt> no we can squeeze at least another 400ms out of the xserver startup time by dropping the pci vendor and card name lookup
[01:48] <bryceh> it's probably worth testing to be sure it's functioning properly
[01:48] <bryceh> Sarvatt, well that's what I was going to mention when I said "if you can lock down the hardware"... ;-)
[01:48] <Sarvatt> which will probably be done in 1.9
[01:48] <RAOF> Sarvatt: We'll pick up those patches for free in 1.9
[01:49] <robert_ancell> ooh, that sounds nice
[01:49] <bryceh> Sarvatt, robert_ancell: but that depends a lot on if you are going to always know ahead of time what the hw is
[01:49] <Sarvatt> its parses the huge pci id list just for mapping the vendor/device name at the very start, the driver prints its own identifying message so its not really useful
[01:50] <bryceh> Sarvatt, can you link robert_ancell the patch for that?
[01:50] <RAOF> bryceh: No, this is basically just for printing the vendor ID (which most of the DDXs do anyway, in a better way) in Xorg.0.log.
[01:50] <Sarvatt> just the one line - [  6357.749] (--) PCI:*(0:1:0:0) 1002:94c3:174b:e370 ATI Technologies Inc RV610 video device [Radeon HD 2400 PRO] rev 0, Mem @ 0xd0000000$
[01:50] <bryceh> ah
[01:51] <Sarvatt> http://patchwork.freedesktop.org/patch/989/ http://patchwork.freedesktop.org/patch/990/
[01:55] <TheMuso> robert_ancell: uploaded
[01:56] <Sarvatt> it's about 400ms for the lookup here on my netbook, about 150ms on a faster core 2
[01:57] <TheMuso> robert_ancell: What is this display manager you are working on?
[02:01] <robert_ancell> TheMuso, lp:lightdm
[02:01] <TheMuso> ah ok
[02:01] <robert_ancell> it's pre-alpha at the momeny
[02:02] <robert_ancell> moment
[02:05] <TheMuso> ok
[03:29] <RAOF> Would anyone like to sponsor a mesa upload?  http://cooperteam.net/Packages/mesa_7.8.1-3ubuntu1_source.changes and http://cooperteam.net/Packages/mesa_7.8.1-3ubuntu1.dsc .  I'm going to have some lunch, so if anyone wants to sponsor it I'll be back at about the time your build has finished :)
[03:38] <TheMuso> RAOF: will take a look.
[03:38] <RAOF> Ta.
[04:15] <Sarvatt> RAOF: should do libdrm first?
[04:27] <RAOF> Sarvatt: Doh!  Of course!
[04:27] <RAOF> Stupid local packages.
[04:28] <RAOF> That said, mesa builds fine against 2.4.20
[04:30] <TheMuso> RAOF: should I wait?
[04:30] <RAOF> Let me double check.  I _think_ it doesn't matter.
[04:31] <TheMuso> RAOF: ok
[04:32] <RAOF> TheMuso: You can proceed.  Mesa builds fine against 2.4.20, and doesn't use any symbols from 2.4.21 as determined by the dpkg dependencies.
[04:33] <TheMuso> RAOF: ok
[04:33] <Sarvatt> the mesa change is insanely huge to review TheMuso, I'm sorry and thanks for doing it :)
[04:33] <TheMuso> Sarvatt: np
[04:34] <RAOF> We'll want the new libdrm for a new -intel DDX, but that can wait and doesn't need to block mesa.
[04:34] <Sarvatt> speaking of which i should update that in debian
[05:05] <TheMuso> RAOF: uploading
[05:13] <RAOF_> Who pinged me?  Things are a little bit weird with the electricians rewiring stuff.
[05:16] <lifeless> 15:34 < RAOF> We'll want the new libdrm for a new -intel DDX, but that can wait and doesn't need to block mesa.
[05:16] <lifeless> 15:34 < Sarvatt> speaking of which i should update that in debian
[05:16] <lifeless> 15:59 -!- tedg<EMAIL_ADDRESS>has joined #ubuntu-desktop
[05:16] <lifeless> 16:05 < TheMuso> RAOF: uploading
[05:16] <lifeless> 16:05 -!- RAOF_<EMAIL_ADDRESS>has joined #ubuntu-desktop
[05:16] <lifeless> 16:13 < RAOF_> Who pinged me?  Things are a little bit weird with the electricians rewiring stuff.
[05:16] <RAOF_> lifeless: Thank you, valiant IRC proxy.
[05:46] <robert_ancell> TheMuso, can you sponsor poppler from bzr?
[05:47] <TheMuso> Sure.
[06:10] <TheMuso> robert_ancell: uploaded
[06:10] <robert_ancell> TheMuso, thanks
[08:03] <didrocks> good morning
[08:03] <didrocks> RAOF: hey, did you see my question about nvidia?
[08:04] <RAOF> didrocks: Good morning.  I did not see your question, no.
[08:04] <RAOF> Would you like to fix it by sponsoring a rebuild of nvidia-graphics-drivers? :)
[08:05] <TheMuso> lol
[08:05] <pitti> Good morning
[08:05] <didrocks> RAOF: that maybe the cause of that, right: http://paste.ubuntu.com/449524/ ?
[08:06] <RAOF> didrocks: Yes, exatly.
[08:07] <didrocks> RAOF: if you have something to be sponsored, I will be pleased to do so :)
[08:08] <RAOF> didrocks: http://cooperteam.net/Packages/nvidia-graphics-drivers_195.36.24-0ubuntu2_source.changes is available for your sponsoring pleasure.
[08:08] <didrocks> RAOF: sweet :)
[08:11]  * TheMuso worked on the 185 variant at some point in the past, the packaging is interesting. I refer more so to now NVIDIA package the drivers than the Ubuntu/Debian/dkms packaging.
[08:11] <baptistemm> hello
[08:13] <didrocks> RAOF: signed and uploaded for your (and mine) pleasure :)
[08:13] <didrocks> thanks
[08:13] <didrocks> baptistemm: salut!
[08:17] <baptistemm> salut didrocks
[08:18] <robert_ancell> desrt, ping
[08:19] <didrocks> hey robert_ancell, how are you?
[08:19] <robert_ancell> didrocks, hey, good
[08:21] <pitti> hey robert_ancell, good morning didrocks
[08:21] <RAOF> Ok.  I'm off to the hardware store to buy some lights for the electricians to put in tomorrow.  I think seb's looking for me; I'll be back on later this evening.
[08:21] <didrocks> Guten Morgen pitti, how are you?
[08:21] <pitti> splendid, thanks
[08:26] <seb128> hey there
[08:27] <didrocks> salut seb128, ça va ?
[08:27] <Sarvatt> fta: your script rocks, thank you! http://sarvatt.com/xorg-edgers/
[08:27] <seb128> lut didrocks, nickel, et toi ?
[08:28] <didrocks> seb128: ça va bien, merci :)
[08:28] <seb128> so mclasen started trolling as well
[08:29] <seb128> robert_ancell, hey
[08:30] <robert_ancell> seb128, morning
[08:30] <seb128> robert_ancell, how are you today?
[08:30] <robert_ancell> busy :)
[08:30] <seb128> robert_ancell, to reply to your email, new poppler depends on cairo 1.9
[08:30] <seb128> do you think we should update cairo?
[08:30] <seb128> I had that discussion with upstream yesterday
[08:31] <pitti> didrocks, seb128: are bug 528557 and bug 229187 fixed in maverick? I can't copy the lucid-proposed
[08:31] <seb128> they plan their next stable in august
[08:31] <ubot2> Launchpad bug 528557 in evolution (Ubuntu Maverick) (and 3 other projects) "cannot turn on alarm for meeting received via email (affects: 4) (heat: 28)" [Low,Fix committed] https://launchpad.net/bugs/528557
[08:31] <ubot2> Launchpad bug 229187 in evolution-data-server (Ubuntu Lucid) (and 2 other projects) "Evolution mailing list does not render accents correctly (affects: 3) (heat: 22)" [Low,Fix committed] https://launchpad.net/bugs/229187
[08:31] <seb128> but they did plan it in january before
[08:31] <robert_ancell> I would say yes, as long as they don't plan anything crazy
[08:31] <seb128> so I don't really trust them for their schedule
[08:31] <seb128> other distro had to go back to cairo 1.8 previous cycles
[08:32] <didrocks> pitti: it's in trunk, we still didn't upload the new version there, but in any case, I'll keep an eye on them
[08:32] <robert_ancell> seb128, hmm, annoying
[08:33] <Sarvatt> cairo 1.10 is a myth! :)
[08:34] <seb128> robert_ancell, upstream would like us to get the new cairo in the xorg-edger ppa for testing
[08:34] <seb128> robert_ancell, if you are interested to get that happening ;-)
[08:34] <robert_ancell> seb128, If there's no specific reason for upgrading, and a risk of it not being ready we should hold back
[08:35] <robert_ancell> I'm willing to do the packaging
[08:35] <seb128> it's in debian experimental
[08:35] <seb128> so it's basically merging our lcd filter change
[08:35] <seb128> I think getting it in the xorg-edget ppa would be a nice start
[08:35] <seb128> it would be there for testing with other xorg edge versions
[08:36] <robert_ancell> I'll put it on the low priority list, and have a look if everything else is working
[08:36] <Sarvatt> is it? i'll put it in the ppa then, i've been building it seperately for over a year now
[08:36] <seb128> robert_ancell, do you read d-d-l?
[08:36] <seb128> Sarvatt, that would be nice, thanks!
[08:36] <robert_ancell> seb128, no
[08:36] <seb128> robert_ancell, ok, that's wise ;-)
[08:37] <robert_ancell> seb128, yes, I had heard legends of how much time it takes to read, so I've never bothered to subscribe
[08:37] <Sarvatt> the lcd filter stuff won't apply i'm sure though
[08:38] <seb128> Sarvatt, so it needs to be updated to apply ;-)
[08:45] <seb128> pitti, what didrocks said
[08:46] <pitti> didrocks: ok, thanks
[08:57] <seb128> ok
[08:58] <seb128> I replied to mclasen troll
[09:00]  * didrocks didn't read d-d-l still today
[09:01] <seb128> not missing anything
[09:03] <seb128> he's trolling us for shipping desktopcouch and saying that shipping 2 gtk versions is a CD space issue
[09:03] <seb128> then trolling us for not shipping GNOME3 this cycle
[09:03] <didrocks> urgh :/ I'm not eager to read this, preferring working first, that's more positive
[09:03] <seb128> saying that we basically don't contribute to it but work on ayatana things at the same time and that we should stop pretending
[09:04] <didrocks> how nice this is…
[09:04] <seb128> didrocks, ignore the troll ;-)
[09:05] <hyperair> hrmm? where's this post?
[09:07] <seb128> desktop-devel-list
[09:07] <seb128> pitti, if your libusb upload fixes the crash we talked about before lucid that would rock really
[09:11] <robert_ancell> later all
[10:14] <huats> morning
[10:34] <RAOF> seb128: You wanted to talk about my work-items?  They might look slightly more scary than they are.  I've knocked off two of the bigger ones today, a number of them are for tools outside the archive which won't be affected by the A2 freeze, and some more are documentation WIs.
[10:36] <seb128> hey RAOF
[10:36] <seb128> RAOF, well, we are mid milestone and you have ticked 2 items on 21
[10:36] <seb128> the maths says you are well behind so I wanted to check if we should delay things ;-)
[10:37] <seb128> it seems those are mostly small tasks though
[10:37] <seb128> so you might have them under control but I wanted to check with you
[10:37] <RAOF> Yup.  I've now got 4/21 done, and the X server transition is done, as is mesa.
[10:37] <seb128> I also wanted to know if you are tracking the kernel team items
[10:37] <seb128> I've noticed, great work on the transitions btw!
[10:38] <RAOF> I haven't been tracking the kernel team items very closely, just every now and then.
[10:39] <seb128> ok
[10:39] <seb128> those seems investigation rather than maverick changes
[10:39] <seb128> could you still try to get an update to know if they still have those on their radars?
[10:39] <seb128> no hurry, when you have time in the next week
[10:40] <RAOF> I'll talk to apw.  There are a couple of maverick changes that could come as a result of their investigations.
[10:40] <seb128> RAOF, do you need some help on anything or should we look at moving some work items to alpha3 or do you think you have things under control?
[10:40] <RAOF> I think I've got things under control.
[10:40] <seb128> ok, great
[10:41] <seb128> I was mainly checking in case you need help or to have some item rescheduled
[10:41] <seb128> RAOF, thanks
[10:41] <seb128> http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html
[10:41] <seb128> we are on the trend line today ;-)
[10:41] <RAOF> The biggest remaining WI deliverable to the archive is the -intel DDX for i8xx cards, either forward-porting an old DDX and throwing it in universe or re-adding an old codepath to the new DDX so that 8xx cards don't die.
[10:43] <seb128> ok
[10:43] <seb128> seems wayland could be quite some work as well
[10:43] <RAOF> Wayland is the thing most likely to slip, yeah.
[10:43] <seb128> that would be fine, we don't rely on it for maverick
[10:43] <seb128> so if we get it a bit later that's fine as well
[10:43] <RAOF> Right.  It's only going to end up in a PPA for developers to play with.
[10:44] <seb128> and other changes seem mostly investigation, talking to other people, updating tools and documentation
[10:44] <RAOF> There's at least one intel hacker interested in re-introducing an old, non-flaming-death codepath for the poor old i8xx cards, so we might get a better outcome than we were dreading at UDS :)
[10:44] <RAOF> That's right.
[10:44] <seb128> which shouldn't be an issue either for alpha2
[10:44] <seb128> RAOF, nice for the i8xx cards ;-)
[10:45] <seb128> RAOF, anyway it seems things look good for alpha2, great work
[10:45] <RAOF> Ooh!  Dinner has been called!
[10:45] <seb128> RAOF, thanks for the update
[10:45] <seb128> RAOF, enjoy your dinner
[10:45] <RAOF> Catch you later :)
[10:45] <seb128> see you
[10:45] <seb128>
[10:45] <seb128> ok
[10:46] <seb128> who knows hiw way with dh7 there?
[10:46] <seb128> how do you make it call dh_girepository
[10:46] <seb128> ?
[10:47] <pitti> seb128: as an addon? or in a particular package?
[10:47] <seb128> pitti, in a package
[10:48] <pitti> if you wnat to run it after e. g. dh_install, you could write something like
[10:48] <pitti> override_dh_install:
[10:48] <pitti>     dh_install
[10:48] <pitti>     dh_girrepository
[10:48] <seb128> thanks
[10:48] <seb128> trying that
[10:49] <pitti> seb128: "man dh", FTR
[10:52] <seb128> pitti, thanks, I tried man dh7 and man debhelper
[10:53] <seb128> the first one didn't work and the second didn't have what I wanted
[11:19] <Sarvatt> ickle seems open to taking that lcdfilter patch for cairo upstream by the way
[11:20] <Sarvatt> (Chris Wilson)
[11:28] <seb128> Sarvatt, oh, nice
[11:28] <seb128> it was briefly upstream
[11:28] <seb128> and they reverted it because it was breaking some testsuite cases
[11:29] <seb128> that was before 1.8
[11:44] <asac> Riddell: hey, can you ping me and alf__ when you have a few minutes to talk about qt and embedded packaging ;)?
[11:45] <Riddell> asac: ping
[11:52] <asac> Riddell: hey
[11:52] <asac> Riddell: so ... we are thinking what we can do for qt-embedded packaging this cycle ... and of course need your input on our ideas
[11:53] <asac> Riddell: so qt-embedded needs a different soname - upstream said they will suggest one so that fine. i wonder if you would feel comfortable to make a two run build out of the qt package
[11:53] <asac> or rather want this to live in a separate source package (copied source)
[12:05] <Riddell> asac: my initial thought is that qt takes quite long enough to build as it is so separate source packages would be best
[12:22] <asac> Riddell: so ... our idea is to make the basic embedded qt stack available in the archive, but then run a ppa for now that has the apps ported to it (probably until lighthouse comes out ... which upstream said they will do a proper sonaming for  etc)
[12:23] <asac> Riddell: however, i wonder if there some kind of "inner-ring" libraries that you would think are essential and we should also make available as embedded packages
[12:24] <Riddell> asac: do you have paticular apps in mind?
[12:24] <Riddell> asac: qtwebkit is split out into a separate source package in maverick so that's an obvious inner-ring
[12:24] <Riddell> possibly phonon too since that's a supported Qt API
[12:24] <asac> Riddell: havent decided on that yet; we first want to bring the dev/sdk environment up to speed
[12:24] <asac> Riddell: but alf__ tested a few qt apps and they apparently just built and worked
[12:25] <asac> we havent went up to kde yet obviously
[12:25] <asac> guess kdelibs would be inner ring too ;) ... though i doubt thats really easy to do ;)
[12:25] <asac> alf__: ^^ ... so we should also keep qtwebkit in mind and phonon
[12:25] <asac> Riddell: did the qtwebkit split already happened?
[12:26] <Riddell> yes
[12:26] <asac> Riddell: do you expect that the libs etc. from maverick are easy to backport for lucid (during alphas having alucid packages for arm often helps as there are times where you cannot produce images etc. from the moving dev release)
[12:27] <Riddell> asac: they're easy to backport yes, we have backports in kubuntu-ppa/beta for KDE 4.5 beta backports
[12:27] <asac> great. that makes things even easier
[12:27] <asac> Riddell: should i send alf__ to you or someone else from your team for reviewing/sponsoring when he is done with the qt-embedded lib etc.?
[12:28] <asac> (i will take a first look before, but i think its better if some "qt" expert does the sanity checking)
[12:29] <Riddell> asac: sure, he's always welcome on #kubuntu-devel
[12:30] <asac> nice ;)
[12:31] <asac> didrocks: do you have good connections to mutter devs for upstreaming?
[12:32] <didrocks> asac: I 've post some patches to them, but I don't personnally know them, why?
[12:32] <asac> didrocks: just wonder if we have an established channel or if should rather go on my own ;)
[12:32] <didrocks> asac: you can go on your own, will be the same than me trying :)
[12:33] <asac> heh ok
[12:51] <mpt> mdz, hi, you asked on design.canonical.com why Ubuntu didn't offer to install Flash for the user test participants. The answer is bug 161818.
[12:52] <ubot2> Launchpad bug 161818 in ubufox (Ubuntu) "firefox flash-plugin automatic installation fails on youtube (affects: 6) (dups: 2) (heat: 46)" [Wishlist,Triaged] https://launchpad.net/bugs/161818
[12:54] <didrocks> mpt: hey, did you have some time to work on oneconf USC design yesterday?
[12:55] <mpt> didrocks, no sorry, it was #3 on my list and I didn't get to it, but it's now moved up to #2
[12:55] <didrocks> yeah \o/ ;)
[12:56] <didrocks> mpt: no worry, it was just to get this moving as alpha2 is pretty closed now. As long as you can give it a look this week, it will be ok, I hope :)
[12:57] <mdz> mpt: ah, thanks. so they always encountered flash first on Youtube, eh?
[12:58] <mpt> mdz, I don't know (I wasn't in the test), but the bug affects people visiting any Web site that uses Adobe's recommended method of detecting Flash.
[12:58] <mpt> Not just YouTube.
[13:00] <soren> mpt: do you have a link to those recommendations?
[13:00] <mpt> soren, it's in the bug report
[13:01] <soren> mpt: ah, thanks.
[13:01] <tydeas> test
[13:05] <soren> mpt: So it seems that people always get pointed to http://get.adobe.com/flashplayer/. Perhaps we could intercept people's attempts to access that and offer them the better way?
[13:07] <didrocks> soren: some kind of "if url ==". That sounds sweet :)
[13:08] <asac> didrocks: one question: why is mutter packaged as a native package :(
[13:10] <mpt> soren, ideally we'd intercept it earlier than that, but that would certainly be better than nothing.
[13:10] <didrocks> asac: hum, you mean? the version is 2.31.2-2ubuntu3 and the debian directory is in mutter_2.31.2-2ubuntu3.diff.gz, no?
[13:10] <asac> didrocks: whatever i copied from the unity ppa was a native package :(
[13:11] <asac> if you say its ok in archive then i am fine ;)
[13:11] <didrocks> asac: previous one was, because of dx packaging, but last one shouldn't, let me check
[13:12] <didrocks> asac: hum, ok, I didn't push the last version to the UNE ppa (it's the same level of patch though), so yeah, it was native for dx daily build as patch inlined
[13:13] <didrocks> asac: I will update this Thursday mutter in the UNE ppa with maverick version. Same level of functionality (same patches), but at least, a real working version
[13:13] <asac> ok let me know. i will happily adopt that ;)
[13:14] <asac> didrocks: is there a good way to test mutter without unity that you would suggest?
[13:14] <didrocks> asac: you can run it into your GNOME session with mutter --replace
[13:14] <asac> ok will try that
[13:14] <asac> wonder what happens if i do that in efl ;)
[13:15] <didrocks> that can be nice to test ^^
[13:15] <asac> didrocks: how can i re-replace that back?
[13:15] <asac> metacity --replace?
[13:15] <didrocks> maybe in a tty is safer for killing the process easily with DISPLAY=:1
[13:15] <didrocks> right
[13:15] <asac> heh
[13:15] <didrocks> or even compiz --replace if you trust the non working 3D card :)
[13:16] <asac> dont ask for too much ;)
[13:24] <asac> yay
[13:24] <asac> it works!!!
[13:24] <asac> artifacts and weird focus issues
[13:24] <asac> but it works ;)
[13:25] <asac> not really that many artifacts; just the mouse pointer/caret has a background colored box around it and isnt transparent
[13:27] <didrocks> asac: sounds awesome :)
[13:27] <didrocks> asac: how does the shiny effects are behaving?
[13:28] <didrocks> not too slow?
[13:28] <asac> didrocks: i dont know if i see the shiny effects ;)
[13:28] <didrocks> asac: you have some zoomout/zoomin while reducing/maximizing windows
[13:29] <asac> didrocks: hmm. i have -efl... there is no minimizing
[13:29] <didrocks> asac: closing maybe? you have a zoom out IIRC
[13:29] <asac> now my board hangs ;)
[13:29] <didrocks> (on the window itself)
[13:29] <didrocks> urgh :-)
[13:29] <asac> let me reboot and try to log into a gnome session or something
[13:29] <asac> wonder if i have gnome session installed
[13:30] <asac> (this thing only has 256m)
[13:30] <didrocks> hum… let's cross the fingers it will start ^^
[13:31] <asac> yep
[13:42] <asac> didrocks: zooming in and out works with desktop session ;)
[13:42] <didrocks> asac: awesome! :)
[13:42] <asac> but killing mutter kills the board reliably ;)
[13:42]  * didrocks cross fingers for unity to behave the same so :)
[13:42] <didrocks> argh :)
[13:53] <asac> for unity we have to make clutk a decent piece of software first ;)
[13:55] <didrocks> asac: ask to njpatel :)
[13:56] <asac> didrocks: already did. he redirected me to jay ;)
[13:56] <didrocks> ahah ^^
[13:56] <asac> but jay seems to hide today ;)
[13:56] <asac> as if he knew what was coming
[13:57] <didrocks> don't trust French people running away from France, they can feel when things can go badly for them :-)
[14:00] <didrocks> seb128: rhythmbox upstream has a fix in trunk for the crash we saw yesterday
[14:00] <seb128> didrocks, a workaround, yes
[14:00] <seb128> didrocks, the issue seems a pygobject one
[14:01] <didrocks> right, a workaround
[14:01] <seb128> didrocks, don't bother backporting it
[14:01] <seb128> I will do a rhythmbox snapshot update in the next days
[14:01] <didrocks> seb128: ok, perfect! Thanks :)
[14:01] <seb128> np
[14:01] <seb128> didrocks, thank you for bringing that upstream and the f-spot issue as well
[14:01] <seb128> and yes I'm watching you ;-)
[14:01] <pitti> chrisccoulson, seb128: so what's the status of firefox and those langpacks? do I have a todo item for copying those to -proposed/-updates or who will?
[14:01]  * didrocks returns and look at his back
[14:02] <seb128> pitti, they need to go to security
[14:02] <didrocks> seb128: no, you aren't there! How do you do?
[14:02] <seb128> didrocks, ;-)
[14:02] <seb128> pitti, but when firefox 3.6.4 will be available from mozilla which is still not the case I think?
[14:02] <seb128> chrisccoulson, ^
[14:02] <pitti> seb128: ok, so those are on hold for now; the copying to the moz ppa was done, I take it?
[14:03] <seb128> pitti, I would appreciate if you could do the copy on time
[14:03] <seb128> pitti, yes
[14:03] <seb128> pitti, they are in the moz ppa right now
[14:03] <seb128> pitti, they will be copied with the security update
[14:03] <pitti> seb128: I can, but I'd appreciate if someone could poke me when ffox gets copied over
[14:03] <seb128> I guess jdstrand or whoever does the copy will copy all together
[14:03] <pitti> seb128: it'd be the very same process as copying ffox itself
[14:03] <pitti> right, that seems easiest
[14:04] <pitti> instead of doing it by two different persons, I mean
[14:04] <seb128> pitti, so no todo item for you ;-)
[14:04] <pitti> ok, thanks
[14:04] <pitti> I was just wondering what to do with ArneGoetje's mails, but seems that it's being handled
[14:04]  * pitti hugs you all
[14:04] <pitti> you see, nobody is missing me :)
[14:04]  * seb128 hugs pitti
[14:04] <seb128> oh, we do!
[14:05]  * didrocks hugs pitti, we miss you
[14:05] <seb128> pitti, but good point about ArneGoetje's emails, chrisccoulson said he would reply to those some days ago
[14:06] <seb128> chrisccoulson, ^ did you copy the extra langpacks from those emails to the mozilla ppa? could you reply to the email saying where we stand with those updates?
[14:06] <pitti> seb128: I did reply with "waiting for fffox to go to -security"
[14:07] <seb128> thanks
[14:07] <desrt> robert ancell and myself are in incredibly incompatible timezones...
[14:07] <chrisccoulson> hey pitti - i don't think you need to do anything with the langpacks do you? they're currently in the u-m-s PPA, and they just get copied to -security with the security update don't they?
[14:07] <chrisccoulson> (i think that's how it's working)
[14:08] <seb128> chrisccoulson, right, that's we concluded as well there
[14:08] <chrisccoulson> seb128 - i uploaded those extra langpacks but forgot to send an e-mail ;)
[14:08] <seb128> chrisccoulson, could you confirm you did grab the updated ones ArneGoetje listed some days ago?
[14:08] <seb128> chrisccoulson, ok
[14:08] <seb128> chrisccoulson, no news of the update from mozilla yet?
[14:08] <chrisccoulson> not yet, but i think it will happen quite soon
[14:09] <chrisccoulson> i'm hoping to have karmic in a state that can be tested by tomorrow
[14:09] <seb128> ok
[14:33] <rickspencer3> tremolux, hey
[14:34] <tremolux> rickspencer3: hey Rick
[14:34] <rickspencer3> tremolux, I see mpt created a design for new apps
[14:34] <rickspencer3> and you have a work item to implement it
[14:34] <rickspencer3> does it seem feasible to get it done for A2?
[14:36] <tremolux> rickspencer3: looking
[14:40] <tremolux> rickspencer3: yep, it's feasible for A2
[14:41] <kenvandine> sucks not being able to read twitter dev docs because of fail whale!
[14:46] <tremolux> rickspencer3: I should qualify that; we may not have it pixel-perfect for A2, but to have the section there displaying the apps should be doable
[14:47] <rickspencer3> tremolux, could you add a work item such as "refine implementation to match specs" to A3?
[14:47] <tremolux> rickspencer3: yes, good idea
[14:49] <jcastro> hey kenvandine, have you been following the twitter api thing ryan is concerned about?
[14:51] <nessita> hello everyone
[14:51] <rickspencer3> hi nessita, 'sup?
[14:52] <nessita> rickspencer3: hey there! just now I remember chipaca told me to talk with you about the agenda in the next sprint in prague
[14:53] <nessita> seb128: about the package I uploaded yesterday (ubuntu-sso-client), do I have to do any further steps? I uploaded an update to https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/maverick
[14:53] <kenvandine> jcastro, yes... we are stressed about getting that resolved and SRU'd
[14:53] <nessita> seb128: would you be able to sponsor it?
[14:53] <nessita> rickspencer3: not sure what "talk about the agenda" means, but maybe you know :-)
[14:54] <rickspencer3> I don't know :/
[14:54] <seb128> nessita, hi, sorry I'm quite busy with other things right now
[14:54] <nessita> seb128: no problem, would you know who can be able to do it?
[14:54] <nessita> rickspencer3: heh, I ask Chipaca then
[16:09] <fta> Sarvatt, excellent. let me know if you have ideas to improve it, or if you need more info on the page
[16:11] <blue_anna> I'm having a problem with empathy client crashing on incoming voice calls (but not outbound)
[16:12] <blue_anna> someone suggested upgrading libpurple, another libtelepathy -- do you know if I should try one, or the other, or both?
[16:13] <didrocks> alf__: I would say, don't bump the ABI if upstream doesn't do it. Can you convince them to remove the exposal of json_*, force the external dep and so bump the soname?
[16:14] <fta> Sarvatt, i will probably add a popup for the Repositories, instead of just an "X". and i probably need to cache the data between sessions, so it's faster to update. btw, how often do you update it?
[16:16] <blue_anna> well I'm just going to guess
[16:17] <alf__> didrocks: I can try :) but I don't expect they will. According to them, the internal json-glib is not supposed to be used by distributions.
[16:17] <didrocks> alf__: another solution is to look at rdepends :)
[16:17] <didrocks> blue_anna: try on #ubuntu
[16:17] <alf__> didrocks: To see if anyone really uses the exported json_* functions?
[16:18] <blue_anna> I did -- but since I got conflicting advice about which libs were involved I thought I'd try to get it clarified here
[16:18] <didrocks> alf__: right, in the internal dependency
[16:19] <alf__> didrocks: internal dependency?
[16:19] <didrocks> alf__: sorry, I meant "to check if they use the internal json-glib"
[16:20] <didrocks>  apt-cache rdepends libclutter-1.0-0 is not that scary
[16:36] <tremolux> rickspencer3: ping for a question about the Software Center update section of the weekly status
[16:36] <rickspencer3> tremolux, sure?
[16:36] <rickspencer3> 'sup?
[16:37] <tremolux> rickspencer3: would you like that to be more a summary of the status of things, or just to highlight what's happened during the week?
[16:37] <tremolux> rickspencer3: meaning, if it's a summary, then unchanged items will be repeated
[16:37] <rickspencer3> tremolux, what happened during the week
[16:37] <rickspencer3> share info people need
[16:37] <tremolux> rickspencer3: ok, sounds good
[16:38] <tremolux> rickspencer3: thx
[16:47] <didrocks> tremolux: for "hiding non app" by default, once you are in the featured app view, you get "19 other technical item", and when you click on it, nothing happen (I just think there is no technical item in the category and apps are counted as such). Known bug?
[16:47] <tremolux> didrocks: yes, known bug  :(
[16:47] <tremolux> didrocks: I have to write it up still
[16:47] <didrocks> tremolux: ok, just to be sure, thanks :)
[16:48] <tremolux> didrocks: thanks!
[16:48] <didrocks> you're welcome ;)
[17:23] <rickspencer3> seb128, thanks for handling the meeting
[17:23] <rickspencer3> I'll be back online for a bit in like an hour or less
[17:30] <seb128> hey everybody
[17:30] <didrocks> hey seb128
[17:30] <ArneGoetje> hi
[17:30] <seb128> ArneGoetje, chrisccoulson, didrocks, tremolux, Riddell, kenvandine, pitti, tkamppeter: hello
[17:31] <seb128> did I forget anybody?
[17:31] <tremolux> hi everybody
[17:31] <seb128> rick is not available for the meeting today
[17:31] <seb128> so I'm going to lead this one
[17:31] <seb128> I hope everybody had a good weekend and start of week ;-)
[17:31] <chrisccoulson> hi :)
[17:31] <seb128> let's get started
[17:31] <seb128> https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-06-15
[17:32] <seb128> so, previous meeting actions, oneconf
[17:32] <seb128> I guess everybody has been busy and there was not happening there?
[17:32] <seb128> didrocks, ^ did you get any feedback this week?
[17:32] <didrocks> I saw tremolux did some testing
[17:32] <didrocks> but I hadn't any feedback, unfortunately
[17:32] <seb128> tremolux, thanks for helping didrocks there ;-)
[17:33] <seb128> didrocks, you might want to try emailing the ubuntu-desktop list
[17:33] <tremolux> yes, I started some testing but got bogged with other things, I will do more this week tho
[17:33] <seb128> or ubuntu-devel-discuss
[17:33] <seb128> I guess it will be easier to get feedback this way
[17:33] <didrocks> will email the list so :)
[17:33] <pitti> TBH it's the first time I hear "oneconf"
[17:33] <seb128> pitti, it's on the meeting agenda for 3 weeks now
[17:34] <tremolux> didrocks: I realize it's important that I test it because of the integration with s-c, so I will make it a priority
[17:34] <seb128> pitti, https://wiki.ubuntu.com/OneConf/Testing
[17:34] <pitti> seb128: sorry
[17:34] <Riddell> hi
[17:34] <didrocks> tremolux: thanks a lot :) users seem more interesting than developers :)
[17:34]  * kenvandine waves... sorry  mission-control-5 had my laptop pegged
[17:34] <seb128> pitti, no need to be sorry, you don't have to watch what's happening there ;-)
[17:35] <seb128> hey Riddell, kenvandine
[17:35] <seb128> ok, moving on
[17:35] <seb128> kenvandine, just on time, it's your turn
[17:35] <kenvandine> :)
[17:35] <kenvandine> ok, for DX... appmenu stuff is in main... yay
[17:35] <kenvandine> and hopefully will be by default in UNE this week
[17:35] <seb128> thanks tedg, bratsche, kenvandine, jcastro for the work on this
[17:36] <kenvandine> and seb128 :)
[17:36] <seb128> ;-)
[17:36] <kenvandine> indicator-network should make it to universe this week, but we won't put it in main yet
[17:36] <kenvandine> it lacks any way to control settings if you have problems
[17:36] <kenvandine> so that will happen in a3
[17:36] <seb128> ok
[17:36] <seb128> let's see how it goes when it's universe
[17:37] <kenvandine> indicator-sound goodies should land this week, should be nice
[17:37] <seb128> nice
[17:37] <kenvandine> on to OLS, their first week of weekly releases went well afaik
[17:37] <kenvandine> they uploaded everything they planned to :)
[17:37] <seb128> rock on!
[17:37] <seb128> go ols go!
[17:38] <kenvandine> they will be decommitting some of their a2 WIs
[17:38] <kenvandine> more to come soon
[17:38] <kenvandine> still discussing it
[17:38] <kenvandine> i think that is all i have for now
[17:38] <seb128> ok
[17:38] <kenvandine> any questions/comments?
[17:38] <seb128> thanks kenvandine
[17:38] <seb128> just a note, current appmenu is in main but still quite buggy
[17:38] <seb128> they are working actively on it
[17:38] <seb128> so maybe wait for next update round to test it
[17:38] <kenvandine> seb128, you getting that gtk patch in maverick?
[17:38] <kenvandine> i uploaded it to the une ppa for lucid
[17:39] <seb128> kenvandine, yes, will upload after the meeting
[17:39] <kenvandine> thx
[17:39] <seb128> np
[17:39] <seb128> does anybody has questions or comments?
[17:39] <seb128> I guess it's a no
[17:39] <seb128> let's move on
[17:39] <seb128> Riddell, hey
[17:39] <seb128> Riddell, kubuntu update?
[17:40] <Riddell>  - KDE SC 4.5 Beta 2 in, still compiling on arm
[17:40] <Riddell>  - MIRs needed: avogadro, openjpeg, librcps, create-resources, rekonq, pstoedit, getfem++, libspnav, plotutils
[17:40] <Riddell>  - pulseaudio added to Kubuntu by default
[17:40] <Riddell> would be nice to get those MIRs before alpha 2
[17:40] <seb128> urg
[17:40] <seb128> I don't know if rick managed to get anything done for those
[17:40] <seb128> asac, pitti: ^ where do we stand for mirs? I guess not active reviewer right now?
[17:41] <Riddell> some of those asac looked at in lucid but we never completed because we decided to keep koffice in universe
[17:41] <seb128> we waved in the unity stack since it's work coming from us but other items are queuing
[17:41] <pitti> I gave up on MIRs since I still have to do a lot on SRUs; asac kindly agreed to take over the role of assigning incoming MIRs to reviewers
[17:41] <seb128> ok
[17:41] <seb128> Riddell, I will check with rickspencer3 and asac after meeting what we can do to unblock those
[17:42] <seb128> thanks
[17:42] <seb128> does anybody has comments or questions for Riddell?
[17:42] <seb128> pitti, ok, fair enough
[17:42] <seb128> ok, moving on
[17:42] <seb128> didrocks, hey
[17:42] <seb128> UNE update?
[17:42] <didrocks> Unity is now the defaut on UNE maverick CD!
[17:43] <didrocks> The transition should be effective for lucid -> maverick UNE upgrade and lucid UNE ppa -> maverick
[17:43] <didrocks> The CD size is scary though, considering that we even don't have all the components in place (and most of them will land post alpha2 :/) (same size than amd64 image btw)
[17:43] <didrocks> New release on Thursday (late), the release will be a little bit sooner and backport to UNE lucid ppa on Friday.
[17:43] <didrocks> Apart from that, there is a wiki page stating how to test Unity on lucid and on maverick: https://wiki.ubuntu.com/DesktopTeam/Unity
[17:43]  * didrocks will add a oneconf link to it (kidding) :)
[17:43] <kenvandine> off topic... holy crap my ~/.mission-control/accounts.cfg file is 512M!
[17:43] <seb128> unity \o/
[17:43] <kenvandine> hehe
[17:44] <seb128> kenvandine, -> #telepathy ;-)
[17:44] <kenvandine> hehe
[17:45] <didrocks> (that's it for me, if nobody has questions :))
[17:45] <seb128> didrocks, thanks
[17:45] <seb128> nicely done for unity
[17:45] <didrocks> thanks :)
[17:45] <seb128> the upgrade went just fine there
[17:45] <tremolux> very cool didrock
[17:45] <tremolux> s
[17:45] <seb128> ok, moving on
[17:45] <didrocks> yeah, if anybody has some issues in upgrading scenario, do not hesitate to bug me!
[17:45] <seb128> tremolux, hey
[17:46] <seb128> software center update?
[17:46] <tremolux> hey
[17:46] <seb128> I see you copied one on https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-06-15
[17:46] <tremolux> sure, warning, wordy paste incoming:
[17:46] <tremolux> New Apps on a Stable Release: mpt has completed the design and spec for discovery/presentation of new apps here: https://wiki.ubuntu.com/SoftwareCenter#Lobby%20screen
[17:46] <tremolux> we can begin implementing the new functionality this week
[17:46] <tremolux> Buy Something: we had an overview of the payments API from Ricardo Kirkner including a walkthrough of the process, it was really helpful
[17:46] <tremolux> I've started prototyping a payments widget to learn/test/use the API
[17:46] <tremolux> Also, mvo's basic LP integration is in place now (in the most recent release), it's still in-development so will be hidden by default at next Software Center release
[17:46] <tremolux> (sort of summarizing)  ;)
[17:47]  * didrocks is eager to play with that :)
[17:47] <seb128> nice summary
[17:47] <seb128> and nice changes coming ;-)
[17:48] <tremolux> yeah, lots of stuff starting to happen for these  :)
[17:48] <seb128> thank tremolux
[17:48] <seb128> that's great work!
[17:48] <seb128> does anybody has comments or questions for tremolux?
[17:49] <tremolux> thanks seb128
[17:49] <seb128> ok, let's say it's a no, moving on
[17:49] <seb128> chrisccoulson, hey
[17:49] <chrisccoulson> hi
[17:49] <seb128> chrisccoulson, I forgot to ask you before, but could you do an update on the firefox work for us?
[17:49] <seb128> where do we stand? what issues do we still have?
[17:49] <chrisccoulson> yeah, i can give a brief update
[17:49] <seb128> thanks
[17:50] <chrisccoulson> hardy is pretty much done, with the exception of a few xulrunner rdepends yet to be ported. micahg is working on those, although they aren't high priority
[17:50] <chrisccoulson> all the issues i know about are either now resolved or have a fix in waiting
[17:50] <seb128> nice
[17:50] <seb128> the font issue got fixed then?
[17:50] <chrisccoulson> i hope to be able to get karmic in to a state to start testing tomorrow
[17:51] <chrisccoulson> yeah, i've got a fix for the font issue
[17:51] <seb128> \o/
[17:51] <seb128> karmic ready for testing, nice
[17:51] <chrisccoulson> i'm just getting the langpacks for karmic uploaded now
[17:51] <seb128> so we are almost "there"
[17:51] <chrisccoulson> firefox, xulrunner 1.9.2 and ubufox were uploaded today
[17:51] <seb128> I'm sure you will be glad once those will be out ;-)
[17:52] <chrisccoulson> yeah, we're pretty much there now. i hope to be able to start winding down from this at the end of the week
[17:52] <seb128> is there still versions to land or test after karmic?
[17:52] <chrisccoulson> there will be jaunty too, but firefox is already uploaded for jaunty
[17:52] <seb128> ok
[17:53] <seb128> thanks chrisccoulson
[17:53] <seb128> great work!
[17:53] <chrisccoulson> thanks for helping out with the testing too :)
[17:53] <tremolux> chrisccoulson: I think you know; I did some upgrade testing on my hardy netbook, it all worked fine for me
[17:53] <seb128> chrisccoulson, do you still need extra testing for those updates you think? do we need to do another call for testing?
[17:53] <chrisccoulson> awesome!
[17:54] <chrisccoulson> yeah, we should do another call for testing when jaunty and karmic are ready, but i think hardy is ok now
[17:54] <tremolux> that's cool, gotta feel good
[17:54] <seb128> ok
[17:54] <seb128> thanks chrisccoulson
[17:54] <seb128> let's move on
[17:55] <seb128> hum, seems it's my turn
[17:55] <seb128> http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html
[17:55] <seb128> so we are approching alpha2
[17:55] <seb128> and we just got back on the trend line
[17:55] <seb128> thanks everybody for updating your workitems!
[17:56] <seb128> the line goes until july 1st but changes should land for next week
[17:56] <seb128> ie june 24th
[17:56] <seb128> then we have some margin for tweaking, fixing and documentation
[17:56] <seb128> seems we are on shape for a2 though
[17:56] <seb128> I've already discussed workitems with team members out of the meeting mostly so no point to go through specs again there I think
[17:57] <seb128> if anybody has anything you want to discuss you are welcome to comment or ask questions now though
[17:57] <seb128> questions? comments?
[17:57]  * didrocks yeah for being on the trend line \o/
[17:58] <seb128> ;-)
[17:58] <seb128> ok, let's move on
[17:58] <kenvandine> ok
[17:58] <seb128> who plans to go to GUADEC there?
[17:59] <didrocks> o/
[17:59] <seb128> seems we lag a bit behind on organization but I talked to rick today
[17:59] <seb128> we will get an update for the team about registration and organization details
[17:59] <kenvandine> not me
[17:59] <seb128> I would just like to have an idea of who is going now
[18:00] <seb128> so didrocks
[18:00] <seb128> I'm going as well
[18:00] <seb128> rick is going
[18:00] <seb128> chrisccoulson, not sure if you planned to go?
[18:00] <jcastro> (remember guadec starts on wednesday this year!)
[18:00] <seb128> the 2 days before are conference days as well though
[18:01] <seb128> but not real GUADEC days
[18:01] <chrisccoulson> seb128 - i hadn't thought about it actually
[18:01] <chrisccoulson> do you think it's worth for me to go?
[18:01] <seb128> chrisccoulson, well, this week would be time to think about it ;-)
[18:01] <seb128> chrisccoulson, not so much for your main tasks
[18:01] <seb128> but you have bit doing quite some desktop and GNOME work
[18:02] <seb128> and it's in Europe
[18:02] <seb128> so it's close enough
[18:02] <seb128> chrisccoulson, let's chat after meeting if you want
[18:02] <seb128> ok
[18:03] <seb128> I think that was it from me or the agenda
[18:03] <seb128> is any having anything to add?
[18:03] <seb128> questions, comments, announces?
[18:03] <didrocks> I want to speak about banshee by default on UNE
[18:03] <didrocks> just to grab some inputs
[18:03] <didrocks> (no jcastro it's not the time to say +1, want 2 minutes ;))
[18:03] <didrocks> so, from the tests this week:
[18:04] <didrocks> IMHO banshee is feature-wise like for netbook user I guess (some corner cases like Upnp support missing, but netbook user can be considered having less need than desktop ones)
[18:04] <didrocks> There is an indicator integration (currently broken in maverick because of indicator sharp bindings) and Bertrand will work on SoundMenuV2 integration
[18:04] <didrocks> There is also the ubuntu music store plugin, it misses the "first time mp3 support download support" though.
[18:04] <didrocks> There is an extension which gives a netbook interface (used in meego). This one is great but needs some tweaking to get to our needs. For instance, you can't import music from there
[18:04] <didrocks> You have also the two interfaces (netbook and traditional ones) launched in the same time, which isn't great
[18:05] <didrocks> So, little tweaking needed to integrate that to ubuntu (maybe something like 3/4 days of work). That can worth it into my mind.
[18:05] <didrocks> Those are basically a switcher between the 2 modes, not showing both interfaces per default, rename of the panel title, activate some library by default, and some lavels, ubuntuone plugin adjustement, and radio music list per default.
[18:05] <didrocks> They can be some issues with exporting the menu (they are using there own tweaks), but we'll have to figure this out in any case.
[18:05] <didrocks> so, for me, banshee by default on UNE is a +1, any other thoughts/remarks?
[18:06] <didrocks> jcastro: do you think there a way we can encourage the community to make the netbook panel more integrated to ubuntu?
[18:07] <kenvandine> jcastro, if anyone can get it done.. it's you man!
[18:07] <didrocks> s/lavels/labels of course :)
[18:09]  * didrocks feels lonely suddenly ;-)
[18:09] <seb128> heh
[18:09] <seb128> do you think we could get input from design or user testing on the netbook ui?
[18:09] <jcastro> didrocks: sure, I just need a list of things you need (which I think we discussed last week for a minute)
[18:09] <seb128> I guess the netbook frontend is the main reason why we would like to use banshee
[18:10] <didrocks> seb128: design is very busy from what I understood, I would maybe go for some hacks, and then, have some feedback to get things moving
[18:10] <didrocks> jcastro: right, I have a more detail list, I will make it understandable and forward it to you tomorrow
[18:10] <didrocks> right
[18:10] <didrocks> for the netbook ui
[18:10] <didrocks> it's really good for small screen
[18:10] <didrocks> it doesn't handle video by design though, only music
[18:11] <kenvandine> didrocks,  and good for touch screen, right?
[18:11] <didrocks> kenvandine: better than rhythmbox or default ui. But it will require still some work
[18:11] <didrocks> but for instance, by default, you have nothing listed in it
[18:11] <bcurtiswx> kenvandine: looking at bug #590619, I'm wondering how long you've had since last reboot. My file is only 3.4K.
[18:12] <ubot2> Launchpad bug 590619 in telepathy-mission-control-5 (Ubuntu) "Unreasonable memory usage (affects: 1) (heat: 488)" [Undecided,New] https://launchpad.net/bugs/590619
[18:12] <didrocks> saw, enabling the "auto import from Music and Videos" and write: "drop some files in Music/ so that it appears here" is an easy patch
[18:12] <kenvandine> i think almost all of the file is one line from the old haze plugin implementation of the facebook chat plugin
[18:12] <seb128> didrocks, I guess we can try to enable banshee by default on UNE and wait on comments?
[18:13] <didrocks> seb128: yeah, seems reasonable. I want to hack for the end of the week on what I can do for the ui
[18:13] <didrocks> so, seeding it eow or beginning of next seems ok
[18:13] <didrocks> (and so, alpha2 with it)
[18:14] <bcurtiswx> kenvandine: OK, so workaround being to remove accounts.config and setup your accounts again.  or is there something less destructive of that file?
[18:14] <kenvandine> yay
[18:14] <kenvandine> bcurtiswx, i tried that it and it fixed the problem... but not sure if that entry was the problem
[18:15] <seb128> ok
[18:15] <seb128> seems there is not a lot of comments
[18:15] <seb128> and bcurtiswx and kenvandine are hijacking the meeting now to discuss bugs
[18:15] <kenvandine> sorry :)
[18:15] <seb128> so let's wrap up
[18:16] <seb128> didrocks, thanks, let's try to get banshee by default and see how it goes
[18:16] <seb128> only for UNE
[18:16] <seb128> don't misquote that ;-)
[18:16] <kenvandine> hehe
[18:16] <bcurtiswx> seb128: apologies, didn't know there was a meeting
[18:16] <didrocks> seb128: sweet, will do :-)
[18:16]  * kenvandine only hears what he wants to hear
[18:16] <seb128> bcurtiswx, no worry
[18:16] <seb128> thanks everybody
[18:16] <didrocks> kenvandine: fix the indicator mono binding first :p
[18:16] <seb128> see you next week
[18:16] <kenvandine> thx seb128... banshee by default :)
[18:16] <tremolux> thanks everyone!
[18:17] <seb128> keep rocking, alpha2 shapes to be a solid alpha version ;-)
[18:17] <didrocks> thanks everyone :)
[18:17] <seb128> kenvandine, lol
[18:17]  * didrocks marks evaluate banshee by default on UNE as DONE :-)
[18:18] <tremolux> didrocks: \o/
[18:18] <jcastro> didrocks: I will make the U1 banshee eval as done!
[18:18] <seb128> didrocks, waouh!
[18:18] <didrocks> jcastro: sweet :)
[18:19] <rickspencer3> kenvandine, so I don't think my desktopcouch databases are syncing between my lucid netbook and maverisk desktop
[18:19] <rickspencer3> is there a known problem, or should I troubleshoot when I get home?
[18:22] <kenvandine> rickspencer3, not known
[18:22] <rickspencer3> kenvandine, ok, I'll poke at it later
[18:23] <kenvandine> thx
[18:23] <seb128> oh, rickspencer3 is back
[18:23] <seb128> hey rickspencer3 ;-)
[18:23] <kenvandine> bcurtiswx, how big is accounts.cfg for me?
[18:23] <kenvandine> s/me/you
[18:23] <bcurtiswx> 3.4K
[18:23] <rickspencer3> seb128, I'll be here for a few minutes, then gone again
[18:24] <rickspencer3> just here long enough to be disruptive and randomizing
[18:24] <seb128> rickspencer3, be as disruptive as you want, we finished the meeting ;-)
[18:24]  * bcurtiswx wasn't any help to that
[18:25] <rickspencer3> seb128, can you repeat the main points of the meeting?
[18:25] <rickspencer3> j/k
[18:25] <seb128> rickspencer3, we agree that everybody would be on holidays for the next 2 weeks and that you would handle alpha2
[18:25] <rickspencer3> thanks seb128
[18:25] <seb128> rickspencer3, that was about it I think ;-)
[18:25] <seb128> yw ;-)
[18:26] <rickspencer3> I knew I could count on you
[18:26] <seb128> always happy to serve you and the team!
[18:28] <didrocks> I agree, my logs clearly state that :)
[18:29] <chrisccoulson> right, karmic langpacks are uploading now
[18:30] <chrisccoulson> that will take a while, so I'm going to disappear for a bit to go and buy some network cable
[18:30] <rickspencer3> chrisccoulson, nice!
[18:30] <tremolux> chrisccoulson: man, you surely do know how to have a good time!  ;)
[18:31] <tremolux> chrisccoulson: (network cable adventure)
[18:31] <chrisccoulson> lol ;)
[18:32] <chrisccoulson> i need to try and hook my printer up to my router, and i thought i could also do with hooking my docking station up to the router too (in preparation for breaking networking i start testing connman)
[18:39] <sabdfl> hi seb128, i've bumped https://bugs.edge.launchpad.net/ubuntu/+source/gtk+2.0/+bug/16492 to high, would you review unclutter for MIR and CD and provide feedback and thoughts?
[18:40] <ubot2> Launchpad bug 16492 in gtk+2.0 (Ubuntu Maverick) (and 3 other projects) "Mouse pointer should disappear when keyboard is in use and mouse isn't (affects: 18) (heat: 111)" [High,Triaged]
[18:41] <seb128> sabdfl, hey
[18:41] <seb128> sabdfl, unclutter is in main already it seems
[18:41] <seb128> sabdfl, I will review it for default installation
[18:42] <sabdfl> thanks seb128, much appreciate feedback either way
[18:42] <sabdfl> only complication is it needs to be in the session to be effective by default, aiui
[18:42] <sabdfl> open to other/better solutions to the bug
[18:43] <seb128> well, it seems something xorg itself should handle to me
[18:44] <seb128> but I don't know enough about the topic to comment on why it's not the case and what it would take to get xorg doing it
[18:44] <seb128> I will review what unclutter is doing and talk with our xorg team about that though
[18:44] <seb128> sabdfl, I will keep you updated, thanks for raising the topic
[19:02] <seb128> rickspencer3, did you have time to do something about the mir issue?
[19:02] <seb128> rickspencer3, seems kubuntu is blocked on it for alpha2 work
[19:09] <fta> tedg, kenvandine: i have the power manager set to never display its icon, yet, the indicator applet recently started to display one (it's a real desktop, i don't need a battery indicator). is that already a known bug?
[19:09] <seb128> fta, yes
[19:09] <seb128> fta, if you use maverickf
[19:09] <fta> yes
[19:10] <seb128> fta, the set_icon call has been broken in the most recent indicator-application update
[19:10] <seb128> ie icons will not change in the indicator right now
[19:10] <fta> seb128, ok, thanks. if it's already tracked, i'm happy :)
[19:11] <seb128> it is
[19:11] <fta> excellent
[19:12] <kenvandine> :)
[19:12]  * kenvandine eats... bbiab
[19:22] <seb128> didrocks, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-une-app-selection
[19:22] <didrocks> seb128: yes?
[19:22] <seb128> didrocks, where did you get a request to evaluate nautilus?
[19:22] <dobey> hey seb128; do you know what rule to specify in debian/rules to run "make check" under during the build, for example?
[19:23] <didrocks> seb128: it was a question on the "request feedback" LP features. However, when you answer those, it removes the question apparently
[19:23] <seb128> dobey, what packaging system?
[19:23] <didrocks> seb128: the question was "will nautilus still be there?"
[19:23] <seb128> didrocks, oh ok
[19:23] <dobey> seb128: hrmm? cdbs
[19:23] <dobey> (i guess that's what you're asking)
[19:23] <seb128> dobey, yes ;-)
[19:26] <fta> dobey, DEB_MAKE_CHECK_TARGET=check
[19:27] <fta> or test, or whatever your check target is called
[19:27] <seb128> dobey, what fta says
[19:27] <dobey> fta: what about for python then?
[19:27] <seb128> fta, thanks, I was searching for it ;-)
[19:28] <fta> not sure python has that, let me check
[19:29] <soren> DEB_MAKE_CHECK_TARGET is defined by class/autotools.mk
[19:30] <fta> nope, it's just implemented for makefile, autotools and perl
[19:30] <soren> it's not there if only debhelper and python-distutils are included.
[19:31] <soren> Err... I'm full of it.
[19:31] <soren> It's used in class/makefile.mk
[19:31] <fta> both autotools and perl* include makefile.mk and it's there
[19:31] <soren> ...but still, if only debhelper and python-distutils are included, it's not used.
[19:32] <soren> fta: Right.
[19:32] <fta> it's trivial to add though
[19:32] <soren> Certainly.
[19:34] <fta> but it's often not needed for python as it could be done in setup.py
[19:36] <bcurtiswx> maverick uploads from debian-unstable or -experimental?
[19:37] <micahg> bcurtiswx: auto-sync is from unstable
[19:37] <seb128> chrisccoulson, do you have any time for a non firefox task?
[19:38] <bcurtiswx> micahg: do you know how a package makes it from -experimental to -unstable?
[19:38] <micahg> bcurtiswx: do you want to merge something?
[19:38] <bcurtiswx> the new empathy is in -experimental
[19:40] <micahg> bcurtiswx: stuff can be merged from experimental as needed, but seb128 or someone else would have to approve that I think
[19:41] <seb128> bcurtiswx, we don't plan to update GNOME this cycle
[19:41] <seb128> bcurtiswx, we will get GNOME3 over 2 cycles
[19:41] <seb128> bcurtiswx, we will take empathy later on if they clarify they will not require gtk3
[19:42] <dobey> seb128, fta: thanks, it at least put me in the right place to look to do it for my python package :)
[19:45] <bcurtiswx> seb128: OK, hmm.  Thx.  Maybe I'll learn to package from a source build and provide empathy for those interested in a PPA until it requires GTK3
[19:45] <seb128> bcurtiswx, isn't the empathy team doing that?
[19:45] <bcurtiswx> seb128: the telepathy team you mean.. right?
[19:46] <bcurtiswx> seb128: the telepathy team has a PPA, yes.
[19:46] <seb128> isn't that the same team?
[19:46] <seb128> but right, them
[19:46] <bcurtiswx> seb128: yeah, i guess i never heard it referred specifically as the empathy team.. but its the same..
[19:46] <seb128> I think they will do 2.31 builds if we don't
[19:53] <baptistemm_> hi there
[19:54] <baptistemm_> pedro_, hi, could you renew my membership to ubuntu-bugcontrol ?
[19:55] <pedro_> baptistemm_, hey, yes let me have a look
[19:55] <baptistemm_> when you have time
[19:56] <pedro_> baptistemm_, renewed
[19:57] <baptistemm_> thanks a lot
[19:57] <pedro_> you're welcome
[20:01] <dobey> why the heck is my clock applet freezing
[20:05] <bcurtiswx> local temporal anomoly in subspace?
[20:05] <bcurtiswx> </being a goof>
[20:07] <LaserJock> didrocks: is there a particular reason why the UNE PPA has a newer Qt?
[20:10] <didrocks> LaserJock: it's for the appmenu testing
[20:11] <LaserJock> I see
[20:21] <LaserJock> didrocks: geeze, it's almost impossible to "uninstall" Unity on lucid
[20:23] <didrocks> LaserJock: what do you mean? you have to downgrade the upgraded package, and remove unity packages, isn't it?
[20:24] <LaserJock> yeah, but it won't downgrade
[20:24] <LaserJock> too many interdependencies that want to wipe out all of gtk
[20:25] <LaserJock> it must be the "transition" plan for the new world order ;-)
[20:25] <didrocks> LaserJock: well, the appmenu things brings a lot, right :-)
[20:25] <LaserJock> perhaps it should have its own PPA
[20:25] <didrocks> but apt-cache policy and apt-get install lib=<…> FTW :)
[20:26] <didrocks> we discussed that a lot, but we think that people wanting to test should have the full maverick experience
[20:26] <didrocks> (an easy way to get it)
[20:27] <jcastro> LaserJock: I should make a note in the wiki about that.
[20:28] <didrocks> jcastro: some big red blinking warning? :)
[20:28] <LaserJock> from that PPA I have 129 .debs listed
[20:28] <LaserJock> that's a rather large PPA
[20:29] <bcurtiswx> seb128: Zdra in #empathy on gimpnet  says he doesn't think they will require gtk3.0 this cycle
[20:29] <didrocks> 129?
[20:29] <didrocks> yeah, but there are binary one whith different version
[20:29] <didrocks> oh qt…
[20:29] <didrocks> maybe it has a lot of packages
[20:29] <bcurtiswx> seb128: but its my word, idk what you would need to make desktop team feel better about including empathy this cycle
[20:30] <didrocks> LaserJock: right, qt ones have a lot, so if you have a qt app, it will upgrade a lot
[20:30] <didrocks> (away for half an hour, bbiab)
[20:30] <bcurtiswx> cya didrocks
[20:30] <didrocks> cia bcurtiswx
[20:32] <jcastro> LaserJock: didrocks: how's this? https://wiki.ubuntu.com/DesktopTeam/Unity
[20:33] <jcastro> oops, pages->packages
[20:33] <didrocks> jcastro: sounds great :)
[20:34] <LaserJock> jcastro: I guess that'd work
[20:34] <didrocks> the missing script is really a script to "clean" from a ppa for you, as xorg-edgers have. But as we don't really support downgrading, it should work for most cases
[20:34] <LaserJock> I had to do: sudo apt-get install gtk2-engines-pixbuf=2.20.1-0ubuntu1 libgail-common=2.20.1-0ubuntu1 libgail18=2.20.1-0ubuntu1 libgtk2.0-0=2.20.1-0ubuntu1 libgtk2.0-dev=2.20.1-0ubuntu1
[20:34] <didrocks> but we can still have cornercases where the behavior isn't exactly the same
[20:34] <LaserJock> the rest I could remove/downgrade OK in synaptic
[20:35] <didrocks> LaserJock: right, you can't say "for this source package, downgrade all binary ones to <version>"
[20:35] <didrocks> that would be sweet as well :)
[20:35] <LaserJock> normally I use synaptic
[20:35] <LaserJock> but it wouldn't let me do those at the same time
[20:35] <didrocks> I don't really know how that works with synaptic TBH
[20:35] <didrocks> ok
[20:36] <LaserJock> I didn't know you could do = with apt
[20:36] <didrocks> well, now you know :)
[20:36] <didrocks> (really away now)
[20:42] <Zdra> bcurtiswx, seb128: Unless something force us to use gtk3.0 (which I doubt since libunique is going to be ported) I don't think we'll hard-dep on gtk3
[20:43] <Zdra> IMO being shipped in ubuntu is by many order of amplitude more important for us than requiring gtk3
[20:44] <bcurtiswx> :)
[20:46] <seb128> Zdra, thanks
[20:46] <seb128> Zdra, I think we will update, if you really needs to depends on gtk3 we will figure what to do
[20:47] <seb128> Zdra, we can distro change to not require gtk3 or you can keep ifdef in the code maybe for this cycle
[20:47] <Zdra> seb128, maybe wait for cassidy's confirmation as he is maintainer, but I think he agree with me on this :)
[20:47] <seb128> right
[20:47] <seb128> there is no hurry for it
[20:47] <Zdra> since today we dep on gtk 2.21.2 and we build with GSeal and everything
[20:48] <Zdra> so we should be gtk3-ready :p
[20:48] <Zdra> once all our deps get ported too
[20:50] <seb128> Zdra, right
[23:09] <TheMuso> Good morning.
[23:33] <RAOF> TheMuso: Good early morning!
[23:36] <TheMuso> Indeed. Tis a lovely morning here in Sydney.
[23:42] <RAOF> It's quite cold here (2℃, apparently).
[23:42] <RAOF> Hm.  Time to shift locations.  Apparently the electricians will want to be pulling the power up and down a lot today.v
[23:51] <TheMuso> heh


[13:03] <BluesKaj> Hi all
[17:28] <configuration> test
[18:48] <lardayn2> he was serious about testing.


[04:54] <pitti> Good morning
[04:55] <pitti> cjwatson: g-i> thanks for the heads-up
[05:47] <lucidfox> Question
[05:47] <lucidfox> Where and how do I ask for my Ubuntu Member status to be revoked?
[06:01] <pitti> lucidfox: you can launch any LP team (like https://launchpad.net/~ubuntumembers) with the "Leave this team" button
[06:01] <pitti> lucidfox: err, "launch" →  "leave", sorry
[06:01] <pitti> in leavepad :)
[06:01] <lucidfox> heh
[06:24] <pitti> infinity: wow! https://launchpad.net/builders
[06:24] <pitti> infinity: we have multi-arch builders now?
[06:25] <pitti> infinity: so if I was to throw 823948239 langpacks at them, they'd  all build them in no time? :-)
[06:27] <StevenK> pitti: We have for a little while. wgrant is who you want to buy a fair bit of beer.
[06:27] <pitti> wgrant: woo! many thanks for this
[06:27] <pitti> lftp wgrant
[06:27] <pitti> lcd /cellar/beer-rack/
[06:27] <pitti> mput *
[06:28] <StevenK> And now wgrant is suffering alcohol poisioning?
[06:28] <StevenK> :-P
[06:30] <wgrant> pitti: Yeah, you can now drown the amd64 buildds as well :D
[06:30] <pitti> first trusty langpacks built and tested, throwing buildd-wards then
[06:32] <pitti> wgrant: I guess https://dev.launchpad.net/Translations/LanguagePackSchedule is not current, right?
[06:32] <pitti> wgrant: do we build trusty langpacks on Tue and Thu now (in LP)?
[06:34]  * pitti watches all his little minions on https://launchpad.net/builders
[06:34] <wgrant> pitti: I've updated that page
[06:34] <wgrant> At least the export column
[06:34] <pitti> thanks
[06:35]  * pitti desperately looks for an "Edit" link
[06:35] <wgrant> You need to log in first
[06:35] <pitti> Logged in as   pitti
[06:35] <wgrant> Ah, you probably need to be a member of ~launchpad-doc
[06:36] <wgrant> What should the PPA schedule look like?
[06:37] <pitti> wed, fri: trusty, thu: saucy, tue: precise (currently disabled)
[06:37] <pitti> wgrant: i. e. export day + 1
[06:38] <wgrant> Right
[06:39] <pitti> wgrant: thanks!
[06:40] <wgrant> np
[07:46] <dholbach> good morning
[08:36] <pitti> xnox, stgraber: FYI, it seems fstrim doesn't support LVM (I created a LUKS and an LVM from two PVs), too bad
[08:37] <pitti> xnox, stgraber: and neither does discard
[08:39] <pitti> curiously, hdparm -I /dev/mapper/testlvm-fivem works (it "looks through" the mapper)
[08:39]  * pitti does some RTFM, "fstrim lvm" has plenty of google juice
[08:42] <pitti> ah, /etc/lvm/lvm.conf needs to have issue_discards = 1
[08:52] <zyga> hi
[08:52] <zyga> running trusty daily, I cannot log in, while mouse works okay in lightdm keyboard seems to just be ignored (apart from being able to switch to other vt)
[08:52] <zyga> has anyone seen this issue?
[08:53] <zyga> currently on lighdm 1.9.5-0ubuntu1
[09:08] <pitti> stgraber: so we'll need to add the "allow-discards" option to crypttab in partman; is that something you feel up to? (I added an unowned WI)
[09:09] <pitti> stgraber: the option isn't enabled by default in cryptsetup because it exposes additional information on the raw device (according to the manpage), but for a "full disk encryption" setup we certainly want it
[09:11] <RAOF> I'm not sure that we do want it for full disk encryption? It leaks filesystem details.
[09:12] <pitti> the alternative is "your SSD sucks after a few weeks of usage"
[09:12] <pitti> "For  example,  information leaking filesystem
[09:12] <pitti>               type, used space, etc. may  be  extractable  from  the  physical
[09:12] <pitti>               device  if  the  discarded  blocks  can  be located later."
[09:13] <pitti> that sounds a bit fuzzy, not sure how big the impact is?
[09:13] <pitti> i. e. if you get the raw SSD, look for discarded/non-discarded blocks, and from their pattern make assumptions about the state of the disk
[09:13] <RAOF> Yeah, probably not much.
[09:14] <pitti> but IMHO that's an acceptable compromise to do to keep your SSD in a working state in the first place
[09:14] <pitti> if you are concerned with that, the first thing you'd need to do is to completely fill your drive once
[09:15] <pitti> and then live with getting 1/50th of its normal write performance
[09:26] <xnox> pitti: those that want privacy with ssd, would use self-encrypting drives. in which case one cannot analyze / infer anything from the filesystem, since block devices are not expose until after ATA unlock.
[09:27] <pitti> xnox: ah, good point
[09:27] <xnox> pitti: thus imho, trim should be enabled.
[09:28] <xnox> pitti: then again why use cryptsetup with self-encrypting drive.... is beyond me =)
[09:29] <pitti> hm, issue_discards doesn't seem to work for me (LVM); there's debian bug 717313, but it didn't get an answer
[09:30] <xnox> pitti: hm =( last time i looked into this, i thought that it is safe enough these days to enable "issue_discards" unconditionally, it just wouldn't do anything on spinny drives.
[09:31] <xnox> pitti: i can test it harder here on an ssd. as well.
[09:31] <pitti> xnox: yes, it says it's only having an effect if kernel and drive support it
[09:31] <pitti> xnox: but I enabled it, update-initramfs, reboot, and still fstrim says "invalid ioctl"
[09:31] <pitti> (IOW, not supported)
[09:34] <pitti> xnox: oh, perhaps I need to do this before pvcreate/vgcreate/lvcreate, /me tries
[09:36] <pitti> xnox: oh, nevermind; I formatted it with ext2, that's the bit which breaks it
[09:37] <zyga> running trusty daily, I cannot log in, while mouse works okay in lightdm keyboard seems to just be ignored (apart from being able to switch to other vt)
[09:37] <zyga> is this a known issue, any way to work around it to do stuff?
[09:38] <pitti> xnox: so, issue_discards isn't necessary for fstrim, only if you modify the LVM structure; we should enable it anyway, though
[09:39] <xnox> pitti: excellent \o/
[09:40] <pitti> xnox: so, for "normal" partitions I do an hdparm -I check and fstrim; for devmapper I do fstrim 2>/dev/null || true
[09:40] <pitti> as decomposing the LVM to its PVs and running hdparm on them is probably way more costly than just tryign to call fstrim
[09:40] <pitti> xnox: does that seem ok to you?
[09:41] <xnox> yeap.
[09:41] <pitti> xnox: now my fstrim cron job works for normal partitions, cryptsteup, and LVM
[09:41] <xnox> which package is it going to live in?
[09:41] <pitti> xnox: http://people.canonical.com/~pitti/scripts/fstrim
[09:42] <pitti> xnox: hm, how about util-linux?
[09:42] <pitti> (that ships fstrim)
[09:42] <pitti> xnox: ideas appreciated
[09:44] <xnox> sounds good, if util-linux maintainer would be ok with that. lamont infinity ^
[09:46] <GunnarHj> xnox: Hi Dimitri!
[09:46] <xnox> GunnarHj: holla! =)
[09:46] <GunnarHj> xnox: Have you noticed bug 1260604?
[09:47] <xnox> GunnarHj: yes, i have. and asked for logs on it.
[09:47] <GunnarHj> xnox: Aha, see that now. ;-)
[09:48] <Laney> xnox: http://paste.debian.net/plain/70639
[09:48] <Laney> from ricotz, haven't looked into it
[09:50] <GunnarHj> xnox: It's easy to install and switch to GDM for test purposes.
[09:53] <xnox> Laney: that seems right.
[09:54] <xnox> Laney: will upload, or can ricotz upload it?
[09:55] <Laney> nope
[09:55] <Laney> you do it if you confirm it fixes the problem
[09:55] <xnox> Laney: ack.
[10:23] <pitti> xnox, lamont, infinity: filed debian bug 732054 FTR
[10:25] <seb128> dpm, pitti: can one of you approve https://translations.launchpad.net/ubuntu/trusty/+source/evolution/+imports ?
[10:25] <seb128> the 3.10 template
[10:26] <seb128> the new langpacks still have 3.8 which means no translation since we are on 3.10 :/
[10:26] <seb128> same for https://translations.launchpad.net/ubuntu/trusty/+source/evolution-data-server/+imports
[10:26] <pitti> seb128: I can't approve :/
[10:26] <seb128> :-(
[10:27] <seb128> let's see if dpm can
[10:27] <seb128> we might need wgrant or somebody with lp powers?
[10:27] <pitti> meh, BP WI diff emails are broken, they only show the removals
[10:28] <seb128> pitti, since when? I got some correct ones yesterday
[10:28] <pitti> for several months already
[10:28] <seb128> are you sure it's not your email client?
[10:28] <pitti> also, it seems if you change WIs with the Ajaxy bits, when saving it back it shows the old one
[10:28] <pitti> you need a page reload to update
[10:28] <pitti> seb128: yes
[10:28] <pitti> its LP
[10:28] <seb128> wfm
[10:29] <pitti> i. e. when changing them twice, you need to reload, otherwise you'll destroy your first changes
[10:29] <pitti> gema had it as well, I'm not alone
[10:29] <Laney> FF?
[10:29] <pitti> Laney: yes
[10:29] <pitti> (our default browser, I might point out :) )
[10:29] <Laney> yeah, just checking
[10:29] <Laney> I use it too (and haven't seen that)
[10:29] <pitti> but as the mails reflect that, it doesn't seem browser specific?
[10:30] <Laney> seems like you were describing two issues
[10:30] <seb128> pitti, wfm
[10:30] <seb128> I just editing https://blueprints.launchpad.net/ubuntu/+spec/client-s-system-settings-panels in firefox
[10:30] <seb128> changed charles in charlesk
[10:30] <seb128> and the page had the correct content without reload
[10:30] <seb128> or refresh
[10:30] <Laney> http://paste.ubuntu.com/6565987/
[10:30] <Laney> I did that yesterday
[10:31] <seb128> right, that's the email I got
[10:31] <seb128> correct diff
[10:31] <brendand> pitti, fstrim script. handy
[10:31] <seb128> pitti, maybe QA blueprints have something special that confuses lp?
[10:31] <Laney> the diff does look a bit weird actually
[10:31] <GunnarHj> xnox: ricotz's suggestion is not sufficient to fix bug 1260604. I added my ~/.xsession-errors to the bug.
[10:31] <Laney> why are there all those Work items: sections?
[10:32] <Laney> unless I did actually break that
[10:32] <pitti> seb128: no idea what the difference is; they are ubuntu specs like everything else
[10:32] <seb128> pitti, yeah, me neither, needs some lp debugging I guess :/
[10:32] <seb128> pitti, I just wanted to point out that the feature is not broken across the board
[10:32] <pitti> seb128: good to know
[10:33] <seb128> Laney, but yeah, that diff of yours is buggy as well, it has several "+ Work items for ubuntu-14.01:"
[10:34] <Laney> so I can believe some parser is going wrong
[10:35] <seb128> pitti, did you file a lp bug about that yet?
[10:35] <pitti> seb128: gema said she was going to back then, I'll have a look
[10:41] <caribou> where is the best place (i.e. irc room) to ask debian packaging specific questions ?
[10:46] <seb128> caribou, you can ask here I guess
[10:47] <caribou> seb128: thanks, but I may have found the answer myself
[10:47] <seb128> caribou, if you need confirmation you can still ask here ;-)
[10:48] <caribou> seb128: I need to run a script only at build time & needed to know where it would fit best
[10:48] <seb128> debian/rules?
[10:49] <caribou> seb128: thought of it, but it's a bunch of subshell cmds so it doesn't fit the Makefile format
[10:49] <caribou> seb128: I created a script in debian/ & used 'override dh_auto_build" to cal lit
[10:49] <seb128> caribou, well, you can always write a shell script in debian/ and call that from the rules
[10:50] <seb128> caribou, +1 ;-)
[10:50] <caribou> seb128: then all good then ;) thanks
[10:50] <seb128> yw!
[11:03] <dpm> seb128, pitti, I was on the phone, let me have a look at it now (re: Evo translations)
[11:05] <seb128> dpm, hey, thanks
[11:06] <dpm> np, evolution is a bit of an annoying template, as they version the .pot file and we have to be careful we don't mess up LP's translation sharing and template names
[11:06] <seb128> right
[11:06] <seb128> we screwed in saucy
[11:07] <seb128> we didn't approve the 3.8 template, so the langpack shipped with 3.6
[11:07] <seb128> which means no translation
[11:08] <dpm> ah, let me fix saucy too, then
[11:10] <dpm> it seems someone fixed the domain and .pot import path in saucy already, let me have a look whether the 3.8 imports worked there
[11:15] <tseliot> pitti: I think I'm going to enable hybrid graphics in ubuntu-drivers-common (in 14.04) following the logic of bug #1260683 (which is really about Jockey in Precise). Any thoughts?
[11:16] <dpm> seb128, pitti, so - saucy: everything seems fixed now, we need a full language pack export and release to get Evo translations shipped; - trusty: imports for the 3.10 .pot files should work now, will need to watch the imports queue for the next hour or so if they really get imported
[11:16] <seb128> dpm, ok, thanks for fixing those!
[11:17] <pitti> tseliot: I thought we already don't offer the nvidia driver on hybrid systems in u-c-commmon? or did you change that as we can properly support hybrid now?
[11:17] <pitti> tseliot: so, what do you want to change, offer nvidia only if there is no battery, or something such?
[11:19] <dpm> seb128, np, if I'm away happyaron can probably help with templates, as he's got permissions as part of the ubuntu-translations-coordinators team. I'm happy to add anyone else to the team in LP if they want to help. They'd simply need to have read https://wiki.ubuntu.com/UbuntuTranslationsCoordinators and be familiar with LP
[11:19] <seb128> dpm, ok, great
[11:21] <tseliot> pitti: in u-d-c I plan to check if it's a laptop. The logic is already in nvidia-prime, so I think I can reuse that code
[11:24] <tseliot> pitti: so, yes, we can look for /sys/class/power_supply/ and  /proc/acpi/button/lid
[11:30] <cjwatson> pitti: multi-arch builders - isn't it glorious
[11:30] <pitti> cjwatson: *sheds a tear*
[11:30] <pitti> it's a joy to look at
[11:56] <davmor2> cjwatson: you seem overly overjoyed by this comment.  So I guess it's hugely important :)  So congratulations :)
[12:16] <xnox> pitti: seb128: i also noticed that email diffs for blueprints, do not match reality.
[12:19] <seb128> xnox, do you have any idea when that started?
[12:20] <seb128> infinity, wgrant, cjwatson: do you know if the code on launchpad that generates diff for blueprints changed?
[12:20] <cjwatson> don't know sorry
[12:21] <seb128> ok, thanks
[12:22] <xnox> seb128: no, i got first notification last night. Where a change of the workitem, arried as "- workitem" without matching "+ workitem new description" and thus I got a ping "why did you drop that workitem" on irc.
[12:23] <seb128> k
[12:28] <seb128> diwic, hey, is https://bugs.launchpad.net/bugs/1131220 still on your todolist?
[12:33] <wgrant> xnox, seb128: I came upon a potential issue in the caching of workitems a few months ago, but I didn't get to the bottom of it
[12:33] <wgrant> I didn't think it was affecting emails too
[12:33] <wgrant> Do you have some idea of when it started?
[12:34] <xnox> wgrant: the ajax behaviour is weird. click edit button; change workitem; confirm. and on display the workitem is gone (and email is sent with workitem gone), yet on page refresh it shows the updated workitem description.
[12:35] <xnox> wgrant: to be honest the cache/ajax behaviour we can live with. But, wrong diff sent in emails is sad. Can email diffs be generated from force updated cache?
[12:35] <seb128> xnox, the ajax issue is a problem because if you click edit again, you undo your previous changed
[12:36] <xnox> wgrant: well, we only started using workitems since last vUDS..... i think previous vUDS was ok. so a window of 3 months?
[12:36] <seb128> changes
[12:36] <wgrant> They're probably the same bug.
[12:36] <xnox> seb128: oh, that's bad =(
[12:36] <seb128> wgrant, pitti mentioned it today, xnox saw it recently
[12:36] <seb128> wgrant, I would say it's fairly recent, but I don't think we have too much details
[12:36]  * seb128 checks his blueprint emails
[12:36] <pitti> wgrant: I think I heard it first from gema during the QA team sprint in Boston, hang on
[12:37] <pitti> wgrant: so around september 12
[12:37] <wgrant> Right, thanks.
[12:38] <wgrant> I don't see a bug. Could someone please file one?
[12:38] <pitti> I'll do
[12:41] <pitti> seb128, xnox, wgrant: bug 1260714
[12:41] <seb128> wgrant, pitti: looking in my blueprint inbox the first "weird diff" is from 11/28, but we don't use blueprint that much recently and the ones I had in the previous weeks before that are mostly simple edit where a couple of lines were changed (and those seem less likely to hit the issue)
[12:41] <seb128> pitti, danke
[12:42] <pitti> feel free to adjust the title to something better, of course
[12:42] <diwic> seb128, yes. I was sprinting in Taipei entire last week, and been mostly on sick leave this week.
[12:43] <seb128> diwic, ok, get better!
[12:59] <wgrant> seb128, pitti, xnox: Thanks for pointing that out, fixed.
[12:59] <pitti> wgrant: nice, thanks!
[12:59] <seb128> wgrant, oh, nice that you figure it out, thanks!
[13:00] <wgrant> (the notification and display bugs were indeed the same thing)
[13:11] <dholbach> cjwatson, thanks a lot! :)
[13:39] <ricotz> GunnarHj, please test https://launchpad.net/~gnome3-team/+archive/gnome3-staging/+sourcepub/3726442/+listing-archive-extra and make sure you restart gdm after
[13:55] <plars> pitti: did you happen to see my comments on bug #1258245 - any chance of getting that group added for syslog, or does it create too many concerns?
[13:59] <pitti> plars: seems acceptable to me
[14:25] <seb128> dpm, wgrant: do you know where is launchpad importing the translation templates from?
[14:25] <wgrant> seb128: What do you mean?
[14:25] <seb128> wgrant, https://translations.launchpad.net/ubuntu/trusty/+source/gtk+3.0/+imports
[14:25] <wgrant> Ubuntu templates are imported from source packages, as alway
[14:25] <wgrant> s
[14:26] <seb128> wgrant, the recent gtk 3.10 update didn't make it there
[14:26] <seb128> the pot is in https://launchpad.net/ubuntu/trusty/+upload/6587684/+files/gtk%2B3.0_3.10.6-0ubuntu2_i386_translations.tar.gz
[14:26] <seb128> which is the translation file from the build
[14:26] <seb128> it's also in the srcdir
[14:26] <seb128> that's from https://launchpadlibrarian.net/159463876/buildlog_ubuntu-trusty-i386.gtk%2B3.0_3.10.6-0ubuntu2_UPLOADING.txt.gz
[14:34] <seb128> wgrant, any idea how to debug that?
[14:36] <wgrant> seb128: Hm, weird
[14:36] <dpm> seb128, wgrant, it might be that LP did not import the pot file because the path in the source package changed
[14:36] <seb128> dpm, I doubt it did
[14:37] <seb128> it should still be po/gtk30.pot
[14:37] <wgrant> Also it should have still appeared in the queue.
[14:37] <seb128> dpm, wgrant: https://translations.launchpad.net/ubuntu/trusty/+source/gtk+3.0/+imports also doesn't list any .po which is weird
[14:37] <seb128> since the tarball I downloaded has those
[14:37] <dpm> wgrant, but it is in the queue, is it not? -> https://translations.launchpad.net/ubuntu/trusty/+source/gtk+3.0/+imports
[14:38] <seb128> dpm, no, those are from 2013-11-01
[14:38] <wgrant> dpm: There should be something from December, I thought
[14:38] <seb128> that's old gtk 3.8
[14:38] <wgrant> There was an upload two days ago
[14:38] <seb128> gtk 3.10 was this week
[14:38] <dpm> ok, I see
[14:38] <wgrant> And I see that the jobs were run
[14:39] <dpm> in any case, it's also strange that the old templates in that queue were not imported, either
[14:44] <seb128> dpm, wgrant: can I upload the template by hand or do you prefer to keep the buggy state for debugging?
[14:45] <dpm> seb128, I'll defer to wgrant to comment on that, as I wouldn't know how to debug LP, but from my side, it's fine to manually upload
[14:47] <wgrant> seb128: I think it's fine to upload manually.
[14:47] <wgrant> I can't easily debug it tonight.
[14:47] <seb128> wgrant, no hurry, do you want a bug report for it?
[14:47] <wgrant> seb128: That'd be good
[14:49] <arun__> guys, the new language has been added to the debian ; now what should I do to obtain the language in the Ubiquity ?
[14:51] <xnox> arun__: as of when new language / translations are uploaded into d-i components in Debian, and as of then those translations are merged into ubuntu d-i components and then finally ubiquity reuploaded.
[14:51] <xnox> arun__: so it's automatic, but it does depend on uploads of d-i components in debian & ubuntu
[14:51] <xnox> arun__: there are some ubiquity specific strings, those would need to be translated on launchpad. but those are not the majority of installer used strings.
[14:52] <xnox> (although usually more visible)
[14:52] <arun__> xnox: the language option must be available in the ubiquity thats all ; will that remained to ubiquity from debian ?
[14:53] <xnox> arun__: define "available" ? cd boot-splash language selection, or ubiquity greeter list of languages, or keyboard selection list of languages?
[14:54] <xnox> i don't understand this sentence "will that remained to ubiquity from debian ?" can you say it in another way?
[14:54] <seb128> dpm, wgrant: https://bugs.launchpad.net/launchpad/+bug/1260754
[14:55] <arun__> xnox: I mean that, if the language selection is available in debian installer, will that remain the same in  the ubiquity installer ??
[14:55] <dpm> thanks seb128, subscribing
[14:56] <xnox> arun__: after a delay, it will eventually.
[14:56] <arun__> xnox: oh ok thanks !!!
[14:56] <xnox> arun__: it depends when ubiquity and d-i was last rebuild.
[14:56] <arun__> xnox: ok
[15:03] <wgrant> seb128: Hum, I think I see why. I'm not sure if the manual upload will work.
[15:03] <wgrant> The whole import system is pretty much a total mess.
[15:04] <wgrant> It tries to eliminate duplicates
[15:04] <wgrant> An upload from a package will helpfully ignore any files where duplicates can't be resolved.
[15:05] <seb128> :/
[15:07] <wgrant> seb128: It probably isn't normally a problem, because there won't be dupes once import processing is enabled and the queue clears
[15:08] <seb128> wgrant, what happened there? we uploaded before the imported was on?
[15:08] <wgrant> seb128: I think the imports were only switched on a few hours ago when dpm poked things
[15:08] <wgrant> The initial vim etc. upload went through just recently
[15:08] <seb128> k
[15:09] <seb128> not sure when "duplicates can't be resolved", but in doubt it seems it should import rather than bail out?
[15:10] <wgrant> I don't know Translations well, I'm afraid
[15:10] <wgrant> But there are frequently duplicates that should be ignored/merged/something
[15:10] <wgrant> Because each arch produces a tarball
[15:10] <wgrant> And they would usually all be effectively identical.
[15:10] <seb128> right
[15:11] <seb128> do you have an idea how to force/fix the current situation then?
[15:11] <stgraber> pitti: should be reasonably straight forward to implement, so sure i can do that
[15:11] <pitti> stgraber: thanks, handed to you
[15:11] <pitti> stgraber: I think we cover all the bases now
[15:12] <wgrant> seb128: The next package or manual upload after the queue clears in a few days should work
[15:14] <seb128> wgrant, thanks
[15:15] <seb128> wgrant, btw while we are speaking about gtk, I just opened https://bugs.launchpad.net/launchpad/+bug/1260760 ... that one is annoying as well ;-)
[15:15] <seb128> but->bug
[15:15] <seb128> wgrant, basically doing any change to a gtk+3.0 bug (without using ajax) unset the source silently
[15:16] <wgrant> wat
[15:17] <seb128> wgrant, try yourself, just go to e.g https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1252112 and click "Save Changes" in the bug table
[15:17] <seb128> without doing anything
[15:17] <seb128> it's "fun" :p
[15:27] <asac> doko: the hostname upload, can you give us some confidence that it wont regress our touch image?
[15:40] <attente> hi, i'm only getting square glyphs in plymouth
[15:40] <attente> is it because of the dependency change from ttf-dejavu-core to fonts-dejavu-core?
[15:41] <seb128> attente, do you have any debug info in /var/log/plymouth-debug.log ?
[15:41] <seb128> hum
[15:42] <seb128> that log is old here
[15:42] <seb128> I've the feeling you need to turn on debug to get that :p
[15:43] <attente> yeah. i don't even have that file
[15:43] <seb128> attente, https://wiki.ubuntu.com/Plymouth#Debugging
[15:43] <seb128> seems like you need "plymouth:debug" on your grub options
[15:43] <seb128> follow the instructions there and see if the log has something useful?
[15:43] <seb128> slangasek, ^ hey, do you know if that's a known issue?
[15:44] <seb128> attente, when did that start?
[15:44] <seb128> xnox did some changes recently, wonder if we can blame him :p
[15:44] <attente> i only just noticed it now
[15:44] <xnox> hm?! =)
[15:45] <xnox> i did not change the fonts though =)
[15:45] <seb128> right
[15:45] <xnox> attente: what theme / plugin are you using?
[15:45] <xnox> (screen or photograph of the problem?)
[15:45] <seb128> xnox, you recent change reminds me I meant to file a bug, when it's checking discuss I don't get progress % indicated anymore
[15:45] <seb128> (since saucy I think)
[15:45] <seb128> attente, I guess you should reboot in debug and get log/photo and open a bug ;-)
[15:46] <attente> xnox, ok, i'll get you a screen
[15:47] <seb128> xnox, slangasek: btw, I set https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1165522 to high, it's the most reported plymouth issue on e.u.c and with a non trivial number of reports
[15:47] <seb128> could be a "nice to fix" for the lts ;-)
[15:48] <xnox> seb128: also please attach a photo / screenshot of the problem were there is no % indication of fsck.
[15:48] <seb128> xnox, I guess it's working for you?
[15:48] <seb128> I wonder if that could be a problem in the french translation
[15:48] <xnox> seb128: there is progress in *-logo and details plugins. That is server  & KMS enabled machines.
[15:48]  * seb128 checks translation
[15:49] <seb128> I've an intel machine
[15:49] <seb128> so KMS I guess
[15:49] <seb128> it was working until some point in saucy
[15:49] <xnox> seb128: there is no progress on "ubuntu-text" aka "Ubuntu 13.10/ . . . . ." splash.
[15:49] <xnox> seb128: please check if you get progress upon pressing Esc
[15:49] <seb128> I've the graphical one
[15:49] <seb128> ok
[15:49] <attente> xnox, https://www.dropbox.com/s/3tspo4u05zlr9x7/2013-12-13 10.47.14.jpg
[15:49] <attente> er
[15:51] <xnox> attente: right, do you use full disk encryption? and what locale is set as the system locale?
[15:51] <attente> https://www.dropbox.com/s/3tspo4u05zlr9x7/2013-12-13%2010.47.14.jpg
[15:51] <xnox> attente: please file a bug with that screenshot, and comments about locale / full-disk encryption.
[15:51] <attente> xnox, yes
[15:51] <seb128> the debug.log might be useful there as well
[15:52] <attente> xnox, using full disk encryption, not sure what the system locale is
[15:53] <attente> is ttf-dejavu-core installed on your systems?
[15:54] <seb128> attente, no, it's transitional
[15:54] <seb128> attente, http://paste.ubuntu.com/6567307/
[15:54] <attente>  /etc/default/locale is en_CA.UTF-8
[15:55] <attente> seb128, i don't have the metapackage, but i guess that's not necessary
[15:55] <seb128> attente, likely not
[15:56] <attente> i'll get a debug log for you
[16:14] <GunnarHj> ricotz: ping?
[16:16] <GunnarHj> ricotz: I built a-s locally earlier today with your patch. Still no success with GDM. See bug 1260604
[16:20] <ricotz> GunnarHj, please test the patch which i attached or https://launchpad.net/~gnome3-team/+archive/gnome3-staging/+sourcepub/3727470/+listing-archive-extra
[16:21] <ricotz> GunnarHj, 0.6.35-0ubuntu6~trusty2 works despite harry33's comment
[16:21] <ricotz> GunnarHj, the pastebin contained a typo
[16:22] <GunnarHj> ricotz: ?? Actually I diff'ed them and found them to be identical.
[16:22] <ricotz> they are not identical
[16:23] <GunnarHj> ricotz: Ok, I'll try with the debs in the PPA then. Getting back to you in 30 min or so.
[16:24] <ricotz> GunnarHj, alright
[16:25] <attente> xnox, seb128, LANG="en_CA.UTF-8"
[16:25] <attente> LANGUAGE="en_CA:en"
[16:25] <attente> er,
[16:25] <attente> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1260792
[16:26] <attente> i didn't see anything related to the font in the debug log
[16:27] <seb128> yeah, me neither
[16:40] <GunnarHj> ricotz: Success with ~trusty2! :)
[16:44] <slangasek> seb128: the remaining plymouth crashes are all things we've never been able to reproduce locally
[16:46] <seb128> slangasek, k
[19:07] <roadmr> hello, the ubuntu-sdk package seems to be uninstallable, is this a good place to ask about that or is there a better place?
[19:07] <beuno> roadmr, #sdk is probably better, although I'm not sure there will be anyone around
[19:08] <roadmr> beuno: just #sdk or #ubuntu-sdk? there's only one other person in the latter (xnox)
[19:09] <beuno> roadmr, oh, I think I made that up
[19:09] <beuno> not sure then  :)
[19:09] <xnox> roadmr: what do you mean "ubuntu-sdk" package is not uninstallable?
[19:09] <roadmr> beuno: hehe it happens :)
[19:09] <xnox> roadmr: where did you install it from, and on to which release?
[19:09] <roadmr> xnox: 12.04.3, I added this ppa: https://launchpad.net/~ubuntu-sdk-team/+archive/ppa
[19:10] <roadmr> xnox: ubuntu-sdk wants qtcreator-plugin-ubuntu-cordova which in turn wants qtcreator-plugin-ubuntu (= 2.8.1bzr56precise0) but only 2.8.1bzr57precise0 is available in that ppa
[19:10] <xnox> roadmr: well then, open a bug report against that ppa.
[19:10] <roadmr> xnox: ok, just wanted to ensure I wasn't doing things wrong. I'll file a bug then, thanks!
[19:10] <xnox> roadmr: it's best to use sdk on trusty ;-) and from the archive, not the PPAs =)
[19:11] <roadmr> xnox: I know, but we have an application that uses the sdk and we need it building and running on precise
[19:11] <xnox> roadmr: cool. ok.
[19:11] <roadmr> xnox: saucy and trusty have no problems :) it's that "legacy" need for precise that makes us suffer
[19:53] <hallyn_> Hi - if a package installs an upstart job, and that upstart job may do {stop; exit 0;}, that seems to cause package install to fail.
[19:53] <hallyn_> is there a clean way to make that 'ok'?
[19:53] <hallyn_> dh_installinit --errorhandler?  seems more work than should be needed
[19:55] <Noskcaj> Can someone please test debian's version of opemmpi on ubuntu armhf? It appears all out diff is fixed, but i need someone to test we don't need any arm support patch
[19:56] <xnox> hallyn_: if there is an example, i can look into that. it shouldn't fail.
[20:03] <hallyn_> xnox: the cgroup-lite package in precise-proposed
[20:03] <hallyn_> at least that's what i think is happening.  i may be misunderstanding...
[20:03] <hallyn_> (install that in a precise container, and apt-get install fails)
[20:07] <xnox> install cgroup-lite in the container.... which already is using cgroup-lite?!
[20:08]  * xnox will try a VM instead.
[20:14] <hallyn_> xnox: just a fresh container
[20:14] <hallyn_> shouldn't have cgroup-lite, if you just 'lxc-create -t ubuntu -n p1 -- -r precise'
[20:16] <xnox> ah ok.
[20:18] <hallyn_> (idea being 'start cgroup-lite' will fail because of the apparmor profile)
[22:25] <Noskcaj> when is the next DMB 19UTC meeting? I'm wanting to apply for MOTU and PPA (xubuntu packages), but cannot attend 15UTC and can only reliably attend 19UTC times before the end of January
[22:35] <darkxst> Accountsservice gir1.2 package is broken. it killed gnome-shell ;(
[22:35] <darkxst> ^xnox
[22:49] <darkxst> is anyone around that can sponsor this? Its pretty urgent given gnome-shell is 100% broken in trusty for the moment. Bug 1260880
[22:53] <ricotz> darkxst, fyi, https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1260604
[22:53] <Noskcaj> Is there an ETA for glew 1.9.0 in ubuntu?
[22:55] <tjaalton> darkxst: i can do that
[22:56] <darkxst> tjaalton, may as well take ricotz patch from bug 1260604
[22:58] <tjaalton> darkxst: next time finalize the changelog and add the bug# ;)
[23:01] <tjaalton> ricotz: why does the -dev package need that dep?
[23:04] <ricotz> tjaalton, it is a convention that the -dev packages pulls in the gir1.2- for a proper build environment
[23:05] <ricotz> not related to this breakage, but still needed
[23:05] <tjaalton> well i'm not adding it here
[23:05] <ricotz> still leaving it is wrong
[23:06] <tjaalton> oh it's a forked package, then I don't care
[23:07] <ricotz> how do you mean "forked"
[23:08] <tjaalton> since raring
[23:08] <ricotz> you mean not "synced from debian" then
[23:09] <tjaalton> right, and I'll add a changelog entry credited to you so you can explain it to the next one :)
[23:10] <ricotz> tjaalton, alright
[23:12] <tjaalton> uploaded
[23:13] <darkxst> tjaalton, thanks
[23:13] <tjaalton> np
[23:14] <ricotz> tjaalton, thx
[23:15] <tjaalton> Noskcaj: you probably need to ask the unity folks if 1.10 would be good for them
[23:15] <Noskcaj> tjaalton, ok, will do
[23:16] <tjaalton> since 1.9 broke the builds or such
[23:16] <tjaalton> as mentioned on the changelog
[23:17] <Noskcaj> yeah
[23:17] <Noskcaj> roaksoax, kirkland: Would you mind putting a testdrive update out? Vbox 4.3 is now in proposed. Could we use this as an excuse to put testdrive in debian?
[23:59] <Noskcaj> roaksoax, kirkland: Please add "Upload to debian. Closes: #718365" to the changelog, and release as just 3.25