<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Jelmer Vernooij wrote: <blockquote cite="mid:1186794560.25033.178.camel@ganieda.vernstok.nl" type="cite"> <pre wrap="">Hi Hendy, Am Samstag, den 11.08.2007, 07:55 +0700 schrieb Hendy Irawan: </pre> <blockquote type="cite"> <pre wrap="">What is the proper way of working on Bazaar with Subversion? I try: ceefour@ojalanow:~/project/humblia$ bzr branch '<a class="moz-txt-link-freetext" href="http://myproject.unfuddle.com/svn/myproject_myproject/">http://myproject.unfuddle.com/svn/myproject_myproject/</a>' bzr: ERROR: Invalid http response for <a class="moz-txt-link-freetext" href="http://myproject.unfuddle.com/svn/myproject_myproject/.bzr/branch-format:">http://myproject.unfuddle.com/svn/myproject_myproject/.bzr/branch-format:</a> Unable to handle http code 401: expected 200 or 404 for full response. I can svn ls to the URL just fine. I'm usually using SVK to work offline with a Subversion repository. After hearing a lot of good things about Bazaar, I'm beginning to think that Bazaar with bzr-svn can be a good substitute/alternative to SVK. Besides I really want to try it anyway. </pre> </blockquote> <pre wrap="">Bazaar always tries to find a native bzr branch first when you specify a location. If the server returns some error indicating that the specified files was present it tries if a branch in some other format (such as Subversion) is present. In the case of a 401 it apparently immediately aborts. I'm not sure whether this is the right thing to do but I'm also not sure whether ignoring the 401 and trying other formats, such as svn, is ok. Is this by any chance a google-code hosted project? As a work-around you can tell bzr that the repository is a subversion repository by prefixing the url with 'svn+', e.g.: $ bzr branch svn+http://myproject.unfuddle.com/svn/myproject_myproject/ Cheers, Jelmer </pre> </blockquote> WHOA WHOAAAAAAAA IT (the workaround) WORKS PERFECTLY!!! THANKS Jelmer!! Is this issue noted in the documentation somewhere? Cause I'd love to post it on my web blog Thanks :-) <pre class="moz-signature" cols="72">-- Hendy Irawan <a class="moz-txt-link-abbreviated" href="http://www.hendyirawan.com">www.hendyirawan.com</a></pre> </body> </html>