[03:55] <pitti> Good morning
[04:11] <smartboyhw> Can someone please upload https://launchpad.net/bugs/1228635 and https://launchpad.net/bugs/1228657 (final fixes for Ubuntu Studio before Beta 2)
[06:58] <smartboyhw> dholbach, heyas, you love sponsoring uploads I know, care to deal with Bug 1228657 and Bug 1228635?
[06:58] <dholbach> good morning
[06:58] <dholbach> hi smartboyhw
[06:58] <pitti> hey dholbach
[06:58] <smartboyhw> dholbach, good afternoon!
[06:59] <dholbach> smartboyhw, one thing at a time - I just started work and will need to go through a bunch of mails first - if you subscribed 'ubuntu-sponsors' it should be in the sponsoring queue though
[06:59] <dholbach> hi pitti
[06:59] <smartboyhw> dholbach, sure
[06:59] <smartboyhw> Hmm, I didn't realize that Len didn't subscribe
[07:07] <pitti> hey smb, wie gehts? made it back in one piece?
[07:08] <smb> pitti, Yeah and with less incidents than the other way round. You seemed to have more "fun". Only my sunglasses did not make it with me. Ok, I had to get new ones anyway sooner or later.
[07:09] <pitti> smb: forgot them in the hotel, or did they look too suspicious during security check? :-)
[07:10] <smb> pitti, Nah, just had them stashed externally on my backpack and somewhere they must have escaped
[07:12] <smb> Not that anybody could use then... well except that someone has -10 on both eyes
[07:14] <smb> pitti, Did you get delayed a lot by that "obstacle" on the tracks?
[07:15] <pitti> smb: not that much any more, I was home around 13:00
[07:15] <smb> Ah, not too bad indeed, I just got back one hour earlier
[07:16] <smb> Then made my two crosses and crashed
[08:19] <cff> How can I install GDB 4.6.1 in Ubuntu 13.04 ?
[08:19] <cff> err
[08:19] <cff> GDB 7.6.1
[08:19] <cff> The repos don't have it : https://launchpad.net/~ubuntu-toolchain-r/+archive/test?field.series_filter=raring
[08:22] <infinity> cff: Is there a reason 7.6 isn't good enough for you?
[08:23] <cff> infinity: the package in the repos reports version 7.5.91.20130417-cvs-ubuntu
[08:23] <cff> infinity: although the package seems to be labeled with gdb 7.6
[08:23] <infinity> cff: Sure, it's a pre-release right before 7.6 shipped.
[08:24] <infinity> cff: Again, is there something fundamentally wrong with that, or are we just suffering versionitis?
[08:24] <infinity> cff: Anyhow, as a general rule, we don't update upstream versions in stable releases.  That's what makes them stable releases.
[08:24] <cff> KDevelop reports all my breakpoints as "Your debugger is too old"
[08:24] <infinity> I'd argue that's a bug in kdevelop that someone should fix, then.
[08:25] <infinity> Ubuntu's version, or your own build?
[08:26] <infinity> Anyhow, if the Ubuntu kdevelop fails to work with the Ubuntu gdb, I'd suggest filing a bug at: https://bugs.launchpad.net/ubuntu/+source/kdevelop/+filebug
[08:27] <infinity> If it's an upstream/PPA/who-knows-what build of kdevelop, you're likely on your own, or you might want to sort out how to build a new gdb, or try installing the "real" 7.6 from saucy on raring and see if that's good enough.
[08:27] <infinity> cff: ^
[08:28] <cff> infinity: okay, thanks for the information
[08:35] <JackYu> infinity, hi, would you please  review the binary NEW of fcitx-qimpanel?
[08:36] <JackYu> infinity, done just now:), thanks.
[08:37] <smartboyhw> dholbach, you finished through the mails? :P
[08:43] <diwic> @pilot in
[08:56] <dholbach> smartboyhw, there are lots of other folks who have upload rights
[08:57] <smartboyhw> dholbach, sure, but the Beta 2 block is dropping:( (It is of course OK to be uploaded after the block, but)
[09:00] <dholbach> smartboyhw, understood, but don't block on me
[09:00] <smartboyhw> dholbach, sure
[09:03] <smartboyhw> diwic, since you are on patch pilot duty, look at Bug 1228635 and Bug 1228657 please:) I want that be uploaded so we can respin images.
[09:03] <smartboyhw> (For Beta 2 effectively)
[09:08] <diwic> smartboyhw, thanks, I saw those, but I don't have upload rights unfortunately
[09:08] <diwic> smartboyhw, (except for pulseaudio)
[09:09] <smartboyhw> -.-
[09:09] <smartboyhw> What the....
[09:09] <diwic> smartboyhw, ask dholbach why he thinks I should be a patch pilot anyway, to me it does not really make sense, but...
[09:09] <smartboyhw> LOL
[09:09] <diwic> oops, there goes the beta freeze
[09:10] <sladen> there /arrives/ the beta freeze
[09:10] <diwic> sladen, yeah, that's a better way to put it
[09:17] <Laney> The idea of being a patch pilot is to help things along, not necessarily to upload them
[09:17] <Laney> So you might for example review these uploads and see if they look OK to you, which will make it easier for someone who can to sponsor it
[09:17] <Laney> Or if you know there is a developer with expertise in this area you could ask them to take a look
[09:19] <diwic> Laney, dholbach, well, for me I feel that the actual upload is what most items actually need help with
[09:20] <diwic> reviewing is already done
[09:20] <dholbach> the actual upload is what takes the least amount of work
[09:20] <dholbach> and I for one would completely trust your judgement if said: "I looked at X, Y and Z - can you please upload/sync them?"
[09:21] <diwic> Laney, dholbach how about that a person with upload should always accompany somebody without, would that make sense?
[09:21] <diwic> then I'd at least know who to ask for upload
[09:21] <dholbach> you're a great engineer, you've worked in Ubuntu and with Debian and Upstream for ages now and you know what you're talking about
[09:22] <dholbach> diwic, if you're suggesting one-on-one mentoring then we tried that for quite a while and it didn't scale very well :-/
[09:22] <diwic> dholbach, no, not at all - I'm suggesting that when patch pilot schedule is set up, one should always work in pairs where at least one has upload rights
[09:23] <dholbach> ah ok
[09:23] <dholbach> if you have a look at https://www.google.com/calendar/embed?src=6k1e5rq45m1bdqq0n1ge3oqaok@group.calendar.google.com&gsessionid=OK - there's always 2 or 3 patch pilots at the same day
[09:23] <dholbach> so that might be one option
[09:24] <dholbach> but you could also just try to ask in here for somebody who can sponsor/sync once you reviewed something
[09:24] <smartboyhw> But uptimes can be different .
[09:24] <smartboyhw> Like, one patch pilot comes up on duty at 12:00 UTC - 16:00 UTC and the another comes up 16:30 UTC - 20:30 UTC
[09:24] <diwic> dholbach, it would feel better if there was a designated uploader rather than just "hey can somebody in here upload"
[09:25] <diwic> dholbach, and also I feel like people expect a patch pilot to have upload rights, like smartboyhw just did
[09:25] <dholbach> smartboyhw, I just set up this schedule as a reminder for everyone - they are free to move things around as it works best for them - I wouldn't like to specify times for everybody (sometimes people work from different timezones or need to get some other work out of the way first, etc.)
[09:25]  * smartboyhw does, actually
[09:26] <dholbach> smartboyhw, well, you'd still need somebody to review and test-build your suggested changes
[09:26] <smartboyhw> dholbach, what I expect from a patch pilot is review + test-build + upload (in my point of view)
[09:27] <dholbach> sure, "it's uploaded" is what everybody's after, but that's just the "end product" of a proper review including reading the changes, test-building them, checking if they should better go upstream first, if all the processes are followed, etc.
[09:27] <smartboyhw> dholbach, maybe we make it like us: diwic reviews and you upload?
[09:27] <dholbach> smartboyhw, and that's all documented here: https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews
[09:27] <smartboyhw> :P
[09:27] <smartboyhw> (Since you said that upload takes the least time)
[09:28] <dholbach> smartboyhw, can you please stop that? I understood your nudge the first time you asked me
[09:28] <dholbach> smartboyhw, I have a couple of other things I need to get out of the way first
[09:28] <smartboyhw> dholbach, sure....
[09:36]  * diwic goes for lunch, will continue piloting after lunch
[09:36] <diwic> @pilot out
[09:48] <mpt> mvo, hi! What do you think of the patch that just got attached to bug 617397?
[10:05] <slickymaster> good morning all
[10:10] <mvo> mpt: hello! this patch should be fine
[10:10] <mpt> cool
[10:32] <mvo> mpt: updated to include a additinal piece of information how it could be improved
[10:32] <mpt> Thanks mvo!
[10:43] <dholbach> smartboyhw, uploaded
[10:43] <smartboyhw> dholbach, MANY THANKS!
[10:43]  * smartboyhw hugs dholbach with tears:)
[10:43] <dholbach> anytime
[10:43] <dholbach> haha
[10:43] <dholbach> it's all good
[10:43] <smartboyhw> dholbach, sorry for being rude:P
[10:44] <dholbach> no, it's fine - I could see that you just wanted to make sure those fixes go in, you just didn't seem to believe them when I said "yeah, later" :)
[11:05] <diwic> @pilot in
[11:08] <doko> cjwatson, apw: who should subscribe to this package? lp: #1196958
[11:09] <doko> foundations or kernel?
[11:24] <cjwatson> doko: neither seems to be subscribed to libnetfilter-conntrack; what's the first thing in the rdep chain with a useful subscriber?
[11:26] <doko> cjwatson, ahh, dnsmasq and squid3, so probably server team
[11:26] <doko> jamespage, ^^^
[11:37] <apw> seems like you have things under control
[11:38] <doko> apw, but while you are here ... any news on running the trinity tests?
[11:54] <jamespage> doko, done
[11:56] <doko> jamespage, thanks, promoted
[11:57] <jamespage> doko, thanks
[12:15] <doko> TheMuso, ping on #1196967
[12:55] <OrokuSaki> I have this bug.. and I don't know what to do.. it involves delta max and a touchscreen. swipes get mistaken for double touches on certain boots.. like 1 out of 5.. put the ts_srv.c in debug mode, everything seems fine with it..
[12:56] <OrokuSaki> maybe its udev.. hmmm
[13:42] <diwic> dholbach, so, I've done some work on bug 1155575 and submitted a MP. You don't have to upload anything, I'll prefer to wait for the review for a few days first
[13:42] <diwic> @pilot out
[13:42] <dholbach> diwic, gotcha
[13:44] <diwic> (and the two other bugs I worked on turned out to be already fixed)
[13:59] <OrokuSaki> How can I test my graphics acceleration settings on my gpu? To detect what is working? vainfo?
[13:59] <OrokuSaki> Sorry to bug you guys
[14:32] <pitti> OrokuSaki: glxinfo might be a good start
[14:39] <geser> OrokuSaki: "/usr/lib/nux/unity_support_test -p" might be helpful too
[15:33] <zul> mterry:  wsme should be good now
[15:34] <mterry> zul, wsme?
[15:34] <zul> https://bugs.launchpad.net/ubuntu/+source/python-wsme/+bug/1207030
[15:42] <mterry> zul, why not run the python3 tests too?
[15:42] <zul> mterry:  dang
[15:43] <mterry> zul, does "setup.py test" do anything?  Or do we need to run each test manually?
[15:52] <mterry> zul, does "setup.py test" do anything?  Or do we need to run each test manually?
[15:52] <zul> mterry:  it doesnt do anything it looks like the other ones need turbogears installed
[15:53] <zul> and there doesnt look like there is a python3 package for flask
[15:56] <mterry> zul, turbogears isn't even in the archive anymore....
[15:56] <zul> exactly
[15:59] <mterry> zul, approved, thanks!
[15:59] <zul> mterry:  cool
[17:14] <slickymaster> \quit
[17:35] <didrocks> jasoncwarner: slangasek: barry: just update the request on the spreadsheet for getting download manager on track for landing
[17:36] <slangasek> didrocks: sorry, do you mean that you have just updated it?
[17:36] <didrocks> slangasek: I don't have all context but it was re: 19:29:42    jasoncwarner | didrocks slangasek says the download service should land tomorrow. can you get with him and barry etc to know what we would need to do to update the updater?
[17:37] <slangasek> didrocks: ok, so this is a reminder to us to update the spreadsheet?
[17:37] <barry> didrocks: i'm told the updated d/l service with everything i need should land tomorrow.  if so, i'm hoping to finish my branch by tomorrow too
[17:38] <didrocks> slangasek: right, as an answer to "what's needed"
[17:38] <slangasek> didrocks: ok.  fyi I don't have edit rights on the spreadsheet
[17:39] <didrocks> asac: I'm fixing that ^
[17:39] <asac> didrocks: if you can thats good
[17:39] <didrocks> slangasek: should be good now
[17:39] <asac> thx
[17:39] <lamont> the default ipv6-enabled config is both a good and a bad thing
[17:40] <lamont> slangasek: who is our favorite ipv6 maven these days?
[17:40] <slangasek> lamont: stgraber, who's off today
[17:40] <slangasek> lamont: but there are others about who have some experience :)
[17:41] <lamont> it would seem that the nifty "too many unreachable, advertised NS hosts causes intermittent resolution falures" bug
[17:41] <lamont> seems to show up well if you have BIND running on a host that has no ipv6 connectivity
[17:42] <slangasek> didrocks: ok, added at the bottom of the first sheet.  but, what are these unlabelled columns that are filled out?  is there more information I should be providing?
[17:42] <lamont> slangasek: specifically, see the output of dig ns salesforce.com
[17:42] <didrocks> slangasek: it's if questions arisent
[17:42] <slangasek> didrocks: ok
[17:42] <didrocks> slangasek: you should have added to the second list I think, but that's fine anyway
[17:43] <slangasek> didrocks: I understood the second page to be for quick'n'easy bugfixes... this is not that
[17:44] <slangasek> lamont: erm?  but each of those nameservers has both an A and a AAAA record
[17:45] <didrocks> slangasek: no, all request on second normally
[17:45] <didrocks> then, we move it to the first one
[17:45] <didrocks> I'll ack something to get it cleaner I guess
[17:45] <slangasek> lamont: so this doesn't seem to be something you need an IPv6 expert for, you just need someone to fix a bug in the bind code ;)
[17:45] <lamont> slangasek: yeah - I'm not sure whether it's doing the RTT weighting on IP or host, tbf
[17:45] <slangasek> didrocks: ah, that's not what I took away from that email
[17:45] <lamont> slangasek: yeah
[17:45] <didrocks> slangasek: that's my understanding of it, but maybe I'm really wrong, I didn't design this process ;)
[17:46] <lamont> slangasek: specifically, when there are multiple unreachable hosts, the unreachables tend to clump together and make life suck when they all win together
[17:57] <alberts> Is there anyone who is familiar with unity-greeter? With time to review merge proposals attached to this bug -  https://bugs.launchpad.net/unity-greeter/+bug/1201127
[18:50] <shadeslayer> pitti: ping
[18:51] <shadeslayer> since you last uploaded automake 1.13, it kind of breaks virtuoso-opensource because of a shell script test-driver not being available
[18:52] <shadeslayer> I've worked around the issue by symlinking /usr/share/automake-1.13/test-driver to where autotools try to find the file
[18:52] <shadeslayer> is that an appropriate solution?
[19:29] <barry> #py-dev
[20:20] <mterry> pitti, what creates the /run/user/$UID directories when you log in?
[20:21] <slangasek> mterry: logind
[20:21] <mterry> slangasek, ah thanks.  hm
[20:22] <slangasek> mterry: (triggered via pam_systemd.so in /etc/pam.d/common-session)
[20:31] <cjwatson> shadeslayer: virtuoso-opensource probably isn't using automake -f
[20:32] <cjwatson> shadeslayer: TBH, I've had consistently bad experiences with cdbs' auto-update rules; you might be best served by migrating to dh-autoreconf (which includes cdbs integration)
[20:32] <cjwatson> basically delete DEB_AUTO_UPDATE_* and include wherever it is that autoreconf.mk lives
[20:33] <cjwatson> and build-dep on dh-autoreconf
[21:08] <cjwatson> doko,wookey: Debian's infrastructure is now coping with :any in both Build-Depends and Depends, so it should be fine to merge such things; the caveat for Depends is that wheezy's apt makes the wrong decisions, so if you use :any in runtime Depends the current consensus appears to be that you need to make sure that there's also a version relationship forcing upgrade to the :any-supporting version, to avoid wheezy->jessie ...
[21:08] <cjwatson> ... upgrade hilarity
[23:54] <wookey> cjwatson: excellent