Try logging in as alex-shpilkin, and clicking on this url
http://patch-tag.com/r/alex-shpilkin/turing
This should bring the repo back, I believe, modulo repo members (which
you will have to recreate)
Sorry about this recurring problem. I would really like to clear this
up for once and all, but time is tight on day gig and I just haven't
been able to.
t.
> --
> You received this message because you are subscribed to the Google Groups "patch-tag-users" group.
> To post to this group, send email to patch-t...@googlegroups.com.
> To unsubscribe from this group, send email to patch-tag-use...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
>
>
--
Need somewhere to put your code? http://patch-tag.com
Want to build a webapp? http://happstack.com
The short answer is "That didn't fix it". The long answer is (quote from
the page I get for the URL you have given):
> Happstack 0.5.0.2
>
> Something went wrong here
> Internal server error
> Everything has stopped
>
> The error was "repo not found"
That is, it reacts just as it would for any other nonexistent repository
(the error message could be improved though).
There's still no mention of neither "turing" nor "tmachine"
on /reposstarted or anywhere else, while (as I've already said) I've
tried to create both. That makes me think that the webapp refuses to
create any repository for me, which is strange.
I haven't attempted to perform any other operations in the meantime.
Alex
I was able (after alex gave me password privately) to fix this,
while logged in as alex, by doing a create repo action with repo name
turing.
Presumably this will work for repo tmachine as well but I'll let
alex test that.
As alex says, the "just click on this url while logged in as alex"
solution I proposed earlier did not work.
I believe this would have worked if a repo existed on file system
but not in macid.
However, in this case, just the turing directory existed on fs,
without apparently any _darcs files or any contents. (Contents should
still be in backup though alex, in the unlikely case that you need
this. My understanding is you deleted these repos intentionally.)
So, I would say the current situation, while ugly, is still
functional enough that I won't take further action other than maybe
improve the troubleshooting docu.
Thomas.
The upshot is that the hoped-for fix is incorporating internal ssh
server function from darcsden lib, as described in latest blog entry.
Till then things may continue to be a little dicey.