[00:15] <stokachu> doko: http://goo.gl/rnQ4y - im having some trouble getting firefox built on raring/saucy and its related to python, any idea on what the error means?
[00:16] <stokachu> http://pastebin.ubuntu.com/5669324/ thats the bottom of the error log
[00:16] <stokachu> same build works on precise/quantal
[02:23] <mwhudson> sigh
[02:23] <mwhudson> why isn't perf finding my source code..
[02:27]  * mwhudson learns that cc -ggdb is something different from cc -g
[02:29] <geofft> -ggdb3! Featuring awesome things like preprocessor macros at the gdb prompt!
[02:30] <mwhudson> huh
[02:30] <mwhudson> i don't think perf will use that :)
[03:06] <swiss> so is this where I could talk about an issue i'm having with a core ubuntu package?
[03:06] <swiss> or would that be app-devel?
[03:07] <mfisch> swiss: there's also ubuntu-bugs, but what's the issue?
[03:07] <mfisch> Logan_: you around? I was updating distribute and wondered about the d/rules change you made in the last version
[03:07] <swiss> mfisch: gnome-control-center-signin is looking for libraries that don't exist when working with stuff like unity-scope-gdrive
[03:08] <swiss> i get an error, i straced it, and i can show you exactly where it's hunting. I tried purging and reinstalling all the related packages, but it didn't fix anything
[03:09] <swiss> I'm assuming it's gnome-control-center-signon, but it might be the unity-scope packages
[03:10] <swiss> in general I feel like I know what I'm doing when dealing with issues like this, the thing I find interesting is I've done most things to make my system similar to that of a fresh install, yet I still have this issue. And I imagine if others had this issue that the update that broke it (that happened with raring) wouldn't have been released
[03:10] <Logan_> mfisch: hi
[03:10] <mfisch> Your best bet is to file a bug on g-c-c-so and attach those straces
[03:10] <mfisch> swiss: ^^
[03:10] <swiss> g-c-c-so?
[03:10] <swiss> oh
[03:11] <swiss> gnome control etc etc
[03:11] <swiss> well, i'm not sure if it's that, or signon, or accountsservice, or what :/
[03:11] <mfisch> Logan_: why did you disable building for 3.2?
[03:11] <mfisch> swiss: the bug control team can look at it
[03:11] <swiss> i'm debating a reinstall right now
[03:11] <mfisch> swiss: send me the bug number and I will look since i'm on bug control
[03:11] <Logan_> mfisch: it was like that in the past - I was just carrying over the delta
[03:11] <Logan_> the current Python 3 version is 3.3 in Ubuntu, in any case
[03:12] <mfisch> yep
[03:12] <mfisch> the latest debian dropped 2.6 support though
[03:12] <mfisch> we need 2.7 and 3.3 I believe
[03:12] <Logan_> oh, that change log entry has a typo
[03:12] <Logan_> should say 2.6 and 3.2
[03:13] <mfisch> Logan_: that makes a lot more sense!
[03:13] <Logan_> could you fix that in a subsequent upload?
[03:13] <mfisch> okay, so I'll update and keep the 3.2 drop
[03:14] <Logan_> oh freenode
[03:14] <mfisch> Logan_: it looks like the python3-sphynx dep was removed upstream so our delta is pretty small
[03:14] <mfisch> Logan_: what did freenode do?
[03:14] <Logan_> looks like a semi-netsplit
[03:32] <mfisch> Logan_: you still here? I was curious about your other changelog comment
[03:33] <mfisch> Logan_: I cannot find python3-sphinx in the build-deps, but you did remove python3.3-dev
[03:39] <swiss> so, this is actually a online-accounts-with-unity issue. Is there a unity specific channel?
[03:43] <mfisch> probably ubuntu-desktop
[03:44] <swiss> is that a channel?
[03:44] <swiss> checked, yep
[03:44] <mfisch> yep
[05:04] <pitti> Good morning
[06:35] <dholbach> good morning
[08:13] <robert_ancell> stgraber, do you know if someone is planning to maintain LTT-ng (source package ust) in Ubuntu? We're looking at taking a dependency on it for Mir, so I'll do a MIR for it. But if someone else is maintaining it I can leave it for them to do. (redirected from tvoss)
[08:25] <infinity> robert_ancell: You might want to ask the kernel team.  rtg, specifically, seemed to have a keen interest in the kernel side of lttng-tools, the userspace library seems like it would go hand-in-hand.
[08:25] <robert_ancell> infinity, thanks. What would be the best way to ask them>?
[08:26] <infinity> robert_ancell: kernel-team mailing list, perhaps, or the #ubuntu-kernel channel.
[08:26] <robert_ancell> infinity, ta
[09:20] <seb128> @pilot in
[09:22]  * dholbach hugs seb128
[09:22]  * seb128 hugs dholbach back ;-)
[11:25] <seb128> does anyone has an opinion on dropping from vsftpd (https://code.launchpad.net/~diddledan/ubuntu/raring/vsftpd/bug-1160372/+merge/162980)? seems like opensuse did it with this rational
[11:25] <seb128> "Kernel autid system prohibits the processes created with CLONE_NEWPID, so an
[11:25] <seb128> attempt to log into ftp server ends with
[11:25] <seb128> audit_log_acct_message() failed: Operation not permitted"
[11:26] <seb128> vsftp seems to be broken on >= raring atm, but I don't know enough about CLONE_NEWPID to feel like making a call on that
[11:26] <seb128> jdstrand, mdeslaur, sarnold, chrisccoulson: ^ any security team view on that?
[11:45] <mdeslaur> seb128: seems reasonable
[11:58] <seb128> mdeslaur, thanks, will sponsor it then
[11:58] <seb128> mdeslaur, oh and good morning ;-)
[11:58] <mdeslaur> seb128: good morning! :)
[12:19] <sunweaver> dbarth: have you found time to look at the X2Go patches for unity-greeter + remote login?
[12:19] <sunweaver> dbarth: have you found time to look at the X2Go patches for unity-greeter + remote login?
[12:20] <sunweaver> dbarth: have you found time to look at the X2Go patches for unity-greeter + remote login?
[12:50] <hulu> helo
[12:51] <hulu> the 13.04 livecd create default live user without copy /etc/skel
[12:51] <hulu> who can help me
[12:55] <mzaza> If I want to contribute to the brightness and lockscreen in system settings, how should I start?
[13:11] <pitti> seb128: actually, I had a closer look and the xwiimote patch doesn't even seem necessary; I'll just sync current Debian
[13:14] <pitti> oh, someone already merged
[13:15] <pjotr> infinity: you've fixed this bug very quickly (which is great!): https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1177324
[13:15] <pjotr> But it's tagged for Saucy
[13:16] <pjotr> does this mean that it won't become available for Raring?
[13:16] <ogra_> pjotr, follow the SRU guidelines
[13:16] <ogra_> you need to open a saucy task and get the SRU team to take care
[13:16] <ogra_> err
[13:17] <ogra_> a raring task indeed
[13:18] <infinity> Given that Q/R/S all had the same version, I probably should have just SRUed to Q and copied it forward to everything else.
[13:18] <infinity> I could still do that.
[13:19] <pitti> seb128: uploaded a revert
[13:19] <pjotr> infinity: that would be great!
[13:25] <dobey> should i file a bug about restart notification in indicator-session against update-manager or indicator-session?
[13:46] <seb128> pitti, danke
[14:47] <seb128> pitti, stgraber: can you set https://code.launchpad.net/~diddledan/ubuntu/raring/vsftpd/bug-1160372/+merge/162980 to merged?
[14:53] <stgraber> seb128: done
[14:53] <seb128> stgraber, thanks
[15:09] <jodh> /join #ubuntu-uds-foundations-1
[15:09] <jodh>  
[15:09] <jodh>  
[15:14] <zequence> diwic: I was working on the pulseaudio reserve card patch today. But, I don't understand how to apply it to for instance lp:~ubuntu-audio-dev/pulseaudio/ubuntu.quantal
[15:14] <diwic> zequence, where are you now? I e, what have you got?
[15:15] <zequence> I have the patch ready for quantal, and am able to apply and build it against the debian package, but I don't know how to apply it to the bzr branch. Do I just include it in debian/patches?
[15:16] <zequence> hmm, I forgot to add it debian/patches/series
[15:16] <diwic> zequence, I usually do "bzr bd-do" "quilt import <patchname>" "exit"
[15:17] <zequence> ok, I was assuming there was some nifty tool for this :)
[15:18] <diwic> zequence, preferrably "quilt push -a" after "quilt import" to make sure it applies
[15:18] <diwic> zequence, then update debian/changelog (with dch or dch -i)
[15:18] <diwic> zequence, bzr add debian/patches/*
[15:18] <zequence> diwic: Great, thanks. I'll give it a go
[15:19] <diwic> zequence, bzr commit, bzr push
[15:22] <psusi> how do you do that thing where you flag a wiki page as broken/needs help?  It doesn't seem to be mentioned in the help page.
[15:23] <ev> mpt: bdmurray and I were talking at the client sprint about how the graph on the bucket page has wild data and seemingly not useful in its current form. I think this is partly because I've made a mistake and our calculation is:
[15:23] <ev> total instances of the problem across all releases / the number of unique systems seen in a 90 day period for a specific release
[15:23] <ev> I can fix not including the release in the numerator (by collecting more data), but in thinking about it more, I wonder if the ideal calculation would be the weighted instances of just this problem for a specific release divided by the unique systems seen in a 90 day period for the specific release.
[15:23] <ev> It's computationally more complex, but if that's going to give the best results then we can always try for it.
[15:26] <ev> mpt, bdmurray: I also was toying around with the idea of having an instance count view, but I kept pulling myself away from it thinking that it was just papering over the problem with the graph in its current form
[15:27] <ev> something akin to the left hand toggles on this: http://nvd3.org/ghpages/stackedArea.html
[15:28] <ev> well, looking more like a toggle
[15:48] <mpt> ev, if I understand you correctly, the formula for the bucket graph is different from the formula for the front page graph when it should be the same.
[15:48] <ev> mpt: same with a smaller numerator for the bucket graph, yes
[15:49] <mpt> yes, and correspondingly smaller scale
[15:59] <ev> okay, I'll get a bug together for that
[16:13] <kees> hrm, does nothing clean up /var/lib/ubuntu-release-upgrader/release-upgrade-available after an upgrade?
[17:26] <bdmurray> barry: do you think it still useful to get more information about these pyc file corruption bugs?
[18:00] <barry> bdmurray: i think so, yes
[18:01] <bdmurray> barry: so gathering interpreter, release, and import failure line from them?
[18:02] <barry> bdmurray: yes, for all three.  if there's a way to figure out the affected imports and upload the pyc files related to them, that would help too]
[18:03] <bdmurray> barry: Okay, I'll see what I can do
[18:07] <barry> bdmurray: awesome, thanks
[18:47] <mfisch> Laney: question on the DMB wiki pages, are the meetings at 15:00 UTC or 14:00UTC, the pages in the wiki disagree on this
[18:52] <mfisch> seb128: you too on that question to Laney ^^
[18:52] <seb128> mfisch, I don't know, I'm not on that board, I would trust the fridge calendar I guess ... what time is listed there?
[18:54] <mlankhorst> oops, forgot to upload wine to the ppa
[18:54] <mfisch> seb128: 14:00 and 19:00
[18:54] <mlankhorst> seb128: did you ever sign my gpg key after I gave it to you in london a few months back? :P
[18:57]  * seb128 looks on his desk, ops
[18:57] <seb128> mlankhorst, will do tomorrow ;-)
[18:58] <zequence> diwic: So, I think I might have applied the patch in a useful way to quantal, but there's something different about applying to patches to precise.
[18:58] <zequence> diwic: edit-patch is not working either, so I'm assuming it's not supporting this type of patch applying
[19:41] <seb128> stgraber, pitti: can you set https://code.launchpad.net/~pataquets/ubuntu/precise/mumble/mumble-bug-934239/+merge/161105 as merged?
[19:42] <stgraber> seb128: done
[19:43] <seb128> stgraber, thanks
[19:49] <pitti> stgraber is too fast
[19:50] <stgraber> ;)
[20:00] <diwic> zequence, I never use "edit-patch", so don't know what this tool can or can't do.
[20:00] <zequence> diwic: I think it's basically just an automation of some quilt things
[20:00] <zequence> diwic: quilt doesn't work either
[20:02] <diwic> zequence, hmm, that's weird, in what way doesn't it work?
[20:02] <zequence> diwic: I do "bzr bd-do", then "quilt import <mypatch>". The patch is loaded somehow, but I don't see it in debian/patches
[20:03] <zequence> I can even apply it with "quilt push -a", but still nothing in debian/patches
[20:03] <diwic> zequence, are you sure QUILT_PATCHES=debian/patches so it doesn't end up somewhere else?
[20:04] <zequence> diwic: Haven't set that variable up. The patch didn't end up anywhere in the source tree anyway :P. I'll try adding that to .bashrc then
[20:05] <zequence> diwic: Yep. It started working now
[20:06] <diwic> zequence, good
[20:49] <bdmurray> hallyn: your lxc upload in the raring proposed queue in the changelog indicates its patch 0005 but its really 0004.  I'd approve it anyway unless you want to fix it.
[20:55] <hallyn> bdmurray: oh.  drat, i copied the msg from the saucy pkg
[20:55] <hallyn> bdmurray: pls go ahead and kick that, and i'll re-push - thanks!
[20:58] <hallyn> bdmurray: note that we're still waiting for the current lxc in raring-proposed to be promoted to -updates
[20:59] <bdmurray> hallyn: that's only been in the archive for a day so I was just going to approve yours.  if it was at 6 days I'd wait.
[21:01] <hallyn> ok, thanks - i've dput'ed with the fixed changelog
[21:21] <bdmurray> roaksoax: https://bugs.launchpad.net/maas/+bug/1171418 is missing Regression Potential information
[21:26] <roaksoax> bdmurray: thanks. will take care of it in a bit
[21:27] <bdmurray> roaksoax: let me know when to rereview it
[21:37] <roaksoax> bdmurray: done!
[21:37] <roaksoax> bdmurray: thanks!
[22:04] <Guest3570> cd
[22:04] <Guest3570> cd
[22:37] <infinity> @pilot in
[23:20] <Guest87491> If I want to contribute to the brightness & lockscreen were to go, which source code? Unity or Ubuntu core?