Fwd: possible bug (rcs, version 5.9, occurs on Debian 7)
Bostjan Vilfan <[email protected]> Fri, 31 Jan 2014 08:51:11 +0100
| Newsgroups | gmane.comp.version-control.rcs.bugs |
|---|---|
| Message-ID | <CAAm34zraMYiSgdX7Y+g9ad-MQnEibrz3K=sj-eQcWwhktAFk7w@mail.gmail.com> |
Sorry, forgot to include the example ---------- Forwarded message ---------- From: Bostjan Vilfan <[email protected]> Date: Fri, Jan 31, 2014 at 8:47 AM Subject: possible bug (rcs, version 5.9, occurs on Debian 7) To: [email protected] I've already sent this to the help-rcs mail list; but haven't received an answer. I am resending it here with some additional information. The example contains one directory, src, with a working file In.cpp, and an RCS subdirectory containing one rcs archive file In.cpp,v. When the command ci In.cpp is executed, a message is generated, file is unchanged; reverting to previous revision 1.7.1.1 following which another message is generated, Aborted and an empty file, ",In.cpp,v,", appears in the RCS subdirectory. I haven't been able to find anything wrong with the In.cpp,v file, and because of that it is probable that a bug in involved. I note that I have observed a similar outcome on other occasions (i.e. when attempting to check in an unchanged file). Note: Before trying the command "ci In.cpp", the user must execute "rcs -l1.7.1.1 In.cpp" to break the current lock of revision 1.7.1.1 and create a new one. Regards, bostjanv
rcsexample.zip
(application/zip, 2.9 KB) - not displayed