Project

General

Profile

Actions

Feature #4741

open

Improve Bazaar repositories error message in case to use shared repository

Added by Joe Julian about 14 years ago. Updated over 12 years ago.

Status:
New
Priority:
Normal
Assignee:
Toshi MARUYAMA
Category:
SCM
Start date:
2009-02-21
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

This was originally miscategorized as Feature #2799.
This is a common use case as it prevents the standard trunk/branch/tag development structure.

A shared repository created with bzr init-repo errors when running ruby script/runner "Repository.fetch_changesets" -e production I get these messages back:
bzr: ERROR: Not a branch: "[...]/project_container/.bzr/branch/".
bzr: ERROR: Not a branch: "[...]/project_container/.bzr/branch/".

If we point at a sub-tree, there's still no support for branches.

There are 2 ways to identify the shared repository:
  • bzr info will list 'shared repository: .'
  • .bzr/repository exists.

If the path points to a shared repo, some file tree should be built.

Branches can be identified by a similar combination of techniques:
  • bzr info will list the root repository as 'shared repository'
  • .bzr/branch exists.
Sub branches:
  • bzr info will list the root repository as 'shared repository' and the parent branch as 'parent branch'

As an example, let's examine the following repo:
[...]

In summary, if the path is a repo, scan the directory tree for directories containing .bzr/branch and run bzr info on those directories. Use that output to find out which branch is the parent and use that information to build the element tree.

I don't know how to do this in ruby, but hopefully someone can take this analysis and put something together.


Related issues

Related to Redmine - Feature #2799: Support for Bazaar's shared reposetories (created with init-repo)New2009-02-21

Actions
Related to Redmine - Defect #7984: Confusing revisions links on repository rootNewToshi MARUYAMA2011-03-24

Actions
Related to Redmine - Patch #9129: Improve wording of Git repository note at project settingClosedToshi MARUYAMA2011-08-26

Actions
Actions #1

Updated by Toshi MARUYAMA almost 13 years ago

  • Priority changed from High to Normal
Actions #2

Updated by Toshi MARUYAMA almost 13 years ago

  • Estimated time deleted (2.00 h)
Actions #3

Updated by Toshi MARUYAMA over 12 years ago

  • Assignee set to Toshi MARUYAMA
  • Target version set to 1.3.0
Actions #4

Updated by André Bachmann over 12 years ago

Is there a way how I can get your changes into my Redmine 1.2.0? Or can I simply copy bazaar_adapter.rb and abstract_adapter.rb from redmine/trunk to my Redmine 1.2.0?

Actions #5

Updated by Toshi MARUYAMA over 12 years ago

  • Subject changed from Bazaar repositories error to Improve Bazaar repositories error in case to use shared repository
Actions #6

Updated by Toshi MARUYAMA over 12 years ago

  • Subject changed from Improve Bazaar repositories error in case to use shared repository to Improve Bazaar repositories error message in case to use shared repository
Actions #7

Updated by Toshi MARUYAMA over 12 years ago

  • Tracker changed from Defect to Feature
Actions #8

Updated by Toshi MARUYAMA over 12 years ago

  • Target version changed from 1.3.0 to Candidate for next major release
Actions

Also available in: Atom PDF