![]() ![]() And Nichola looks so happy that Lili is interested in this topic. Gilbert is just like, 'here you can have this gun, Ive got so many back at the mansion'. You must previously have locked the files using the Subversion lock command. Dante is like, 'I really dont want you to have this, but if it keeps you safe then here'. Now the path looks different in the address bar. A Developers Guide for the JDeveloper Subversion VCS extension. So far, so good.īut when I navigate to the 'destination' directory, Windows explorer seems to resolve the symlink all of a sudden. When first navigating to the 'source' directory of the move (via the directory symlink), the path is still showing with the symlink name. Well, upon further inspection, it turns out the directory path changes while I am navigating around in explorer from the 'source' directory to the 'destination' directory of the move. However now the "database is locked" messsage appears. Normally a SVN popup appears and SVN will move your files inside the repo. In order to move a file with turtoise svn you can cut ( CTRL- X) the files using Windows explorer first, then select Paste from the turtoise SVN context menu. ![]() Let's see how this can go wrong while moving files for instance: My local SVN directory is a actually directory symlink to the real local SVN repo folder. If the lock problem disappears, then the problem is with your Apache http configuration.In case you use symbolic links on your file system, note that SVN can get confused as well. Did you do a dump and load from before? Did you do an svnadmin upgrade? Upgrading from 1.5 to 1.7 is a big, big change in the repository structure. Do you get the same error? If so, there's a problem with your repository. To prevent Subversion 1. You will need to update your repository's conf\nf file to enable the passwd file, and then update passwd to include a few user names and passwords.ĭo a clean checkout, and then try doing a lock. Shutdown Apache http and start the repository using the svnserve command (which should come with Subversion server). ![]() Let's try to eliminate Apache as the problem. This tutorial will walk you through setting up a wiki with ikiwiki. You changed two things on us: The version of the repository, and the version of the OS. you through setting up a wiki that is stored in Subversion and that has -optional support for commits from the web. The question is whether this is a problem with the repository or your Apache http instance. work, but not locking files in the repository?Īpparently, after investigating the event log, it seems that httpd.exe keeps crashing, blaming mod_dav.so:įaulting application name: httpd.exe, version: 2.2.21.0, time stamp: 0x4e6a3015įaulting module name: mod_dav.so, version: 2.2.21.0, time stamp: 0x4e6a3023 However, using the command-line svn tool from a console with administrator privileges works without problems.Ĭould this really just be a problem with read/write permissions? And if so, why does checkout/commit/etc. 'D:\SVNRepositories\TempRepo_OnlyToPlayWith\db\write-lock': Some more investigation has uncovered that, when I don't go through https, but use Tortoise on the server directly to the repo using file:///, I get the following error message: Help me, StackOverflow - you're my only hope. I've been searching for what the problem might be, without luck. (Where is the site where subversion is hosted) Checkout and commit works, however when users try to lock files, they get this message:Įrror: LOCK of '/SVN/TempRepo_OnlyToPlayWith/Documents/Test.docx': Could not readĮrror: status line: An existing connection was forcibly closed by the remote host. I just migrated some Subversion repositories from a Windows 2003 server to a Windows 2008 server, and upgraded Subversion from 1.5 to 1.7 in the process. ![]()
0 Comments
Leave a Reply. |