[02:33] <kgoetz> ah. i just exploded bzr
[02:38] <kgoetz> does the bot report bug numbers? just filed https://bugs.launchpad.net/bzr/+bug/756228 . would it be useful for me to keep a copy of the repo for testing?
[06:01] <d1b> hi um i did a bzr clone lp:~launchpad-pqm/launchpad/stable in a vm with 256mb of ram
[06:01] <d1b> it is taking a long time and using a fair amount of memory
[06:01] <d1b>  539m 171m  956 D  4.6 69.9   3:15.61 bzr
[06:02] <d1b> it is Bazaar 2.1.2
[06:45] <d1b> interesting it got oom killed :P
[06:47] <d1b> fail++
[06:54] <lifeless> uyeah
[06:54] <lifeless> you'll need a little more ram than that
[19:42] <methods> can the bzr web repo browser allow people to edit and commit ?
[19:54] <jelmer> methods: no, although you can e.g. run wikkid to allow editing of bzr branches from the web
[19:55] <methods> hm wikkid ?
[19:55] <methods> https://launchpad.net/wikkid
[19:55] <methods> that one ?
[19:57] <jelmer> yep
[20:30] <vokoda> hi, is it ok to ask about loggerhead in here?
[20:35] <lifeless> sure
[20:41] <vokoda> ok, so I'm running loggerhead 1.18.1 on a high port, and serving it up via nginx pass_proxy, which works fine at mydomain.com. but now I want to serve from mydomain.com/bzr - i've set my nginx location in the usual way, and i can see the requests going through to loggerhead: GET /bzr/ HTTP/1.0... etc. but i just get a 404 response and "The resource could not be found."
[20:41] <vokoda> i've set prefix=/bzr in my loggerhead.conf
[20:41] <vokoda> but that was on a whim
[20:42] <vokoda> i couldn't find any real docs for loggerhead config
[20:45] <vokoda> is prefix= deprecated? it doesn't seem to be doing anything
[20:45] <lifeless> do you have pastedeploy installed ?
[20:46] <vokoda> not sure, i installed via apt-get from debian stable. but it works at mydomain.com/, so presumably i do?
[20:48] <lifeless> loggerhead looks for HTTP_X_FORWARDED_SERVER
[20:48] <lifeless> to determine its virtual path
[20:48] <lifeless> is nginx setting that ?
[20:48] <lifeless> (see loggerhead/main.py)
[20:54] <maxb> Random other comment, loggerhead.conf is deprecated and does not exist in future loggerhead versions
[20:55] <vokoda> maxb: i'm actually using serve-branches.conf, I presume that's just a different name for loggerhead.conf?
[20:56] <maxb> actually, no :-)
[20:56] <maxb> serve-branches.conf is an invention of the debian packaging which just passes a few values to the init script to use on the command line starting the server
[20:57] <vokoda> right, ok
[20:57] <vokoda> mine is very simple
[20:57] <vokoda> http://paste.pocoo.org/show/369250/
[20:58] <vokoda> lifeless: googling 'HTTP_X_FORWARDED_SERVER nginx' turns up nothing
[20:58] <vokoda> so i guess it's a job for tcpdump
[20:58] <vokoda> or pdb but I'm not up for that right now
[20:59] <mDuff> IIRC, setting up any headers to be added on proxying has to be explicit in nginx
[21:00] <vokoda> mDuff: ah, proxy_set_header
[21:03] <vokoda> lifeless: looks like loggerhead/main.py raises an error if 'HTTP_X_FORWARDED_SERVER' is set?
[21:04] <lifeless> vokoda: *and* paste.deploy is not present
[21:04] <lifeless> vokoda: python-pastedeploy is the package, I think
[21:04] <lifeless> pastedeploy is needed to run behind a proxy
[21:08] <vokoda> lifeless: sigh.. installing pastedeploy worked, i feel stupid now. I thought serve-branches would be a bit louder about an import error
[21:08] <vokoda> at least it's working
[21:08] <vokoda> thanks
[21:20] <lifeless> vokoda: cool