branching from rich-root to non-rich-root gives confusing errors

Bug #172360 reported by Alexander Belchenko
4
Affects Status Importance Assigned to Milestone
Bazaar
Expired
Medium
Unassigned

Bug Description

C:\work\Bazaar\plugins-repo>bzr get http://people.samba.org/bzr/jelmer/bzr-rebase/trunk rebase
bzr: ERROR: Repository KnitPackRepository(u'file:///C:/work/Bazaar/plugins-repo/.bzr/repository/') is not compatible
 with repository KnitRepository('http://people.samba.org/bzr/jelmer/bzr-rebase/.bzr/repository/')

C:\work\Bazaar\plugins-repo>bzr -Derror get http://people.samba.org/bzr/jelmer/bzr-rebase/trunk rebase
bzr: ERROR: bzrlib.errors.IncompatibleRepositories: Repository KnitPackRepository(u'file:///C:/work/Bazaar/plugins-r
epo/.bzr/repository/') is not compatible with repository KnitRepository('http://people.samba.org/bzr/jelmer/bzr-reba
se/.bzr/repository/')

Traceback (most recent call last):
  File "bzrlib\commands.pyc", line 802, in run_bzr_catch_errors
  File "bzrlib\commands.pyc", line 758, in run_bzr
  File "bzrlib\commands.pyc", line 492, in run_argv_aliases
  File "bzrlib\builtins.pyc", line 893, in run
  File "bzrlib\bzrdir.pyc", line 828, in sprout
  File "bzrlib\repository.pyc", line 860, in fetch
IncompatibleRepositories: Repository KnitPackRepository(u'file:///C:/work/Bazaar/plugins-repo/.bzr/repository/') is
not compatible with repository KnitRepository('http://people.samba.org/bzr/jelmer/bzr-rebase/.bzr/repository/')

bzr 0.92.0 on python 2.5.1.final.0 (win32)
arguments: ['C:\\Program Files\\Bazaar\\bzr.EXE', '-Derror', 'get', 'http://people.samba.org/bzr/jelmer/bzr-rebase/t
runk', 'rebase']
encoding: 'cp1251', fsenc: 'mbcs', lang: 'ru'
plugins:
  bzrtools C:\work\Bazaar\plugins-repo\bzrtools [0.92.1]
  depend C:\work\Bazaar\plugins-repo\depend [unknown]
  gzipped_bundle C:\work\Bazaar\plugins-repo\gzipped_bundle [unknown]
  heads C:\work\Bazaar\plugins-repo\heads [unknown]
  launchpad C:\Program Files\Bazaar\lib\library.zip\bzrlib\plugins\launchpad [unknown]
  multiparent C:\Program Files\Bazaar\lib\library.zip\bzrlib\plugins\multiparent.pyc [unknown]
  qbzr C:\work\Bazaar\plugins-repo\qbzr [0.8.0dev0]
  repo_push C:\work\Bazaar\plugins-repo\repo_push [1.1.0]
  win32symlinks C:\work\Bazaar\plugins-repo\win32symlinks [0.92.0]
  x_bit C:\work\Bazaar\plugins-repo\x_bit [unknown]

** Please send this report to <email address hidden>
   with a description of what you were doing when the
   error occurred.

Tags: ui
Revision history for this message
Alexander Belchenko (bialix) wrote :

bzr init + bzr pull is also does not work.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 172360] bzr 0.92 unable to branch from knit repo to pack repo

On Tue, 2007-11-27 at 16:45 +0000, Alexander Belchenko wrote:
> Public bug reported:
>
> C:\work\Bazaar\plugins-repo>bzr get http://people.samba.org/bzr/jelmer/bzr-rebase/trunk rebase
> bzr: ERROR: Repository KnitPackRepository(u'file:///C:/work/Bazaar/plugins-repo/.bzr/repository/') is not compatible
> with repository KnitRepository('http://people.samba.org/bzr/jelmer/bzr-rebase/.bzr/repository/')
>
> C:\work\Bazaar\plugins-repo>bzr -Derror get http://people.samba.org/bzr/jelmer/bzr-rebase/trunk rebase
> bzr: ERROR: bzrlib.errors.IncompatibleRepositories: Repository KnitPackRepository(u'file:///C:/work/Bazaar/plugins-r
> epo/.bzr/repository/') is not compatible with repository KnitRepository('http://people.samba.org/bzr/jelmer/bzr-reba
> se/.bzr/repository/')

I think this is a display problem. I bet that bzr-rebase is in a Format3
repository - with rich roots.

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

Revision history for this message
Vincent Ladeuil (vila) wrote : Re: bzr 0.92 unable to branch from knit repo to pack repo

Is this still valid ?

Changed in bzr:
status: New → Incomplete
Changed in bzr:
status: Incomplete → Invalid
Revision history for this message
John A Meinel (jameinel) wrote :

Well, you still can't fetch from a RichRoot into a non-rich root. But that is by design (Won't Fix).

At present the result is:

$ bzr init --rich-root source
$ bzr init --pack-0.92 target
$ bzr commit -m "unchanged" --unchanged source
$ cd target
$ bzr pull ../source
Format <RepositoryFormatKnit4> for file:///.../source/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
bzr: ERROR: KnitPackRepository('file:///.../target/.bzr/repository/')
is not compatible with
KnitRepository('file:///.../source/.bzr/repository/')
different rich-root support

So we don't actually give the fact that the source has rich roots and the target does not, but we *do* tell the user that there is a rich-root incompatibility. Is that sufficient?

Changed in bzr:
importance: Undecided → Medium
Jelmer Vernooij (jelmer)
Changed in bzr:
status: Invalid → Triaged
Revision history for this message
Robert Collins (lifeless) wrote :

Jelmer, this should be 'wont fix' according to the history - if marking something contrary to its log or that is otherwise ambiguous please include some rationale :)

Changed in bzr:
status: Triaged → Incomplete
Revision history for this message
Robert Collins (lifeless) wrote :

Oh also, the 'bzr' project does not use 'Triaged' as per our HACKING guidelines.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Ok, fair enough.

The error message is still confusing for people who are not familiar with rich roots, it should probably refer to whatever docs there are about rich roots and perhaps mention "bzr upgrade".

Revision history for this message
Eduardo Mucelli Rezende Oliveira (eduardo-mucelli) wrote :

This error happened to me when I was trying to use, in Jaunty, a branch that I modified while using Intrepid. 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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Bazaar because there has been no activity for 60 days.]

Changed in bzr:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.