misc/131774: cvs - commits files then aborts

[TerryP]

>Number:         131774
>Category:       misc
>Synopsis:       cvs - commits files then aborts
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 17 11:40:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     TerryP
>Release:        RELENG_7
>Organization:
>Environment:
FreeBSD dixie.launchmodem.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Mon Jan  5 00:42:11 UTC 2009     root at dixie.launchmodem.com:/usr/obj/usr/src/sys/VIPER  i386

>Description:
When committing files with CVS, if I specify a log file for the commit command; it splits out a bogus abort message after the commit has completed.

Here is an example of the output:

Terry at dixie$ cat > /tmp/log                                               11:35
superficial commit for problem-report
Terry at dixie$ cvs commit -F /tmp/cvs-ci.8K04g33j
cvs commit: Examining . 
  ... snip ...
?   ... snip ...
Checking in .Terry_shrc;
/srv/cvs/Terry/.Terry_shrc,v  <--  .Terry_shrc
new revision: 1.27; previous revision: 1.26
done
Checking in .vimrc;
/srv/cvs/Terry/.vimrc,v  <--  .vimrc
new revision: 1.40; previous revision: 1.39
done
cvs [commit aborted]: cannot specify both a message and a log file
Terry at dixie$

Afterwords, the commit message can be reviewed with cvs log, changes viewed with cvs diff, checkout/update the file from other machines, etc as normal. It just acts like a moron if you say -F file.


>From cvs --version:

Concurrent Versions System (CVS) 1.11.22.1-FreeBSD (client/server)
>How-To-Repeat:
$ echo some message > logfile
$ cvs ci -F logfile
$ cvs log

You should see that it was "done", followed by a "commit aborted" message during the commit. The data was really committed, so you can view it in the log and so on.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: