bzr upgrade gives a KnitCorrupt traceback when branch contains any revision with \n in filenames
Bug #274250 reported by
Mary Gardiner
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
I upgraded an Ubuntu Hardy system from bzr 1.3 (or whatever is currently default in Hardy) to the 1.7 PPA package today. I ran "bzr upgrade" on a checkout. It gave a traceback.
I will attach the traceback information here. I have a copy of the checkout captured and can supply it off-site if needed, but would prefer not to have it permanently archived forevermore by Launchpad, so will not attach it here.
Revision history for this message
| Mary Gardiner (puzzlement) wrote | #1 |
Revision history for this message
| Mary Gardiner (puzzlement) wrote | #2 |
| Changed in bzr: | |
| status: | New → Confirmed |
| tags: | added: check-for-breezy |
To post a comment you must log in.
IRC with Andrew Bennetts:
<spiv> You have newlines in filenames again, apparently.
<spiv> <file file_id=
<spiv> Oh, that's an old, unreferenced revision from your earlier problem.
<spiv> Which is harmless, except for upgrade which tries to rewrite every single revision. :(
<mary> Well, that kinda sucks.
<mary> I am hardly going to back those back out.