bzr shelve created shelf that couldn't be restored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned | ||
Breezy |
Triaged
|
High
|
Unassigned |
Bug Description
I just ran bzr shelve on a lightweight checkout, and am now unable to restore this shelved pack a few minutes later. The exact steps were
1) Working on a lightweight checkout using a local shared repository, but bound to a remote branch (in a remote shared repository), I did a bzr add, then bzr shelve --all
2) Switched to a new remote branch... didn't do anything with this
3) Switched back to the original branch and attempted to run bzr unshelve
At this point the following error was spat back out at me:
C:\Source\
Using changes with id "1".
bzr: ERROR: bzrlib.
Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\shelf.pyo", line 401, in get_unshelver
File "bzrlib\shelf.pyo", line 321, in from_tree_and_shelf
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
NoSuchRevision: CHKInventoryRep
bzr 2.1.2 on python 2.5.4 (Windows-
arguments: ['bzr', 'unshelve']
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
bzrtools C:\Program Files\Bazaar\
explorer C:\Program Files\Bazaar\
launchpad C:\Program Files\Bazaar\
netrc_
qbzr C:\Program Files\Bazaar\
rebase C:\Program Files\Bazaar\
svn C:\Program Files\Bazaar\
upload C:\Program Files\Bazaar\
xmloutput C:\Program Files\Bazaar\
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
including this traceback and a description of the problem.
I've attached the shelf file for perusal. I would like this to remain a non-public bug for now though as the actual bundle itself contains some possibly sensitive material... though if I can find reproduction steps I will happily re-raise this in a new public bug.
I haven't tested for reproducibility yet... I have found this setup (as in multiple shared repo's) is causing some other issues though (I use bzr-svn, and have been bitten by quite a few bugs in the last few months... potentially the repo itself is in an inconsistent state somehow).
visibility: | private → public |
tags: | added: missing-inventory shelf |
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → High |
Ok... it *appears* as if the local shared repository missed out on a revision that was pushed to the remote branch. I ran a bzr up in the lightweight checkout, and this pulled in an extra revision that was present in the remote branch (and the remote shared repo), but not the local branch. I wonder if this is an issue in wider bzr potentially...