[00:11] <pedro> hi
[00:13] <pedro> hi
[00:13] <pedro> who are you jelmer
[00:22] <pedro> who is awaka here
[00:22] <pedro> give me a poem
[13:49] <xapantu> Hi :)
[18:17] <sjamaan> I am trying to view files on http://bazaar.qastaging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/files but it keeps redirecting endlessly
[18:17] <sjamaan> The "Updating branch..." message doesn't go away either
[18:18] <sjamaan> Is this a known bug?
[18:19] <tsimpson> it kind-of works if you use https://
[18:19] <sjamaan> heh
[18:19]  * sjamaan tries
[18:21] <tsimpson> infinite redirects are obviously not expected though
[18:22] <sjamaan> not expected, but possibly known
[18:22] <tsimpson> staging is working fine though
[18:23] <sjamaan> yeah, I just saw it
[18:23] <sjamaan> I'll use that for my test
[18:23] <sjamaan> Is there a way to fetch a file at "the latest revision" from loggerhead?
[18:23] <sjamaan> I'm trying to construct a raw file URL that downloads this file: http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/view/head:/spiffy.release-info
[18:24] <sjamaan> The "download file" link encodes all sorts of codes
[18:25] <sjamaan> replacing "view" with "download" just causes an error
[18:25] <tsimpson> I think you're supposed to use bzr for that ;)
[18:26] <sjamaan> Is there a http-only way to do it though?
[18:27] <tsimpson> well bzr can use http
[18:27] <sjamaan> Does launchpad offer that?
[18:27] <tsimpson> bzr cat http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/spiffy.meta
[18:28] <tsimpson> the lp: address shortcut uses bzr+ssh, but there's nothing stopping you from using the "real" URL
[18:28] <sjamaan> hm, that does some magic apparently because a straight GET doesn't fetch the file
[18:28] <tsimpson> yes, it uses bzr :)
[18:28] <sjamaan> But why does it say http then?
[18:28] <tsimpson> bzr the program, not "the protocol"
[18:28] <sjamaan> yes
[18:29] <sjamaan> But the URI has a prococol of http
[18:29] <tsimpson> bzr can sit on top of http just fine
[18:29] <sjamaan> But that resource isn't really there as a normal HTTP resource
[18:29] <sjamaan> curl http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/spiffy.meta  gives a 404
[18:29] <tsimpson> bzr figures out how to get the file and just downloads it's "real" URL
[18:30] <tsimpson> it's all done over HTTP, bzr it just knows how to get the real file from the repo
[18:31] <sjamaan> What exactly is done over HTTP?
[18:31] <sjamaan> And why doesn't that URL work with a HTTP GET request?
[18:31] <tsimpson> everything is done over HTTP
[18:31] <tsimpson> bzr breaks the URL apart at the branch and figures out how to get the file from the rest of the URL
[18:32] <sjamaan> Is there a way to figure out that URL without digging in the bzr sources?
[18:32] <tsimpson> not easily, that's why bzr is there
[18:32] <sjamaan> Or is it not an URL but a special header or something?
[18:33] <tsimpson> you can use the python API if you don't want to actually run bzr directly
[18:33] <tsimpson> bzr does nothing to the HTTP protocol, it just uses it as a transport mechanism
[18:34] <sjamaan> hm, ok
[18:34] <tsimpson> file:// http:// bzr+ssh://, it doesn't matter as long as it can send a request and get some data back
[18:34] <sjamaan> But there's no way to get an URI like  http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/download/head:/spiffy.releaseinfo-20110326171946-vqfrwsi51nna9bj3-46/spiffy.release-info without going to http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/view/head:/spiffy.release-info ?
[18:37] <tsimpson> no, it's a generated URI
[20:25] <Meths> Why is code browsing looking sucky again?
[20:27] <lifeless> do you mean bazaar.launchpad.net ?
[20:29] <Meths> Yep
[20:29] <lifeless> what do you mean by being sucky?
[20:29] <Meths> The same line spacing I filed a bug and you fixed before.
[20:32] <lifeless> ah
[20:32] <lifeless> new theme I guess
[20:32] <lifeless> want to file a new bug? I'll nudge our UI dude on monday
[20:33] <lifeless> (it may be missing css, or it may be a defect in the new theme)
[20:33] <Meths> File a new bug or reopen the old one?
[20:33] <lifeless> new bug
[20:33] <lifeless> always a new bug :)
[20:33] <Meths> k
[20:34] <Meths> Will always a new bug translate into a process that gets this tested in future rather than always just another new bug?
[20:36] <lifeless> it will depend on the cause
[20:36] <lifeless> we deploy loggerhead on two machines
[20:36] <lifeless> one machine just serves the css
[20:37] <lifeless> the other just serves the dynamic bits
[20:37] <lifeless> I suspect the former machine hasn't been deployed to
[20:37] <lifeless> because the other stuff on the former machine is not able to updated without downtime
[20:37] <lifeless> if that the case, updating our process/docs should solve this
[20:37] <lifeless> if its something else - well, will analyse
[20:41] <Meths> Well CSS was the bug before so if it's CSS the docs didn't get updated last time.  New bug filed.
[20:46] <lifeless> thanks
[21:40] <akoskm> evening
[21:43] <akoskm> I built some packages through launchpad for ubuntu - maverick, is it possible to build packages from the same source to older releases of ubuntu?
[22:58] <aroman> hello, are there bindings to access launchpad in any languages other than python?