Hello,

Just wondering if anyone else has seen this - and maybe this will save you time in case you do see it.

The files in my FreeRTOS SVN repository under the .svn dir -

all-wcprops
entries
and
format

had the directory in them reset to svn.sourceforge.net - rather than freertos.svn.sourceforge.net -
I use the Tortoise SVN explorer - and it produced an error message making you think something was wrong with
your DNS service rather than the directory name. Luckily my repository on my laptop was working - so I was able
to figure this out. If these files become corrupt or the root repository name changes - it isn't fun nor fast to
track this down.

Regards,
John W.

Hi John,

SourceForge changed their SVN hosting configuration a little while back (some months back now), this involved the URL to the repository changing. I was not aware of it so when my repository stopped working I sent them a support request, the result of which was instruction on how to use the Tortoise menu to switch the repository location.

Maybe this could be related?

The current path I am using is: https://freertos.svn.sourceforge.net/svnroot/freertos/trunk so it looks like yours is correct, but its the only thing I could think of that may have caused a problem.

Regards.

Richard,

Possibly this is what happened - but I'm pretty sure I'd updated to 4.3.1 since then - so that was less than a few months ago - so I'm not 100% sure...

Thanks,
John

Richard,

I had an external USB drive that went bad - I'd been using the repository off of that, and had moved that onto my main drive when the external USB drive was going down for the count. I think this must be the source of the problem - I'd definitely upgraded to 4.3.1 before that happened - so that's post what you'd mentioned above.

I just wanted to bring this up in the forum because it cost me some time, the error message is divergent from the cause, and hopefully it'll save someone some time in the future if it happens again.

I think SVN is a useful tool and all - but I thought the era of 'error-message crytography' were gone - evidently not.

Another reason for a die-hard CVS man like me to remain so.

Regards,
John