bazaar error on repository

[Tata Dano-4]

Hi Guys,

At first we tried to do bazaar on a 2.5GB files but its not successful. At this point we change our repo to just a small files but when trying to push I got this kind of error.

bzr: ERROR: KnitPackRepository('ftp://[e-mail]/testdeploy/.bzr/repository/')
is not compatible with
CHKInventoryRepository('file:///C:/Documents%20and%20Settings/etch/Desktop/bazaar_repo/.bzr/repository/')
different rich-root support

Any advice on how to address this one? Thanks a million in advance.

Sincerely,

Tata

[Alexander Belchenko]

Tata Dano пишет:

> Hi Guys,
>
> At first we tried to do bazaar on a 2.5GB files but its not successful.
> At this point we change our repo to just a small files but when trying
> to push I got this kind of error.
>
> bzr: ERROR: KnitPackRepository('ftp://atat%40i360pro.com
> <http://40i360pro.com>@i360connect.com/testdeploy/.bzr/repository/
> <http://i360connect.com/testdeploy/.bzr/repository/>')
> is not compatible with
> CHKInventoryRepository('file:///C:/Documents%20and%20Settings/etch/Desktop/bazaar_repo/.bzr/repository/')
> different rich-root support
>
> Any advice on how to address this one? Thanks a million in advance.

Your local repository in 2a format (default in bzr 2.0+) but your remote
repo in old format (pack-0.92 maybe). You can ask format of remote repo
using command:

bzr info -v ftp://...

Upgrading local repo to 2a makes it incompatible with old
(non-rich-roots) format. You should upgrade your remote repository.
E.g.

bzr upgrade ftp://...

Ensure all your coworkers using bzr 2.0 or at least 1.17-1.18, otherwise
they won't access new 2a format of repo.

[Tata Dano-4]

Yeah..you are right. The remote repo is on pack-0.92 format.

I have access on the remote repo so I execute:

bzr upgrade (inside my repo folder) but I got this message instead:

[root@xxxx xxxxxx]# bzr upgrade testdeploy/
bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.

Any thoughts on this one?

Your local repository in 2a format (default in bzr 2.0+) but your remote repo in old format (pack-0.92 maybe). You can ask format of remote repo using command:

bzr info -v ftp://...

Upgrading local repo to 2a makes it incompatible with old (non-rich-roots) format. You should upgrade your remote repository.
E.g.

bzr upgrade ftp://...

Ensure all your coworkers using bzr 2.0 or at least 1.17-1.18, otherwise they won't access new 2a format of repo.

On Tuesday 13 October 2009 10:16:21 Tata Dano wrote:

May it be the remote bzr version on the remote host has not been updated?
You probably used ssh to access the remote location, right?

Try running "bzr --version" there and check if you're really using bzr 2.0
there.

Since you're using ftp you may update the remote repository directly
bzr upgrade ftp://path_to_use_branch


Joke de Buhr

> Yeah..you are right. The remote repo is on pack-0.92 format.
>
> I have access on the remote repo so I execute:
>
> bzr upgrade (inside my repo folder) but I got this message instead:
>
> [root@xxxx xxxxxx]# bzr upgrade testdeploy/
> bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is
>  already at the most recent format.
>
> Any thoughts on this one?
>
> > Your local repository in 2a format (default in bzr 2.0+) but your
> > remote repo in old format (pack-0.92 maybe). You can ask format of
> > remote repo using command:
> >
> > bzr info -v ftp://...
> >
> > Upgrading local repo to 2a makes it incompatible with old
> > (non-rich-roots) format. You should upgrade your remote repository.
> > E.g.
> >
> > bzr upgrade ftp://...
> >
> > Ensure all your coworkers using bzr 2.0 or at least 1.17-1.18,
> > otherwise they won't access new 2a format of repo.
>

[Alexander Belchenko]

Tata Dano пишет:

> Yeah..you are right. The remote repo is on pack-0.92 format.
>
> I have access on the remote repo so I execute:
>
> bzr upgrade (inside my repo folder) but I got this message instead:
>
> [root@xxxx xxxxxx]# bzr upgrade testdeploy/
> bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is
> already at the most recent format.
>
> Any thoughts on this one?

Read this: http://doc.bazaar-vcs.org/latest/en/upgrade-guide/index.html

[Ian Clatworthy-2]

Tata Dano wrote:
> Yeah..you are right. The remote repo is on pack-0.92 format.
>
> I have access on the remote repo so I execute:
>
> bzr upgrade (inside my repo folder) but I got this message instead:
>
> [root@xxxx xxxxxx]# bzr upgrade testdeploy/
> bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is
> already at the most recent format.

What does 'bzr version' show (when running on the server)?

Ian C.

[Tata Dano-4]

On Tue, Oct 13, 2009 at 4:29 PM, Ian Clatworthy <ian.clatworthy@...> wrote:

Tata Dano wrote:
> Yeah..you are right. The remote repo is on pack-0.92 format.
>
> I have access on the remote repo so I execute:
>
> bzr upgrade (inside my repo folder) but I got this message instead:
>
> [root@xxxx xxxxxx]# bzr upgrade testdeploy/
> bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is
> already at the most recent format.

What does 'bzr version' show (when running on the server)?

 

[root@xxxxxx xxxxxxx]# bzr version
Bazaar (bzr) 1.3.1
  Python interpreter: /usr/bin/python 2.4.3.final.0
  Python standard library: /usr/lib/python2.4
  bzrlib: /usr/lib/python2.4/site-packages/bzrlib
  Bazaar configuration: /root/.bazaar
  Bazaar log file: /root/.bzr.log

Copyright 2005, 2006, 2007, 2008 Canonical Ltd.
http://bazaar-vcs.org/

bzr comes with ABSOLUTELY NO WARRANTY.  bzr is free software, and
you may use, modify and redistribute it under the terms of the GNU
General Public License version 2 or later.

[Tata Dano-4]

On Tue, Oct 13, 2009 at 4:27 PM, Alexander Belchenko <bialix@...> wrote:

Tata Dano пишет:

Yeah..you are right. The remote repo is on pack-0.92 format.

I have access on the remote repo so I execute:

bzr upgrade (inside my repo folder) but I got this message instead:

[root@xxxx xxxxxx]# bzr upgrade testdeploy/
bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.

Any thoughts on this one?

Read this: http://doc.bazaar-vcs.org/latest/en/upgrade-guide/index.html

I read the instructions but how can this be done on CentOS machine since the tutorial and the versions is for Ubuntu only?

[Tata Dano-4]

Your local repository in 2a format (default in bzr 2.0+) but your remote repo in old format (pack-0.92 maybe). You can ask format of remote repo using command:

bzr info -v ftp://...

Upgrading local repo to 2a makes it incompatible with old (non-rich-roots) format. You should upgrade your remote repository.
E.g.

bzr upgrade ftp://...

Ensure all your coworkers using bzr 2.0 or at least 1.17-1.18, otherwise they won't access new 2a format of repo.

If ever I can't upgrade my remote repo, is it possible to downgrade the version of our workstation to fit in the format of the server?

[Alexander Belchenko]

Tata Dano пишет:

>     Your local repository in 2a format (default in bzr 2.0+) but your
>     remote repo in old format (pack-0.92 maybe). You can ask format of
>     remote repo using command:
>
>     bzr info -v ftp://...
>
>     Upgrading local repo to 2a makes it incompatible with old
>     (non-rich-roots) format. You should upgrade your remote repository.
>     E.g.
>
>     bzr upgrade ftp://...
>
>     Ensure all your coworkers using bzr 2.0 or at least 1.17-1.18,
>     otherwise they won't access new 2a format of repo.
>
>     If ever I can't upgrade my remote repo, is it possible to downgrade
>     the version of our workstation to fit in the format of the server?

Unfortunately, no.

There is not possible to downgrade 2a format to pack-0.92. You have to
start your repo from the scratch and initialize local repo in proper
format first:

bzr init --format=pack-0.92

On Tuesday 13 October 2009 10:40:07 Tata Dano wrote:

If CentOS does not provide recent bzr binary packages within their own
distribution repositories you can use the source tarballs of bzr.

  http://bazaar-vcs.org/SourceDownloads
  http://bazaar-vcs.org/InstallationFaq

You need a running python version to use the source tarballs but you
should already have one installed because the old bzr version is running
five.


Joke de Buhr


> On Tue, Oct 13, 2009 at 4:27 PM, Alexander Belchenko <bialix@...>
wrote:

> > Tata Dano пишет:
> >> Yeah..you are right. The remote repo is on pack-0.92 format.
> >>
> >> I have access on the remote repo so I execute:
> >>
> >> bzr upgrade (inside my repo folder) but I got this message instead:
> >>
> >> [root@xxxx xxxxxx]# bzr upgrade testdeploy/
> >> bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is
> >> already at the most recent format.
> >>
> >> Any thoughts on this one?
> >
> > Read this:
> > http://doc.bazaar-vcs.org/latest/en/upgrade-guide/index.html
> >
> > I read the instructions but how can this be done on CentOS machine
> > since
>
> the tutorial and the versions is for Ubuntu only?
>

[Matthew D. Fuller]

On Tue, Oct 13, 2009 at 04:42:01PM +0800 I heard the voice of
Tata Dano, and lo! it spake thus:
>
> If ever I can't upgrade my remote repo, is it possible to downgrade
> the version of our workstation to fit in the format of the server?

No, but you could move the server to a rich root capable format; then
it would work (though crossing the format boundary can be slow).
1.3.1 is new enough to support rich-root-pack.


--
Matthew Fuller     (MF4839)   |  fullermd@...
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.