weird situation: repository browser doesn't work, while branches macro works
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Trac-Bzr |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I found a very weird situation when trac-bzr behaves strange.
I use trac 0.10.5 @ python 2.4 + bzrlib 2.3.4 + trac-bzr 0.3.3
I have the following trac environment structure:
mytracenv/
attachments/
conf/
db/
htdocs/
branches/
foo/ # this is a branch
bar/ # this is a second branch
log/
plugins/
templates/
wiki-macros/
Pretty standard I think.
It works fine as long as there is no bzr branch intialized in parent directories (related to htdocs/branches). If for example I initialize a branch at htdocs/ or right in mytracenv directory then trac-bzr is unable to browse my branches, it says:
No node at revision current:
But in the same time [[Branches]] macro still works as expected! That's strange.
I suspect branches browser and branches macro report generator they use different code to get the list of available branches.
I'm not sure it's a real bug, because that's me who breaks plugin behavior in really weird way, but it takes me several hours today to find out why it's broken. Maybe there is simple way to better handle this problem. Or maybe you can point me to the place in the code where I can look at and maybe I can figure a simple solution to workaround this problem. I don't really need the proper support for such weird configuration but I would be very grateful if trac-bzr will show me something more informative in this situation. Like: "hey, you stupid, we found a branch outside branches root and that cause us problems. Do something about it!" :-)
summary: |
- repository browser doesn't work, while branches macro works + weird situation: repository browser doesn't work, while branches macro + works |
It seems I found workaround for this problem. If I put a control directory to the branches/ directory (in my directory structure explained above) then trac-bzr seems works fine and stops looking for bzr brances outside defined branches root.
To create a control directory I just `bzr init-repo branches` and then `cd branches/.bzr; rm -rf repository` so I have only "branch-lock" directory inside .bzr, and 2 files: "branch-format" and "readme".
I close this bug as Invalid.