Which say this:
Submit new documentation | View Documentation | Admin
If you are extending SQLUnit, it makes sense to use the code in CVS rather than what was supplied with the latest release. While there should not be much difference, since we release code changes fairly rapidly, having the CVS tree locally allows you to build patch files easily, which is very helpful. The instructions assume a *nix client (Windows users can use Cygwin or adapt the instructions).
$ export CVSROOT=:pserver:anonymous@cvs.sourceforge.net:/cvsroot/sqlunit
$ cvs login
CVS Password: <enter your email address here>
$ cvs -z3 checkout sqlunit
$ cvs logout
Now, I am running on windows, but I do have access to other sourceforge projects (with developer rights).
When I try the above instructions:
cvs login
Logging in to :pserver:anonymous@cvs.sourceforge.net:2401/cvsroot/sqlunit
CVS password:
cvs login: authorization failed: server cvs.sourceforge.net rejected access to /
cvsroot/sqlunit for user anonymous
The instructions say:
CVS Password: <enter your email address here>
What email address?
My personal email address
My sourceforge email address (ie bob@sourceforge.net)
Or just "bob" assumig sourceforge..
I have tried all of the above, never changing my CVSROOT from what was specified, but I never have any luck.
Thanks,
Dave
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right, the anonymous login seems to have stopped working... here is what I had to do to download the code from an user other than the one I normally use for SQLUnit.
export CVSROOT=:pserver:spal@cvs.sourceforge.net/cvsroot/sqlunit
cvs login<enter>
Enter my sourceforge password when prompted
cvs checkout sqlunit
and it worked fine. (You can use -z3 for compression so your download is faster). I have updated the FAQ with the new information.
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have seen the "read lock failed" from sourceforge's CVS server before. It appears to be intermittent and a possible cause is overload. Retrying a couple of times usually does it.
So anonymous works too. That is surprising, I thought I tried it the last time and it did not work the last time I tried it.
Oh, well, I guess I will update the FAQ to try anonymous as well. Thanks for checking it out.
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I dont think it is a CVS hiccup, since I have tried a million times and have never managed to get access using my id. Where as, the same configuration works for the other sourceforge projects I am on.
I googled around and found this response:
-------------------------
If a user wants any kind of access at all - even read-only access - to a given subdirectory of the repository, she usually needs file system-level write permission to that subdirectory. This is necessary because CVS creates temporary lock files in the repository to ensure data consistency. Even read-only operations (such as checkout or update) create locks, to signal that they need the data to stay in one state until they're done.
As noted in Repository Administration, you can get around this writeability requirement by setting the LockDir parameter in CVSROOT/config, like this:
LockDir=/usr/local/cvslocks
Of course, then you would need to make sure the directory /usr/local/cvslocks is writeable by all CVS users. Either way, most CVS operations, including read-only ones, are going to require a writeable directory somewhere. By default, that directory is the project's repository; if you're very security conscious, you can change it to be somewhere else.
-------------------------
Would you be able to verify any of this?
Thanks,
Dave
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will check this, right after I finish putting in Mario's new tags. Although Mario's code will fit right in, he has done some refactoring which I want to apply to some of the other tags as well, to make the source more consistent. I am doing this, should be done by end of the week.
We can then try making changes to CVSROOT with your existing privileges and then with developer access, so we can work out and fix the cvs problems we are having.
Thanks
Sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I went through the docs again (updated the FAQ entry with the link, as well as some more info about developer access that I happened to re-learn) and it says for non-project team access, you need to use anonymous pserver access. So what you saw was how it is configured, sorry for misleading you.
I have added you to the project team, so you should now have write access to post your tests for Sybase ASA. Welcome to the SQLUnit team. Let me know if the access works. Mario had a problem, I think I know why, but I may be wrong.
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am following these directions:
Here is the link to the FAQ which I set up sometime back, slightly more detailed than what I gave you, it should be the last one but you will need to login as well.
.
https://sourceforge.net/docman/display_doc.php?docid=21828&group_id=77832
Which say this:
Submit new documentation | View Documentation | Admin
If you are extending SQLUnit, it makes sense to use the code in CVS rather than what was supplied with the latest release. While there should not be much difference, since we release code changes fairly rapidly, having the CVS tree locally allows you to build patch files easily, which is very helpful. The instructions assume a *nix client (Windows users can use Cygwin or adapt the instructions).
$ export CVSROOT=:pserver:anonymous@cvs.sourceforge.net:/cvsroot/sqlunit
$ cvs login
CVS Password: <enter your email address here>
$ cvs -z3 checkout sqlunit
$ cvs logout
Now, I am running on windows, but I do have access to other sourceforge projects (with developer rights).
When I try the above instructions:
cvs login
Logging in to :pserver:anonymous@cvs.sourceforge.net:2401/cvsroot/sqlunit
CVS password:
cvs login: authorization failed: server cvs.sourceforge.net rejected access to /
cvsroot/sqlunit for user anonymous
The instructions say:
CVS Password: <enter your email address here>
What email address?
My personal email address
My sourceforge email address (ie bob@sourceforge.net)
Or just "bob" assumig sourceforge..
I have tried all of the above, never changing my CVSROOT from what was specified, but I never have any luck.
Thanks,
Dave
Hi Dave,
You are right, the anonymous login seems to have stopped working... here is what I had to do to download the code from an user other than the one I normally use for SQLUnit.
export CVSROOT=:pserver:spal@cvs.sourceforge.net/cvsroot/sqlunit
cvs login<enter>
Enter my sourceforge password when prompted
cvs checkout sqlunit
and it worked fine. (You can use -z3 for compression so your download is faster). I have updated the FAQ with the new information.
-sujit
Using my userid does not work...
C:\OpenSrc\sqlunit>cvs -z3 -d:pserver:dfishburn@cvs.sourceforge.net
:/cvsroot/sqlunit update -dAP
? lib/.new.pg73b1jdbc3.jar
cvs update: Updating .
cvs update: failed to create lock directory for `/cvsroot/sqlunit/sqlunit' (/cvs
root/sqlunit/sqlunit/#cvs.lock): Permission denied
cvs update: failed to obtain dir lock in repository `/cvsroot/sqlunit/sqlunit'
cvs [update aborted]: read lock failed - giving up
I can only do this using anonymous....
C:\OpenSrc\sqlunit>cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net
:/cvsroot/sqlunit update -dAP
? lib/.new.pg73b1jdbc3.jar
cvs update: Updating .
cvs update: Updating docs
cvs update: Updating lib
U lib/pg73b1jdbc3.jar
cvs update: Updating sqlunit
...
I have seen the "read lock failed" from sourceforge's CVS server before. It appears to be intermittent and a possible cause is overload. Retrying a couple of times usually does it.
So anonymous works too. That is surprising, I thought I tried it the last time and it did not work the last time I tried it.
Oh, well, I guess I will update the FAQ to try anonymous as well. Thanks for checking it out.
-sujit
I dont think it is a CVS hiccup, since I have tried a million times and have never managed to get access using my id. Where as, the same configuration works for the other sourceforge projects I am on.
I googled around and found this response:
-------------------------
If a user wants any kind of access at all - even read-only access - to a given subdirectory of the repository, she usually needs file system-level write permission to that subdirectory. This is necessary because CVS creates temporary lock files in the repository to ensure data consistency. Even read-only operations (such as checkout or update) create locks, to signal that they need the data to stay in one state until they're done.
As noted in Repository Administration, you can get around this writeability requirement by setting the LockDir parameter in CVSROOT/config, like this:
LockDir=/usr/local/cvslocks
Of course, then you would need to make sure the directory /usr/local/cvslocks is writeable by all CVS users. Either way, most CVS operations, including read-only ones, are going to require a writeable directory somewhere. By default, that directory is the project's repository; if you're very security conscious, you can change it to be somewhere else.
-------------------------
Would you be able to verify any of this?
Thanks,
Dave
Hi Dave,
I will check this, right after I finish putting in Mario's new tags. Although Mario's code will fit right in, he has done some refactoring which I want to apply to some of the other tags as well, to make the source more consistent. I am doing this, should be done by end of the week.
We can then try making changes to CVSROOT with your existing privileges and then with developer access, so we can work out and fix the cvs problems we are having.
Thanks
Sujit
Ok, I went through the docs again (updated the FAQ entry with the link, as well as some more info about developer access that I happened to re-learn) and it says for non-project team access, you need to use anonymous pserver access. So what you saw was how it is configured, sorry for misleading you.
I have added you to the project team, so you should now have write access to post your tests for Sybase ASA. Welcome to the SQLUnit team. Let me know if the access works. Mario had a problem, I think I know why, but I may be wrong.
-sujit
Thanks for adding me.
I have successfully checked out (which I couldn't before).
Dave