Re: [darcs-users] Converting foreign repos to Darcs
On Sat, May 08, 2010 at 10:37:06PM +0200, Ben Franksen
benjamin.frank...@bessy.de wrote:
I would really like to offer to take over maintenance of the
darcs-fast-import script, as it looks as if this format is going to be the
de-facto standard for repository interchange. With a robust and
feature-complete darcs-fast-import we could cover most of the demands for
easy migration to Darcs. However, I just took over maintenance of another
open source project and I fear this will be more than I can take on,
especially since I am not very versed in Python.
Don't worry, when I wrote darcs-fast-{import,export} first it was a
separate project and then I realised I don't have time to maintain it.
So it got merged to bzr-fastimport where the Canonical guys test and use
it regularly, and now I don't have to care about releases, they do it.
OTOH it's still an open project, you can hack it whenever you want and
and patches are still accepted in the launchpad bts.
pgpmmMTsW4vYR.pgp
Description: PGP signature
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Converting foreign repos to Darcs
On Sat, 08 May 2010 22:37:06 +0200
Ben Franksen benjamin.frank...@bessy.de wrote:
Lele ... Thank you!
No problem at all, thank you for the clarification anyway! :-)
I would really like to offer to take over maintenance of the
darcs-fast-import script, as it looks as if this format is going to
be the de-facto standard for repository interchange. With a robust and
feature-complete darcs-fast-import we could cover most of the demands
for easy migration to Darcs.
Nod. I still think tailor should be able to grok with the
fast-{import|export} format, maybe with a generic source/target
backends. But I never had the pleasure to use that, yet, and I don't
foresee a need in the near future.
ciao, lele.
--
nickname: Lele Gaifax| Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas| comincerò ad aver paura di chi mi copia.
l...@nautilus.homeip.net | -- Fortunato Depero, 1929.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Converting foreign repos to Darcs
Lele I am sorry if I sounded grumpy and demanding. This was not what I intended, but I see that it has come out like that. Fact is, I *am* glad and thankful for the work you did with tailor. Without tailor I would never have had the opportunity to establish Darcs at where I work. And, BTW, I would not care to write long messages to this list if I wasn't a very dedicated fan of Darcs, and also very glad that it keeps getting better and better, thanks to the good work of all you people here. So, all of you, please accept a big, huge Thank you! It was *not* my goal to criticise you personally or diminish the work you did with tailor. I can perfectly understand if you cannot support it any longer, or at least not in the way you used to. Nevertheless, it is a fact that must be taken into consideration. What I wanted to achieve is bring the problem to the attention of the Darcs development team. In the past, whenever someone asked about a tool to convert some foreign repo to Darcs, he/she was told to use tailor. Most of the other VCSes have more or less tightly integrated tools to convert other repository formats into their own. Darcs used to have tailor, but if tailor is starting to suffer from bit-rot then the whole Darcs community has a problem, as this will make it very hard to get more users, and as a result people will loose interest. Now, as you indicated in your answer, tailor was never designed with the primary goal of supporting migration to Darcs, right? It was designed as a tool for general VCS to VCS conversion *and* simultaneous one- or bi-directional cooperation between VCSes. This is much more than what Darcs needs to offer smooth migration. I would love to see someone take over development of tailor, but in order to fix the immediate problem something simpler would suffice and be less work to maintain. I mean, something that is specialized to the X-to-Darcs conversion task. I would really like to offer to take over maintenance of the darcs-fast-import script, as it looks as if this format is going to be the de-facto standard for repository interchange. With a robust and feature-complete darcs-fast-import we could cover most of the demands for easy migration to Darcs. However, I just took over maintenance of another open source project and I fear this will be more than I can take on, especially since I am not very versed in Python. If it appears that all I can do is criticise and not help make things better, well, I am sorry but I can't help it (except to shut up, which is what I am going to do now ;-). Cheers Ben ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Converting foreign repos to Darcs
On Fri, 07 May 2010 21:01:24 +0200 Ben == Ben Franksen benjamin.frank...@bessy.de wrote: Ben I tried to convert via other VCSes (bzr,hg). Conversion to bzr Ben added the tags just fine, so I thought maybe tailor can convert Ben from the bzr repo. If you were able to convert to bzr, then I suggest to use bzr's fast-export/import for conversion to darcs. Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 signature.asc Description: PGP signature ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Converting foreign repos to Darcs
Gour wrote: On Fri, 07 May 2010 21:01:24 +0200 Ben == Ben Franksen benjamin.frank...@bessy.de wrote: Ben I tried to convert via other VCSes (bzr,hg). Conversion to bzr Ben added the tags just fine, so I thought maybe tailor can convert Ben from the bzr repo. If you were able to convert to bzr, then I suggest to use bzr's fast-export/import for conversion to darcs. Excuse me, are you saying that bzr offers conversion *to darcs* (even if only from fast-export/import)? This would be fantastic if it were true but I just can't believe it (...watch me googling as I write this...) Cheers Ben ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Converting foreign repos to Darcs
Ben Franksen wrote: Gour wrote: On Fri, 07 May 2010 21:01:24 +0200 Ben == Ben Franksen benjamin.frank...@bessy.de wrote: Ben I tried to convert via other VCSes (bzr,hg). Conversion to bzr Ben added the tags just fine, so I thought maybe tailor can convert Ben from the bzr repo. If you were able to convert to bzr, then I suggest to use bzr's fast-export/import for conversion to darcs. Excuse me, are you saying that bzr offers conversion *to darcs* (even if only from fast-export/import)? This would be fantastic if it were true but I just can't believe it (...watch me googling as I write this...) Ha. It seems this is the no-longer-maintained python script my colleague spoke of. I will investigate. Cheers Ben ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Converting foreign repos to Darcs
On Fri, 07 May 2010 21:15:26 +0200 Ben == Ben Franksen benjamin.frank...@bessy.de wrote: Ben Excuse me, are you saying that bzr offers conversion *to darcs* Ben (even if only from fast-export/import)? This would be fantastic Ben if it were true but I just can't believe it (...watch me Ben googling as I write this...) See http://vmiklos.hu/project/darcs-fast-export/ Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 signature.asc Description: PGP signature ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Converting foreign repos to Darcs
On Fri, 07 May 2010 21:01:24 +0200 Ben Franksen benjamin.frank...@bessy.de wrote: Hello Darcsers a few days ago I started converting a Subversion repo to Darcs. This did not go very smoothly. I used tailor as this seems to be the only existing tool for the job. The conversion process went fine, however (1) tailor ignores svn tags: they do not appear as darcs tags in the result tailor was not born to replicate another repo kind. I didn't care at all about tags. All tags support in tailor has been contributed and happily merged in. More, properly handling of svn tags is even more tricky than, say, CVS ones, so I'm more than happy if some else wrote a working implementation, something I'm surely not going to reinvent. (2) when I tried to insert the missing tags manually, I found that the resulting darcs repo contains broken patches. I would have written a pre/post commit hook, feeded with a parsed svn ls -v /tags output, executing darcs tag at the right time. But what do you mean with broken patches? I converted tons of svn repos to darcs with tailor, and never had that bad experience (well, almost :-). I tried to convert via other VCSes (bzr,hg). Conversion to bzr added the tags just fine, so I thought maybe tailor can convert from the bzr repo. Nope. It ran immediately into an error. Next thing I tried is to 'hg convert' the bzr repo to mercurial. Went through like butter. But when I tried to use tailor to convert from the resulting hg repo to darcs, ... well, by now you probably guess what happened: I got a stack trace saying something about some constructor not expecting 5 args but only 2. It turned out this is just bit-rot, as there was a change mercurial's python API some time ago. Yes, I may understand the feeling. To fix that call, I'm inclined to wait for hg 2.0 when hopefully they will get it right and written in stone, or for an actual hg user (easy, I'd say) contribution, whichever come first. :-) Next thing that happened was the tailor web page broke down, somehow trac runs into an error. Since this problem persists, I reported this to the tailor mailing list. While doing so, I found that there was just one other (un-answered) message with a 2010 date. Yes, zooko sent me an email, and I restarted the apache daemon, apparently stuck somewhere. Sorry about that. And yes, tailor's mlist is very very quiet, always been like that. I still hang on #tailor on irc.freenode.net, though. So, it appears tailor is no longer an actively maintained project. Uhm, well, it's definitely not easy to admit, but yes, I could not spend any more on it as I used to in the past. Primarily because I'm finally and happily busy doing work-for-living, second because my dependency on tailor is weak these days, as I currently do almost everything in pure darcs, with a single on going experience with bazaar. That's probably make the project no longer actively maintained. OTOH, the section The future on the main wiki page stated that more than 9 months ago. So, little surprise there. I think this conversion business needs more serious attention from the community. For me it is a much heavier show-stopper than any of the performance problems. I think the community, in particular you in this case, should first of all respect whoever wrote some piece of software you happen to be using. Darcs itself would be stuff of the past, if the community simply shouted at David and his no-more-maintained-pile-of-bugs :-) A supporting community can make the difference, as it can even take over the maintenance effort, if convincing the author to keep it going on is impossible for whatever reason. Even a single unsatisfied user can make the difference, by choosing the right words to ask or propose a fix. Last, *maintaining* any amount of code is not just a matter of keeping it inside the darcs repo. Expecially when that amount of code deals with a versioning system. And really expecially when it deals with two of those. ciao, lele. -- nickname: Lele Gaifax| Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas| comincerò ad aver paura di chi mi copia. l...@nautilus.homeip.net | -- Fortunato Depero, 1929. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
