it seems that the repo on the fs was somehow modified, because it is not accessible via hg any more:

$ hg pull
remote: User IgorMinar not authorized to read repository s4~main
abort: no suitable response from remote hg!

The message in your attached screenshot is actually to be expected – you were creating another repository with the same display name, which we disallow to avoid confusion. You should be able to rename the old repository something like "Source Code Repository (old)", even temporarily, and then create the new repo as expected.

Similarly, the error you're getting from Mercurial is because the first rename (main -> main.old) succeeded, and so the old 'main' repo has been moved. You should be able to clone s4~main.old and see the old repo right away, and use the same s4~main URL as soon as the display name conflict I mentioned above has been resolved.

the thing is that I can't do anything with the existing repo: http://skitch.com/me3x/bu3wf/working

So the edit breaks because of 404 from the xhr response and delete returns empty http 406

Igor,

I tracked down the root cause of this – we were mistakenly allowing periods in repository names, even though the default Rails routing treats them as a special character for determining the desired response content type for a request (i.e., 'filename.ext').

I've fixed the issue in our source code, and also manually renamed your repo back to 'main' for the time being. Please try renaming it again, this time with a name that doesn't include a period.

Thanks for your patience. I'm still looking into the cause of the original commit email issue that caused us to trigger this bug.

cool, that helped. I was able to rename the repo and create an empty repo and finally remove the old repo. thanks!

closing as verified (revision 20090619.006b533) - cannot rename repo name with period, successful rename of all repositories