Unexpected error message about inconsistent delta .
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When working with bazaar, I encountered the following message:
bzr: ERROR: An inconsistent delta was supplied involving 'W/De Wit/Natuur en Menschen in Indi\xc3\
back.jpg', 'back.jpg-
reason: working tree does not contain new entry
Running bzr update did revert the repository in a working conditions without further apparent issues. The image file involved appeared correct.
Attaching bzr-log and commands entered around this issue on the command line.
Maybe related to #256409
Version:
Bazaar (bzr) 1.10
Python interpreter: F:\Programs\
Python standard library: F:\Programs\
bzrlib: F:\Programs\
Bazaar configuration: C:\Documents and Settings\
Bazaar log file: D:\Jeroen\.bzr.log
23.141 Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
I also was hit by this bug today after committing two "bzr mv --after". This is the output:
$ bzr commit -m "Renames" removed# ####### ## 20091008002321- byp80pau7xm2131 1-3' 6.28-15- generic- x86_64- with-Ubuntu- 9.04-jaunty python2. 6/dist- packages/ bzrlib .bazaar .bzr.log
Committing to: #######
renamed Übung 1 => Übung 1 - Sinus-Plot mint Qwt
renamed Übung 2 => Übung 2 - Harmonischer Oszillator mit Runge Kutta und GnuPlot
bzr: ERROR: An inconsistent delta was supplied involving '\xc3\x9cbung 1 - Sinus-Plot mint Qwt1/main.cpp', 'main.cpp-
reason: working tree does not contain new entry
$ bzr --version
Bazaar (bzr) 2.0.0
Python interpreter: /usr/bin/python 2.6.2
Python standard library: /usr/lib/python2.6
Platform: Linux-2.
bzrlib: /usr/lib/
Bazaar configuration: /home/tschaboo/
Bazaar log file: /home/tschaboo/
Since I don't know in which state my repository is now, and it doesn't contain a lot of revisions, I will keep a copy of the directory as is (in case you need any more information) and will start afresh with a new repository from the current working tree.
It makes me feel a little bit uncomfortable, that this bug has not got a single comment although it was reported more than half a year ago. I switched to bzr 2.0.0 only recently, using the version included in Ubuntu Jaunty before.