[00:12] <ebroder> Spamaps: ...weird. It definitely killed it for me
[00:32] <ebroder> NCommander: Did you manage to summon uploading capabilities? I was hoping to harrass the patch pilot into sponsoring bug #601732 :)
[00:34] <NCommander> ebroder: I'm not a core dev.
[00:34] <NCommander> ebroder: MOTU and some Kubuntu
[00:35] <ebroder> NCommander: Oh, didn't realize. No worries then
[00:35] <Riddell> NCommander: if something needs uploading I'm sure there are people who would help the friendly patch pilot to do that
[00:36] <NCommander> Riddell: if I review the patch, would you be willing to upload?
[00:36] <Riddell> NCommander: yes
[00:45] <NCommander> ebroder: this looks sane (and important) and my netbook is running maverick, so I'll test and review there
[00:46] <NCommander> Don't have a lucid system thats currently functional so I can't easily test there
[00:46] <abuDawud> New dev here, I found a bug and patched it but the original package reported differs from where I found the actual issue and patched it
[00:46] <abuDawud> does someone have a minute to go over this with me?
[00:47] <abuDawud> and when I say patched it, I mean I just found the code and corrected the issue. I haven't actually created a patch, cause well... derp
[00:47] <NCommander> abuDawud: sounds like the bug was reported against a previous release (or pre-release version) and you fixed it in a later one
[00:48] <abuDawud> NCommander, the package it was reported against was Apport, but I found the issue in apport-symptoms.
[00:48] <bdrung> kirkland: how to progress with bug #427612? should i wait for a review by upstream or should i add the patch to the ubuntu package?
[00:48] <NCommander> abuDawud: sounds like pitti (apport's upstream) split the package in maverick or natty.
[00:48] <bdrung> kirkland: will it reviewed by upstream or is there something to do for me?
[00:48] <Ian_Corne> 7-
[00:49] <NCommander> abuDawud: so what you need to do is when you make a patch is properly file it against both the old and new packages (there's a button in LP to do this)
[00:49] <NCommander> abuDawud: alternatively, the original subbitter could have filed it against the wrong package (fairly common if it came from a non-dev)
[00:49] <abuDawud> NCommander, can you go over this with me if you have a minute or is there a wiki article on this?
[00:50] <abuDawud> there is no package in launchpad for apport-symptoms.
[00:50] <NCommander> abuDawud: sure, I'm patch pilot for today, so I can look at it. I don't know if there is a wiki page for this
[00:50] <ebroder> NCommander: Feel free to push my stuff to a lower priority
[00:50] <NCommander> abuDawud: Launchpad only sees source packages for bug reportting purposes
[00:50] <abuDawud> I'll try and create a diff or a patch and put it up for you to look at and maybe go over what needs to happen with me
[00:50] <NCommander> ebroder: your next on deck after I finish with MAME
[00:51] <NCommander> I'm waiting for pbuilder to finish building, I haven't used this netbook for dev work before and ports.u.c. is very slow tonight
[00:52] <NCommander> abuDawud: it looks like the bug is against the wrong package in this case, if you can link me, I can look to be sure
[00:53] <abuDawud> NCommander, give me a minute, gonna eat with the family then I'll get a patch up
[00:53] <abuDawud> thanks for your help thusfar
[00:54] <NCommander> abuDawud: I meant the launchpad bug you were workng against ;-)
[00:54] <NCommander> but dinner++
[00:57] <NCommander> pbuilder on armel [00:57] <NCommander> ugh
[00:58] <micahg> NCommander: you're working on mame?
[00:58] <ari-tczew> regards to main sponsors - you have a lot of work to sponsor
[00:58] <NCommander> micahg: yeah, commentted on the bug.
[00:58] <micahg> NCommander: I thought the patch pilots were supposed to be focusing on the core packageset
[00:59] <NCommander> micahg: wiki says anything I can choose. I can actually touch universe/multiverse packages (and some kubuntu).
[01:00] <NCommander> micahg: so those get priority for me unless something looks urgent. At most, on a core packageset I can say a patch is sane but can't upload it
[01:00] <micahg> NCommander: well, the main backlog is the stuff that MOTU can't upload
[01:00] <abuDawud> NCommander, heres the bug https://bugs.launchpad.net/ubuntu/+source/apport/+bug/678371
[01:01] <NCommander> micahg: argh
[01:01] <micahg> NCommander: not your issue I guess
[01:01]  * NCommander had a kernel oops break a filesystem
[01:01] <NCommander> ARGH
[01:01] <NCommander> [ 4247.950000] EXT4-fs error (device sda1) in ext4_dirty_inode: Journal has aborted
[01:01] <NCommander> I can't win today
[01:04] <micahg> NCommander: BTW, I had a build issue with mame in pbuilder for natty, it was trying to use an arch specific gcc
[01:04] <NCommander> micahg: I'm on an armel netbook ATM, if it FTBFS's, I'll throw it in a PPA and try there.
[01:07] <NCommander> ah
[01:07] <NCommander> Architecture: i386 amd64
[01:07] <NCommander> blast
[01:07] <NCommander> Oh well, will check it later
[01:14] <abuDawud> So the issue I am working on a package that does not have a /debian/patches folder so edit-patch is kicking me out.
[01:14] <abuDawud> I ended up just making a diff file but I'm unsure what to do now
[01:15] <NCommander> Adri2000: apport-symptons is maintained in bzr, you should pull the branch down and apply it to the source directly since apport-symptons is a native package and only exists in Ubuntu
[01:16] <abuDawud> wrong person, but I got it. I pulled the bazaar package and the apt-get source down so after I have the patch I should just apply it and request a merge?
[01:16] <NCommander> ebroder: I managed to confirm the bug
[01:16] <NCommander> eek
[01:17] <NCommander> abuDawud: sorry about that, I multitask-failed :-). If a package is maintained in bzr, you shouldn't use apt-get source, you should grab the source branch (apt-get source will tell you what it is), apply it there, upload it, then request merge, and I'll review it and make comments
[01:17] <abuDawud> stupid question, how do I request a merge?
[01:18] <NCommander> abuDawud: upload the branch to LP under your own namespace, then click it, and then click request merge, and then put the branch its going against. Also make sure when you make the commit on your own branchdo bzr ci --fixes lp:bugno
[01:19] <NCommander> that will tell LP that branch is for the bugm and magically connect it to the bug
[01:19] <abuDawud> awesome, I'll give it a go
[01:19] <abuDawud> thanks
[01:19] <NCommander> abuDawud: NP
[01:19] <micahg> debcommit does bzr ci --fixes magic with the changelog entry as the commit message
[01:20] <NCommander> ^- abuDawud
[01:20]  * NCommander may be a luddite with some of the tools we use due to  old habits
[01:20] <abuDawud> so the recommendation is package it myself then upload it?
[01:21] <abuDawud> I'm not familiar with debcommit, but I'm about to read the man page so expert incoming
[01:21] <NCommander> abuDawud: grab the branch, download it, edit it, push it, request a merge, and then poke the sponsors queue or patchpilot
[01:21] <NCommander> abuDawud: debcommit is fairly straightforward
[01:22] <NCommander> Riddell: you still around?
[01:22] <Riddell> NCommander: yo
[01:22] <NCommander> abuDawud: there's a good guide somewhere on the wiki on the specifics of VCS packaging
[01:22] <micahg> abuDawud: here the beginning of the docs on Ubuntu bzr dev stuff (UDD) https://wiki.ubuntu.com/DistributedDevelopment/Documentation
[01:23] <NCommander> ah
[01:23] <NCommander> :-)
[01:23]  * NCommander is saved from using the wiki's search 
[01:23] <abuDawud> micahg, thanks. I'll give it a go
[01:23] <NCommander> Riddell: I think I have a patch I'm ready for you to look at, ebroder's patch for maverick looks sane
[01:24] <NCommander> ebroder: silly questionm, why did all the po files get regenerated?
[01:25] <ebroder> NCommander: Hmm. Good question
[01:25] <NCommander> ebroder: the po's looks like they got regenerated inproperly
[01:26] <NCommander> ebroder: can you respin your branch without them there, since I'm seeing blank Language fields which seems to be wrong.
[01:26] <NCommander> Riddell: disregard, currently not recommending merger
[01:26]  * NCommander comments on the bug
[01:26] <ebroder> NCommander: I don't see those changes in my branch. I wonder if it's just something that happens when you debuild -S
[01:26] <abuDawud> Anyone, since the version number is already at 0.9 what should I move it up to?
[01:27] <NCommander> ebroder: hrm
[01:27] <NCommander> ebroder: modified: debian/po/cs.po
[01:27] <micahg> abuDawud: is this for Natty?
[01:27] <NCommander> abuDawud: 0.10
[01:27] <NCommander> (if its for natty, if its a backport/SRU, it changes)
[01:28] <NCommander> ebroder: er, indeed. modified: debian/po/cs.po
[01:28] <abuDawud> I was doing just the Natty side right now
[01:28] <abuDawud> working off the current bazaar branch
[01:28] <NCommander> ebroder: *coughs*
[01:28] <NCommander> disregard the noise
[01:28] <ebroder> NCommander: Looking
[01:28] <micahg> abuDawud: dch -i usually does the right thing for new version
[01:28] <abuDawud> it put in 0ubuntu1 at that end
[01:29] <micahg> abuDawud: ah, hmm...
[01:29] <abuDawud> and marked it as Maverick
[01:29] <abuDawud> argh
[01:29] <NCommander> Riddell: https://bugs.launchpad.net/ubuntu/+source/cernlib/+bug/601732 - can you look at the mvercik branch and merge/upload please if it also looks sane to you?
[01:29] <micahg> abuDawud: you can set the series with -D
[01:29] <NCommander> abuDawud: just change it by hand, although its recommended if your doing Ubuntu dev work, you be on the latest version.
[01:30] <NCommander> or what micahg said
[01:30] <NCommander> :-)
[01:30] <abuDawud> coolbeans, I'll set to 0.10 and natty
[01:30] <abuDawud> thanks gents
[01:31] <NCommander> ebroder: Thank you for your contribution to Ubuntu.
[01:31] <ebroder> NCommander: Haha, thank you for piloting :)
[01:32]  * micahg will file a bug about Ubuntu native package versioning being incorrect
[01:34] <micahg> bug 680334 in case anyone wants to subscribe
[01:35] <abuDawud> I have a nasty feeling I am going to screw this up. I don't have a ppa set up or anything and I think this is ready to go up
[01:35] <NCommander> abuDawud: from every failure comes a lesson learned
[01:35] <abuDawud> can either micahg or NCommander walk me through how to do this without destroying everything?
[01:35] <NCommander> (or something like that)
[01:36] <NCommander> abuDawud: 1. Don't Panic
[01:36] <NCommander> abuDawud: pbuilder is your friend (or pbuilder-dist)
[01:36] <NCommander> which you can use to test build packages
[01:37] <abuDawud> NCommander, in the process of moving pbuilder to natty
[01:38] <NCommander> Riddell: ping?
[01:39] <Riddell> NCommander: hi
[01:39] <Riddell> I'm looking at it
[01:40] <NCommander> Riddell: thanks, just wanted to make sure the earlier ping didn't drop into the void
[01:40] <Riddell> NCommander: uploading
[01:40] <NCommander> ebroder: ^
[01:46] <ebroder> Riddell: Thanks :)
[01:46] <NCommander> Riddell: also: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/642071 - no-changes rebuild required. If you have amd64, can you quickly check and confirm for me?
[01:47] <NCommander> ebroder: or do you have an amd64 install?
[01:47] <ebroder> NCommander: Yeah, I can test
[01:48] <NCommander> ebroder: thanks, if you can test, Riddell can sponsor :-)
[01:48] <abuDawud> NCommander, I think I broke it
[01:48] <NCommander> abuDawud: well, what's your patch? (stuff it in a pastebin or on paste.ubuntu.com)
[01:49] <abuDawud> NCommander, I tried to upload it to a personal branch and.... it gave some upsetting info
[01:49] <abuDawud> see: http://pastebin.com/XMZkUKbc
[01:50] <abuDawud> ah I see, bzr status shows uncommitted changes, hrm
[01:51] <NCommander> abuDawud: got your SSH keys in LP properly and told bzr of your launchpad-login?
[01:51] <abuDawud> yep
[01:53] <mwhudson> is there a good place to ask about python-apt?
[01:53] <NCommander> did you do bzr unbind to make the branch local and stop trying to commit to the trunk?
[01:54] <ebroder> NCommander: I can reproduce the kexec bug. Doing a rebuild now
[01:54] <NCommander> mwhudson: just ask
[01:54] <NCommander> ebroder: on natty or maverick?
[01:54] <ebroder> NCommander: maverick
[01:54] <ebroder> Do you want a natty repro?
[01:54] <mwhudson> is there a way to get the version of a apt.debfile.DebPackage ?
[01:54] <ebroder> (I've got one of those lying around, too)
[01:54] <NCommander> ebroder: that would be nice
[01:54] <NCommander> mwhudson: no idea :-/, you might want to poke mvo, or ask in one of the Debian channels
[01:55] <NCommander> mwhudson: (or someone else here might nice, pitti possibly)
[01:55] <NCommander> might KNOW
[01:55] <NCommander> ARGH
[01:55] <mwhudson> :-)
[01:55] <mwhudson> ok thanks
[01:55] <abuDawud> NCommander, I was able to commit my changes and tried pushing to the same location and it said it pushed up to Revision 10
[01:56] <abuDawud> buha! Worked.
[01:56]  * ebroder thinks this quid pro quo thing could be a real win
[01:56] <abuDawud> https://code.launchpad.net/~abudawud0/apport/apport-symptoms
[01:58] <NCommander> ebroder: ?
[01:58] <ebroder> NCommander: I just think you're doing a good job of getting other people involved
[01:59] <NCommander> ebroder: that's the idea of the patch pilot
[02:00] <Riddell> NCommander: I need to sleep, anything you need me for?
[02:02] <ajmitch> mwhudson: I can see an ugly way to do it, but it doesn't seem like a nice solution at all (looking at _sections)
[02:02] <NCommander> Riddell: looks like a double no-changes rebuild? Up for the task, or do I need another victi^H core dev?
[02:02] <Riddell> NCommander: can do if it needs doing now
[02:03] <mwhudson> ajmitch: is python-apt the sort of wrapper where things get added as needed?
[02:04] <ebroder> NCommander: no-change rebuild is good on maverik
[02:04] <ajmitch> it's the sort of wrapper that seems to have multiple confusing layers
[02:04] <ebroder> *maverick
[02:04] <ebroder> Same for natty
[02:04] <NCommander> Riddell: just got confirmation
[02:04] <NCommander> Riddell: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/642071
[02:04] <ajmitch> mwhudson: I've only used it a bit, I just found _sections['Version'] by a bit of trial & error
[02:05] <mwhudson> ajmitch: that works for now, i guess, and i'll bug mvo tomorrow
[02:05] <mwhudson> ajmitch: thanks :-)
[02:07]  * ajmitch was hoping for something that would return a Version object (iirc)
[02:08] <lifeless> mwhudson: what are you looking for ?
[02:08] <NCommander> Riddell: thanks for the sponsorships
[02:08] <Riddell> NCommander, ebroder: so upload kexec-tools to maverick-proposed and natty?
[02:08] <lifeless> mwhudson: 'debian' might be a better module to work with.
[02:09] <NCommander> Riddell: bingo
[02:09] <ebroder> Riddell: Yes
[02:09] <abuDawud> NCommander, I am proposing the merge, who should I set as the 'reviewer'?
[02:09] <mwhudson> lifeless: i'm writing something that creates debian packages on the fly (a bit like pbuilder does for build deps); am trying to test it
[02:09] <NCommander> abuDawud: ubuntu-reviewers or ubuntu-sponsors I *think*
[02:09] <ebroder> abuDawud: If you're merging to lp:ubuntu/whatever, you can leave the reviewer blank
[02:10] <abuDawud> k
[02:10] <ebroder> (It'll get automatically set to...something reasonable; no clue what, though)
[02:11] <mwhudson> i went for python-apt because we're using that already in the project, but that's not actually a good reason to use it for this, i guess
[02:12] <mwhudson> lifeless: is 'debian' documented somewhere? "python-debian documentation" is fairly google proof :-)
[02:12] <abuDawud> Ergh... It won't let me propose a merge to apport-symptoms, should it be merged to apport?
[02:13] <lifeless> mwhudson: pydoc ?
[02:13] <mwhudson> yeah, that actually works ok
[02:13] <NCommander> abuDawud: I'm not sure
[02:13] <ebroder> abuDawud: I think you want to merge to lp:~ubuntu-dev/apport/apport-symptoms
[02:14] <abuDawud> let me give that a try
[02:14] <NCommander> ebroder: I think that's sane
[02:14] <NCommander> wow
[02:14] <ebroder> NCommander: It's the Vcs-Bzr field for the package
[02:14] <NCommander> it just started snowing heavily outside :-/
[02:14] <NCommander> ebroder: do you have a lucid box by any chance? :-)
[02:14] <ebroder> NCommander: Wow, really? Where are you based?
[02:15] <ebroder> NCommander: I have Lucid chroots
[02:15] <NCommander> ebroder: about 20 miles north of Portland, OR
[02:15] <NCommander> ebroder: https://bugs.launchpad.net/ubuntu/+source/cernlib/+bug/601732 - can you test and confirm on lucid? I already poked maverick
[02:15] <abuDawud> neat :) I think I am to the actual pilot part, https://code.launchpad.net/~abudawud0/apport/apport-symptoms/+merge/41542
[02:16]  * NCommander looks
[02:16] <NCommander> abuDawud: your diff looks ... insane
[02:17] <ebroder> NCommander: I tested it on Lucid before I submitted the MP
[02:17] <NCommander> ebroder: MP?
[02:17] <NCommander> abuDawud: your branch is badly broken, and has conflicts
[02:17] <ebroder> merge proposal. I'm trying to get the abbreviation to catch on, but it doesn't seem to be working yet :)
[02:18] <abuDawud> abuDawud, I honestly have no idea what I am doing, all I know is I believe I patched the issue
[02:18] <ajmitch> ebroder: doesn't everyone call them MPs anyway? :)
[02:18] <abuDawud> I have a pdebuild of it, is that what should have been uploaded?
[02:20] <abuDawud> wow what the hell happened to my diff lol
[02:20] <NCommander> abuDawud: no, you need a clean branch. The diff is very very messy. I don't know what you did ...
[02:20] <ajmitch> NCommander: no common branch ancestor
[02:21] <NCommander> ajmitch: ah, can you help abuDawud fix it?
[02:21]  * NCommander marked it resubmit on LP for the merge proposal
[02:21] <ajmitch> due to lp:ubuntu/apport-symptoms being a different branch from lp:~ubuntu-dev/apport/apport-symptoms
[02:22] <abuDawud> ajmitch, any guidance on how to correct it, is it just because I messed up the upload to my personal branch?
[02:22] <NCommander> ah
[02:22] <NCommander> I see what happened
[02:23] <NCommander> abuDawud: you pulled the wrong branch, you pulled the LP packaging branch and not the dev branch (I realize this is confusing, but basically, for every package, LP makes a bzr branch for each upload to the archive)
[02:23] <NCommander> abuDawud: what you need is to grab the actual development branch and put your changes against it, then push to LP, and submit a new merge propsal
[02:23] <NCommander> ajmitch: thanks :-)
[02:24] <ajmitch> NCommander: sorry I can't help more right now, having to do some javascript hackery :)
[02:24] <abuDawud> NCommander, I'll give it a run, thanks guys
[02:24] <NCommander> ajmitch: eek :-P
[02:25] <ajmitch> NCommander: jquery helps, but it's never fun :)
[02:30]  * NCommander is properly caffinated now 
[02:38] <abuDawud> NCommander, okay, now its not a bajillion pages long
[02:38] <abuDawud> https://code.launchpad.net/~abudawud0/apport/apport-symptoms/+merge/41543
[02:38] <abuDawud> shit and I already see an error
[02:39] <ajmitch> 'head the test tones'?
[02:39] <abuDawud> heh, before that
[02:39] <abuDawud> press close this window
[02:40] <abuDawud> *sigh*
[02:40] <ajmitch> yeah, that was also a bit confusing
[02:41] <ajmitch> at least pushing a new commit isn't too hard, I think the diff updates
[02:41] <abuDawud> well, at least I am getting some practice lol
[02:42] <abuDawud> well its pushed, I don't see it updating though, maybe it takes a sec
[02:43] <NCommander> back
[02:43] <NCommander> laptop decided it wanted to lock up
[02:43]  * NCommander <3s irssi+screen+ssh
[02:44] <ajmitch> abuDawud: it takes a minute or so, also there's a link on https://code.launchpad.net/~abudawud0/apport/apport-symptoms/+merge/41543 saying that it has been superseded by a later proposal - following that will take you to the new commit
[02:45] <abuDawud> ajmitch, yea I resubmitted over it
[02:45] <abuDawud> its up
[02:45] <abuDawud> https://code.launchpad.net/~abudawud0/apport/apport-symptoms/+merge/41544
[02:45] <mwhudson> the diff on merge proposals will be updated on a push of a new revision btw
[02:45] <mwhudson> but it can take a couple of minutes
[02:46] <NCommander> abuDawud: patch looks sane, but I'm not sure this is the correct approach. I'll mark that I looked at it, and the code changes look sane
[02:46] <NCommander> abuDawud: but I'll leave it for pitti to decide if this is the correct approach or not
[02:47] <abuDawud> NCommander, there is another way to do it but honestly I don't know how to create a new UI window, and don't know if its good to create the one UI window just for that specific window
[02:47] <NCommander> abuDawud: as I said, I'll leave for pitti to decide, he's basically apport's upstream
[02:48] <abuDawud> NCommander, k, thanks for all the help anyway. Back to my bug reporting land where I feel at least a bit comfortable
[02:49] <NCommander> abuDawud: marked Approved by me, but pitti will be the final judge
[02:49] <NCommander> Thank you for your contribution to Ubuntu
[03:24] <NCommander> any core devs abount?
[03:24]  * NCommander pokes asac 
[03:25] <micahg> NCommander: if he's home, he's in UTC+1
[03:25] <NCommander> micahg: I know, but I was gambling on him not having a life and being around
[03:26]  * micahg thinks people w/out a life are definitely sleeping at 4AM
[03:26] <ajmitch> heh
[03:26] <NCommander> ajmitch: your not a core dev, are you?
[03:26]  * NCommander has lost track on who is who
[03:26] <ajmitch> NCommander: I am, what do you need?
[03:27] <NCommander> ajmitch: review and sponsor please: https://bugs.launchpad.net/ubuntu/+source/cheetah/+bug/663343
[03:29] <ajmitch> slightly confusing with the branch statuses & the comments
[03:29] <ajmitch> 217k line diff is pretty special :)
[03:31] <micahg> 217k lines deleted in 7 files?
[03:31] <ebroder> That's the best kind of diff!
[03:31] <ajmitch> yeah, one file was test.strace
[03:31] <ajmitch> so you can imagine how big that was
[03:32] <micahg> that was uploaded by someone?
[03:32] <NCommander> >.<;
[03:32] <ajmitch> not sure, I'm still trying to untangle the branches & what's been uploaded
[03:32] <micahg> that shouldn't be in the merge proposal :-/
[03:32] <NCommander> micahg: there are times where that is valid (massive diffs), but very rare
[03:33] <ajmitch> this bug is a bit confusing with a couple of separate branches & differing statuses
[03:34]  * micahg won't complain so much since it was uploaded over a year ago
[03:34] <ajmitch> a year?
[03:34] <micahg> ajmitch: http://bazaar.launchpad.net/~clint-fewbar/ubuntu/natty/cheetah/natty-merge-with-debian/revision/11
[03:35] <ajmitch> I hadn't checked, I'd assumed that that file was added in the most recent upload this week
[03:35] <ajmitch> what a waste of space :)
[03:35] <micahg> ajmitch: so did I which should warrant a new merge proposal
[03:35] <micahg> *should have
[03:36] <micahg> but it wasn't
[03:36] <ajmitch> orig.tar.gz is 186K, diff.gz was 1.4MB :)
[03:36] <micahg> right
[03:44] <NCommander> ajmitch: ugh, I hate when that happens
[03:44] <NCommander> ajmitch: I think I sent you looking at a bad bug
[03:44]  * NCommander fails
[03:45] <ajmitch> NCommander: still valid, the first branch had been uploaded, the 2nd was a valid branch for review
[03:46] <NCommander> thanks ajmitch
[03:58] <NCommander> I'm calling it a day
[03:58] <NCommander> @pilot off
[03:58] <udevbot> (pilot (in|out)) -- Set yourself an in or out of patch pilot.
[03:59] <NCommander> ...
[03:59] <NCommander> oh
[03:59] <NCommander> @pilot out
[04:01] <ajmitch> NCommander: ok, thanks for your efforts :)
[04:02]  * NCommander decides if he wants to head home yet
[04:03]  * ajmitch should decide if he should put his name down for the patch pilot programme
[04:03] <ebroder> ajmitch: Dooooo it :)
[04:04] <ajmitch> ebroder: requires time & dedication on a particular day
[04:04] <ebroder> ajmitch: It's true. I'm kind of tempted to do it some time, given how much success NCommander had harrassing core-devs
[04:05] <ajmitch> I'll be sure to hide next time then :P
[04:05] <NCommander> ajmitch: talk to jono. Right now, all ubuntu devs from Canonical are on the list, but I'm pretty sure we can get more on there
[04:05]  * micahg suggests a cloak that says ImNotACoreDev
[04:05] <ebroder> NCommander: There's some space at the end of months for community members to fill in. Also weekends
[04:06] <NCommander> micahg: heh ;-)
[04:06] <ajmitch> NCommander: it certainly looks open to getting more people involved
[04:07]  * micahg wonders if the main sponsors queue will be affected by this programme
[04:07] <ajmitch> micahg: isn't that sort of the point?
[04:07] <micahg> ajmitch: not from what I can tell
[04:08] <ebroder> It was definitely a big motivator for the UDS discussion
[04:08] <ajmitch> the patch pilot discussion came out of trying to get sponsoring to work well, from what I know
[04:08] <ebroder> ajmitch: Right, and core is where sponsoring isn't working well already
[04:09] <ajmitch> right, because we're all lazy
[04:09] <ajmitch> or at least I am :)
[04:11] <micahg> I think NCommander did a great job as pilot though
[04:12] <NCommander> micahg: I pointed core developers to bugs and got three knocked out
[04:12] <NCommander> I think its a success
[04:12] <ajmitch> it'll depend on who's around to poke, though
[04:16]  * ajmitch must run
[07:47] <StevenK> RAOF: My theory was that if I locked my machine, DPMS wouldn't fire. My machine disproved that during my lunch break. Perhaps my DPMS has moods ...
[07:53] <pitti> Good morning
[07:53] <pitti> cjwatson: d-i> sure, thanks
[07:54] <pitti> Sarvatt, bdrung: just wanted to rebuild those two (128 and mach), since these haven't changed in a while, and they carried big changelogs
[07:54] <pitti> I uploaded no-change uploads for packages where the chance is very high that they won't get another "regular" upload in natty
[07:55] <pitti> NCommander: apport package structure hasn't changed in ages; apport-symptoms has always been a separate package, FYI
[07:56] <dholbach> good morning!
[07:58] <NCommander> pitti: didn't know
[07:58] <didrocks> good morning
[08:26] <pitti> apw: the WI tracker is yelling at me now
[08:26] <pitti>   File "/home/platform/work-items-tracker/report_tools.py", line 160, in workitems_over_time
[08:26] <pitti>     ') GROUP BY status, date' % ms_sql, (team,))
[08:26] <pitti> sqlite3.OperationalError: no such column: status
[08:26]  * pitti RTFS
[08:27] <apw> pitti, huh, that has to be my fault
[08:27] <apw> but i'd swear i'd run the full tests
[08:28] <pitti> and I don't see a fundamental change there, too
[08:28] <apw> bibble
[08:28] <pitti> oh, hang on
[08:28] <pitti> there's a subselect now
[08:28] <pitti> apw: ah
[08:29] <pitti> it stumbles over the outer GROUP BY status in report_tools.py:160
[08:29] <pitti> apw: not sure what the column header is called with that, "w.status"?
[08:29]  * pitti tries a "w.status as status" in the inner select
[08:29] <apw> well when i tested it in sqlite it was status ... hrm
[08:30] <apw> i even have that exact piece of sql in my sqlite history
[08:30] <apw> select status, date, count(status) from (SELECT DISTINCT w.status, date, w.description, w.assignee  FROM work_items w, specs s ON w.spec = s.name LEFT JOIN teams ON (s.assignee = teams.name OR w.assignee = teams.name) WHERE (teams.team = 'canonical-kernel-team' OR w.assignee = 'canonical-kernel-team' OR s.assignee = 'canonical-kernel-team')) group by status, date;
[08:31] <apw> which runs and produces output !?!
[08:31] <apw> pitti, just be aware there are 4 the same in that function
[08:31] <pitti> *nod*
[08:32] <pitti> platform@lillypilly:~/work-items-tracker$ ./burndown-chart -d ../work-items-db/natty.db -t canonical-desktop-team -o /tmp/x.svg
[08:32] <pitti> ok, that reproduces it nicely and quickly
[08:32] <apw> apw@dm$ ./burndown-chart -d current.db -t canonical-desktop-team -o /tmp/x.svgapw@dm$
[08:32] <apw> hrm, no error for me
[08:33] <pitti> apw: lillypilly is on hardy -- different python/sqlite?
[08:33] <apw> poop
[08:33] <apw> it must be something like that
[08:33] <apw> as that command here produced a nice little graph :(
[08:34] <apw> well at least i know why my testing is a fail
[08:36] <apw> pitti, feel free to just revert that commit and i can go work out how to do it with hardy
[08:36] <pitti> I'll try to bang on this for a while
[08:36] <pitti> "w.status AS status" doesn't seem to work unfortunately
[08:37] <apw> pitti, crap, well as i say i am happy to take it offline and sort it out
[08:38] <pitti> oh, hang on -- just forgot a trailing space
[08:38] <pitti> ah, that does it
[08:38] <apw> pitti, where ?
[08:39] <apw> after the ( ?
[08:39] <pitti> apw: pushed
[08:39] <pitti> apw: no, I forgot it when I added "AS status"
[08:39] <apw> ahhh
[08:39] <pitti> so it ended up being "w.status AS statusFROM
[08:40] <apw> pitti, wel thank you for fixing that one
[08:40] <pitti> thanks for fixing the original bug
[08:40]  * apw adds 'test on people' to his list
[09:02] <zyga> mvo, hi, I'm trying to upgrade my machine to maverick using do-release-upgrade, it fails and points me at some log files, would you mind having a look and telling me what is wrong? I've tried this several times but I fail to see the "that's why" error message
[09:03] <zyga> mvo, the log (main.log) is here http://pastebin.ubuntu.com/535478/
[09:08] <mvo> zyga: sure, could you mail me the "apt.log" file as well? it can not resolve some dependencies, that file contains the details
[09:10] <zyga> mvo, may I pastebin, thunderbird fails to display on this device
[09:11] <zyga> mvo, apt.log http://pastebin.ubuntu.com/535479/
[09:11] <zyga> mvo, I removed all my PPAs and removed/purged all the packages that were "obsolete/local" in aptitude
[09:11] <zyga> mvo, trying again
[09:14] <zyga> mvo, that worked
[09:15] <mvo> zyga: cool, looking at the log it seems like libdrm-poulsbo1 might be the trouble maker
[09:16] <mvo> and xserver-xorg-video-psb  - out of curisoity, what repo has/had that?
[09:16] <mvo> the "gma500" ppa?
[09:16] <zyga> mvo, yes
[09:16] <zyga> mvo, special handling needed?
[09:17] <zyga> mvo, unfortunately without that ppa my hardware is useless
[09:21] <mvo> zyga: yeah, I think there should be a quirk handler for this in the release upgrader if its a common ppa
[09:23] <zyga> mvo, do you have any code for quirks like that already?
[09:26] <mvo> zyga: not for the exact problem, but for similar ones in DistUpgrade/DistUpgradeQuirks.py
[09:27] <zyga> looking
[09:28] <AnAnt> Hello
[09:47] <zyga> mvo, wow, you even have arm quirks!
[09:51] <mvo> zyga: yes :)
[09:51] <mvo> zyga: nothing that I can test it against, but there are some /proc/cpuinfo fixtures in tests/ for this
[09:51] <mvo> (nothing real)
[09:52] <zyga> mvo, yeah I wac curious if it's possible to test the quirk resolver alone against a set of fixtures
[09:52] <zyga> mvo, othewise developing this is a lot harder
[09:54] <mvo> zyga: the tests infrastructure in that code is not ideal :/ but its relatively straightforward to add the fixture stuff with apt.Cache(rootdir="./testdir"). then testsidr just needs etc/apt/sources.list, var/lib/apt/lists etc
[09:54] <mvo> zyga: most importantly var/lib/dpkg/status
[09:55]  * ogra puts on helmet and overall 
[09:56] <mvo> ogra: what for?
[09:56]  * dholbach cheers for ogra
[09:57] <zyga> mvo, I see, ... still I have no idea how I'd use that to test the quirks code, sorry :-(
[09:58] <mvo> ogra: fffffllllllyyyyyy
[09:59] <mvo> zyga: no worries, if you report a bug I will check it out, make sure to include the system_state file (that contains the dpkg status file)
[09:59] <ogra> @pilot on
[09:59] <udevbot> (pilot (in|out)) -- Set yourself an in or out of patch pilot.
[09:59] <ogra> @pilot on ogra
[09:59] <udevbot> (pilot (in|out)) -- Set yourself an in or out of patch pilot.
[09:59] <ogra> @pilot in
[10:00] <ogra> adies and gentlement, we welcome you on our flight to patchland today, please remain seated until we reached our flight altitude, life vests are under your seat ... in the unlikely event of cabin pressure loss oxygen masks will fall off the ceiling, try to find them on the floor if you can :P ... during the flight please make sure to wear your seatbelt while seated, as turbulences can occur at any time during the flight ... we wish you a pleasent fli
[10:00] <ogra> ght with ubuntu airlines now
[10:00] <dholbach> haha
[10:00]  * dholbach hugs ogra
[10:00] <ogra> ;)
[10:00] <mvo> haha - you fly too often ;)
[10:00]  * micahg hopes the pilot takes a walk through the "main" cabin later :)
[10:00] <ogra> i surely do ;)
[10:04] <zyga> mvo, can I do that while upgrading to maverick now? where's the file
[10:04] <mvo> zyga: sure, its in /var/log/dist-upgrade/
[10:05] <zyga> mvo, got it
[10:05] <zyga> mvo, filing bug now
[10:06] <\sh> mvo: moins :) do you have a link to your bzr branch for the fix you did yesterday regarding apt-key net-update and the timeout? :)
[10:10] <mvo> \sh: yes, http://bazaar.launchpad.net/~ubuntu-core-dev/apt/ubuntu/revision/1835
[10:10] <mvo> zyga: thanks!
[10:13] <zyga> mvo, thank you https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/680422
[10:14] <\sh> mvo: thx
[10:17] <ogra> didrocks, hmm, i'm looking at the utouch-grail branch, in bug 667802 ... seems the branch you committed the last change to is the natty packaging branch instead of the maverick one
[10:17] <mvo> zyga: thanks
[10:18] <didrocks> ogra: it's the same for both
[10:18] <didrocks> ogra: the last one was a bugfix release
[10:18] <ogra> the comments indicate differently
[10:18] <didrocks> ogra: yeah, but I talked with them and the .1 was basically all the commits
[10:18] <ogra> https://bugs.launchpad.net/ubuntu/+source/utouch-grail/+bug/667802/comments/28
[10:18] <didrocks> ogra: they just thought that for an sru they don't have the right to make a new . version
[10:19] <ogra> ah
[10:19] <didrocks> thanks, I read it :)
[10:19] <didrocks> I remember very well
[10:19] <didrocks> Yes, utouch-grail/packaging contains the change in source, whereas
[10:19] <didrocks> utouch-grail/packaging.maverick contains the change as a patch
[10:19] <ogra> then i misunderstood, i just wondered how to sponsore a natty upload that way
[10:20] <didrocks> same changes, better to keep the same version ^
[10:20] <ogra> since the natty branch already has a maverick changelog entry
[10:20] <ogra> and a tag
[10:22] <didrocks> ogra: hum, I didn't push to the maverick branch, not sure why it diverged
[10:22] <ogra> no, you commited to the natty branch
[10:22] <ogra> https://code.launchpad.net/~utouch-team/utouch-grail/packaging has as last commit the changelog and tag for maverick
[10:23] <ogra> i would have sponsored it for natty but dont know how now
[10:23] <ogra> at least without messing up the changelog and tags
[10:27] <didrocks> ogra: as it should be the same, just wait for -proposed to be accepted (if not already) and copy to natty
[10:27] <didrocks> ogra: when we are in sync, no need for double uploads…
[10:27] <ogra> k
[10:29] <ogra> pitti, (or another archive admin) bug 667802 see above, can you copy it over from maverick to natty please ?
[10:29] <pitti> ogra: can we please do proper natty uploads at this point, so that they build against the current toolchain and pkgbinarymangler?
[10:30] <ogra> oh, right, i forgot the toolchain :P
[10:33] <ogra> didrocks, so it seems that wont work
[10:33] <didrocks> ogra: yeah, just make a dummy .real maybe
[10:35] <ogra> well, i cant even upload to any of the utouch branches, just piloting here
[10:35]  * ogra leaves a comment on the bug
[11:01] <quadrispro> hi all
[11:04] <Keybuk> mvo: someone told me a German joke the other day
[11:04] <Keybuk> Two bratwurst in a frying pan; first one says "Boy, i'm really hot".  The second goes "Argh! A talking bratwurst!"
[11:05] <soren> *chuckle*
[11:06] <zyga> time to reboot into maverick
[11:06] <zyga> brb
[11:06] <apw> Keybuk, heh, a real insight into their jokes :)
[11:10] <mvo> Keybuk: heh :) I can only link to monty python http://www.youtube.com/watch?v=LhmnOpoGAPw
[11:11] <Keybuk> mvo: you realise that Monty Python is hilarious, right? :p
[11:11] <mvo> I do
[11:12] <Keybuk> (context: ev is still trying to persuade me that The Onion is funny)
[11:12] <ev> it is!
[11:16] <mvo> I have no idea aobut the onion, but monty python rules :)
[11:18] <davmor2> Keybuk: the iwheel from onion was funny you can't deny it...
[11:18] <ev> mvo: http://www.theonion.com/video/obama-replaces-costly-highspeed-rail-plan-with-hig,18473/
[11:24] <mvo> ev: haha - that is great
[11:24] <ev> that settles it then
[11:24] <ev> American humor wins
[11:24]  * mvo is away for a couple of minutes to have lunch
[11:25] <mvo> well, monty python and terry pratchett vs the onion ? isn't that 2:1 ?
[11:26] <ev> I'd show you the daily show, but the videos are locked to the US
[11:27]  * persia mumbles about proxy servers
[11:27] <azeem> ev: you can watch the daily show from Germany
[11:27] <azeem> at least the last three weeks
[11:28] <ev> oh, there you go then :)
[11:31] <mvo> lunch first :)
[11:37] <tjaalton> the archives work too.. like this one http://www.thedailyshow.com/watch/tue-april-21-2009/the-stockholm-syndrome-pt--1
[11:37] <tjaalton> and pt. 2
[11:37] <ev> tjaalton: only in the US :(
[11:37] <tjaalton> ev: I'm from Finland ;)
[11:38] <ev> weird, it doesn't work in the UK
[11:38] <tjaalton> hmm, sound only?
[11:38] <ev> I guess Comedy Central hates us
[11:38] <ev> "Sorry, videos are not currently available in your country"
[11:39] <ev> I suspect it's because they have a deal with Channel 4
[11:39] <tjaalton> oh
[11:40] <azeem> right, individual clips still work (like the above), but full episodes only go back three weeks
[11:48] <BlackZ> ogra: can you have a look at http://launchpadlibrarian.net/59440471/2.4.10.1-2_to_2.4.10.1-2ubuntu1.patch ?
[11:49] <ogra> BlackZ, are you sure graphviz is still in the way ?
[11:52] <BlackZ> ogra: what do you mean exactly? (sorry, going to lunch now, will reply later)
[11:52] <ogra> ok, go to lunch, i'm here for a few more hours indeed :)
[12:05] <didrocks> ogra: ok, I've upload utouch myself then, no need to make it harder than it should be :)
[12:06] <mvo> tjaalton: don't do this to me (and my productivity ;)
[12:06] <ogra> didrocks, great, thanks for being a co-pilot :)
[12:06] <BlackZ> ogra: so, what do you mean exactly?
[12:06] <tjaalton> mvo: :P
[12:06] <didrocks> :)
[12:06] <mvo> 10 weeks of payed vacation, eh? thats just like france!
[12:06] <tjaalton> mvo: careful, or I'll post links to <gasp> finnish humor :)
[12:06] <didrocks> mvo: !!!
[12:07] <mvo> lol
[12:07] <tjaalton> though youtube has some with english subtitles..
[12:08] <ogra> BlackZ, a) you should close the bug in your changelog with the merge, b) are you sure the graphviz change you carry over is still needed
[12:09] <ogra> assuming that patch belongs to bug 657324
[12:09] <BlackZ> ogra: a) the bug will be closed: "Merge from Debian experimental, remaining changes (LP: #657324):" b) checking that :)
[12:09] <BlackZ> ogra: yes, it does
[12:09] <ogra> oops, i missed the LP in the first line, sorry
[12:11] <ogra> BlackZ, i think we can assume that the problem with the buildds and graphviz still exists (given the buildds didnt change), so let me just upload that for you
[12:12] <BlackZ> ogra: yeah, thanks! :) (I didn't that merge but I'm interested in that merge too, that's why I'm asking you to review it)
[12:17] <ogra> BlackZ, uploaded
[12:17] <BlackZ> ogra: thanks! :)
[12:17] <ogra> BlackZ, thanks for being a co-pilot !
[12:21] <ogra> stgraber, i'm looking at bug 457702 has the promised upload from teh last comment ever happened ? (if so, could you close the bug)
[12:22] <tkamppeter> seb128, hi
[12:23] <ogra> cjwatson, given that dpkg was uploaded without optimizations, should we probably revert the debootstrap hack ?
[12:23] <ogra> cjwatson, talking about bug 674146 and lool's upload
[12:24]  * ogra thinks one fix is enough
[12:24] <ogra> s/fix/workaround/
[12:26] <cjwatson> ogra: I'd be fine with that
[12:26] <cjwatson> I should deal with the Debian side of the bug at some point mind you
[12:26]  * cjwatson is deep inside grub2 atm
[12:27] <ogra> i didnt want to be pushy it just seems useless to work around the issue in two places
[12:27]  * ogra is fine to work on the debsootstrap reversion
[12:32] <ari-tczew> I'm looking for sponsorship, bug 626379
[12:44] <bdrung> kenvandine: welcome in the core-dev team
[12:44] <persia> Uh, it will be a few more minutes :)
[12:44] <bilalakhtar> ken became core-dev? wow!
[12:44] <persia> will become.
[12:45] <bilalakhtar> but approved nevertheless :D
[12:48] <seb128> tkamppeter, hey
[12:53] <ogra> ari-tczew, heh, i didnt watch IRC while i uploaded the fix ...
[12:54] <ogra> thanks for the pointer though, its already up
[12:54] <ari-tczew> ogra: did you upload this one to lucid-proposed?
[12:55] <quadrispro> persia, thanks for the add
[12:57] <ogra> ari-tczew, yep
[12:59] <ari-tczew> ogra: could you comment this on bug? thanks for sponsorship, but I'm not a witch
[12:59] <ogra> ?? i commented
[12:59] <ari-tczew> hmmm
[13:00] <ogra> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/626379/comments/15
[13:00] <ogra> :)
[13:00] <ari-tczew> ogra: ah, 7 minutes ago ...
[13:00] <ogra> yeah, i took the time to review it before uploading :)
[13:01] <ari-tczew> nice
[13:01] <ogra> feel frr to ping me directly while i'm patch pilot, i didnt look at IRC after my conversation with colin above
[13:01] <ogra> *free
[13:01] <ogra> only noticed your pint after the upload
[13:01] <ogra> *ping
[13:01] <ari-tczew> ogra: what is patch pilot?
[13:01] <ogra> someone to help with patches and sponsoring
[13:02] <ogra> we have one every day now, you can see who it is in the topic
[13:02] <BlackZ> ari-tczew: https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews#Patch%20Pilots
[13:04] <ari-tczew> ogra: so Canonical employees are patch pilots?
[13:04] <cjwatson> there's no reason why it should be restricted to Canonical employees, but we are the only ones who can be *instructed* to take part ;-)
[13:04] <doko> bdrung: why do you want to sync gcc-snapshot? what do you gain?
[13:04] <ogra> ari-tczew, https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews there is a scedule
[13:05] <ogra> *schedule
[13:05] <ogra> doesnt need canonical amployees, anyone acn apply indeed
[13:05] <ari-tczew> aha got it
[13:08] <persia> Well, other folk who happen to do this for their day job can also be so instructed, but they are less common :)
[13:08] <seb128> ogra: don't forget to use -v
[13:08] <seb128> ogra: when you build merges from debian
[13:08] <ogra> seb128, argh
[13:08] <ogra> did i ?
[13:08] <seb128> ogra: libgphoto yes
[13:09] <ogra> ouch, sorry
[13:10] <seb128> no worry
[13:10] <ari-tczew> ogra: I see waiting bug 663343 :)
[13:11] <ogra> will take care for it after the arm meeting
[13:11] <ari-tczew> nice
[13:11] <ogra> thanks for the pointer and for being a co-pilot :)
[13:11] <ari-tczew> ogra: love it :D
[13:13] <tkamppeter> seb128, it is about the photo printing Blueprint.
[13:13] <tkamppeter> seb128, in the work items is mentioned for you to check why paper size widget is disabled by default.
[13:14] <seb128> I will
[13:16] <tkamppeter> seb128, as GNOME bug 551409 shows that a method to activate the page size and orientation widgets was added to the GTK printing dialog I consider the configuration without "Page Setup" as supported upstream and so I think we should change the photo applications now.
[13:17] <seb128> tkamppeter, ok, can you open bugs on softwares that need to be updated and update the spec with the bug numbers?
[13:18] <mdeslaur> @pilot in
[13:18]  * dholbach hugs ogra and mdeslaur
[13:18] <ogra> hey mdeslaur !
[13:18]  * mdeslaur hugs dholbach 
[13:18] <tkamppeter> seb128, I have looked into the patch for eog in GNOME bug 614451 and eliminating the Page Setup dialog is a small patch doing nothing more than calling said method when initializing the print dialog, saving page setup settings when clicking OK/Apply/Print in the dialog, and removing all code which creates the Page Setup dialog. I have done this with shotwell for testing.
[13:18] <mdeslaur> hi ogra :)
[13:19]  * ogra offers mdeslaur a seat in the cockpit
[13:19] <tkamppeter> seb128, I will report appropriate bugs.
[13:19] <seb128> tkamppeter, thanks
[13:22] <mdeslaur> -ETOOMUCHWIKIDOC
[13:23] <ogra> mdeslaur, https://bugs.launchpad.net/~ubuntu-sponsors/+subscribedbugs is a good start
[13:23] <mdeslaur> ogra: ah! the exact information I was looking for :)
[13:24] <mdeslaur> ogra: thanks :)
[13:24] <seb128> http://qa.ubuntu.com/reports/sponsoring/index.html
[13:24] <seb128> why not using that?
[13:24] <ogra> or that
[13:25] <mdeslaur> ogra: so I don't start working on the same stuff as you...are you going down that list, or up?
[13:26] <dholbach> seb128's list is better, it includes merge proposals too
[13:27] <mdeslaur> dholbach: cool
[13:27] <ogra> mdeslaur, random :)
[13:27] <mdeslaur> ogra: ok
[13:27] <ogra> dholbach, the buglist has them too
[13:28] <dholbach> ogra: only if there's merges that have sponsoring bugs attached to them :)
[13:28] <ogra> mdeslaur, i'm in a meeting atm, after that i'll look at bug 663343
[13:29] <seb128> ogra: no it doesn't
[13:29] <seb128> ogra: the launchpad list only has bugs
[13:30] <ogra> seb128, well, libgphoto2 was a merge request (with ready made patch)
[13:30] <seb128> ogra: which had a bug as well?
[13:30] <ogra> yes
[13:30] <seb128> well quite some people don't use bugs
[13:31] <ogra> there are enough bugs for merges still
[13:31] <seb128> see the sponsoring page for some example
[13:31] <hallyn> lool: i just did 'bzr co lp:ubuntu/natty/qemu-kvm', and ended up with the maverick tree ?
[13:31] <seb128> ogra: not sure what your point is, the qa reports list has bugs and things which don't have bugs, seems a better list to work on?
[13:32] <seb128> ogra: or do you want to ignore people who don't file bugs for some reason?
[13:32] <ogra> seb128, well, the title is "patch" pilot
[13:32] <ogra> so i'm looking for patches
[13:32] <ogra> which usually go with bugs
[13:32] <seb128> well a merge request is a diff which is a patch is some way
[13:32] <ogra> sure
[13:32] <seb128> we are moving away from adding manual diffs to bugs
[13:33]  * ogra really doesnt think it matters how the lists are getting empty 
[13:33] <ogra> as long as they do get empty
[13:33] <seb128> right, we are just telling that your list is not reflecting the really of things needed review
[13:33] <seb128> if you drive your list to 0 you still ignore contributors, those who don't open bugs
[13:33] <ogra> well, patches are patches
[13:34] <ogra> if the list is 0 i will move on to another list
[13:34] <seb128> ok, your call
[13:34] <seb128> if you have enough to keep busy on the list you use go for it
[13:34] <ogra> right
[13:35] <seb128> the comment was just to point that things are waiting out of this list
[13:35] <seb128> http://qa.ubuntu.com/reports/sponsoring/index.html reflects both
[13:35] <ogra> yeah
[13:35] <ogra> got that
[13:35] <seb128> you might find things easy to sponsor there that interest you and are not on the other listing
[13:35] <seb128> so it might be worth watching it
[13:35] <seb128> now you do what you want from it ;-)
[13:36] <ogra> thanks :)
[13:36] <lool> hallyn: the importer didn't import the newer revisions yet as it seems
[13:36] <persia> seb128, I'm not sure it's fair to say "we're moving away" from attaching diffs to bugs: I think it's better to say that we're supporting UDD workflows, and encourage their use.
[13:36] <lool> hallyn: james_w is on leave this week, let's check whether barry can hepl
[13:36] <lool> barry: hey!
[13:36] <persia> There's just too many folk out there who know diffs and don't know bzr who can help to completely drop diff attachments.
[13:36] <lool> barry: Would you have some time to help us with a qemu-kvm package-import issue?>
[13:36] <seb128> persia, ok, said different "increasing number of request come without bugs"
[13:36] <seb128> which is just what I noticed
[13:37] <persia> seb128, I firmly agree with that.  Positive statements :)
[13:37] <lool> barry: Basically, a new upstream version was merged without merge-upstream; I reverted these commits now, but the importer didn't reimport the uploads, despite a new qemu-kvm having been uploaded
[13:37] <seb128> which suggest that a class of users is moving away from filing bugs
[13:37] <seb128> there was nothing else suggested in my comment ;-)
[13:40] <hallyn> lool: so what is 'the importer'?  isn't this just a bzr tree to be pushed?
[13:42]  * hallyn googles while waiting for vpn
[13:43] <cjwatson> not everyone uses branches, so there's a process that looks at uploads and constructs bzr trees for them if it doesn't already find them
[13:44] <hallyn> uploads as in 'dput' ?
[13:44] <hallyn> (if so, then i see - interesting.  given my last hard FAIL, i wonder if it's safer if i do that :)
[13:45] <cjwatson> yes
[13:46] <cjwatson> (as in dput, dupload, whatever)
[13:48] <lool> hallyn: http://package-import.ubuntu.com/status/
[13:48] <lool> hallyn: and see also the UnderTheHood link I sent in my email
[13:50] <hallyn> lool: thanks
[13:53] <pitti> quadrispro: congratulations to your core-dev badge!
[13:59] <quadrispro> thanks for all the support pitti !
[14:00] <bilalakhtar> Congrats quadrispro !
[14:01] <sladen> cyphermox: that changelog of yours for evolution is *very* impressive
[14:03] <cyphermox> sladen, there's a lot in it, yes
[14:04] <cyphermox> and still ftbfs on i386 for some reason now, despite lots of build testing and functionality testing >.<
[14:19] <apw> is it me or are we getting a much higher percentage of random 'failed to build's with no logs in PPAs ... all of a sudden
[14:21] <om26er> 'Friendly Patch Pilots' is it on?
[14:22] <diwic> BlackZ, about bug #680386, the reason it is two patches, is because there was two patches in F14
[14:23] <om26er> bug 652944
[14:23] <diwic> BlackZ, could you explain why it is important to have it as one patch only?
[14:23] <BlackZ> diwic: so any reason to not merge them? they exist for the same purpose, don't they?
[14:24] <om26er> i have a branch with the fix backported. can anyone please sponser? https://code.launchpad.net/~om26er/ubuntu/maverick/telepathy-haze/telepathy-haze-fix-652944/+merge/41597
[14:24] <diwic> BlackZ, the reason is mainly to keep things identical to F14. If that counts as a reason, I don't know
[14:25] <seb128> om26er, subscribe ubuntu-sponsors or ask review from the team for it
[14:25] <seb128> om26er, if the day patch pilots don't review it someone in desktop land will
[14:26] <om26er> seb128, ok subscribed ubuntu-sponsors .thanks
[14:26] <BlackZ> diwic: if they're not for the same purpose, choose a different name for each patch, if they're for the same purpose I don't see the point of splitting two patches for the same purpose
[14:27] <seb128> om26er, thank you for working on that ;-)
[14:30] <diwic> BlackZ, ok, so if I fix that according to your wishes, is it ready for upload or is it anything else I should do at the same time?
[14:32] <BlackZ> diwic: you could add where you take the patch or the upstream commit, then it looks fine to me apart for that :)
[14:32] <diwic> BlackZ, are you looking for an URL?
[14:33] <BlackZ> diwic: an url where you took the patch from would be ok
[14:35] <stgraber> ogra: oops, this bug should have been closed indeed (457702). I usually do a pass through all our bugs at the hackfest, but for some reason didn't this year :(
[14:35] <ogra> stgraber, well, close it so it doesnt start smelling ;)
[14:35] <stgraber> ogra: done ;)
[14:52] <mdeslaur> cjwatson: I'm slightly stumped by this build log: http://launchpadlibrarian.net/59497625/buildlog_ubuntu-natty-i386.pbuilder_0.199ubuntu2_FAILEDTOBUILD.txt.gz
[14:52] <mdeslaur> cjwatson: any ideas? the "LANG=C MANWIDTH=80 man --warnings -E UTF-8 -l pbuilder.8 >/dev/null" works fine for me in a natty schroot
[14:56] <geser> I can reproduce this in my natty pbuilder (but not my natty chroot)
[14:58] <cjwatson> mdeslaur: it happens only if you have no locales
[14:58] <cjwatson> sounds like a man-db bug though
[14:59] <mdeslaur> cjwatson: ok, will fiddle with man-db. What do you mean by "no locales"?
[14:59] <cjwatson> mv /usr/lib/locale/locale-archive /usr/lib/locale/locale-archive.safe
[14:59] <cjwatson> is enough to trigger the bug
[15:00] <mdeslaur> cjwatson: hmm...I don't have locale-archive in my schroot, yet am not able to trigger it
[15:00] <cjwatson> sorry, for avoidance of doubt, when I say "sounds like a man-db bug though" that's me accepting it as an upstream bug
[15:00] <cjwatson> well, whatever's in /usr/lib/locale/
[15:00] <mdeslaur> cjwatson: it's empty
[15:00] <cjwatson> huh
[15:00] <cjwatson> triggered it for me :)
[15:01] <mdeslaur> odd
[15:01]  * ogra grabs his parachute 
[15:01] <ogra> @pilot out
[15:01] <mdeslaur> ogra: bye! :)
[15:01] <ogra> thanks for flying ubuntu airways today :)
[15:02] <cjwatson> I installed a horrible hack for col's locale in response to Debian #555331
[15:02] <cjwatson> I bet it's related to that
[15:03] <cjwatson> may depend on the locale in your environment too
[15:03] <mdeslaur> cjwatson: huh...I can reproduce it now
[15:04] <barry> lool: hi.  i had a school meeting this morning, but i'm back now.  what can i help with?
[15:04] <cjwatson> actually, wait, man-db probably can't do anything more
[15:04] <cjwatson> there's no UTF-8 locale available, so it can't make col work
[15:04] <cjwatson> pbuilder should probably generate a temporary UTF-8 locale
[15:05] <cjwatson> mdeslaur: see e.g. http://git.debian.org/?p=lintian/lintian.git;a=commitdiff;h=9b7c0896ae937cc29662cc4d385d94df27626268
[15:07] <chrisccoulson> heh, i have to do something similar in firefox to get a UTF-8 locale so that some of the unit tests work properly
[15:07] <mdeslaur> cjwatson: ah! thanks for the hint, I'll try that
[15:08] <mdeslaur> (I'm still kind of stumped how it worked fine in my chroot 5 minutes ago, and now doesn't anymore...)
[15:09] <lool> barry: Can you arrange for the package importer to retry qemu-kvm?
[15:09] <lool> barry: I think it got flagged as broken, and I arranged to "fix" the branch
[15:10] <barry> lool: i don't believe i have permissions to do that
[15:10] <lool> barry: Ah how unfortunate; ok, thanks
[15:10] <barry> lool: yeah.  i should really talk with james_w about that
[15:12] <james_w> barry, please file an RT
[15:12] <barry> james_w: file an RT on doing the retry or getting permission so i can request it?
[15:12] <james_w> barry, on getting permissions
[15:13] <james_w> lool, retried
[15:13] <dholbach> seb128, I will never forgive you!
[15:13] <seb128> dholbach, lol
[15:13]  * james_w &
[15:13]  * seb128 hugs dholbach
[15:13] <seb128> dholbach, did you get the comment with it?
[15:13] <lool> james_w: Thank you!  you go back to leave  :)
[15:13] <dholbach> yes :)
[15:13] <barry> james_w: gotcha.  are the retries done on package-import.ubuntu.com or launchpad?
[15:13] <dholbach> seb128, can I still commit to the branches?
[15:13] <dholbach> or don't you use them any more?
[15:13] <james_w> barry, the former
[15:13] <seb128> dholbach, ok, the ui is confusing, it's not clear if the comment is specific to expiration
[15:14] <james_w> barry, you need to be in the pkg_import group IIRC
[15:14] <dholbach> seb128, can I still commit to the branches?
[15:14] <ogra> barry, hrm
[15:14] <barry> james_w: gotcha.  i thought it was p-i.u.c but when i look at e.g. the qemu-kvm package page, i didn't see any knobs i could twiddle
[15:15] <james_w> barry, the pages are read-only
[15:15] <seb128> dholbach, you can commit for things you have upload rights for still
[15:15] <ogra> barry, i just uploaded the diff from bug 663343 ...
[15:15] <seb128> dholbach, other teams are subteam from this one
[15:15] <dholbach> seb128, you don't use lp:~ubuntu-desktop/..... any more?
[15:15] <ogra> barry, any idea why there is a newer cheetah in the archive but the bug is still open ?
[15:15] <seb128> dholbach, we do but ubuntu main uploaders are members of ubuntu-desktop
[15:15] <james_w> barry, we could add retry buttons, but going to a read/write webapp is a fairly large step
[15:15] <ogra> (there is no newer one in debian)
[15:15] <dholbach> seb128, alrightie
[15:15] <dholbach> thanks
[15:15] <seb128> dholbach, so anybody who can upload to main can commit to the team as well
[15:16] <dholbach> gotcha
[15:16] <seb128> dholbach, we still love you ;-)
[15:16]  * seb128 hugs dholbach
[15:16] <dholbach> yeah, I know... in a special way
[15:16] <barry> james_w: ah. so when i get in the pkg_import group, how do i request a re-import?
[15:16]  * dholbach hugs seb128 back
[15:16] <dholbach> :-P
[15:16] <seb128> lol
[15:16] <seb128> dholbach, should I be scared now? ;-)
[15:16] <dholbach> no, you kick me out of the team and say "yeah, don't worry - we still love you"
[15:16] <dholbach> a special way of "love"
[15:17] <dholbach> nevermind :)
[15:17] <seb128> lol
[15:17] <james_w> barry, https://wiki.ubuntu.com/DistributedDevelopment/UnderTheHood/Importer
[15:17] <seb128> dholbach, you know what, if you are nice to me I can get you back in :p
[15:17] <lool> https://wiki.ubuntu.com/DistributedDevelopment/UnderTheHood/Importer/Operational
[15:17] <dholbach> don't worry - it's fine
[15:17] <lool> ah too late
[15:17] <dholbach> it's over!
[15:17] <seb128> dholbach, now maybe you should be scared ;-)
[15:17]  * dholbach storms out
[15:17] <barry> lool: thanks
[15:17]  * seb128 cries
[15:17] <barry> james_w: thanks
[15:19] <lool> barry: So if you're tempted to help fix that one, that would be appreciated
[15:19] <barry> ogra: i think the bug report title is out of date.  we sync'd from debian but SpamapS has a couple of other minor changes to add
[15:20] <lool> barry: What happened is that a new upstream version was committed by hand, but without bzr import-upstream; this broke the importer with bzrlib.errors.NoSuchTag: No such tag: upstream-0.13.0+noroms
[15:20] <lool> https://bugs.launchpad.net/udd/+bug/494481
[15:20] <ogra> SpamapS, feel free to ping me for a new upload once your changes are in sync
[15:20] <lool> barry: then I bzr uncommit-ed all revs in the hope that the importer would just reimport all versions properly
[15:20] <lool> barry: but now I get AssertionError: qemu-kvm 0.13.0+noroms-0ubuntu1 ubuntu natty is marked but not imported
[15:20] <lool> http://package-import.ubuntu.com/status/qemu-kvm.html#2010-11-23%2015:13:47.151829
[15:21] <barry> ogra: from the merge proposal, it looks like there's still some uncertainty about the patch.  i guess SpamapS has to straighten that out (i see he's waiting on a response)
[15:21] <ogra> barry, ok, i'm fine to be the upload bitch once there is a patch ready
[15:22] <ogra> since i touched it now already
[15:22] <james_w> lool, looking
[15:23] <BlackZ> diwic: uploaded
[15:23] <barry> ogra: cool.  i think i'm out of the loop on that one now, though i'm happy also to re-review anything for SpamapS
[15:23] <ogra> oki
[15:23] <diwic> BlackZ, thanks :-)
[15:24] <barry> lool: i agree with james_w on that bug.  subscribed now ;)
[15:24] <lool> barry, james_w: I understand that the sqlite db mentions versions that were already imported but notin the bzr branch anymore
[15:27] <james_w> lool, correct, and I just deleted that row
[15:27] <james_w> lool, it's now importing
[15:27] <lool> james_w: awesome, thanks
[15:29] <lool> james_w: Branch looks good, thanks!!
[15:29] <james_w> np
[15:29] <bilalakhtar> james_w: Just a general question: Are there a large number of people using UDD already?
[15:29] <hallyn> lool: fwiw i have not yet gotten the link you mentioned.
[15:29] <bilalakhtar> I use it, but many AFAIK dislike it calling it a bit bulky to download branches
[15:30] <barry> james_w: rt submitted
[15:30] <james_w> bilalakhtar, I can't remember the numbers, but see recent mails to ubuntu-distributed-devel@
[15:30] <james_w> barry, cool, thanks
[15:30] <bilalakhtar> thanks james_w for the ML address
[15:31] <lool> hallyn: Really?  mail from Date: Mon, 22 Nov 2010 16:47:34 +0100
[15:32] <hallyn> lool: oh, the underthehoodone
[15:32] <hallyn> got it.  thx
[15:44] <pitti> cjwatson: would you mind uploading a d-i in maverick-proposed against 2.6.35-23?
[15:45] <cjwatson> not at all, give me a minute to fettle branches
[15:50] <pitti> skaet: lucid/maverick kernels copied to -updates, FYI
[15:50] <lool> doko: alpha 1 is in 10 days, but in https://bugs.launchpad.net/gcc-linaro/+bug/675347/comments/20 you ask for no more compiler upload before alpha 1; however this breaks all builds based on qt including qt itself; what can we do to avoid this?
[15:51] <skaet> pitti,  thanks!  :)
[15:51] <lool> doko: should we change the default build flags on armel to -fno-strict-volatile-bitfields
[15:51] <doko> lool: well, if I can pick the patch from the Linaro repo, or if it's accepted upstream, fine
[15:52] <doko> currently doesn't have a review
[15:52] <lool> doko: Ok; let's wait for an ack then
[15:52] <lool> doko: what's the deadline to upload gcc-4.5 with that fix?
[15:53] <doko> I thought alpha1 would be this week, but if I can upload it before the weekend, that should be ok
[15:54] <lool> doko: I see eglibc was not updated in natty; the linux-libc-dev fix seems to be in the archive though
[15:54] <lool> doko: it's a bit confusing since linux is still in NEW, but the linux-libc-dev changelog includes   * net: rtnetlink.h -- only include linux/netdevice.h when used by the kernel
[15:56] <cjwatson> apw asked me to reject the kernel from NEW because it was broken
[15:56] <doko> lool: well, I don't do the NEW processing. and I did want to wait with the eglibc upload for the 2.13 release
[15:56] <lool> cjwatson: Yes; the linux-libc-dev changes are already in the archive though
[15:56] <cjwatson> though I see there's a new upload there
[15:56] <apw> cjwatson, yep there is a new kernel on its way through
[15:56] <lool> doko: I mean linux is in NEW, but the one in the archive is good enough
[15:56] <cjwatson> apw: is -6.17 healthier then?
[15:56] <apw> it would be built already if we hadn't had a random failure on an i386 build
[15:57] <apw> yep, muchly so
[15:57] <doko> lool: did you test the merge?
[15:57] <lool> doko: I've built it on maverick
[15:57] <lool> doko: But I didn't build/test it under natty
[15:57] <lool> and some additional commits made their way into the branch in the mean time
[15:57] <lool> from Kees and you I believe
[15:57] <doko> I'll try to do it this week, but IMO it's not a priority for me
[15:57] <apw> cjwatson, looks like it would be finished building in about half hour
[15:58] <lool> doko: Ok; I thought you wanted that before A1, that's why I bring it up as well
[15:58] <cjwatson> apw: ok ...
[16:00] <doko> lool: there's too much I want for alpha1 ... \o/
[16:00] <lool> I want a pony!
[16:00] <apw> lool, you really don't they are soooo expensive to run
[16:00] <lool> ;)
[16:01] <bdrung> doko: because angelabad requested it. the gain? probably getting it off the m-o-m list
[16:03] <doko> bdrung: that's little gain, and blocking the buildds
[16:09] <mdeslaur> lool: I'm trying to fix a pbuilder FTBFS on natty...the Makefile tests manpages with -E UTF-8, but locales aren't properly installed in buildds
[16:10] <mdeslaur> lool: would you rather I disable the man page tests, or try and generate a locale in the rules file (ugh...)
[16:11] <lool> mdeslaur: Perhaps test for the availability of the locale, and disable the tests if it's not available?  I could merge that in Debian
[16:12] <mdeslaur> lool: ah, I'll try that...thanks
[16:13] <mdeslaur> lool: in the Makefile, or in the rules file?
[16:13] <lool> mdeslaur: Ideally in Makefile
[16:15] <cjwatson> generating the locale would really be better
[16:15] <lool> mdeslaur: I wonder what local is used
[16:15] <cjwatson> it can be done without root access - you can generate one in a temporary directory
[16:15] <mdeslaur> cjwatson: so, using localedef in the rules file and then setting LOCPATCH before the make test?
[16:16] <SpamapS> ogra_ac: ping, that bug report includes a merge proposal to merge the /debian changes from 2.4.2.1-1 into 2.4.3-0ubuntu1
[16:16] <mdeslaur> s/LOCPATCH/LOCPATH/
[16:16] <lool> barry: Just wanted to let you know that the subversion failure on armel (KWallet test) is due to bug #675347
[16:16] <cjwatson> it's certainly what I'd do (well, I haven't looked at exactly where the localedef should go)
[16:16] <lool> so not subversion's fault
[16:17] <mdeslaur> cjwatson, lool: ok, I'll generate a locale file in debian/rules
[16:17] <ogra_ac> SpamapS, yeah, i was tricked by the title it seems
[16:18] <cjwatson> pitti: uploaded
[16:20] <pitti> cjwatson: cheers
[16:21] <SpamapS> ogra_ac: you were tricked by barry running off and uploading 2.4.3 without applying the debian dir changes from 2.4.2.1-1 ;) the title is still more or less accurate. ;)
[16:22] <ogra_ac> SpamapS, so are your changes in the branch ready for upload or do they still need to mature a bit ?
[16:24] <tkamppeter> seb128, I reported bug 677575, bug 680483, bug 680521, and bug 680550
[16:24] <SpamapS> ogra_ac: they've been tested.. very minor stuff
[16:42] <chrisccoulson> Sarvatt, ok, i've uploaded the fix for xulrunner-1.9.2 hanging now, hopefully that should work ;)
[16:43] <Sarvatt> chrisccoulson: thanks! sorry to bug ya in IRC instead of a bug :)
[16:43] <chrisccoulson> that's ok. i don't often read bug mail, so IRC is much quicker ;)
[16:44] <SpamapS> cjwatson: ping? wondering if you can answer a plymouth question definitively for me
[16:45] <SpamapS> cjwatson: trying to resolve this issue where apache2 has a very small window to ask for a password before the system boots.. does plymouth deactivate/quit terminate an ask-for-password ? Shoudn't it wait for that password to be entered first?
[16:47] <ScottK> SpamapS: Isn't any server application asking for a password on boot broken by design?
[16:47] <Keybuk> ScottK: SSL passphrases
[16:48] <ScottK> That's not normally how I deal with that issue on a server.
[16:52] <SpamapS> ScottK: how do you deal with it?
[16:52] <cjwatson> SpamapS: the quit handler seems to just exit the event loop; I don't know for sure but my guess would be that that does not wait for pending input.  As for what it should do, I'm inclined to agree with you but you should ask #plymouth really
[16:52] <ScottK> SSL certs the don't require a passphrase.
[16:53] <SpamapS> I actually think "encryption pass phrases" seems to be the only reason for a system level service to ask for user input.
[16:53] <SpamapS> cjwatson: will do
[16:53] <ScottK> Perhaps.
[16:53] <ScottK> I just don't see a boot process that involves human intervention being reasonably scalable for server use.
[16:55] <cjwatson> at the same time we shouldn't design to intentionally break that, I think
[16:57] <ScottK> True.
[16:57] <SpamapS> ScottK: I happen to think that the encrypted private key is just a mediocre solution to the problem, but probably the best that software only can provide. You either need to trust that your root privileges + other security layers are secure, or you need to put your keys on removable media that can be physically secured.
[16:59] <SpamapS> Either way, with the change uploaded to natty yesterday.. now you at least have a chance at entering the pass phrase during boot rather than having to start it manually post-boot..
[17:00] <geser> cjwatson: I've tried to add anon login to edit_acl.py: querying the packageset contents works, but not the uploaders. Is that enough for your use case?
[17:04] <pitti> didrocks: hm, I do have unity installed, but I don't see a session for it any more in /usr/share/xsessions?
[17:04] <pitti> didrocks: I just created a fresh test user, but that starts GNOME, and I don't see how to select unity as a session in gdm?
[17:05] <ogra_ac> gnome is the new unity ?
[17:05] <didrocks> pitti: yeah, it will be the default this week as "Next release will mean unity by default" :)
[17:05] <didrocks> pitti: wasn't stable enough last week, wanting to wait for a week
[17:06] <didrocks> pitti: the gnome session will get unity by default (apart from existing natty user as explained because of the settings), I'll add a gnome-classic session in the same upload
[17:06] <pitti> didrocks: ok, so it's not actually possible to test it right now?
[17:06] <pitti> didrocks: thanks for confirming; seems it's all well underway :)
[17:07] <didrocks> pitti: testing unity? you can, in checking it in ccsm
[17:07] <pitti> ah
[17:07] <didrocks> https://wiki.ubuntu.com/Unity/InstallationGuide
[17:07] <pitti> well, when I said "starts GNOME" I should have said "half of GNOME", all the indicators crashed..
[17:07] <pitti> but I guess I should be able to run ccsm
[17:07] <pitti> didrocks: merci!
[17:07] <cjwatson> geser: I suppose that would be OK; in that case anonymous login will have to be a non-default option
[17:07] <cjwatson> geser: and yes, thinking about it that's probably what I saw
[17:08] <didrocks> pitti: you're welcome
[17:16]  * mdeslaur pulls ejection seat lever
[17:16] <mdeslaur> @pilot out
[17:57] <RoAkSoAx> kirkland: howdy!! Let me know if you have a lil bit of time to discuss PowerNap
[18:33] <lubosz>  hi. is there an automatic way to disable as much as unneeded modules possible in the kernel config, to shorten build time?
[18:46] <lubosz> is there a possibility to not rebuild everything with make-kpkg every time?
[18:51] <akheron> lubosz: try #ubuntu-kernel
[18:51] <akheron> lubosz: and if you find out, tell me
[18:51] <lubosz> akheron: thanks
[18:51] <akheron> I once spent a week bisecting a kernel bug because one build took so long
[18:52] <akheron> s/one/each/
[18:52] <lubosz> sounds awfull :D
[18:52] <lubosz> i have a core 2 notebook
[18:52] <lubosz> and it takes about one hour
[18:52] <lubosz> to compile the whole thing
[18:52] <akheron> yes, for me it was like hour and a half
[18:53] <akheron> and I had over 4k commits to bisect
[18:53] <lubosz> i pulled patches today and had to recompile a lot
[18:53] <lubosz> i guess the whole kernel
[18:53] <lubosz> but i didnt check the time
[18:53] <lubosz> 4k Oo
[18:53] <lubosz> so a week sound fast for that :p
[18:53] <lubosz> did you run git bisect with a script?
[18:54] <lubosz> to check good or bad?
[18:54] <akheron> no
[18:54] <lubosz> hm, you had to do that by hand? :D
[18:54] <akheron> yes
[18:54] <akheron> after each build was finished, I copied the kernel to another machine and rebooted
[18:54] <akheron> I had a boot time issue with an old laptop
[18:54] <akheron> but hey, I found the offending commit and it's fixed now :D
[18:55] <lubosz> so about 10 times to compile?
[18:55] <akheron> no, it was more like 15 or 20
[18:55] <akheron> as near the end there was a huge octopus merge of 10 branches or so
[18:55] <lubosz> and you found the bug at the end ;) ?
[18:55] <akheron> yes :)
[18:56] <lubosz> nice
[18:56] <akheron> actually, I'm using the laptop right now that didn't run back then
[18:57] <lubosz> i hate compiling large things on a laptop
[18:57] <lubosz> its a huge difference with a quad core with hyperthreading
[18:57] <akheron> I didn't compile on a laptop, no way
[18:58] <lubosz> my desktop is at home, and i'm at my partents, so i have to hack on my laptop :D
[19:12] <akgraner> Anyone know the status of cobbler? https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-cobbler  I've got someone asking me and not sure where to point them to or just tell them it's permanently deferred?
[19:15] <RoAkSoAx> akgraner: kirkland is looking into it for natty afaik
[19:16] <akgraner> RoAkSoAx, thanks!
[19:17] <RoAkSoAx> akgraner: ur welcome :)
[19:21] <om26er> hi kenvandine
[19:21] <kenvandine> hey om26er
[19:21] <om26er> this is the branch https://code.launchpad.net/~om26er/ubuntu/maverick/gwibber/gwibber-fix-674894/+merge/40899
[19:22] <om26er> can you upload it to -proposed
[19:23] <kenvandine> om26er, sure can, i'll sponsor that
[19:24] <om26er> kenvandine, congrats core-dev ;)
[19:24] <kenvandine> thx
[19:24] <kenvandine> :)
[19:25] <fEnIo> hello
[19:25] <fEnIo> could someone tell me why devscripts from Ubuntu doesn't contain debsign script?
[19:27] <cjwatson> fEnIo: it does here
[19:27] <cjwatson> $ zgrep debsign ~/ubuntu/dists/natty/Contents-i386.gz
[19:27] <cjwatson> usr/bin/debsign                                             devel/devscripts
[19:27] <fEnIo> ok... that was the most stupid question I've asked today
[19:27] <cjwatson> :-
[19:27] <fEnIo> sorry
[19:27] <cjwatson> )
[19:27] <cjwatson> (and that was stupid typing to make up for it)
[19:28] <fEnIo> I installed devscripts but only in virtual machine, and then checked on host os
[19:28] <fEnIo> nevermind
[19:28] <fEnIo> sorry for bothering
[19:31] <om26er> when i push a change to a branch does the reviewer get the email? or do i have to make a comment?
[19:32] <lifeless> they do not [yet] get a notification that you have pushed more changes to the branch
[19:32] <lifeless> assuming you have a merge proposal already existing :)
[19:35] <stgraber> cjwatson: Hi, could you move sabayon from the ubuntu-desktop package set to the edubuntu packageset. It's a gnome upstream project but is only shipped by edubuntu and one of the upstream developers is in edubuntu-dev.
[21:29] <ikonia> Riddell: you there ?
[23:18] <testi> chrisccoulson, i made you the approver of a blueprint i wrote. (I'm new to this process, not sure if I'm doing things right here)
[23:21] <testi> multiseat-admin-graph-ui
[23:34] <quadrispro> hi all!