cscvs does not treat cr as newline

Bug #49398 reported by David Allouche
Affects Status Importance Assigned to Milestone
Launchpad CSCVS

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 :

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.

Revision history for this message
David Allouche (ddaa) wrote :

The xine-lib-head import exhibits this problem in <email address hidden>/xine-lib--MAIN--0--patch-5316.

Changed in launchpad-bazaar:
importance: Untriaged → Low
status: Unconfirmed → Confirmed
Revision history for this message
David Allouche (ddaa) wrote :

Subscribing siretart, since he asked about the xine-lib import and will likely be interested in the status of the bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers