{"thread":{"id":"24373","subject":"[GSoC update] git-remote-svn: Week 11","startedAt":"2010-07-12T14:35:46Z","lastAt":"2010-07-14T08:58:22Z","messageCount":7,"participants":["Ramkumar Ramachandra","Michael J Gruber","Stefan Sperling","Will Palmer"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"145365","messageId":"20100712143546.GA17630@debian","threadId":"24373","inReplyTo":null,"subject":"[GSoC update] git-remote-svn: Week 11","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2010-07-12T14:35:46Z","receivedAt":"2010-07-12T14:35:46Z","isPatch":false,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Hi,\n\nI'm happy to report that I'll soon be getting partial committer access\nto the ASF repository (thanks to Greg for this) and will be able to\ncommit the svnrdump there. At the moment, all the validations pass\nwithout any issues and I've shifted my focus towards writing a\ndumpfile v3 parser [1] to get the data into David's exporter. I will\nre-roll a series for git.git in some time again after I've fixed a few\npending things pointed out by Jonathan in his excellent reviews and\nmerged a few patches from Will; although this isn't top priority, it\nwill be pretty painful for Git developers to compile the SVN trunk\neven if they want to try out git-remote-svn.\n\nCurrently, I'm implementing svndiff0 parser component of the dumpfile\nv3 parser using Sam's Perl implementation [2] as a guideline. In\naddition, with an excellent specification present in the Subversion\ntrunk [3], this shouldn't be a problem.\n\n-- Ram\n\n[1]: dumpfilev3 branch of\nhttp://github.com/artagnon/svn-dump-fast-export/\n[2]: http://search.cpan.org/~samv/Parse-SVNDiff/\n[3]: http://svn.apache.org/repos/asf/subversion/trunk/notes/svndiff\n"},{"id":"145366","messageId":"4C3B2B48.4070408@drmicha.warpmail.net","threadId":"24373","inReplyTo":"20100712143546.GA17630@debian","subject":"Re: [GSoC update] git-remote-svn: Week 11","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2010-07-12T14:48:40Z","receivedAt":"2010-07-12T14:48:40Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Ramkumar Ramachandra venit, vidit, dixit 12.07.2010 16:35:\n> Hi,\n> \n> I'm happy to report that I'll soon be getting partial committer access\n> to the ASF repository (thanks to Greg for this) and will be able to\n> commit the svnrdump there. At the moment, all the validations pass\n> without any issues and I've shifted my focus towards writing a\n> dumpfile v3 parser [1] to get the data into David's exporter. I will\n> re-roll a series for git.git in some time again after I've fixed a few\n> pending things pointed out by Jonathan in his excellent reviews and\n> merged a few patches from Will; although this isn't top priority, it\n> will be pretty painful for Git developers to compile the SVN trunk\n> even if they want to try out git-remote-svn.\n\nWhile this is certainly true for the \"compilation\" part, at least\ngetting the source is a snap for us:\n\ngit://git.apache.org/subversion.git\ngit://github.com/apache/subversion.git\n\n:)\n\nMichael\n"},{"id":"145370","messageId":"20100712152403.GH1931@jack.stsp.name","threadId":"24373","inReplyTo":"4C3B2B48.4070408@drmicha.warpmail.net","subject":"Re: [GSoC update] git-remote-svn: Week 11","fromName":"Stefan Sperling","fromEmail":"stsp@elego.de","sentAt":"2010-07-12T15:24:03Z","receivedAt":"2010-07-12T15:24:03Z","isPatch":false,"sender":{"key":"stsp@elego.de","avatar":"https://avatars.githubusercontent.com/u/9281333?v=4"},"body":"On Mon, Jul 12, 2010 at 04:48:40PM +0200, Michael J Gruber wrote:\n> Ramkumar Ramachandra venit, vidit, dixit 12.07.2010 16:35:\n> > it will be pretty painful for Git developers to compile the SVN trunk\n> \n> While this is certainly true for the \"compilation\" part, at least\n> getting the source is a snap for us:\n> \n> git://git.apache.org/subversion.git\n> git://github.com/apache/subversion.git\n\nRegarding compilation, take a look at tools/dev/unix-build/Makefile.svn\nin the Subversion tree. Possibly the most painful thing for git devs is\nthat you'll need an svn binary somewhere in PATH, but any version will do.\nThen create an empty directory (say, ~/svn), copy the Makefile in there,\nand run make (requires GNU make). That will download and compile Subversion\nfrom trunk, including various dependencies.\nIf all goes well, binaries (with debug symbols) end up in ~/svn/prefix/\n\nOn Linux, -devel packages for a couple of libaries may be needed\n(most likely openssl, zlib, expat, libproxy).\n\nStefan\n"},{"id":"145371","messageId":"1278949191.1611.5.camel@wpalmer.simply-domain","threadId":"24373","inReplyTo":"20100712152403.GH1931@jack.stsp.name","subject":"Re: [GSoC update] git-remote-svn: Week 11","fromName":"Will Palmer","fromEmail":"wmpalmer@gmail.com","sentAt":"2010-07-12T15:39:51Z","receivedAt":"2010-07-12T15:39:51Z","isPatch":false,"sender":{"key":"wmpalmer@gmail.com","avatar":"https://avatars.githubusercontent.com/u/357044?v=4"},"body":"On Mon, 2010-07-12 at 17:24 +0200, Stefan Sperling wrote:\n> On Mon, Jul 12, 2010 at 04:48:40PM +0200, Michael J Gruber wrote:\n> > Ramkumar Ramachandra venit, vidit, dixit 12.07.2010 16:35:\n> > > it will be pretty painful for Git developers to compile the SVN trunk\n> > \n> > While this is certainly true for the \"compilation\" part, at least\n> > getting the source is a snap for us:\n> > \n> > git://git.apache.org/subversion.git\n> > git://github.com/apache/subversion.git\n> \n> Regarding compilation, take a look at tools/dev/unix-build/Makefile.svn\n> in the Subversion tree. Possibly the most painful thing for git devs is\n> that you'll need an svn binary somewhere in PATH, but any version will do.\n> Then create an empty directory (say, ~/svn), copy the Makefile in there,\n> and run make (requires GNU make). That will download and compile Subversion\n> from trunk, including various dependencies.\n> If all goes well, binaries (with debug symbols) end up in ~/svn/prefix/\n> \n> On Linux, -devel packages for a couple of libaries may be needed\n> (most likely openssl, zlib, expat, libproxy).\n> \n> Stefan\n\nThis is all moot, because the whole point is that svndumpr compiles\nagainst libsvn, so you don't need the whole svn source-tree. All you\nneed to get svndumpr working are some header files and a working libsvn.\nEveryone who currently uses git-svn already has a working libsvn, since\nperl's svn bindings wrap around libsvn anyway.\n"},{"id":"145373","messageId":"4C3B3C14.8040002@drmicha.warpmail.net","threadId":"24373","inReplyTo":"20100712152403.GH1931@jack.stsp.name","subject":"Re: [GSoC update] git-remote-svn: Week 11","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2010-07-12T16:00:20Z","receivedAt":"2010-07-12T16:00:20Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Stefan Sperling venit, vidit, dixit 12.07.2010 17:24:\n> On Mon, Jul 12, 2010 at 04:48:40PM +0200, Michael J Gruber wrote:\n>> Ramkumar Ramachandra venit, vidit, dixit 12.07.2010 16:35:\n>>> it will be pretty painful for Git developers to compile the SVN trunk\n>>\n>> While this is certainly true for the \"compilation\" part, at least\n>> getting the source is a snap for us:\n>>\n>> git://git.apache.org/subversion.git\n>> git://github.com/apache/subversion.git\n> \n> Regarding compilation, take a look at tools/dev/unix-build/Makefile.svn\n> in the Subversion tree. Possibly the most painful thing for git devs is\n> that you'll need an svn binary somewhere in PATH, but any version will do.\n> Then create an empty directory (say, ~/svn), copy the Makefile in there,\n> and run make (requires GNU make). That will download and compile Subversion\n> from trunk, including various dependencies.\n> If all goes well, binaries (with debug symbols) end up in ~/svn/prefix/\n> \n> On Linux, -devel packages for a couple of libaries may be needed\n> (most likely openssl, zlib, expat, libproxy).\n> \n> Stefan\n\nThat Makefile pulls in (and compiles) a lot of stuff which may or may\nnot be what you want.\n\nIn terms of Git development, I prefer a Git checkout (rather than a svn\ncheckout) of the subversion code where I can bisect happily. Fulfilling\nmost dependencies using devel packages was not a real problem (Fedora\n13), just an iterative process...\n\nThe most painful part is that older svns (e.g. 1.4.6) don't seem to like\nnewer autoconf (2.65) so that compatibility testing gets difficult,\nespecially because (due to the branch structure of the code) merge bases\nof, say, 1.5.0 and trunk go quite a way back (1.5.0~955).\n\nMichael\n"},{"id":"145383","messageId":"20100712181233.GC17630@debian","threadId":"24373","inReplyTo":"1278949191.1611.5.camel@wpalmer.simply-domain","subject":"Re: [GSoC update] git-remote-svn: Week 11","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2010-07-12T18:12:33Z","receivedAt":"2010-07-12T18:12:33Z","isPatch":false,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Hi,\n\nWill Palmer writes:\n> This is all moot, because the whole point is that svndumpr compiles\n> against libsvn, so you don't need the whole svn source-tree. All you\n> need to get svndumpr working are some header files and a working libsvn.\n> Everyone who currently uses git-svn already has a working libsvn, since\n> perl's svn bindings wrap around libsvn anyway.\n\nYes, I meant that people will need the complete Subversion tree if I\nDON'T get svnrdump merged somewhere in git.git (I'll attempt to get\nthe version that compiles against libsvn 1.6 merged). The instructions\nto checkout the right branches and place it in the git tree can be\ncomplicated: git-remote-svn relies on a chain of tools including\nDavid's exporter and svnrdump to work.\n\n-- Ram\n"},{"id":"145520","messageId":"20100714085822.GC25630@jack.stsp.name","threadId":"24373","inReplyTo":"1278949191.1611.5.camel@wpalmer.simply-domain","subject":"Re: [GSoC update] git-remote-svn: Week 11","fromName":"Stefan Sperling","fromEmail":"stsp@elego.de","sentAt":"2010-07-14T08:58:22Z","receivedAt":"2010-07-14T08:58:22Z","isPatch":false,"sender":{"key":"stsp@elego.de","avatar":"https://avatars.githubusercontent.com/u/9281333?v=4"},"body":"On Mon, Jul 12, 2010 at 04:39:51PM +0100, Will Palmer wrote:\n> On Mon, 2010-07-12 at 17:24 +0200, Stefan Sperling wrote:\n> > Regarding compilation, take a look at tools/dev/unix-build/Makefile.svn\n> This is all moot, because the whole point is that svndumpr compiles\n> against libsvn, so you don't need the whole svn source-tree.\n\nIt's not moot. svndumpr may now or in the future be using API calls which\nare specific to the Subversion 1.7 libraries, in which case you'll need\nto compile Subversion from trunk to get compatible libraries until\n1.7 is released. Maybe Ramkumar wants to maintain a 1.6.x-specific\nversion you can use, but that won't be living in our repository anyway.\n\nStefan\n"}]}