emory
Thu, 9 Mar 2006 @ 05:43 ¶


Authentication realm:  rousette.org.uk
Password for ‘guest’:
subversion/libsvn_ra_dav/util.c:826: (apr_err=175002)
svn: PROPFIND request failed on ‘/svn’
subversion/libsvn_ra_dav/util.c:296: (apr_err=175002)
svn: PROPFIND of ‘/svn’: 403 Forbidden (http://www.rousette.org.uk)

</pre>

I used ‘guest’ as the password. 

Oops.

squiddle
Thu, 9 Mar 2006 @ 20:51 ¶

still not working :( but download works. so it is no big deal.

keep going on tracks. i like it.

bsag
Fri, 10 Mar 2006 @ 10:06 ¶

squiddle and david: Well, that?s a bit weird, because it really does work fine here when I?m logged in as guest. I tried a new checkout just to be sure. Are you sure that your svn installation is working OK?

Subversion can be a bit tenacious in hanging on to old usernames and passwords, I?ve found.

Marco Wise
Tue, 21 Mar 2006 @ 01:43 ¶

I received the same error message as emory. I think it?s due to an extra space between svn/ and the line continuation character \ in the command above.

The command that worked for me is:

svn co?username=guest http://www.rousette.org.uk/svn/\
tracks-repos/tags/tracks-1.04 tracks-1.04

Chris
Mon, 27 Mar 2006 @ 22:09 ¶

The download link isn’t working for me. I’ve tried using Safari, Firefox and Camino. I think it has something to do with ExpressionEngine and your .htaccess file. ExpressionEngine is intercepting the download link and trying to parse it.

bsag
Tue, 28 Mar 2006 @ 08:48 ¶

Chris and brain: It was an .htaccess issue, which I’ve solved now. It seems to be working OK now.

TC
Thu, 30 Mar 2006 @ 08:04 ¶

Tracks is great but Ruby on rails is just such a MESS! I wish you have built it in PHP instead. I think this is my 6th attempt to install and it always fails somewhere. Ruby is a jungle of incompatible component versions and mystical errors.

brian
Thu, 30 Mar 2006 @ 17:32 ¶

bsag: i was able to download tracks via SVN. It works GREAT!! Good job!

TC: I had a lot of trouble starting out to get Ruby on Rails working. Give us some more details and hopefully we can help you out. It took me about 10-15 solid hours to get stuff working, but now that I have the basic configuration ideas under my belt, I can create rails apps quickly. Rails is great, it just takes some ‘tinkering’ to get it working.

Are you on your own machine or shared hosting? Have you tried the various tutorials that are online? Have you checked out the wiki? Have you checked out the IRC chat rooms?

I will tell you that it took me a long time to figure out what the problem was with my rails configuration, but once I saw what the problem was, the fix took about 5 minutes. Remember: log files are your friend.

bsag
Sun, 9 Apr 2006 @ 10:25 ¶

Mirta: Rather than erasing your Tracks 1.03 install, I would create a new directory and a new database and install Tracks 1.04 into that. Then, if everything goes well, you can delete the old installation. The database structure has changed, so you do need to create a new database or update the old one to get Tracks 1.04 to work.

If you follow the instructions carefully, you should be OK. Note that some people find that ‘rake migrate’ doesn’t work initially, so the alternative instruction to use ‘rake db_schema_import’ might be needed, and should work fine.

Software
Tue, 8 Apr 2008 @ 14:30 ¶

Clear, concise instructions- thanks very much!