Comment 11 for bug 496721

I would really like to see this bug resolved, as it is a barrier to adoption of Bazaar for our organization. I have updated the branch with relevant information, and I am happy to do whatever work needs to be done to see this through.

I believe I may have found a related bug that affects repositories whose names need to be escaped. Every repository that I have tested against whose name does not conform to URL specs (e.g. gtk+, an internal repository whose name contains a space) results in the first character of the name of the the directory following the root being removed (e.g. https://svn.gnome.org/svn/gtk+/trunk becomes https://svn.gnome.org/svn/gtk+/runk). For this reason, testing against gtk+ may not be the best way to validate my fixes. Is there another repository that we can test against? Should I just attach a sample repository to this issue?

I will try to tackle the related bug that I described above very soon.