Stale lock file
Paul Snively
There seems to be a stale lock file in my test repo. Is there some way
that I can delete it? Short of that, is there some way that an
administrator can delete it? :-)
Best regards,
Paul
thomas hartman
about it)
2) I just ran
psnively-testproject # rm _darcs/lock
psnively-testproject # darcs check
The repository is consistent!
manually.
In general, if your repository is borked and you want to recover
without administrative intervention, you can pull all to local->delete
patch-tag repo-> recreate patch-tag repo with same name -> push to
patch tag repo as described in
http://patch-tag.com/troubleshoot-wiki-browsing
I may add web-enabled user actions to recover from common failure
scenarios such as stale lock file etc. I probably am not going to
enable any kind of shell abilities beyond the completely crippled
shell you can currently get, for security reasons.
happy tagging :)
thomas.
thomas hartman
bug tracker, hosted as an anonymously editable gitit wiki on patch
tag:
It has been running in stealth mode for a few days... hello world : )
A few words about this.
Gitit for bugs a bit of an experiment for me, trying to eat my own
dogfood by using an existing patch-tag feature to bug track rather
than using a more full featured free tracker/todo list such as google
code or basecamp, or building my own.
Until now, patch-tag has used fogbugz in free 2-person mode, but I
didn't want to spend $25/month to upgrade out of 2-person mode, and
yet I really need a place for public to list their bugs and suggested
features.
I will try not to be a fanatic about dogfooding. If gitit for bug
tracking seems to be more work than it is worth, I will switch to
something that gets the job done better. It seems to be working ok in
the limited test so far, so I am going for it :)
http://patch-tag.com/r/tphyahoo/patchtag-public-bugs/wiki/
thomas.
On Jan 17, 11:49 am, thomas hartman <thomashartm...@googlemail.com>
wrote:
Eric Kow
wrote:
> This seems like a fortuitous point to introduce the patch-tag public
> bug tracker, hosted as an anonymously editable gitit wiki on patch
> tag:
>
Hooray! Thanks
> Gitit for bugs a bit of an experiment for me, trying to eat my own
> dogfood by using an existing patch-tag feature to bug track rather
> than using a more full featured free tracker/todo list such as google
> code or basecamp, or building my own.
It's a bit free-form, which can be good or bad.
> I will try not to be a fanatic about dogfooding. If gitit for bug
> tracking seems to be more work than it is worth, I will switch to
> something that gets the job done better. It seems to be working ok in
> the limited test so far, so I am going for it :)
Here's an alternative that I've been told to try, but never got around
to http://bugseverywhere.org/be/show/HomePage
The key feature is that it explicitly supports Darcs (along with other
revision control systems).
Eric