Switched to Git
October 30th, 2009 19:27 by tbhAs we had enormous trouble with Darcs recently (Darcs processes running wild, sucking up all CPU power), and as I became quite a fan of Git, we decided to switch. You can now clone the repository using the following command:
$ git clone http://holumbus.fh-wedel.de/src.git
Thanks for your patience and keep on using Hayoo! :)
October 30th, 2009 at 20:43
Had the same issue as well, when pushing to another repository. Haven’t had the same issue since I upgraded; I’m now running 2.3.1 (+ 264 patches).
October 30th, 2009 at 22:32
Do you know what version of darcs you were using and what repository format you were using?
October 30th, 2009 at 22:41
I’d like to know more about the problems you had if you have a moment. What kind of repository is this? Could you show us the results of darcs show repo? What was the operation that was causing the hang? Thanks! (and if I forget to check back, please feel free to contact us at bugs@darcs.net or darcs-users@darcs.net)
October 31st, 2009 at 20:27
The version of darcs is 2.2.0 … unfortunately, I already deleted the repo. I think the problem had to do with the trac darcs plugin, specifically the source browser. As far as I remember it was an old darcs-1.0 style repo, but not 100% sure.
November 3rd, 2009 at 0:00
Just as expected. This is something that has been substantially improved in trac-darcs plugin a few months back. I don’t care if you switch, but please avoid the FUD next time around.
November 3rd, 2009 at 19:44
Thanks for the details. Could I poke a little more into this? First of all, what version of the trac-darcs plugin were you using?
Tracdarcs 0.7 has some simple optimisations that avoid this problem with the source browser ( see http://bugs.darcs.net/issue1477 ). It substitutes one slow darcs command with a much faster one where appropriate. So it’s quite likely that just upgrading to a later version of trac-darcs would have stopped the spinning. In the long run, of course, it would be great if darcs could solve the underlying issue. Meanwhile, it’s good to know that simple and practical workarounds do exist!
Also: any chance you were bitten by robots visiting your source browser?
Anyway, have fun with git! Once you go distributed, you don’t go back :-)
November 7th, 2009 at 18:42
Eric, thanks for the details. I compiled the trac-darcs plugin directly from a checkout of its darcs repo, somewhen in July 2008. This is fairly old, so that might have been the problem. Good to know that workarounds exist, I probably should have updated the plugin.
Regarding the robots, I regularly have a look at the logs and hence I’m quite sure that this wasn’t the problem.
Nevertheless, I don’t think that we’re spreading FUD here. I don’t blame darcs or trac-darcs for anything, I just became more used to git (as I use it at work and darcs unfortunately is no option there). Still, I am missing the better merge capabilities of darcs :)