[08:02] <oSoMoN> good morning
[08:02] <oSoMoN> how can I create a new repository under https://code.launchpad.net/~chromium-team/chromium-browser/+git/ ?
[08:03] <wgrant> oSoMoN: Just push to lp:~chromium-team/chromium-browser/+git/NAME
[08:06] <oSoMoN> wgrant, I get the following error:
[08:06] <oSoMoN> $ git push origin stable
[08:06] <oSoMoN> error: src refspec stable does not match any.
[08:06] <oSoMoN> error: failed to push some refs to 'git+ssh://osomon@git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source'
[08:06] <oSoMoN> with origin configured as "url = lp:~chromium-team/chromium-browser/+git/snap-from-source"
[08:07] <wgrant> oSoMoN: You don't have a branch named stable.
[08:07] <oSoMoN> d'oh, indeed locally it's master
[08:09] <oSoMoN> and after renaming my local branch, that worked
[08:09] <oSoMoN> thanks wgrant
[08:09] <wgrant> np
[10:15] <oSoMoN> is there a way to increase the size of the buildlog window for an ongoing build, to see more useful information? it appears commands generated by ninja for chromium builds are too long, and thus for deb builds I can't see one complete line, and for snaps it's even worse, I can't see anything: https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source-stable/+build/218022
[10:16] <oSoMoN> I understand that it's an edge case, the default height is probably fine for 99.99% of the projects that lp builds
[10:19] <cjwatson> I'm afraid there isn't
[10:19] <cjwatson> It's very hardcoded right now
[10:20] <cjwatson> Are you sure that snap build even started?
[10:20] <cjwatson> I mean you should at least get a partial line
[10:23] <oSoMoN> cjwatson, yes, earlier in the build I was seeing some output, for shorter commands
[10:23] <oSoMoN> cjwatson, is it worth filing a feature request against lp?
[10:24] <oSoMoN> something like a URL parameter to change the default height would be fine (i.e. no need for additional UI), if that's possible
[10:26] <oSoMoN> if it's not a task that would realistically end up being scheduled, I won't bother, I can live without it
[10:31] <cjwatson> oSoMoN: The thing is that the backend simply doesn't store more than the tail of the buildlog right now, so it doesn't have the data to show to you regardless of URL params
[10:32] <cjwatson> oSoMoN: We already have a backlogged task somewhere to fix that by storing the whole buildlog in buildd-manager and streaming it from there via the webapp, rather than doing the buildlog tail hack
[10:32] <oSoMoN> cjwatson, cool, is there a bug I can subscribe to?
[10:34] <cjwatson> oSoMoN: https://bugs.launchpad.net/launchpad/+bug/1617809
[10:35] <oSoMoN> cjwatson, perfect, thanks!
[20:05] <gpiccoli> Folks, quick question: is there a way to search for Ubuntu bugs in LP given a Debian bug?
[20:06] <gpiccoli> I want to see if there's any Ubuntu bug that relates to some Debian bug
[20:06] <gpiccoli> thanks in advance!
[20:39] <smoser> i have a git reviews question
[20:39] <smoser>  https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/345113
[20:39] <smoser> there, larse has several different versions of the merge proposal
[20:39] <smoser> and those can be selected via 'Preview Diff'
[20:39] <smoser> but is there any way i can get an old version from a 'git fetch' ?
[20:41] <smoser> ie, i want access to see what dd61338 looked like (or 74671dc or 288fbfe).   All I can currently get is the most recent commit (68c2ca5).
[20:48] <nacc> smoser: https://git.launchpad.net/~larsks/cloud-init/tree/?id=dd61338 ?
[20:48] <nacc> smoser: that is, go back to the source repo with the commit hash?
[20:49] <smoser> nacc: well, i git fetch'd that repo
[20:49] <smoser> but the hash isn't necessarily availble in his repo either
[20:50] <smoser> right? as it got garbage collected
[20:50] <nacc> smoser: well the above existed
[20:50] <smoser> then why dont i see it i wonder.
[20:50] <nacc> smoser: as in the above URL should work :)
[20:51] <nacc> so does 74671dc
[20:51] <nacc> smoser: so locally `git show 74671dc` after fetching the remote doesn't work?
[20:51]  * nacc clones to try as well
[20:52] <smoser> nacc: http://paste.ubuntu.com/p/y755HXMpxB/
[20:53] <nacc> smoser: yeah, weird
[20:53] <nacc> oh i wonder
[20:54] <nacc> so it's not reachable, now, i expect
[20:54] <nacc> so fetch wouldn't download it
[20:55] <smoser> yeah. that makes sense. and its not reachable. but i want it. :)
[20:55] <smoser> i was told once (cant find doc) that github has in its pull requests you can effectivelyd o this stuff.
[20:55] <nacc> one sec, i'm testing someting
[20:57] <nacc> smoser: http://help.github.com/articles/commit-exists-on-github-but-not-in-my-local-clone ?
[20:58] <smoser> well on github https://gist.github.com/piscisaureus/3342247
[20:58] <smoser> they have refs/pull/
[20:58] <nacc> oh separate refs
[20:58] <smoser> i was told once that you can also get all old versions of a pull requests
[21:00] <nacc> smoser: i honestly don't know ... not something Git does by default, obviously; and not sure LP has any special handling of it (you *might* be able to do something via the LP API, since LP itself is able to do it)
[21:00] <smoser> well, clearly launchpad has a reference to that commit
[21:00] <smoser> as you pointed out in the web ui
[21:00] <smoser> and also obviosly as the MP thing can show  me different versions
[21:00] <nacc> yeah
[21:01] <nacc> that's what I mean, the API might be able to do it, because it's using the Git repo as on-disk possibly?
[21:01] <nacc> which still has those commits
[22:16] <rbasak> Yeah. AIUI, git fetch won't let you get something unreachable by any ref, and that's deliberate. But locally you can.