Bazaar

bzr info fails in lightweight checkout when master branch not found

Bug #86653 reported by Alexander Belchenko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned
Breezy
Triaged
Medium
Unassigned

Bug Description

I copy my devel tree from one machine to another. On one machine my tree resides on drive D:, but on another it's on drive C:. But relative paths between branches stay the same.

I have lightweight checkout. After copying branches master branch of lightweight checkout resides by another full path, but on the same relative path. Any operations with checkout ends with NotBranchError. The worst part is command 'info' also fails with the same error.

C:\work\Bazaar\plugins.work\bzr-gtk.bialix>bzr info
bzr: ERROR: Not a branch: D:/Bazaar/bzr-gtk/bzr-gtk.win32.bialix/

I think 'bzr info' should be more robust against disappearing of master branch and say something reasonable to user in this situation.

See original description
Tags: easy info
Alexander Belchenko (bialix)
description: updated
Revision history for this message
Matthieu Moy (matthieu-moy) wrote :

I have the same problem.

Alexander Belchenko (bialix)
Changed in bzr:
status: New → Confirmed
James Westby (james-w)
Changed in bzr:
importance: Undecided → Medium
Andrew Bennetts (spiv)
tags: added: easy
Revision history for this message
Neil Martinsen-Burrell (nmb) wrote :

I am unable to reproduce this bug on Mac OS X:

nmb@guttle[~/tmp]$ mkdir -p test/branch
nmb@guttle[~/tmp]$ cd test
nmb@guttle[~/tmp/test]$ bzr init branch
Created a standalone tree (format: 2a)
nmb@guttle[~/tmp/test]$ bzr co --lightweight co
bzr: ERROR: Not a branch: "/Users/nmb/tmp/test/co/".
nmb@guttle[~/tmp/test]$ bzr co --lightweight branch co
nmb@guttle[~/tmp/test]$ ls
branch/ co/
nmb@guttle[~/tmp/test]$ mv co ..
nmb@guttle[~/tmp/test]$ cd ../co
nmb@guttle[~/tmp/co]$ bzr info
Lightweight checkout (format: 2a)
Location:
  light checkout root: .
   checkout of branch: /Users/nmb/tmp/test/branch

Is this something that only happens on win32 or am I misunderstanding the relevance of the drive letters here?

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 86653] Re: bzr info fails in lightweight checkout when master branch not found

Neil Martinsen-Burrell пишет:
> I am unable to reproduce this bug on Mac OS X:
>
> nmb@guttle[~/tmp]$ mkdir -p test/branch
> nmb@guttle[~/tmp]$ cd test
> nmb@guttle[~/tmp/test]$ bzr init branch
> Created a standalone tree (format: 2a)
> nmb@guttle[~/tmp/test]$ bzr co --lightweight co
> bzr: ERROR: Not a branch: "/Users/nmb/tmp/test/co/".
> nmb@guttle[~/tmp/test]$ bzr co --lightweight branch co
> nmb@guttle[~/tmp/test]$ ls
> branch/ co/
> nmb@guttle[~/tmp/test]$ mv co ..
> nmb@guttle[~/tmp/test]$ cd ../co
> nmb@guttle[~/tmp/co]$ bzr info
> Lightweight checkout (format: 2a)
> Location:
> light checkout root: .
> checkout of branch: /Users/nmb/tmp/test/branch
>
> Is this something that only happens on win32 or am I misunderstanding
> the relevance of the drive letters here?

And now rename the "branch" to "new-branch" and run `bzr info co` again.

--
All the dude wanted was his rug back

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

The initial description could be a bit unclear.

I've moved from one drive to another both branch and checkout. They
still at the same relative positions, but absolute path is of course
different. Therefore checkout no more can find the branch and
everything fail.

Neil, you're awar eof this problem, and in bzr-colo you have
implemented colo-fixup as workaround for it.

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: removed: check-for-breezy
Changed in brz:
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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