For some reason, I get the following when I try to svn commit through TextMate:
svn: Commit failed (details follow): svn: OPTIONS request failed on '/path/to/trunk/' svn: OPTIONS of '/path/to/trunk/': authorization failed ( http://svn.server.net/)
Commits work, however, through the terminal.
Regardless, I trashed the cached authorization and (for the sake of sanitation) checked out a brand new copy of the code (re-providing authorization) with the terminal, but after making a cosmetic change to a file with TextMate, a subsequent commit fails (while Terminal successfully commits the file).
Am I missing something here? I've successfully used the svn bundle with a different setup.
On 22. Jun 2007, at 21:34, Stephen Celis wrote:
For some reason, I get the following when I try to svn commit through TextMate: [...] Commits work, however, through the terminal.
Is password requested in the Terminal? or does it use a cached authorization?
It might be related to the options handed to svn when called from TM or it might be something about which file is used as the path to commit.
Allan Odgaard <throw-away-1@...> writes:
On 22. Jun 2007, at 21:34, Stephen Celis wrote:
For some reason, I get the following when I try to svn commit through TextMate: [...] Commits work, however, through the terminal.
Is password requested in the Terminal? or does it use a cached authorization?
It might be related to the options handed to svn when called from TM or it might be something about which file is used as the path to commit.
The password is not requested in the Terminal, so I'm sure it's cached.
It's strange, TM obviously executes svn (the path is configured correctly, and I get the error message), but why would it execute it differently than the Terminal?
-
Allan Odgaard -
Stephen Celis