[10:29] <smb> lucent, Seems there is a fix for you heading our way through stable. :)
[11:44] <Kano> hi, where is i386 for 36rc8
[12:01] <ogra_ac> Kano, for natty ?
[12:02] <Kano> mainline
[12:03] <ogra_ac> ah, no idea ... for natty it might have ended up in universe ... happens sometimes with a new release 
[12:05] <Kano> only amd64 available
[12:06] <ogra_ac> yeah, probably a packaging issue ... might be though that most of the kernel team is on vacation this week
[12:06] <ogra_ac> pre-UDS week is a typical time for that
[12:27] <apw> Kano, it didn't build, upstream bug
[12:27] <Kano> ah
[12:27] <apw> the build log clearly shows the error, there is a subsequent upstream commit
[12:29] <apw> lag, http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
[12:30] <Kano> so rc9/final will build again
[12:31] <apw> lag, https://wiki.ubuntu.com/Kernel/MainlineBuilds is where they are documented
[12:31] <apw> Kano, yes, likely the daily after it built
[12:31] <apw> someone didn't do their build tests before submitting their patches there
[12:36] <apw> lag, https://edge.launchpad.net/~kernel-ppa/+archive/pre-proposed
[14:45] <jcastro> pgraner: you need to start accepting/declining sessions here or they won't get scheduled: https://blueprints.edge.launchpad.net/sprints/uds-n/+settopics
[14:49] <diwic> jcastro, what's the deadline for me who wants to have a session but has no privileges to authorize them?
[14:50] <jcastro> diwic: we keep scheduling all through UDS depending on room, speaking to the track lead sooner will help
[14:52] <diwic> jcastro, so can I affect the scheduling algorithm by saying I want to attend some sessions (and the scheduler will try to make them non-overlapping), and if so, how?
[14:52] <jcastro> you affect it if you mark yourself as essential when you subscribe to a blueprint
[14:53] <jcastro> if you just subscribe yourself it will do it's best to not overlap, but "essential" is what guarantees it not to happen
[14:53] <jcastro> https://blueprints.edge.launchpad.net/ubuntu/+spec/appdevs-desktop-n-opportunistic-apps-stable-release
[14:53] <jcastro> it's the subscribe thing on the right.
[14:53] <jcastro> red people are essential
[14:54] <diwic> so for how long can this rescheduling appear?
[14:54] <jcastro> what do you mean?
[14:54] <diwic> I mean, if I subscribe to two currently overlapping sessions, will one move?
[14:54] <jcastro> I believe so
[14:55] <jcastro> it's supposed to prevent them from being scheduled in the first place like that
[14:55] <apw> jcastro, when is primary scheduling going to occur (or has it already)
[14:55] <diwic> right, but the scheduling has already begun, and I can still subscribe to blueprints, right?
[14:56] <apw> jcastro, i think pete is on-site today so unlikely to respond
[14:57] <diwic> jcastro, just to take it to the extremes, can I on next monday realize that I want to attend two sessions going in parallel, mark myself, and it will reschedule, confusing all other people currently walking towards that room?
[14:57] <jcastro> apw: it's supposed to have been occuring over the past few weeks, do any of you have power to approve blueprints? Most tracks have one or two assistants
[14:58] <jcastro> diwic: no, that doesn't happen
[14:58] <jcastro> diwic: I recommend subscribing to the ones you want
[14:58] <apw> jcastro, how does one find out who has, i am pretty sure i do not
[14:58] <jcastro> then using your personal schedule to make sure they don't collide
[14:58] <jcastro> apw: it would probably be the people who did it last time
[14:58] <jcastro> apw: let me look
[14:58] <apw> that likely means pgraner and ogasawara 
[14:59] <jcastro> apw: yep, you are correct
[14:59] <apw> who are both on-site today
[14:59] <diwic> jcastro, thanks for the answers, I'm just trying to figure out how the system works :-)
[15:00] <apw> i probabally need to get self added to that list, will have to hastle pete when he is back
[15:00] <jcastro> diwic: duct tape and parachute cord.
[15:00] <apw> jcastro, coo advanced
[15:00] <jcastro> apw: he can't add, only people on the techboard unfortunately. If you ping pitti or colin ask them to put you in ~uds-organizers
[15:00] <jcastro> apw: if you have an idea of what pete wants I suggest you ask them and tell them you talked to me
[15:01] <apw> (i was assuming they would need his authorisation)
[15:01] <jcastro> well, if leann is around later today she can just clean up the queue
[15:02] <apw> yeah no idea of their availability later ... i'll see what i can do
[15:02] <smb> She is onsite as well
[15:02] <apw> yep
[15:03] <jcastro> apw: I can approve obvious ones if you'd like
[15:03] <jcastro> like the typical review sessions you always have, etc.
[15:03] <apw> those i think are already done are they not?
[15:03] <jcastro> let me check
[15:04] <JFo> bug handling needs to be scheduled if it isn't already
[15:04] <jcastro> JFo: done!
[15:04] <apw> jcastro, is https://blueprints.edge.launchpad.net/ubuntu/+spec/hardware-kernel-n-config-review approved enough ?
[15:05] <lag> apw: Pseudo-terminal will not be allocated because stdin is not a terminal.
[15:05] <JFo> thanks jcastro :)
[15:05] <jcastro> apw: yep, ok I think I see the problem, the linaro hardware ones are piling up
[15:06]  * apw looks vague
[15:06] <jcastro> apw: ok I will send them both a mail reminding them. When you see pete mention to him that it's probably a good idea to get one other person in the uds team
[15:06] <apw> jcastro, oh is he in charge of hardware-*
[15:06] <apw> jcastro, will do
[15:07] <jcastro> apw: yeah, it's more of 2 UDSes
[15:09] <apw> jcastro, could you shove over https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review and https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance, we are going to defiantly need both of those
[15:10] <jcastro> ok
[15:10] <apw> jcastro, i know that doesn't help you with your issues
[15:11] <jcastro> getting them in there does. :)
[15:31] <apw> jcastro, who is handling blueprints which have no track prefix ?
[15:52] <slow-motion> http://paste.ubuntuusers.de/399129/ that is the dmesg and wscan output from my terratec cinergy t2. before maverick it was working. why does it stopped working?
[16:15] <jcastro> apw: they have to have track prefixes or they don't get scheduled at all
[16:26] <apw> jcastro, and is anyone sweeping for them >?
[16:26] <apw> i see a qemu- prefix
[16:27] <jcastro> I have the power to rename some of them
[16:27] <jcastro> but mostly it's up to the person who filed it to fix it
[16:28] <apw> i wonder if we should have a report or script which spams people if they are using a stoopid prefix
[16:28] <jcastro> well, theoretically if you file a blueprint most people check after a while to see if it got scheduled
[17:00] <cking> jcastro, how does one see if a blueprint is scheduled?
[17:02] <jcastro> cking: check the schedule with the track view: http://summit.ubuntu.com/uds-n/track/hardware/
[17:06] <cking> jcastro, hrm, so any idea why my bp is not there?
[17:07] <jcastro> cking: link?
[17:07] <cking> https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements
[17:07] <cking> back in a mo - kids...
[17:08] <jcastro> cking: ah, it hasn't been approved yet that's why
[17:08] <jcastro> cking: apw, ogasawara, or pgraner needs to accept it
[17:27] <apw> cking, jcastro done
[17:27] <jcastro> ta
[17:28] <jcastro> apw: that's basically it, ensure the sessions are accepted and they'll autoschedule
[17:30] <cking> apw, ta
[17:31] <jcastro> apw: the cron job runs hourly to autoschedule btw, so accepting them won't show up right away. During UDS it will run much quicker.
[17:36] <apw> jcastro, no worries ta
[17:40] <cking> thanks jcastro
[17:46] <cking> sconklin, http://www.youtube.com/watch?v=4YZeX8ti7Io&feature=player_embedded
[17:48] <sconklin> cking: fun!
[17:49] <cking> sconklin, makerbot + lego = fun :-)
[17:50] <sconklin> there's a new model of the makerbot out with a conveyor which dumps completed objects from the build platform, so you can make multiple copies
[17:56] <cking> nice
[18:35] <apw> jcastro, ok there was some confusion on linaro as to what to do, so they have some cleanup todo ... when thats done i should be able to approve the right ones in short order
[18:36] <jcastro> rock and roll
[21:24] <lucent> smb: Yeah, glad to hear it's on the radar. Discussion with Stefan Richter proved out and I found the commit which broke my firewire setup. 
[21:26] <smb> lucent, Yep, saw his mail today and also a pull request for Linus for .36
[21:26] <lucent> it's kind of ... I don't get star struck but hey having my first and last name on something being submitted to Linus Torvalds, kind of makes me feeling shy in a hurry
[21:26] <smb> Its the kind of thing that makes the whole thing running. :)
[21:27] <lucent> yes, I see :)
[21:27] <lucent> there's one more regression I want to address soon, in the mct_u232 usb serial module
[21:27] <lucent> do you know who I would begin discussion with about that?
[21:29] <smb> Hm, usb serial may be big GregKH... You could either check in git who normally is the last one signing of that driver or in the MAINTAINERS file (to find mailing lists)
[21:33] <lucent> got it, thanks
[21:36] <smb> So yes, seems to be him and/or linux-usb@vger.lernel.org. And a good backing is when you can say you tried one of the mainline (very recent) kernels and its still broken. Did I tell you where to find the mainline kernel. Forgot whom I already told
[21:36] <smb> lucent, ^
[21:37] <lucent> thank you, and yes I have been testing with mainline to do rough bissection
[21:37] <smb> ok, cool :)
[21:38] <lucent> my last question about the kernels is when I build a custom kernel, how do I change the version so that it is unique when I install the resultant deb packaging?
[21:38] <lucent> there were "new" and "old school" methods described on the Ubuntu wiki
[21:38] <lucent> the "new" method does not say how to set my own versioning
[21:38] <lucent> say, "DEB_BUILD_OPTIONS=parallel=2 AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic"
[21:40] <smb> What I usually do is modifying the first line in debian.master/changelog to have an extension like "+debug1" or so
[21:41] <lucent> okay, by modifying the file, and not an environment variable?
[21:42] <smb> right