SVN being worked on

[Bruceper]

Now that I have resolved an external issue, I am working on getting the SVN version back up and working.

Right now the SVN script is mostly working, but is failing at one point. It worked before so I'm a little confused as to why it stopped working.

Anyways, it's a directory changing issue. I'm not too good at bash scripts so I'm just letting you know that I'm working on it and so far have created the SVN version manually.

Yes you can download revision 1074 right now!

I'll let you know how it goes after this.

[Bruceper]

Wierd stuff for me. The script now runs fine from the command prompt (manually entered) but fails when run via cron or from the bash script.

Looks like I'll need some assistance here so it won't be fixed right away. I'll keep you updated.

[Dr. Jekyll]

the SVN version

SVN

[Bruceper]

It's a beta version. If you don't know what it is then I wouldn't concern yourself with it as it can cause more trouble than it's worth.

[Dr. Jekyll]

It's a beta version. If you don't know what it is then I wouldn't concern yourself with it as it can cause more trouble than it's worth.

Thanks! But anyway, what SVN stands for?

[Bruceper]

SubVersioN

[Dr. Jekyll]

Thanks!

[Bruceper]

IT IS DONE!

This was almost like a comedy of errors, pains in the butt and all sorts of other issues beyond my control.

Add another external issue, throw in some unix carraige returns/line feeds (CR+LF), add a dash of "oops I forgot to do that", a pinch of a vanished password, throw in a locked account and top it all off, sprinkle it all with a billing issue.

And now you have SVN that should be working without issue.

And if it breaks again, I'm not fixing it