I'm constrained to use Subversion 1.6.x, and this breaks the Subversion bundle I have. I did try checking out the current bundle into /Library/Application\ Support/TextMate/Bundles, but that seems not to have helped.
Is there any relief for this? Either a new bundle or some Subversion properties I can set?
I searched the Nabble archive for this list, and looked back a few months, but found nothing relevant.
— F
On Aug 19, 2009, at 8:30 AM, Allan Odgaard wrote:
On 18 Aug 2009, at 19:19, Fritz Anderson wrote:
I'm constrained to use Subversion 1.6.x, and this breaks the Subversion bundle I have [...]
How so? I am using 1.6.3.
In previous versions "svn update" would print a straightforward file- status list and exit. Now:
===== $ svn --version svn, version 1.6.2 (r37639) compiled May 20 2009, 01:36:41
$ svn update Conflict discovered in 'test/unit/person_test.rb'. Select: (p) postpone, (df) diff-full, (e) edit, (mc) mine-conflict, (tc) theirs-conflict, (s) show all options: =====
and the tool waits on stdin; the Subversion bundle I'm using doesn't expect that. I'm willing to believe there are environment variables or directory properties that are mis-set.
— F
On 19 Aug 2009, at 16:20, Fritz Anderson wrote:
[...] In previous versions "svn update" would print a straightforward file- status list and exit. Now: [...] the tool waits on stdin; the Subversion bundle I'm using doesn't expect that. I'm willing to believe there are environment variables or directory properties that are mis-set.
We would need to give ‘--non-interactive’ to svn to prevent this.
A “new” svn bundle is in the works which I think does handle this properly, it can be found here: http://svn.textmate.org/branches/Subversion%20(Interactive%20Input).tmbundle... — I hope this will simply replace the old one, but I think Luke still has a few things he wants to do before pushing it as main.
I’ll ping Michael about fixing the default update command.
-
Allan Odgaard -
Fritz Anderson