Recovering from bad --fixes information

Glenn Morris rgm at gnu.org
Fri Dec 28 19:49:08 UTC 2012


Hi,

(Sorry, this is one of those "how do I fix my repository" mails.)
I accidentally did the equivalent of

bzr commit --fixes "123
"

That is, had a newline in the --fixes argument.
Bzr accepted this commit no problem, but now "bzr log" fails with:

bzr: ERROR: Invalid line in bugs property: 'http://debbugs.gnu.org/123'

I made a bug report, because it seems like bzr should not let me get
into this situation:
https://bugs.launchpad.net/bzr/+bug/1094180

But is there any way to recover from this?
Ideally, I just want to edit the --fixes information from the bad
commit.

In tests, bzr uncommit seems to work (there have been a few other
commits since, so I would have to undo and redo those too).
But this is a public repository that people have already pulled from, so
I'm unsure what the consequences will be for people who have already got
the bad commit. It seems like bound branches will be fine, and unbound
branches must use "pull --overwrite"?

Or would it be better to leave it alone?

TIA for any help.

(Sorry for posting so soon after making a bug report, but of course the
longer I leave this, the worse it gets.)



More information about the bazaar mailing list