RCS problems

I ran into problems with RCS refusing to check in a new version of a
binary file, apparently when RCS attempted to do a diff against the
old version (I cannot remember the exact error message now). A search of
the newsgroups suggested using uuencode to convert binary files to ASCII
before archiving, so this is what I’ve been doing.

But now I’ve encountered a new problem checking in the uuencoded file:

ci: ,v: backward insertion in diff output: a581 25
ci aborted

We really need some way of using RCS to archive binary files.
Any suggestions would be appreciated.

At one time, you required a version of the “diff” util that supported
binary files because the shipped “diff” didn’t do this.

Will Parsons <wbp@alfa.eng.sun.com> wrote:

I ran into problems with RCS refusing to check in a new version of a
binary file, apparently when RCS attempted to do a diff against the
old version (I cannot remember the exact error message now). A search of
the newsgroups suggested using uuencode to convert binary files to ASCII
before archiving, so this is what I’ve been doing.

But now I’ve encountered a new problem checking in the uuencoded file:

ci: ,v: backward insertion in diff output: a581 25
ci aborted

We really need some way of using RCS to archive binary files.
Any suggestions would be appreciated.


Kirk Russell Bridlewood Software Testers Guild

What version of rcs do you have?
“rcs -V” will give you the version number.
Mine says “RCS version 5.7” and the rcs files are dated 1996.

I have been checking in/out binary files for several years now.
I know that back in 1995 we were also encoding/decoding but when we started
using it more in 1999 it was no longer necessary.

ms…




“kirk” <kirussel@NOSPAMrogers.com> wrote in message
news:agacnk$qrs$1@inn.qnx.com

At one time, you required a version of the “diff” util that supported
binary files because the shipped “diff” didn’t do this.

Will Parsons <> wbp@alfa.eng.sun.com> > wrote:
I ran into problems with RCS refusing to check in a new version of a
binary file, apparently when RCS attempted to do a diff against the
old version (I cannot remember the exact error message now). A search
of
the newsgroups suggested using uuencode to convert binary files to ASCII
before archiving, so this is what I’ve been doing.

But now I’ve encountered a new problem checking in the uuencoded file:

ci: ,v: backward insertion in diff output: a581 25
ci aborted

We really need some way of using RCS to archive binary files.
Any suggestions would be appreciated.


Kirk Russell Bridlewood Software Testers Guild

RCS is version 5.7 and is also dated 1996. The original error message
attempting to check rev. 1.2 of a binary file was:

ci: ,v: unexpected EOF in diff output
ci aborted

The file was a Photon abapp.dfn file, FWIW.

Mike Schneider <Mike.Schneider@us.heidelberg.com> wrote:

What version of rcs do you have?
“rcs -V” will give you the version number.
Mine says “RCS version 5.7” and the rcs files are dated 1996.

I have been checking in/out binary files for several years now.
I know that back in 1995 we were also encoding/decoding but when we started
using it more in 1999 it was no longer necessary.

ms…




“kirk” <> kirussel@NOSPAMrogers.com> > wrote in message
news:agacnk$qrs$> 1@inn.qnx.com> …
At one time, you required a version of the “diff” util that supported
binary files because the shipped “diff” didn’t do this.

Will Parsons <> wbp@alfa.eng.sun.com> > wrote:
I ran into problems with RCS refusing to check in a new version of a
binary file, apparently when RCS attempted to do a diff against the
old version (I cannot remember the exact error message now). A search
of
the newsgroups suggested using uuencode to convert binary files to ASCII
before archiving, so this is what I’ve been doing.

But now I’ve encountered a new problem checking in the uuencoded file:

ci: ,v: backward insertion in diff output: a581 25
ci aborted

We really need some way of using RCS to archive binary files.
Any suggestions would be appreciated.

kirk <kirussel@NOSPAMrogers.com> wrote:

At one time, you required a version of the “diff” util that supported
binary files because the shipped “diff” didn’t do this.

Does RCS use an external diff program? There seems to be an rcsdiff
utility in /usr/bin.

Will Parsons <> wbp@alfa.eng.sun.com> > wrote:
I ran into problems with RCS refusing to check in a new version of a
binary file, apparently when RCS attempted to do a diff against the
old version (I cannot remember the exact error message now). A search of
the newsgroups suggested using uuencode to convert binary files to ASCII
before archiving, so this is what I’ve been doing.

But now I’ve encountered a new problem checking in the uuencoded file:

ci: ,v: backward insertion in diff output: a581 25
ci aborted

We really need some way of using RCS to archive binary files.
Any suggestions would be appreciated.