Am 13.03.2005 um 17:11 schrieb Allan Odgaard:
<snip> I haven't seen this error before, and I just did a fresh checkout to /tmp as anon w/o problems.
I'm using (from Darwin Ports): svn, version 1.1.1 (r11581) compiled Jan 3 2005, 08:45:07
The above does look like maybe the login/password is not accepted. Try
- remove --username/--password from the options to see if it then
prompts for password and 2) remove the ~/.subversion directory (where it caches authentication)
#2 will remove cached authentications, your configuration (if you have one) etc. -- so maybe back it up first, if you think there might be info in there you need.
Tried, does not work:
[moerk@mungon]~ 501 % rm -rf Bundles [moerk@mungon]~ 502 % rm -rf .subversion [moerk@mungon]~ 503 % svn co http://macromates.com/svn/Bundles/trunk Bundles Authentication realm: http://macromates.com:80 macromates.com Password for 'moerk': Authentication realm: http://macromates.com:80 macromates.com Username: anon Password for 'anon': svn: REPORT request failed on '/svn/Bundles/!svn/vcc/default' svn: REPORT of '/svn/Bundles/!svn/vcc/default': 503 unknown method (http://macromates.com)
Would it be possible to make the entire trunk available as a .tbz or something similar?
I could, but it would be nice to figure out why svn isn't working :)
Yep.
(Actually, rsync would be absolutely perfect for me, but I can understand that I might be in the minority here...)
svn should be better than rsynch, I have the repository checked out as ~/Library/Application Support/TextMate/Bundles -- that way, I just need to cd to that directory and do 'svn up' when there's new stuff, and I can naturally also commit my customizations directly.
From my perspective right now, not yet being tempted to contribute, rsync looks superior: I have it working in various setups, some over ssh, some over http. Syncing is trivial. rsync comes with every vanilla OSX - thus it would be possible to sync the Bundle Directory via a Command from TM (I _do_ know this would also be possible with svn - once I have it working :-)). It might even be possible to put a nifty "Get latest Bundles" Button into the Bundle Editor GUI and have it working in every users setup (svn does not come with a vanilla OS X...).
Can anyone with the Fink svn-client-ssl please try to do a full checkout of the repository, preferably with the same version as Mark, to check if the problem is related to this build of svn?
Meanwhile, I am trying rebuilding svn from the sources - it _should_ not change anything, but things like this _have_ happened in the past with fink. :(
Thank you for your prompt response (and on a sunday, no less! We all need to get out more! ;)),
Greetings from deepest Bavaria,
Mark Sapa