Virtual repository not working via http

Bug #681304 reported by Charon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Explorer
Confirmed
Medium
Unassigned

Bug Description

I have a bazaar server up and running. The server contains many repositories, which I would like to browse with the explorer.
If I open an URL of the server where the repositories are located, I get the message:

bzr+https://eiche/bzr ist kein Branch, kein Checkout oder kein Repository.

Do you want to open it as a virtual repository, searching for nested locations?

I say yes, and the next message is:

Unable to change to /home/charon/some_more_paths/bzr+https:/eiche/bzr - closing page.

However, before this message, the location is searched for correctly, I can see the repositories in the GUI already.
When I acknowledge the error message, the repositories are gone..

So it seems, the explorer is mixing local paths with URLs which is a bug IMHO.

Revision history for this message
Charon (charon030) wrote :

I just hat a quick look into the source code. It seems, that the flag whether the location is local or not is just set in case of a branch or a repository (location.py, function reopen_location).
The if...elif... construct should be extended to:

if branch:

elif repository:

else: # or check for whatever variable tells about a virtual directory
    self._local = self._root.startswith("file://")

Revision history for this message
Charon (charon030) wrote :

OK, that's not the solution. How can I write debug messages to the log file or to the console?

Revision history for this message
mathew (meta23) wrote :

I have an almost identical problem, except I'm using a repository url starting bzr+ssh rather than bzr+https. Same failure mode, an error saying it can't change to /home/meta/bzr+ssh:/servername/srv/bzr.

bzr explorer 1.1.0 on Kubuntu 10.10.

Revision history for this message
Alexander Belchenko (bialix) wrote :

@Charon: to write debug message you need the following code:

at the beginning of the module add import:

from bzrlib.trace import mutter

and then in the code you want to trace:

mutter("your debug message here")

It will go to .bzr.log only.

Changed in bzr-explorer:
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.