RCS related error migrating content from Twiki 4.2.3(RcsLite) to Foswiki VM

After finishing setup of the Foswiki VM, I began to migrate content from TWiki 4.2.3 on Windows (using RcsLite).

I copied my user topics into the Main web and a handful of topics (*.txt and *.txt,v) into a newly created web.

I ran chown -R www-data:www-data * on both web directories, and set the permissions of the *.txt,v files to 0444

I then edited my user topic.

This (on save) created the following:

Foswiki detected an internal error - please check your Foswiki logs and webserver logs for more information.

path -r%REVISION|N% %FILENAME|F% of ...path failed:
RCS file: path,v
Working file: CraigBowers.txt
head: 1.4
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 1
description:

I deleted the CraigBowers.txt,v file and my User topic rendered correctly again.

I then created a link in my user topic to a not yet created topic in the newly created web with some topics already migrated in.

After hitting save on my user topic, I got the above error again but this time it referenced one of the files in the other web.

I would delete that matching .txt,v file and another error as above would result, referencing the next recently added topic. Only after deleting all the other .txt,v files that were copied in from windows would topics render correctly again.

Does this, and the mention of: http://foswiki.org/Tasks/Item3212 indicate that my RcsLite files are incompatible with Foswiki and Rcs, or is there some work-around?

---

For reference, I created the same simple 3 line topic in both instances and saved it.

Went back in and deleted the middle line, and added a final line.

The contents of each Rcs file will be listed below.

But dragging this topic pair from the windows sandbox to the Foswiki VM sandbox (and setting matching ownership and permissions) allowed to be viewed, but on save after an edit gave:

Attention

Error saving topic

During save of SandboxTestTopic101 an error was found by the version control system.

/usr/bin/ci  -m%COMMENT|U% -t-none -w%USERNAME|S% -u %FILENAME|F% of .../Trash/SandboxTestTopic101.txt failed: 
 

---

SandboxTestTopic101.txt,v (from Windows TWiki 4.2.3)

head 1.1;
access ;
symbols;
locks; strict;
comment @@;

1.1
date 2009.01.25.18.24.55; author CraigBowers; state Exp;
branches;
next ;


desc
@@


1.1
log
@@
text
@%META:TOPICINFO{author="CraigBowers" date="1232907895" format="1.1" reprev="1.1" version="1.1"}%
Content Line 1

Content Line 3

Deleted Line 2, added supplemental line.
@

<--- Concluding LF here

TestTopic1.txt,v (from Foswiki VM)

head 1.1;
access;
symbols;
locks; strict;
comment @# @;


1.1
date 2009.01.25.12.50.25; author CraigBowers; state Exp;
branches;
next ;


desc
@none
@


1.1
log
@none
@
text
@%META:TOPICINFO{author="CraigBowers" date="1232887825" format="1.1" reprev="1.1" version="1.1"}%
Content Line 1

Content Line 3

Deleted Line 2, added supplemental line.
@

---

Further update: I can't find full documentation for the RCS file format but it does appear obvious that @@ is an escaped @ where @ literally occurs in the content. That's not the case in this topic. Breaking up the pair of @@ in the manner as the Foswiki VM does, unbreaks the display of the Topic in the Foswiki VM. Perhaps a search and replace on the *.txt,v files can be done but I yield to someone who can shed more light on the Rcs file format and the proper fix.

---

damn. a bug in RcsLite when moving from Windows to UNIX :/ Hopefully we can add a unit test for this.

-- SvenDowideit - 25 Jan 2009

I just recently have switched back from RcsLite to RcsWrap and can confirm the massive problems as outlined above. I have been using RcsLite for a very long time now as it is the primary choice when running perl accelerators. Alas, now it seems as if all these revision files are broken.

-- MichaelDaum - 26 Jan 2009

Bit of additional information. I ran into the same problem with data files from a pre-release CVS build of Foswiki migrated to a Foswiki VM. Splitting the @@'s into @none\r@ fixed part of the problem. I also ended up having to delete blank lines before the @ separator at the end of what I'll call the "section diffs", for lack of familiarity with RCS naming conventions. Sections that did not have a deletion at the end appeared to require this treatment.

-- LandisVinchattle - 17 Feb 2009

AFAICS you are wrong about the @@ part. The @@ are used to quote the content, ie. see them as "content" type of delimiters. @@ means the content is empty, if there is a content (except for the comment string, which has no newline), then \n@ starts the content and @\n ends it. If @ appears inside the content, then it is doubled. For example

no description, valid RCS

desc
@@

some log message

log
@this is my log message
@

and some real content

text
@first line
some email@@address.com
last line
@

So your example from above is a valid RCS, but there could be a CRLF mixup. Could you please mail me a couple of .txt and .txt,v files from your windows installtion inside a ZIP archive (so no CRLF munging is done). You can reach me at uspoerlein at gmail dot com.

-- UlrichSpoerlein - 04 Apr 2009