:O What's that people thing?? (I'm too shaky too look at the code :P)

Hmm, now I need a password to get in

Okay, I'm about ready to throw in the towel on svn.

1. Can't make it commit after adding a file.
2. Even though I've set up permissions, it never prompts me for a username or password and allows me to both read and write.

It just doesn't fucking work right.

No. Apparently no-one can help me out, and the documentation is ass.

Wish I could help.

At this point, I'm not switching to a different one. I've spent too long trying to get this one to work to start all over again, now.

Another option:
post to their mailing list http://subversion.tigris.org/servlets/ProjectMailingListList , take a deep breath and let your wife give you a massage. Relax afterwards with a movie. Don't check the mailing list before you're entirely relaxed again (today is certainly forbidden).

LOL @ jos :)

They ARE the devil.. I just can't handle them.. Way too complicated :(

The only way to tell them is via the mailing list. A kind of vicious circle, isn't it? :-D

Anyway I noticed the SVN server has been removed..? The Url gives me a 404 :)

Don't get me wrong, Iam always way too impatient ;-)

Well, they say they'll have to get back to me tomorrow.

So, unless anyone here has any great ideas, it looks like I didn't make that "End of November" deadline.

For the record, here is where I am at...

My apache2 conf file for mysvndomain.com is:

<VirtualHost 67.18.176.227:80>
        ServerName mysvndomain.com
        DocumentRoot /applications/lussumo/mysvndomain/
        ErrorLog /applications/webalizer/mysvndomain/error.log
        CustomLog /applications/webalizer/mysvndomain/access.log combined
       
        <location /svn>
            Order allow,deny
            Allow from all
           
            DAV svn
            SVNParentPath /subversion
           
            # our access control policy
            AuthzSVNAccessFile /etc/apache2/auth-files/lussumo-svn-authzfile

            # how to authenticate a user
            AuthType Basic
            AuthName "Lussumo Subversion Repository"
            AuthUserFile /etc/apache2/auth-files/lussumo-svn-authfile   
           
            # only authenticated users may modify the repository
            <LimitExcept GET PROPFIND OPTIONS REPORT>
                Require valid-user
            </LimitExcept>
        </location>   
    </VirtualHost>

As you can see from the "location" declaration, I've created a folder in the root of my system called "subversion". I've chowned that folder to www-data:www-data (the apache user/group on Debian). I su'd to www-data and created a vanilla repository within that folder.

I have created the AuthzSVNAccessFile as follows:

# Directory specific authorization control
[groups]
owner = mark
vanilla-developers = mark

[/]
@owner = rw

[vanilla:/]
@vanilla-developers = rw
* = r

My idea here is that I want everyone to be able to browse the repository, but I only want the owner or vanilla-developers to be able to read AND write to the repository. I've currently got myself as the owner and I've only added myself as a developer. Others will follow once I get things working properly.

I've already got a system account for "mark". When I created my /etc/apache2/auth-files/lussumo-svn-authfile file, I gave "mark" the same password as the system "mark" account.

Once all of that was done, I did an "apache2ctl graceful" on the server.

Then I went to the repository on my local machine (via command prompt) and ran this:

svn import vanilla http://mysvndomain.com/svn/vanilla/ -m "Initial Import"


It did NOT prompt me for my password. I have tried this multiple times and I can't remember if it prompted me for my password the first time or not. I read through the SVN docs and found that yes, it does store a cache of authenticated users. I changed the svn config so that it should no longer store cached authentications (it should prompt for a username and password every time) just because I wanted to be sure that it wouldn't be open to everyone to modify. The docs said that even after you make those changes, it doesn't work for authenticated users who were already authenticated and you have to go delete those authentications. I went in to where it said in the docs they would be, and there was nothing there at all. So, I don't really know what to make of that.

So, I guess this is the first problem: it never prompted me for authentication.

At that point if I browsed to http://mysvndomain.com/svn/vanilla, it showed me the repository just fine.

After that I went to another folder on my local machine and checked out the repository's trunk folder

svn checkout http://mysvndomain.com/svn/vanilla/trunk vanilla


That worked fine and gave me everything I needed - again, without requiring a username and password (which is what I wanted).

Here is the second problem: I then modified a file and did an svn commit -m "Testing File Modifications". It did NOT prompt me for a username or password and it did the commit successfully.

Here is the third problem: I then created a phpinfo.php file in the root of my local vanilla folder. I did an "svn add phpinfo.php" and that worked. Then when I tried to commit the repository, I got this error:

    C:\applications\subversion\vanilla>svn commit -m "Testing New File"
    Adding         phpinfo.php
    svn: Commit failed (details follow):
    svn: PROPFIND request failed on '/svn/vanilla/trunk/phpinfo.php'
    svn: PROPFIND of '/svn/vanilla/trunk/phpinfo.php': 302 Found (http://mysvndomain.com)

After googling a LOT, all I can come up with is that this error happens when your virtual server's documentroot and your location declaration's folder overlap so apache doesn't know what to do with the file. And that obviously isn't the case here since my settings do not overlap.

Even if someone commits crap overwriting one of the files, it would still keep copies of all the old versions; the ability to rollback the whole program is one of the key benefits to version control systems.

I don't want to have to concern myself with x people performing modifications to the core. For the time being I'd prefer to concern myself with a select few who have permission to modify - and everyone else can just read.

I didnt mean to bring ya down, was just trying to be funny. :/

I knew it.. I woke up and thought mark had so much trouble with SVN that he hasn't released the new version :(

You probably have crossed this resource also but in case you didn't: the online version of "Version Control with Subversion" (o'reilly) There are some chapters (notably chapter 6) about apache and access control too.

http://svnbook.red-bean.com/

When you can't get stuff to work, and you've spend a lot of time on it, and it still doesn't work... just leave it, and try to use something else :) Else you'll get frustrated as hell! And for such a simple, clean and small project as Vanilla, you don't have to use high-tech subversion systems... but those are just my thoughts...

What time is it now in Canada? :)

Time doesn't actually pass in Canada.

Come on guys. Mark is working overtime to solve some problems to give us the newest release, and all I read are comments that betray a lack of appreciation of it.

all I read are comments that betray a lack of appreciation of it.

That isn't really fair, for a number of reasons:

1. If we didn't apprecate the work that has gone into Vanilla, we wouldn't be here; we'd be at some other forum software's site whining about the lack of their updates.


2. According to what Mark said in the beginning of the thread, 0.9.3 is ready, except for SVN tree problems. As I have said twice before, this is incredibly silly; toss the files in a zip and sort out the version control stuff after you get the rabid Vanillaphiles (me) off your back.


3. Short of paypalling cash, there really isn't any way other than forum whining to spur Mark's creative spirit.

I decided to leave the svn problems behind and work on the one last big thing for the next rev: feeds.

I've made Atom and RSS2 extensions. Both of them work based on the scope of the page. So, if you run a search on the search page and then click on the Atom or RSS2 button, you get *those* results. The same goes for if you apply filters to the discussion index. It also works on the comments page.

It came to me last night when I was trying to think of what else to do to clear my head. It's a pretty slick solution, actually.

I'm not a feed-user, so you guys may want to have some different info in some of the fields, but we can work that out after it's released.

Anyway. That's done. I'm going to eat some food and then get back on SVN. I had some ideas for how to fix it today while I was working on the feeds.

No worries, mini.

If I can't get svn working tonight, I'll release a zip.

Is there any upgrade procedures or is it just file edits you've made?