VCS Repository settings Not finding repository

The error means that the repository can't be accessed for any reason - I should probably change the error text accordingly. Analysing what went wrong probably requires the error output that the 'svn' binary returns for that invocation. Given that I should implement error messages anyways for issue #227446: exec statements, it's obviously time that I get proper error reporting to work now.

Oh right, and if you can read a bit of PHP you might be able to assemble the command that is invoked by svnlib_log() (which is responsible for the error). Of course you could also wait until proper error reporting is implemented.

I tried the command fired from within svnlib_log() on the command line at the server and it completed successfully. I will wait for the expanded error messages. Not intending to rush you, but do you have an idea of when that might happen?

Thanks

I really want to do this today - on the one hand, I'll get more bug reports if I don't, on the other hand I can close two in one stroke, and on the third (three hands? :-o ) I don't feel like being bothered too much with SVN related issues at the moment, so I want everything to work.

I completely understand. I'll stay tuned!

Thanks

Ok, I added proper error reporting to CVS. If you feel like trying out now (so that I don't have to do a release before fixing your real error) you can check out versioncontrol_svn from the DRUPAL-5 branch. Let me implement the second part of #227446: exec statements, afterwards I'll do a 1.2 (in case you're fast enough and I can fix your bug right now) or 1.2-beta1 (in case I'm faster).

Ok, I'm faster :P

Please get 5.x-1.2-rc1 (should be generated and deployed to the servers in about 5-10 minutes), try fetching again, and see what the error output says.

Let's also have a status update... nothing that I can do for this issue right now.

Sorry it took me a little while to test this. You're too fast for me!

I am now receiving the message:

The repository at svn://business/example/trunk could not be accessed. Error message from 'svn info':
The filename, directory name, or volume label syntax is incorrect.

I have verified it functions from the command line.

Hm... we may need the actual command displayed as well then. Minus the password, that would be bad thing to be shown (which is why I don't display the command itself, currently - takes a bit more effort). Expect an -rc2 release soon.

Hi.. i'm getting the same errors too (svn is in the path and i can run the commands via cmdline no probs).

I've also been testing the separate subversion module that works with the project module - i have an open issue [http://drupal.org/node/218826] there relating to the exec debug output. I'm testing both as i'm dying to get subversion linked up - but am i right in thinking that this versioncontrol-api is meant to be replacing subversion module etc.

Anyway, i'll keep an eye on this thread and test anything that comes out. Thanks for your effort on this.

@ajudson: Yes, you're right that Version Control API + Subversion backend is supposed to replace the Subversion module. It's not at the same level of functionality yet, that might still take a while, but it's the common perception that Version Control API is the future of VCS support in Drupal. (I'm trying to live up to those expectations.)

As for this issue, please give me a bit more time (or maybe provide a patch :D ) as I currently need to prepare for an exam and also have a tight schedule for completing the database schema port for Version Control API 5.x-2.x (which is more important to me at the moment). Should make for a few more days of waiting.

no worries jpetso... whilst you study for your exam i'll go and to some long over due study on php and drupal module dev. Good luck for your exam.

Hi,

Is there any progress on this topic, cause I've just got the same error as ajudson
"he repository at file:///192.168.2.5/tcs/svn/tcsdev could not be accessed. Error message from 'svn info':
De syntaxis van de bestandsnaam, mapnaam of volumenaam is onjuist."

The second error line is in dutch because my server is dutch it means "The filename, directory name, or volume label syntax is incorrect."

Thanks in advance,
really appreciate the work here by the way!

Work here is currently stalled, patches from outside people are very much appreciated (and in fact, required, as we might not get back to the SVN backend until other issues have been solved first, which might take time).