Allow higher level trunk layouts
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar Subversion Plugin |
Fix Released
|
Low
|
Jelmer Vernooij | ||
| bzr-svn (Debian) |
Fix Released
|
Unknown
|
|||
Bug Description
I've just started using Bazaar, and initially want to continue using a remote Subversion repository using the 'svn+ssh' protocol. What I find is that it works when 'subversion.conf' does *not* exist. If that file exists (i.e. after any successful previous access of the Subversion repository), then I get the following error:
----
bzr: ERROR: exceptions.
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
attaching the crash file
and including a description of the problem.
The crash file is plain text and you can inspect or edit it to remove
private information.
----
The temporary fix each time is to delete 'subversion.conf'.
'bzr --version' gives
----
Bazaar (bzr) 2.0.2
Python interpreter: /usr/bin/python 2.6.4
Python standard library: /usr/lib/python2.6
Platform: Linux-2.
bzrlib: /usr/lib/
Bazaar configuration: /home/tony/.bazaar
Bazaar log file: /home/tony/.bzr.log
----
Related branches
| abcoates (abcoates) wrote | #1 |
| Jelmer Vernooij (jelmer) wrote | #3 |
| Changed in bzr-svn: | |
| status: | New → Incomplete |
| abcoates (abcoates) wrote | #4 |
| summary: |
- Bazaar error when working with 'svn+ssh' Subversion repository, and - 'subversion.conf' exists + Allow higher level trunk layouts |
| Changed in bzr-svn: | |
| status: | Incomplete → Fix Committed |
| importance: | Undecided → Low |
| assignee: | nobody → Jelmer Vernooij (jelmer) |
| Changed in bzr-svn (Debian): | |
| status: | Unknown → Confirmed |
| Changed in bzr-svn: | |
| status: | Fix Committed → Fix Released |
| milestone: | none → 1.0.3 |
| Changed in bzr-svn (Debian): | |
| status: | Confirmed → Fix Released |
This is probably a bug in bzr-svn, so I'm going to thunk it over there. Jelmer can always change it back. :)
IIRC, this error came up once before... I don't remember what happened, though.