How to checkout the svn

[Raúl Alexis Betancor Santana]

How can I checkout the current svn version?, As far as I could see on the web,
only autenticated access is allowed.

--
Saludos.

Raúl Alexis Betancor Santana
Director Gerente
Dimensión Virtual S.L.

[Duncan McGreggor]

On 4/11/06, Raúl Alexis Betancor Santana <ra...@dimension-virtual.com> wrote:

How can I checkout the current svn version?, As far as I could see on the web,
only autenticated access is allowed.

Yes, the svn check out "thing" has a bit of history. Subversion access has only been over ssh, due to security concerns and proprietary code in subdirectories of various projects. There are many svn repos on that server, and to change the way that one is managed requires that all are changed. So change is slow here ;-)

This winter, I converted to darcs only to discover that when maintaining multiple/distributed branches (pulling, recording, pushing) I kept getting tons of errors. Essentially, each push had to be accompanied by manual maintenance.

This, of course, defeated the whole purpose of moving to darcs. I also understand that it is most likely a problem with the way I was doing it. I deemed the effort to discover the issue too much (given my other obligations), so I scrapped it and went back to svn.

I have been pondering how to resolve this issue, and believe I have a workable, maintainable solution: use tailor to convert from svn to svn (I had used tailor to convert my svn repos to darcs repos):
1) The primary svn repos would be maintained on a secure, limited-access svn server
2) At regular intervals, tailor would "convert" them (tailor keeps state information, so only changes since last "convert" would be "exported")
3) These "conversions" would then be pushed to a publicly accessible remote a  server(s) where
4) Anyone could checkout the code via HTTP

I'm not sure when I will have to time to do this, though.

However, until that time, you can download the latest release candidate here:
  http://projects.adytum.us/tracs/PyMonitor/browser/releases/

The one you want is the most recent file, RC2.

There is a known issue with this release: the WARN emails are not getting sent. This was fixed in RC3, but a bunch of other stuff was broken. At some point I need to rollback all the trunk changes but the WARN fix, and upload RC3.

Some installations of the pymon egg go very smoothly, and some are really tricky. It seems that the complicating factor is setuptools: on differenet systems, setuptools has to do different things (like downloading the latest setuptools). Keep us posted on your progress and any problems you run into, and we'll help you get through them.