Loggerhead does not support "nested style" repository layout

Bug #311513 reported by Alexandre Garnier
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
loggerhead
Triaged
Low
Unassigned
loggerhead-breezy
Triaged
Low
Unassigned

Bug Description

I use "nested style" repository layout (http://bazaar-vcs.org/SharedRepositoryLayouts#nested-style-project-branch-sub-branch) and with loggerhead, I can access only the trunk wich is the repository. (http://localhost:8080/project/files in the layout example)
Even if I change the URL to link to sub-branches (http://localhost:8080/project/joe/feature1/files in the layout example), it doesn't work with a "The resource could not be found." error.

Tags: affects-gnu
Revision history for this message
Matt Nordhoff (mnordhoff) wrote : Re: [Bug 311513] [NEW] Loggerhead does not support "nested style" repository layout

FWIW, it does when using serve-branches.

This is already known, but I can't find a bug report. Hm.

Revision history for this message
Alexandre Garnier (zigarn) wrote :

I use serve-branches !

I have this configuration :
/data/bzr --> folder of repositories
|-- project1 --> repository of project1 AND trunk of project1
| |-- branches --> folder of project1 branches
| | `-- ... --> project1 branches
| `-- releases --> folder of project1 release branches
| `-- ... --> project1 release branches
`-- project2 --> repository of project2 AND trunk of project2
    |-- branches --> folder of project2 branches
    | |-- branch1 --> project2 branch1 branch
    | | |-- sub-branch1 --> project2 branch1 sub-branch
    | | `-- ... --> project2 branch1 sub-branches
    | `-- ... --> project2 branch
    |-- teams --> folder of project2 teams branches
    | `-- ... --> project2 teams branches
    `-- releases --> folder of project2 release branches
        `-- ... --> project1 release branches

./serve-branches /data/bzr/ --> access to all projects trunks but not branches
./serve-branches /data/bzr/project1/ --> access to project1 trunk but not branches
./serve-branches /data/bzr/project2/teams/ --> access to all project2 teams branches
./serve-branches /data/bzr/project2/branches/branch1/ --> access to project2 branch1 branch but not sub-branches

Revision history for this message
Martin Albisetti (beuno) wrote :

So, the reason why Loggerhead doesn't support nested trees, is because bzr doesn't support them well.
I can't really think of a good way to display them :(

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 311513] Re: Loggerhead does not support "nested style" repository layout

On Tue, 2008-12-30 at 16:11 +0000, Martin Albisetti wrote:
> So, the reason why Loggerhead doesn't support nested trees, is because bzr doesn't support them well.
> I can't really think of a good way to display them :(

This isn't really nested trees Martin, though I do understand the
challenge in rendering this well.

-Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Revision history for this message
Alexandre Garnier (zigarn) wrote :

Maybe by adding a 'sub-branches' tab when the current branch contains sub-branches (well detected by 'branches' command of BzrTools) which will show an embed 'Browsing' view.
In addition, an expander on global 'Browsing' view to expand the folder or branch and show sub-branches and sub-folders containing sub-branches rendering something like the attachment.

Changed in loggerhead:
status: New → Confirmed
Revision history for this message
Martin Albisetti (beuno) wrote :

still unsure how to address this.

Changed in loggerhead:
importance: Undecided → Wishlist
status: Confirmed → Triaged
Revision history for this message
Alexandre Garnier (zigarn) wrote :

Here is a try : http://bazaar.zigarn.com:8080/. It use the repository layout given in my comment

The default mode is directory.
If a branch have no sub-branch, the view is switched to changes of this branch.
To open a branch, the only way is to use the link on branch-folder icon.
There is now a '.' entry in directory view to open the current branch.

Changed in loggerhead:
assignee: nobody → Alexandre Garnier (zigarn)
status: Triaged → In Progress
Changed in loggerhead:
assignee: Alexandre Garnier (zigarn) → nobody
status: In Progress → New
Changed in loggerhead:
status: New → Confirmed
Changed in loggerhead:
status: Confirmed → Triaged
importance: Wishlist → Low
Revision history for this message
Randall Whitman (ubuntu-whizman) wrote :

Marked this bug as affecting me, because it impacts GNU Enterprise.
http://savannah.gnu.org/support/?107780
http://bzr.savannah.gnu.org/lh/gnue/

Martin Pool (mbp)
tags: added: affects-gnu
Jelmer Vernooij (jelmer)
Changed in loggerhead-breezy:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers