This is a bug we uncovered while running sanity.sh. If you look at the test rmadd-14 in sanity.sh, it is trying to do a dir level commit:

---
  dotest_fail rmadd-14 "${testcvs} -q ci -r mybranch -m add" \
"${PROG} commit: Up-to-date check failed for .file2'
${PROG} \[commit aborted\]: correct above errors first!"
---

The commit fails with an up-to-date check as file2 is not on the baranch, yet the file3 is surreptiously added to the Attic! The CVS client does not get any message to that effect. This is in violation of the normal commit behaviour of aborting the entire commit if any one of the file is not up-to-date.

The next test in the suite, rmadd-15 should not be finding the file in Attic:

-----
  dotest rmadd-15 "${testcvs} -q ci -r mybranch -m add file3" \
"RCS file: ${CVSROOT_DIRNAME}/first-dir/Attic/file3,v
done
Checking in file3;
${CVSROOT_DIRNAME}/first-dir/Attic/file3,v  <--  file3
new revision: 1\.1\.2\.1; previous revision: 1\.1
done"

---

We don't have a bug fix/patch for this yet but just want to track the issue for now.


Regards,
Rahul Bhargava,
WANdisco, Inc.
http://www.wandisco.com