Re: svn export bug in 1.6.13
Am Freitag, 29. Oktober 2010 schrieb Daniel Shahaf: http://subversion.tigris.org/issues/show_bug.cgi?id=3727 Chris Seawood wrote on Fri, Oct 29, 2010 at 10:04:17 -0700: Hi, our workflow currently does not work due to this bug. Is there a fixed 1.6.13 version in the repository we can check out to replace the broken 1.6.13? Or do you recommend that one goes back to 1.6.12? Chrsitoph
Re: svn export bug in 1.6.13
On Tue, Nov 09, 2010 at 10:37:02AM +0100, Christoph Bartoschek wrote: Am Freitag, 29. Oktober 2010 schrieb Daniel Shahaf: http://subversion.tigris.org/issues/show_bug.cgi?id=3727 Chris Seawood wrote on Fri, Oct 29, 2010 at 10:04:17 -0700: Hi, our workflow currently does not work due to this bug. Is there a fixed 1.6.13 version in the repository we can check out to replace the broken 1.6.13? Or do you recommend that one goes back to 1.6.12? The bug has been fixed in trunk. The fix has not been nominated for backport to 1.6.x yet but I will do so shortly. Until the fix appears in a new Subversion release, you can go back to 1.6.12. Alternatively, if you feel comfortable compiling svn yourself from source, you will be able to check out a branch from our repository that contains recent 1.6.x code (currently very close to 1.6.13) plus the fix. If you want to do that let me know and I'll send you the URL once it exists. Stefan
Re: svn export bug in 1.6.13
The bug has been fixed in trunk. The fix has not been nominated for backport to 1.6.x yet but I will do so shortly. Until the fix appears in a new Subversion release, you can go back to 1.6.12. Alternatively, if you feel comfortable compiling svn yourself from source, you will be able to check out a branch from our repository that contains recent 1.6.x code (currently very close to 1.6.13) plus the fix. If you want to do that let me know and I'll send you the URL once it exists. Yes, I would like to compile the recent 1.6.x code with the fix. Please send me the URL. Thanks Christoph
Re: svn export bug in 1.6.13
Am Dienstag, 9. November 2010 schrieb Stefan Sperling: https://svn.apache.org/repos/asf/subversion/branches/1.6.x-issue3727 Please note that my fix hasn't been reviewed yet by other developers. If you encounter problems using this fix please let me know. Thanks, works for us as expected. Christoph
svn export bug in 1.6.13
Hi, I just ran across a bug in the 1.6.13 release. Historically, 'svn export $SVNROOT/$PATH .' has just exported the contents of $PATH into the current directory. Under 1.6.13, the client creates a subdir named after the last directory component of $PATH and puts the contents there. This change in behavior breaks some of our release scripts and we've been forced to downgrade to 1.6.12. # 1.6.13 [cseaw...@localhost foo]$ svn export --force $SVNROOT/trunk -N . Atrunk Atrunk/top.mk Exported revision 50141. # Replace 1.6.13 rpm with 1.6.12 [cseaw...@localhost foo]$ svn export --force $SVNROOT/trunk -N . A. Atop.mk Exported revision 50141. - cls
Re: svn export bug in 1.6.13
http://subversion.tigris.org/issues/show_bug.cgi?id=3727 Chris Seawood wrote on Fri, Oct 29, 2010 at 10:04:17 -0700: Hi, I just ran across a bug in the 1.6.13 release. Historically, 'svn export $SVNROOT/$PATH .' has just exported the contents of $PATH into the current directory. Under 1.6.13, the client creates a subdir named after the last directory component of $PATH and puts the contents there. This change in behavior breaks some of our release scripts and we've been forced to downgrade to 1.6.12. # 1.6.13 [cseaw...@localhost foo]$ svn export --force $SVNROOT/trunk -N . Atrunk Atrunk/top.mk Exported revision 50141. # Replace 1.6.13 rpm with 1.6.12 [cseaw...@localhost foo]$ svn export --force $SVNROOT/trunk -N . A. Atop.mk Exported revision 50141. - cls
