Understood. Here is the output of 'cvs -f -d cvsroot version' with an
invalid repository path:
$ cvs -f -d username@cvshost:/invalid/path version; echo $?
Client: Concurrent Versions System (CVS) 1.12.13 (client/server)
Server: Cannot access /invalid/path/CVSROOT
No such file or directory
1
Thanks for the info. We'll get this fixed for the next releases.
-David
On Thu, May 15, 2014 at 9:03 AM, Jason Woodrich jwoodr...@gmail.com wrote:
Understood. Here is the output of 'cvs -f -d cvsroot version' with an
invalid repository path:
$ cvs -f -d username@cvshost:/invalid/path
Greetings,
I'm had a problem with adding a CVS repository running on CVS 1.11. I'm
accessing it using ssh with a key and my CVSROOT is valid. When I click
Save on the Add Repository page it returns the message A repository was
not found at the specified path. This is on CentOS 6 with both
Jason,
Thanks for the report. Would you mind filing a bug on our issue tracker?
https://code.google.com/p/reviewboard/issues/entry
-David
On Wed, May 14, 2014 at 2:05 PM, Jason Woodrich jwoodr...@gmail.com wrote:
Greetings,
I'm had a problem with adding a CVS repository running on CVS
Actually, one question, too.
Does 'cvs -f -d cvsroot version' actually check that the cvsroot is
valid, or does it just check that the local cvs binary runs? The goal of
this method is to verify the remote repository.
-David
On Wed, May 14, 2014 at 2:05 PM, Jason Woodrich jwoodr...@gmail.com
