[07:35] * apw yawns [08:56] rtg [09:06] heh, that makes so much sense [12:37] Hi [12:38] I'm hitting this issue here http://www.spinics.net/lists/git/msg217736.html when I try to clone from kernel.ubuntu.com GIT repositories [12:38] would it be possible to contact the admins somehow ? [12:38] The patch for the issue has to be applied server-side and is already in upstream GIT repository, see http://www.spinics.net/lists/git/msg217744.html [13:07] Marex, is that after a very long wait ? [13:07] Marex, and ... does dropping the -q help [13:07] was that you who said that ? [13:08] apw: dropping -q fixes it, yes [13:08] apw: it was me who posted to the git@vger ML, yes [13:08] so you have a work around at least [13:09] apw: I'm invoking the git from Yocto build and as yocto adds the -q option to the git command line, the workaround is not much of an option [13:10] apw: would it be possible to get a proper fix applied ? [13:10] Marex, well yokto isn't being very helpful now is it [13:11] Marex, everything is possible, though that machine is on lucid, ick [13:11] Marex, so i wouldn't bet my house on it [13:11] can the patch not be backported on that version of git? the patch doesn't seem too big [13:14] apw: the patches are here http://www.spinics.net/lists/git/msg217019.html http://www.spinics.net/lists/git/msg217020.html btw [13:15] Marex, in the unlikely event that a patch against tip still applied it might well be possible, though it would have to go thorugh the SRU process so its not going to be less than weeks [13:16] Marex, you would need to file a bug against git in the first instance [13:16] Marex, though can you not work round this by cloning the tree locally and then just doing the yocto commands against a local mirror? [13:16] apw: it's a server side bug, why would I work around it instead of fixing the server ? [13:17] Marex, presumably because you arn't running the command for fun but to get somethign donw [13:17] apw: certainly, but it's not only me running into these issues [13:18] apw: I just so happened to be too annoyed by it to push for a fix [13:19] Marex, the backport looks to be non-trivial, so its not going to happen right now [13:20] Marex, can you file a bug against git with the relevant info above in the description please, 'ubuntu-bug git' and give me the number, so i can thnk about it [13:21] I dont even have a lunchpad account, would it be too much to ask to leave this in your hands ? [13:21] well normally one gets the reporter to test etc [13:23] apw: let me see [13:27] ugh [13:27] apw: where do I need to navigate to file a bugreport for ubuntu kernel git ? [13:28] file it against the package git, as that is the issue [13:28] it's rather git-core , no ? [13:29] https://bugs.launchpad.net/ubuntu/+source/git/+filebug [13:29] old 'git' went away somewhen in the last 2 years, and git-core -> git === fmasi_afk is now known as fmasi === fmasi is now known as Guest8464 [13:49] apw: is this the correct bug report https://bugs.launchpad.net/ubuntu/+source/git/+bug/1228148 ? [13:51] Marex, yep that lookfs goo thanks [13:57] apw: thanks, I will also update the redhat bugzilla, where this was initially reported and the git mailing list [14:25] jsalisbury, yo ... we discussed using aliases for git bisect good/bad to allow reverse bisects to not blowup ones head ... [14:26] jsalisbury, if you ended up codifying that, i wonder if it would make sense to update https://wiki.ubuntu.com/Kernel/KernelBisection with that knowledge [15:01] apw, never put anything into code, just been keeping track in my head when I do them [15:05] jsalisbury, ok ... [16:46] jodh, yo ... i have a couple of boxes which 'recently' are rebooting when i ask for power off ... ie when i say sudo poweroff it doesn't === kentb is now known as kentb-afk [18:16] * apw wanders to another location where there are beverages [18:18] * bjf thinks that's a fine idea === kentb-afk is now known as kentb === kentb is now known as kentb-out