All plans are unable to retrieve changelogs for the files that changed.

The bamboo.log shows:
—
2007-03-13 00:05:50,943 INFO [BAM::BuildChangeDetector] [CVSRepository] Found 6 changes from update
2007-03-13 00:05:50,986 INFO [BAM::BuildChangeDetector] [CVSRepository] Running CVS log command: "log -N -r -d>2007-03-12 17:55:32 build-macros.xml AtomicLazyReference.java DefaultThreadFactory.java DefaultMessageID.java AbstractSecurityToken.java FakeProxyServer.java "
2007-03-13 00:05:50,987 INFO [BAM::BuildChangeDetector] [CVSRepository] ... in: "/spare/bamboo/data/xml-data/build-dir/LW-COMPILE/limewire"
2007-03-13 00:05:53,154 INFO [BAM::BuildChangeDetector] [CVSRepository] Found 0 changes sets in the change logs
2007-03-13 00:05:53,154 INFO [BAM::BuildChangeDetector] [CVSRepository] something wrong with the change logs, so lets work out what's changed...
—

A little bit of detective work (by running the command and similar commands on the commandline) shows the following problems:

1) None of the files include their directories, which leads to the server knowing nothing about the files.
2) The date & time are not quoted, which leads to the server printing out a change on the given date, not at the given time. It also causes the server to look for a change in a file whose name is the time.
3) The '>' is not escaped, which on the commandline caused the result to be piped to a file whose name was the date. (I don't know if this effects the process the CVS command is run in.)
4) The '-r' parameter is used, which leads to only a single revision being shown. This effectively hides any earlier commit messages on files that were updated twice between builds.

This is a huge problem. Any help would be greatly appreciated.