bzr status with a revision range requires a working tree

Bug #392391 reported by Colin D Bennett
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned

Bug Description

In a shared repository without trees, ‘bzr status’ fails even when given a revision range.

$ bzr st -c 5284
bzr: ERROR: No WorkingTree exists for "file:///home/cdb/Code/sdcc/repo/sdcc/trunk/.bzr/checkout/".

Both ‘bzr st -c X’ and ‘bzr st -r X..Y’ fail.

I think this used to work. I'm using Bazaar 1.16.

Martin Pool (mbp)
Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Paul Pelzl (pelzlpj) wrote :

The bug is still present in bzr 2.1.1.

Jelmer Vernooij (jelmer)
tags: added: status
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
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.