[cvsnt] BUG: Corrupted binary files

[David Somers]

> First and foremost, thanks for the reply :-) I thought the thread was not
> being followed!

:-)

> I tried to look up this version in the site but there is no documentation
> about it. OTOH I found it in the archive.

The cvsnt documentation is, um, a bit lacking.

If I get some spare time I might get around to writing a book (more tutorial
than reference) on cvsnt.

> - What files are affected?

When you did an import over an existing file, as the rcs file was rewritten
the -k got corrupted.

> If the kopt line was corrupted by the erroneous entry, was this the *only*
> thing that happened to the file or was it also losing some data from the
> binary part of the versions?

Possibly not.. since -k would be sticky after the initial import, so it
might not screw up binaries... but I could be wrong... that import.cpp code
is horrible to follow.

> - Does anyone have some macro to finds the corupted files repo?

fgrep is your friend.

> - Better still is there a macro that fixes the files?

I don't think so. What you would possibly have to do is pick up the last
valid -k opton and force that into subsequent invalid revisions. Tony might
have some other/better ideas.

Remember its a development release and not yet stable, so expect a few
hiccups along the way. (Build 1998 seems quite stable: YMMV).

Greetings from Luxembourg,

David