bzr seems to bugs when commiting. (exceptions.ValueError: math domain error)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned |
Bug Description
Hi!
I’m recently encoutering some problems with bazaar when commiting.
It’s the second it bugs when typing “bzr ci”.
I’ve haven’t add or remove files yet, just modify some of my files already commited.
In the attached file is the traceback of Bazaar.
After the bug, I type “bzr diff”. It seems that all were as if the commit wasn’t done: it show differences.
But when typing “bzr visualise”, it seems as if it has been committed: the changes appears in the tree. (Which is more a line for me than a tree… I’m alone in my project now.)
Then, when retyping “bzr ci”, I get the following message: (The first and the second time)
“bzr: ERROR: Working tree is out of date, please run 'bzr update'.”
Typing “bzr update” works well.
After that, “bzr diff” show no differences.
I’ve recently go back in my project using “bzr revert -r <number>”, without saving my changes (in fact I’ve made a mistake using sed and all my files were empty…) to go have my files restored.
Maybe it’s that…
Hoping it will be helpful.
Martin.