cvsmonitor no longer can monitor our cvs repository in savannah, as they no longer accept pserver log in, but require ext.
We have changed the CVS_RSH environment variable to ssh, and used as CVSROOT
:ext:anoncvs@subversions.gnu.org:/cvsroot/gnumed
but log in still fails.
Has anyone overcome this? Where do the cvsmonitor logs live usually. I can't seem to access them for failed connects.
Thanks,
Tony Lembke
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As for :ext support, it's really not that far away now that 0.6.3 has much better abstracted backends.
What would help a lot is access to such a repository, or someone to document in depth all the elements required to do :ext, including any environment variables etc, and get me access to a repository.
Essentially
1. Know if the OS is capable of it
2. Know what to set to make it work
3. Do the actual thing
Given 1. and 2., 3. is I would think not too difficult.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
cvsmonitor no longer can monitor our cvs repository in savannah, as they no longer accept pserver log in, but require ext.
We have changed the CVS_RSH environment variable to ssh, and used as CVSROOT
:ext:anoncvs@subversions.gnu.org:/cvsroot/gnumed
but log in still fails.
Has anyone overcome this? Where do the cvsmonitor logs live usually. I can't seem to access them for failed connects.
Thanks,
Tony Lembke
Tony
The logs are really pretty crap...
I have some better logging code lying around in a different project, but I haven't had the time to upgrade it to the better version.
How's your perl? :)
As for :ext support, it's really not that far away now that 0.6.3 has much better abstracted backends.
What would help a lot is access to such a repository, or someone to document in depth all the elements required to do :ext, including any environment variables etc, and get me access to a repository.
Essentially
1. Know if the OS is capable of it
2. Know what to set to make it work
3. Do the actual thing
Given 1. and 2., 3. is I would think not too difficult.