Bazaar Version Control System

bzr: ERROR: KnitPackRepository is not compatible with CHKInventoryRepository different rich-root support - unclear what to do next

Reported by Tata Dano on 2009-10-13
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Unassigned

Bug Description

Hello,

Our remote repo is CentOS and workstations is using windows. When trying to push or pull on the remote repo this is the error I got on my Windows workstation.

bzr: ERROR: KnitPackRepository('ftp://atat%<email address hidden>/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 to address this one. Thanks a million in advance.

Andrew Bennetts (spiv) wrote :

Try this command:

    bzr upgrade --2a ftp://atat%40i360pro%<email address hidden>/testdeploy/

It appears that you've upgraded your local repository to the new format in 2.0.0, while your FTP server has a repository in either pack-0.92, 1.6 or 1.9 format. (bzr info -v can tell you exactly which if you're curious.)

See also <http://doc.bazaar-vcs.org/latest/en/upgrade-guide/index.html#data-migration>.

shaman.sir (shaman-sir) wrote :

This also affects Launchpad repositories, getting:

bzr: ERROR: RemoteRepository(...)
is not compatible with
CHKInventoryRepository(...)
different rich-root support

same to launchpad repos, you need to perform:

bzr upgrade lp:<name-of-your-repo>

and then all goes ok, even there.

Bazaar developers, please add information about it in console client and TortoiseBzr also, because it is not obvious

Daniel Hahler (blueyed) wrote :

See also bug 328146 (dupe?).

The workaround is to upgrade the stacked/target branch (AFAIU), but might not be possible, if you're not the owner of the branch..

Martin Pool (mbp) on 2010-02-17
summary: - bzr: ERROR: KnitPackRepository is not compatible with
- CHKInventoryRepository different rich-root support
+ bzr: ERROR: KnitPackRepository is not compatible with
+ CHKInventoryRepository different rich-root support - unclear what to do
+ next
Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
tags: added: formats

Hi,

I think we have the same situation before. But we are able to address this
one. During making init on the folder on a windows machine make sure that
the repository format should be pack-0.92 so that it will match on your
server repository format.

Second method would be, install a new yum.repos: (you can try that one, I
think its the latest)

rpm -Uhv
http://apt.sw.be/redhat/el5/en/i386/RPMS.rpmforge/rpmforge-release-0.5.1-1.el5.rf.i386.rpm
rpm -Uvh
http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm

- after your done with this one you can execute these commands:

yum repolist
yum update or yum update bzr (it will upgrade bazaar to version 2.0.9 which
will solved the issue you encounter)

But I could not guarantee that it will work on your situation, however it
works on mine.

Hope that helps. Thanks.

Regards,

Tata
On Wed, Feb 17, 2010 at 4:04 PM, Martin Pool <email address hidden> wrote:

> ** Summary changed:
>
> - bzr: ERROR: KnitPackRepository is not compatible with
> CHKInventoryRepository different rich-root support
> + bzr: ERROR: KnitPackRepository is not compatible with
> CHKInventoryRepository different rich-root support - unclear what to do next
>
> ** Changed in: bzr
> Importance: Undecided => Medium
>
> ** Changed in: bzr
> Status: New => Confirmed
>
> ** Tags added: formats
>
> --
> bzr: ERROR: KnitPackRepository is not compatible with
> CHKInventoryRepository different rich-root support - unclear what to do next
> https://bugs.launchpad.net/bugs/450147
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Confirmed
>
> Bug description:
> Hello,
>
> Our remote repo is CentOS and workstations is using windows. When trying to
> push or pull on the remote repo this is the error I got on my Windows
> workstation.
>
> bzr: ERROR: KnitPackRepository('ftp://atat%40i360pro.com@
> 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 to address this one. Thanks a million in advance.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bzr/+bug/450147/+subscribe
>

--
Tata Dano
http://SocialSAM.com
Linux Registered User #383849

This error happened to me when I was trying to use, in Jaunty, a branch that I modified while using Intrepid. The "bzr upgrade --2a" did not work for me. The version of bzr was 1.6. To solve it, I had to use the bzr PPA (https://edge.launchpad.net/~bzr/+archive/ppa) in order to get the 2.2.2 version.

James Hunt (jamesodhunt) wrote :
Download full text (7.1 KiB)

I have just got this error when attempting to push to a brand new branch on launchpad using a maverick client. The second attempt (worryingly) appeared(?) to work. Here is an extract from my ~/.bzr.log showing both attempts:

________________________________________________________________________

Wed 2011-02-16 09:30:32 +0000
0.034 bazaar version: 2.2.1
0.034 bzr arguments: [u'push', u'-v', u'lp:~jamesodhunt/byobu/ulevel-a11y-and-permissive-options']
0.043 looking for plugins in /home/james/.bazaar/plugins
0.047 looking for plugins in /usr/lib/python2.6/dist-packages/bzrlib/plugins
0.105 encoding stdout as sys.stdout encoding 'UTF-8'
0.133 opening working tree '/data/bzr/byobu/byobu'
0.804 ssh implementation is OpenSSH
3.907 opening working tree '/data/bzr/byobu/byobu'
8.328 Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 912, in exception_to_return_code
    return the_callable(*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 1112, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 690, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 705, in run
    return self._operation.run_simple(*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/bzrlib/cleanup.py", line 135, in run_simple
    self.cleanups, self.func, *args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/bzrlib/cleanup.py", line 165, in _do_with_cleanups
    result = func(*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/bzrlib/builtins.py", line 1161, in run
    use_existing_dir=use_existing_dir)
  File "/usr/lib/python2.6/dist-packages/bzrlib/push.py", line 90, in _show_push_branch
    create_prefix=create_prefix, use_existing_dir=use_existing_dir)
  File "/usr/lib/python2.6/dist-packages/bzrlib/branch.py", line 1393, in create_clone_on_transport
    create_prefix=create_prefix, use_existing_dir=use_existing_dir)
  File "/usr/lib/python2.6/dist-packages/bzrlib/bzrdir.py", line 288, in clone_on_transport
    make_working_trees=make_working_trees, shared_repo=want_shared)
  File "/usr/lib/python2.6/dist-packages/bzrlib/bzrdir.py", line 2072, in initialize_on_transport_ex
    make_working_trees=make_working_trees, shared_repo=shared_repo)
  File "/usr/lib/python2.6/dist-packages/bzrlib/bzrdir.py", line 3382, in initialize_on_transport_ex
    stack_on_pwd, repo_format_name, make_working_trees, shared_repo)
  File "/usr/lib/python2.6/dist-packages/bzrlib/bzrdir.py", line 3420, in _initialize_on_transport_ex_rpc
    remote._translate_error(err, path=path)
  File "/usr/lib/python2.6/dist-packages/bzrlib/remote.py", line 2934, in _translate_error
    err.error_args[1], err.error_args[2])
IncompatibleRepositories: KnitPackRepository('lp-78103504:///~kirkland/byobu/trunk/.bzr/repository')
is not compatible with
CHKInventoryRepository('lp-78103504:///~jamesodhunt/byobu/ulevel-a11y-and-permissive-options/.bzr/repository')
different serializers

8.328 Transferred: 1kB (0.1kB/s r:0kB w:0kB)
8.328 return code 3

Wed 2011-02-16 09:30:50 +0000
0.027 bazaar ve...

Read more...

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers