cscvs does not treat cr as newline
Bug #49398 reported by
David Allouche
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad CSCVS |
Triaged
|
Low
|
Unassigned | ||
Bug Description
There are some broken cvs commit log out there where \r is used as a line separator. cscvs should be smarter in handling those.
Revision history for this message
| David Allouche (ddaa) wrote | #1 |
Revision history for this message
| David Allouche (ddaa) wrote | #2 |
| Changed in launchpad-bazaar: | |
| importance: | Untriaged → Low |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| David Allouche (ddaa) wrote | #3 |
To post a comment you must log in.
That has unfortunate interaction with the Arch patchlog format, as those \r can end up in the Summary: header, and parsed as line separators by the email parser used by pybaz.Revision, and can cause CSCVSID and other metadata not to be parsed as headers.
Affected imports cannot be fixed without bumping the namespace version of baz-import.
Native bzr imports will be more resilient to this problem, but should still process log messages to convert "\r\n" and "\r" to "\n", because single \r characters are interpreted by terminal emulators and cause surprising display problems.