Subversion - Commit problems

XML, Perl, Python, and other languages can be discussed here, even if it isn't PHP (We might forgive you).

Moderator: General Moderators

Post Reply
User avatar
Hades
Forum Commoner
Posts: 35
Joined: Mon May 08, 2006 4:49 pm

Subversion - Commit problems

Post by Hades »

Hi

I've got a subversion server set up on a box running SuSE Linux 9.3 Pro.

I can access the repositories via my web browser just fine.
I can also checkout and import with the repositories using TortoiseSVN.

The problem I'm having is that I cannot commit new files into the repository.

I have the following structure.

Code: Select all

root
   |-tags
   |-branches
   |-trunk
         |-includes
         |-models
         |-actions
         |-lib
         |-sql
         |-templates
         |-index.php
         |-common.inc.php
         |-rebuild.php
I am trying to add an XML file to the "sql" directory called "schema.xml".

I created the file. I then right-clicked on it and selected TortoiseSVN->Add.

It put the little plus sign on the files icon.

I then right-clicked on it again and selected SVN Commit...

It gave me a dialogue box with the schema.xml file listed. I tick it and click ok and then it gives me the following error...

Code: Select all

Adding: F:\Lee\websites\edit-pc-site\trunk\sql\schema.xml  
Error: Commit failed (details follow):  
Error: PROPFIND request failed on '/edit-pc-site/trunk/sql/schema.xml'  
Error: Could not open the requested SVN filesystem
I've been through the svn website so many times now and can't find anything even remotely similar.

All the repository files are owned by the web server and chmod 777.

I'm all out of ideas.. can anyone offer me a lifeline?
magicwizard
Forum Newbie
Posts: 5
Joined: Sat Oct 15, 2005 3:49 pm

Post by magicwizard »

afaik svn uses BerkleyDB as filesystem, maybe any problem with that?
User avatar
Hades
Forum Commoner
Posts: 35
Joined: Mon May 08, 2006 4:49 pm

Post by Hades »

Nothing to do with berkley, I'm using the native file system instead.

Any other ideas?
User avatar
Christopher
Site Administrator
Posts: 13596
Joined: Wed Aug 25, 2004 7:54 pm
Location: New York, NY, US

Post by Christopher »

There looks like a configuration difference between "F:\Lee\websites\edit-pc-site\trunk\sql\schema.xml" and "/edit-pc-site/trunk/sql/schema.xml". Is document root "F:\Lee\websites\" or "F:\Lee\websites\edit-pc-site\" ?
(#10850)
User avatar
Hades
Forum Commoner
Posts: 35
Joined: Mon May 08, 2006 4:49 pm

Post by Hades »

"F:\Lee\websites\edit-pc-site\trunk\sql\schema.xml" is on my local machine.

I imported "F:\Lee\websites\edit-pc-site\" into the repository, then deleted it from my local machine and checked it out from the repository before doing anything else.

I then added the file "schema.xml" to the "F:\Lee\websites\edit-pc-site\trunk\sql\" directory on my local machine. Then used the "Add" command on that file in TortoiseSVN, then tried to commit. I get the error when trying to commit.

"/edit-pc-site/trunk/sql/schema.xml" is on the server.

The full path is "/usr/local/svnroot/edit-pc-site/trunk/sql/schema.xml" but the "schema.xml" file does not yet exist in the repository.

EDIT: I managed to do it now... wierd.

It seems that it doesn't like commiting new files unless they're in a new directory and the directory and the file(s) are added at the same time.
User avatar
Maugrim_The_Reaper
DevNet Master
Posts: 2704
Joined: Tue Nov 02, 2004 5:43 am
Location: Ireland

Post by Maugrim_The_Reaper »

A chicken before the egg problem, Hades? :)
User avatar
Hades
Forum Commoner
Posts: 35
Joined: Mon May 08, 2006 4:49 pm

Post by Hades »

I'm not sure whether it's a problem with the latest versions of Apache2 and Subversion together or if it's a problem with TortoiseSVN.

It seems as though it's trying to do a PROPFIND on the file I try to commit... which in the case of a new file will fail since it doesn't exist in the repo yet.


Looking around some more on the net I found only one thread regarding this sepecific problem and that was on about page 23 of a google search.

In that they said it appears to be a problem with the latest versions of Apache2 and Subversion... something has gone wrong in the compatibility area for them it seems.

However, if that were the case surly it would fail earlier... PROPFIND is initiated by the client isn't it? Therefore it's the client trying to do a command that won't work?

I'm sooo confused. :?
Post Reply