Unknown branch format if line endings are modified
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Breezy |
Fix Released
|
Low
|
Jelmer Vernooij |
Bug Description
Running Bazaar 0.91 on both Linux and Windows. Linux install came from distro, Windows install from installer on the website. Created and used branches on both hosts.
Gzipped a branch on Linux and copied it to the Windows host. Bzr is unable to use this branch:
bzr: ERROR: Unknown branch format: 'Bazaar-NG meta directory, format 1\r\n'
Unix file endings are not the problem - converted line endings with gvim (on the Win32 host) - same error.
Copied to ".bzr\branch-
bzr: ERROR: Unknown branch format: 'Bazaar Branch Format 6 (bzr 0.15)\r\n'
Strangest thing is that I don't see a diff between the two "branch-format" files, but putting back the old one makes the first error return !?
Please suggest further tests - can submit gzipped branch that causes the error.
Related branches
- Martin Packman: Approve
-
Diff: 54 lines (+21/-1)3 files modifiedbreezy/bzr/__init__.py (+4/-1)
breezy/errors.py (+9/-0)
breezy/tests/test_bzrdir.py (+8/-0)
Changed in bzr: | |
status: | In Progress → Confirmed |
tags: | added: easy patch-needswork ui |
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in brz: | |
status: | Triaged → Fix Committed |
milestone: | none → 3.0.0 |
assignee: | nobody → Jelmer Vernooij (jelmer) |
Changed in brz: | |
status: | Fix Committed → Fix Released |
My bad. Line ending *is* the cause for the first error. Maybe line ending in another file is the cause for the second error?
Windows unzip utilities have a habit of converting to windows line endings :(