Re: linux subversion checkout hangs since server was virtualized
Jörg Buchberger lists at joerg-buchberger.de writes: First of all, thanks for the quick response. Hmm, perhaps I should mention that the server is windoze (2003) and that this is not a normal apache setup but visualsvnserver (2.1.5) - however, I tried both - ordinary apache setup and visualsvnserver - either way it worked out fine on physical host, yet not in virtual environment. I'm afraid, I won't be able to compile myself as suggested by the FAQ entry. Regards, Joerg Hello Joerg, if it's working on Windows but not on Linux: did you compare the network traffic with wireshark? Maybe you make a checkout on both OSs without SSL, so you get all messages. Further more you can also compare the old host with the virtualized host... Best regards, Charly
Combining public and private paths
Dear Colleagues, I am trying to setup the following policy: a private repository with some public paths. Is such configuration supported at all? The following configuration: == conf/svnserve.conf: anon-access = read auth-access = write authz-db = authz == conf/authz: [/] @noc = rw [/foo] $anonymous = r $authenticated = rw does not work. A valid user from the noc group receives the following reply: $ svn diff -c2237 www.txt svn: Unreadable path encountered; access denied If I change anon-access = read to anon-access = none, it begins to work for the valid user, but there is no anonymous access to anyone even to svn://myserver/foo despite the $anonymous = r clause. What am I doing wrong? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru
svnadmin create complains about subrepositories
Hi, I just recently upgraded to svn 1.6.12 and had to realize svnadmin create wont let me create Repositories inside directories where have already repositories been created. Why is that a feature and can you please add an --force switch to still being able to create Repositories within the path of another? Thank you! Regards Fabian
RE: svnadmin create complains about subrepositories
I just recently upgraded to svn 1.6.12 and had to realize svnadmin create wont let me create Repositories inside directories where have already repositories been created. Why is that a feature and can you please add an --force switch to still being able to create Repositories within the path of another? I guess my question would be why do you want to do that... and I would also say DON'T do that. Bob
Re: svnadmin create complains about subrepositories
On Thu, Feb 10, 2011 at 04:15:16PM +0100, Fabian Richter wrote: Hi, I just recently upgraded to svn 1.6.12 and had to realize Which version did you upgrade from? As far as I can tell this behaviour has existed for some time, since at least 1.5. Did you upgrade from an earlier version which had different behaviour? I've checked current trunk and 1.5, and the behaviour is the same in both. The check only works within the top-level directory of the repository, though: $ ls README.txt conf/db/ format hooks/ locks/ $ svnadmin create repos subversion/libsvn_repos/repos.c:1203: (apr_err=165002) svnadmin: 'repos' is a subdirectory of an existing repository rooted at '' $ cd db/ $ svnadmin create repos $ cd .. $ cd hooks/ $ svnadmin create repos $ svnadmin create wont let me create Repositories inside directories where have already repositories been created. Why is that a feature Because it's likely a mistake. Nesting repositories is not what many people want. and can you please add an --force switch to still being able to create Repositories within the path of another? That's a reasonable request, I think. Not a usual use case but why not? But I also think that the check for an existing repository should work within any subdirectory of the repository, not just within the top-level directory of the repository. Can you help by filing a DEFECT issue in our issue tracker (http://subversion.tigris.org/issue-tracker.html) requesting that the check be expanded to also work within subdirectories of a repository? And an ENHANCEMENT issue that allows the check to be overridden by a new command line option (named something like '--allow-nested-repositories' since we don't use --force anymore because it's not always clear what's being forced). You can use this link to refer to this thread from the issue as required by our bug filing guidelines: http://svn.haxx.se/users/archive-2011-02/0162.shtml Maybe you'd even be willing to try to send a patch for either of these items? Thanks, Stefan
Subversion Permissions Question.
Hello, A Subversion server with a big repository was inherited to me recently and I'm trying to figure out its configuration. We are using an old version that we are going to upgrade as soon as we are confident that we understand the current configuration and setup. We have subversion 1.4.3 (r23084) installed on a SunOS. The server configuration is svnserve over SSH. I have experience administering other source control tools, like Perforce, ClearCase, MKS, PVCS, etc. on Unix and Windows. I read the the book 'Version Control with Subversion' and I still have some questions. The authz file contains the following three lines. If I understood correctly, svnadmin will have rw permissions to the whole repository and the rest of the users will have read-only access. But all users are able to 'checkout' and 'submit' files. So what are these permissions really doing? [/] svnadmin = rw * = r I see the files svnserve.conf and authz on different subdirectories. Shouldn't these files be only in the main or initial folders of the repository? Other questions that I have are: - How can I get a full repository layout? - How can I get the repository history since the revision 0 to the newest? - How can I get the list of revisions or commits for the whole repository? I'm doing using 'svn log' but I only get the current folder not recursive to the whole repo. Also, I don't think I understand when a repository is a repository and when it is a directory under that repository. I checked some of the folders under the repository directory structure and I found that i can follow the directory structure up to certain point and then I cannot. For example: svn+ssh://user@server/Repo_name/main_folder1 /main_folder1/ subfolder1 /main_folder1/ subfolder1/trunk /main_folder1/ subfolder1/branches /main_folder1/ subfolder1/tags /main_folder2/ subfolder1 /main_folder2/ subfolder1/trunk /main_folder2/ subfolder1/branches /main_folder2/ subfolder1/tags I cannot follow using a normal cd command the directory level of 'trunk', 'branches' and 'tags' in the repository directory. I only have the folders conf, dav, db,format, hooks, locks, README.txt but not 'branches', 'tags' and 'trunk'. So, are main_folder1 and main_folder2 two different repositories or only one under Repo_name? Where I can find information about the database FSFS layout, schema and design? I'm sorry if this are silly questions, please let me know of any book or other information that will help me understand better the subversion whole system. Thank you. Monica Sanchez
Re: svnadmin create complains about subrepositories
On Feb 10, 2011, at 09:59, Stefan Sperling wrote: and can you please add an --force switch to still being able to create Repositories within the path of another? That's a reasonable request, I think. Not a usual use case but why not? Really? What possible reason could exist for doing this? :)
Re: svnadmin create complains about subrepositories
Am Thu, 10 Feb 2011 11:24:09 -0600 schrieb Ryan Schmidt subversion-20...@ryandesign.com: On Feb 10, 2011, at 09:59, Stefan Sperling wrote: and can you please add an --force switch to still being able to create Repositories within the path of another? That's a reasonable request, I think. Not a usual use case but why not? Really? What possible reason could exist for doing this? :) We are using Redmine as a projectmanagement Tool and there projects can have subprojects. This hierarchy we also want in the file system level so we can see from the url of the repos which category it belongs to. @Stefan: I have no idea what the former Version was, but I upgraded from debian Lenny to squeeze so it was probably 1.5.1. Would it hurt to add a force switch? I mean its at the users risk isnt it? Fabian
Re: svnadmin create complains about subrepositories
On 2/10/2011 10:19 AM, Fabian Richter wrote: Am Thu, 10 Feb 2011 13:07:27 -0500 schrieb Bob Archerbob.arc...@amsi.com: I expect that this all happens inside the repository. A repository's contents can have whatever folder layout you want. However, the repositories themselves on the server each need to be peers. You can't nest repos nor should you need to. To be frank: I dont see why I am not able to create nested repos or what you mean that they need to be peers... You say a repo folder can have the content i need it to have. I need them to have other repos. To be sure we are talking about the same thing: /repos1 /repos1/repos2 /repos1/repos3 something like that. And the comparison to mysql DB doesnt make sense, because in a dbms I am able to deklare multiple databases for the same server or root dir, thats what is apparently not possible for svn... In Subversion, the subdirectories are stored within a single repository. You are not creating a repository that holds a single directory of files; a repository is a versioned file system that can have subdirectories within it. One repository directory = multiple controlled file directories in a virtual, versioned file system. Rather than nested repositories as you suggest, the usual way of doing things is to have subprojects within a single repository: /repos /repos/subproject1 /repos/subproject2 /repos/subproject3 These are all virtual directories, and you can check out or traverse them separately even if they are managed by a single repository and its server. Otherwise you would have multiple repositories stored in directories which are peers of each other (cf. SVNParentPath in httpd.conf), and your workspace setup script would check out the necessary directories from the individual repositories. Storing repository files (which are a kind of database, BTW) inside a directory that hold files for another repository is very likely to cause problems someday. The repository files are managed by the Subversion software, and it has certain implicit assumptions about what will be there. It's not expecting arbitrary data in arbitrary places. Support of this feature would greatly constrain the developers and I wouldn't expect them to like it (I know I wouldn't, if I were a Subversion developer). -- David Chapman dcchap...@acm.org Chapman Consulting -- San Jose, CA
Re: svnadmin create complains about subrepositories
Fabian Richter wrote: To be frank: I dont see why I am not able to create nested repos A Subversion repository, from the point of view of the filesystem it lives on, is intended to be (mostly) a black box that you interact with through the SVN repository access layer you've configured. or what you mean that they need to be peers... You can have a set of repositories side-by-side like so: /path/to/repo1 /path/to/repo2 /path/to/repo3 You can't put another repository inside another, *at the same filesystem level*, like so: /path/to/repo1 /path/to/repo1/repo2 /path/to/repo1/repo3 You *can*, if you really want, add a filesystem location containing a SVN repository as content to an existing repository... although how you'd access it usefully is another matter. You say a repo folder can have the content i need it to have. I need them to have other repos. To be sure we are talking about the same thing: /repos1 /repos1/repos2 /repos1/repos3 Can you expand on why you really need to do this? Why can't you use folders in a single repository, or just leave /repos1 as a regular filesystem directory, that contains repositories? To ask things a bit differently, does arbitrary content under the URL that leads to /repos1 need to be version-controlled (eg, /repos1/file1), or is all the version-controlled content one layer deeper (/repos1/repos2/file1)? something like that. And the comparison to mysql DB doesnt make sense, because in a dbms I am able to deklare multiple databases for the same server or root dir, thats what is apparently not possible for svn... Well, when you create a MySQL database, the tabledefs at least all go into /path/to/mysqldir/database2 - you can't put them in /path/to/mysqldir/database1/database2. Subversion is pretty much the same, except you as administrator have somewhat more control of the filesystem location of each repository; it's perfectly possible (if inadvisable unless you need to isolate repo groups) to put a couple of repositories under /path/to/repgroup1, and another group under /another/place/repogroup2, and a lonely one off by itself in /some/other/repo. -kgd
Re: svnadmin create complains about subrepositories
On Feb 10, 2011, at 12:55, Kris Deugau wrote: something like that. And the comparison to mysql DB doesnt make sense, because in a dbms I am able to deklare multiple databases for the same server or root dir, thats what is apparently not possible for svn... Well, when you create a MySQL database, the tabledefs at least all go into /path/to/mysqldir/database2 - you can't put them in /path/to/mysqldir/database1/database2. Exactly. Exactly!
Re: svnadmin create complains about subrepositories
On Feb 10, 2011, at 09:15, Fabian Richter wrote: Why is that a feature and can you please add an --force switch to still being able to create Repositories within the path of another? I should add: this check was added to Subversion to prevent people from doing things that make no sense. If you believe you know better than Subversion (and I continue to think you do not in this case) then it is of course trivial to bypass this check: $ svnadmin create repo1 $ svnadmin create repo1/repo2 svnadmin: 'repo1/repo2' is a subdirectory of an existing repository rooted at 'repo1' $ svnadmin create repo2 $ mv repo2 repo1 $ ls repo1 README.txt db hooks repo2 confformat locks $ Et voilà, you have repo2's directory inside repo1's directory. So no --force switch or modification of the Subversion source code is necessary to accomplish this questionable goal.
svn switch problems
Hello, I'm trying to do an svn switch and keep getting an error: svn switch https://.../services/branches/ementor . svn: Directory 'ementor' is missing svn: Directory 'ementor' is missing [hostname]$ The directory is currently switched to the trunk. The trunk has no ementor directory. There is an ementor directory in the ementor branch. Why doesn't svn create the ementor directory, since that directory is in the branch I'm switching to? I tried an svn cleanup, but that didn't work, I still got the error. Thanks, Doug
Re: svnadmin create complains about subrepositories
On Thu, Feb 10, 2011 at 07:02:18PM +0100, Fabian Richter wrote: Am Thu, 10 Feb 2011 11:24:09 -0600 schrieb Ryan Schmidt subversion-20...@ryandesign.com: On Feb 10, 2011, at 09:59, Stefan Sperling wrote: and can you please add an --force switch to still being able to create Repositories within the path of another? That's a reasonable request, I think. Not a usual use case but why not? Really? What possible reason could exist for doing this? :) I have no idea, to be honest. But then again I'm not going to guess. Maybe someone can present a good use case for this? Dunno. We are using Redmine as a projectmanagement Tool and there projects can have subprojects. This hierarchy we also want in the file system level so we can see from the url of the repos which category it belongs to. I would recommend against doing this because it's usually not done this way. If you do this you might run into various problems. Especially if you're ever going to use backup scripts or other repository management tools that exist -- they might fail in some way. You should put your repositories into a flat hierarchy. But that does not prevent you from naming them in accordance with the hierarchy you see in redmine: project1 project1-subproject1 project1-subproject2 project1-subproject2-subproject1 project2 ... etc. Basically, use dashes instead of slashes. You can also put repositories for different top-level projects into separate directories if a single flat hierarchy becomes too cumbersome: project1-repositories/ -- a normal directory project1 -- a repository project1-subproject1 -- a repository project1-subproject2 -- a repository project1-subproject2-subproject1 -- a repository project2-repositories/ -- a normal directory project2 -- a repository ... etc. @Stefan: I have no idea what the former Version was, but I upgraded from debian Lenny to squeeze so it was probably 1.5.1. Then the behaviour isn't new. I thought you were implying that what you were trying to do was working with an older version? Would it hurt to add a force switch? I mean its at the users risk isnt it? Let's add it only if someone comes up with a good reason for having it. Thanks, Stefan
possible bug - org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
Hello there, I am writing because my Subversion is reporting a situation that it feels is a bug. Unfortunately, I am not really a programmer (yet), so please accept my apologies in advance for any shortcomings in this report. I am also not dead certain that when it says please report, it means the report is to go to you, to Oracle, or? Per the Synaptic package manager on my Ubuntu 10.04, my Subversion is up to date. I was attempting to commit a shiny new Wordpress folder to my svn. It happens every time I try. Here's the report - hope it is helpful: - Message: org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report svn: Commit failed (details follow): svn: Directory '/var/www/kendradodd/blog/wp-content/themes/modularity-lite/.svn' containing working copy admin area is missing Exception Stack Trace: org.tigris.subversion.svnclientadapter.SVNClientException: org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report svn: Commit failed (details follow): svn: Directory '/var/www/kendradodd/blog/wp-content/themes/modularity-lite/.svn' containing working copy admin area is missing at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.commit(AbstractJhlClientAdapter.java:325) at org.tigris.subversion.subclipse.core.commands.CheckinResourcesCommand$1.run(CheckinResourcesCommand.java:118) at org.tigris.subversion.subclipse.core.SVNProviderPlugin$5.run(SVNProviderPlugin.java:469) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782) at org.tigris.subversion.subclipse.core.SVNProviderPlugin.run(SVNProviderPlugin.java:464) at org.tigris.subversion.subclipse.core.commands.CheckinResourcesCommand.run(CheckinResourcesCommand.java:94) at org.tigris.subversion.subclipse.core.SVNTeamProvider.checkin(SVNTeamProvider.java:139) at org.tigris.subversion.subclipse.ui.operations.CommitOperation.execute(CommitOperation.java:124) at org.tigris.subversion.subclipse.ui.operations.SVNOperation.run(SVNOperation.java:90) at org.eclipse.team.internal.ui.actions.JobRunnableContext.run(JobRunnableContext.java:144) at org.eclipse.team.internal.ui.actions.JobRunnableContext$ResourceJob.runInWorkspace(JobRunnableContext.java:72) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report svn: Commit failed (details follow): svn: Directory '/var/www/kendradodd/blog/wp-content/themes/modularity-lite/.svn' containing working copy admin area is missing at org.tigris.subversion.javahl.SVNClient.commit(Native Method) at org.tigris.subversion.javahl.SVNClient.commit(SVNClient.java:524) at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.commit(AbstractJhlClientAdapter.java:319) ... 13 more Session Data: eclipse.buildId=M20100211-1343 java.version=1.6.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86
Re: possible bug - org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
See this FAQ: http://subclipse.tigris.org/wiki/PluginFAQ#head-73584410a8d4fbad6781c7b16be39f6518410a61 The error usually means that some tool you are using deleted a folder and then recreated it. The problem is that this deletes the .svn metadata folder inside it. SVN 1.7 will solve this problem by not needing these .svn folders in every folder. Mark On Thu, Feb 10, 2011 at 4:00 PM, Shannon Dillman shannon.dill...@gmail.com wrote: Hello there, I am writing because my Subversion is reporting a situation that it feels is a bug. Unfortunately, I am not really a programmer (yet), so please accept my apologies in advance for any shortcomings in this report. I am also not dead certain that when it says please report, it means the report is to go to you, to Oracle, or? Per the Synaptic package manager on my Ubuntu 10.04, my Subversion is up to date. I was attempting to commit a shiny new Wordpress folder to my svn. It happens every time I try. Here's the report - hope it is helpful: - Message: org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report svn: Commit failed (details follow): svn: Directory '/var/www/kendradodd/blog/wp-content/themes/modularity-lite/.svn' containing working copy admin area is missing Exception Stack Trace: org.tigris.subversion.svnclientadapter.SVNClientException: org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report svn: Commit failed (details follow): svn: Directory '/var/www/kendradodd/blog/wp-content/themes/modularity-lite/.svn' containing working copy admin area is missing at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.commit(AbstractJhlClientAdapter.java:325) at org.tigris.subversion.subclipse.core.commands.CheckinResourcesCommand$1.run(CheckinResourcesCommand.java:118) at org.tigris.subversion.subclipse.core.SVNProviderPlugin$5.run(SVNProviderPlugin.java:469) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782) at org.tigris.subversion.subclipse.core.SVNProviderPlugin.run(SVNProviderPlugin.java:464) at org.tigris.subversion.subclipse.core.commands.CheckinResourcesCommand.run(CheckinResourcesCommand.java:94) at org.tigris.subversion.subclipse.core.SVNTeamProvider.checkin(SVNTeamProvider.java:139) at org.tigris.subversion.subclipse.ui.operations.CommitOperation.execute(CommitOperation.java:124) at org.tigris.subversion.subclipse.ui.operations.SVNOperation.run(SVNOperation.java:90) at org.eclipse.team.internal.ui.actions.JobRunnableContext.run(JobRunnableContext.java:144) at org.eclipse.team.internal.ui.actions.JobRunnableContext$ResourceJob.runInWorkspace(JobRunnableContext.java:72) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report svn: Commit failed (details follow): svn: Directory '/var/www/kendradodd/blog/wp-content/themes/modularity-lite/.svn' containing working copy admin area is missing at org.tigris.subversion.javahl.SVNClient.commit(Native Method) at org.tigris.subversion.javahl.SVNClient.commit(SVNClient.java:524) at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.commit(AbstractJhlClientAdapter.java:319) ... 13 more Session Data: eclipse.buildId=M20100211-1343 java.version=1.6.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: possible bug - org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
On Thu, Feb 10, 2011 at 16:00, Shannon Dillman shannon.dill...@gmail.com wrote: Hello there, I am writing because my Subversion is reporting a situation that it feels is a bug. Unfortunately, I am not really a programmer (yet), so please accept my apologies in advance for any shortcomings in this report. I am also not dead certain that when it says please report, it means the report is to go to you, to Oracle, or? Per the Synaptic package manager on my Ubuntu 10.04, my Subversion is up to date. Please be sure to specify the actual version of Subversion you're using. Up to date could have two meanings here - up to date with regard to what's in the Ubuntu 10.04 repository, or up to date with regard to Subversion releases. From what I can tell, Ubuntu 10.04 has Subversion 1.6.5 or 1.6.6, and the current official release of Subversion is 1.6.15.
Re: possible bug - org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
On Feb 10, 2011, at 15:19, Andy Levy wrote: Please be sure to specify the actual version of Subversion you're using. Up to date could have two meanings here - up to date with regard to what's in the Ubuntu 10.04 repository, or up to date with regard to Subversion releases. From what I can tell, Ubuntu 10.04 has Subversion 1.6.5 or 1.6.6, and the current official release of Subversion is 1.6.15. It could also mean up to date with what I think is up to date in one of the above two senses, which might be different from what is actually up to date.
Re: possible bug - org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
Thanks guys - I was just reporting a bug, and didn't expect help. It is much appreciated, and I now have things working. Ryan - that's why I qualified up to date with per the Synaptic package manager I am sorry I didn't specify further, which brings me to Andy - you were right. 1.6.6 is what's installed, and I should have known to dig a little deeper and not believe the package manager, since I JUST installed Wordpress itself from a download, since the version in the package manager was quite old. Mark - thank you for pointing me at the FAQ. I deleted the project, cleaned the Wordpress folders of everything .svn, re-created the project - and got the error back. Repeated the above, but instead of creating it as a PVP project, I created it as a general web project (I'm not really going to build anything). Et voila! Also thanks for the heads up on V 1.7 - I am really looking forward to that. Again, I appreciate the help and ideas. On Thu, Feb 10, 2011 at 4:44 PM, Ryan Schmidt subversion-20...@ryandesign.com wrote: On Feb 10, 2011, at 15:19, Andy Levy wrote: Please be sure to specify the actual version of Subversion you're using. Up to date could have two meanings here - up to date with regard to what's in the Ubuntu 10.04 repository, or up to date with regard to Subversion releases. From what I can tell, Ubuntu 10.04 has Subversion 1.6.5 or 1.6.6, and the current official release of Subversion is 1.6.15. It could also mean up to date with what I think is up to date in one of the above two senses, which might be different from what is actually up to date.
Re: .htaccess commit issue
On Feb 10, 2011, at 20:43, debu --- Debajit kataki wrote: This is an issue only while I try to commit via any GUI client/rep browser. Currently I am using Tortoise and I could reproduce it there. Some people also saw it in Eclipse which I am yet to reproduce. Via command line I have no issue at all to commit any ^.ht files. So i guess apache definitely is NOT the culprit here!!? I see some thread around this as well on the google: http://languor.us/eclipse-subversion-ra-layer-request-failed-could-not-read-status-line-errors Or is it more of a compatibility issue ? I am using Apache/2.2.15 (Unix), subversion-1.1.4-2, tortoise 1.6.0 I can't explain what you're seeing above, but please confirm -- are you really using Subversion 1.1.4 on the server? Versions earlier than 1.5 are not supported anymore, and you should upgrade to the current version, which is 1.6.15.
Re: Combining public and private paths
The problem is probably in the following. When anon-access is other than none, svnserve does not request authentication for some important operations like svn log, and I have found no way to force it to request authentication. This effectively breaks path based authorization. I have found some tricky solutions for the http access method (like defining two aliases for the same repository), but none for the svnserve method. Any help? Victor Sudakov wrote: I am trying to setup the following policy: a private repository with some public paths. Is such configuration supported at all? The following configuration: == conf/svnserve.conf: anon-access = read auth-access = write authz-db = authz == conf/authz: [/] @noc = rw [/foo] $anonymous = r $authenticated = rw does not work. A valid user from the noc group receives the following reply: $ svn diff -c2237 www.txt svn: Unreadable path encountered; access denied If I change anon-access = read to anon-access = none, it begins to work for the valid user, but there is no anonymous access to anyone even to svn://myserver/foo despite the $anonymous = r clause. What am I doing wrong? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru
Combining public and private paths
For what it's worth, I have run into the same problem and the only solution I have found is to switch to a different access method. As best as I can tell svnserve is simply not an option when trying to set up a repository with path based authentication when select areas are flagged inaccessible to anonymous users. I have recently switched from a svnserve to apache based setup and using the exact same authz-db file, svnserve failed to return svn log results for protected paths while apache worked correctly. The below issue on the SVN tracker I think refers to this issue and it has been open since Oct. 2009: http://subversion.tigris.org/issues/show_bug.cgi?id=3516 Anyway, I could be totally wrong here, but I do not think what you want to do is possible with svnserve. I hope I am mistaken, but if not, sorry to be the bearer of bad news. On Thu, Feb 10, 2011 at 9:30 PM, Victor Sudakov suda...@sibptus.tomsk.ru wrote: The problem is probably in the following. When anon-access is other than none, svnserve does not request authentication for some important operations like svn log, and I have found no way to force it to request authentication. This effectively breaks path based authorization. I have found some tricky solutions for the http access method (like defining two aliases for the same repository), but none for the svnserve method. Any help? Victor Sudakov wrote: I am trying to setup the following policy: a private repository with some public paths. Is such configuration supported at all? The following configuration: == conf/svnserve.conf: anon-access = read auth-access = write authz-db = authz == conf/authz: [/] @noc = rw [/foo] $anonymous = r $authenticated = rw does not work. A valid user from the noc group receives the following reply: $ svn diff -c2237 www.txt svn: Unreadable path encountered; access denied If I change anon-access = read to anon-access = none, it begins to work for the valid user, but there is no anonymous access to anyone even to svn://myserver/foo despite the $anonymous = r clause. What am I doing wrong? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru
diff-cmd =
Colleagues, I like very much the default output of the FreeBSD diff program. So I prefer using svn diff --diff-cmd=/usr/bin/diff -x --normal instead of just svn diff. However, when I put the line diff-cmd = /usr/bin/diff -x --normal into ~/.subversion/config, I get the following error message: exec of '/usr/bin/diff -x --normal' failed: No such file or directorysvn: '/usr/bin/diff -x --normal' returned 255 I guess it is trying to exec '/usr/bin/diff -x --normal' as a whole which is kind of expected. For the present, I have created a shell alias for the svn diff command, but I am curious what the correct ~/.subversion/config syntax is to achieve what I want? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru
Re: diff-cmd =
On Feb 10, 2011, at 23:33, Victor Sudakov wrote: I like very much the default output of the FreeBSD diff program. So I prefer using svn diff --diff-cmd=/usr/bin/diff -x --normal instead of just svn diff. However, when I put the line diff-cmd = /usr/bin/diff -x --normal into ~/.subversion/config, I get the following error message: exec of '/usr/bin/diff -x --normal' failed: No such file or directorysvn: '/usr/bin/diff -x --normal' returned 255 I guess it is trying to exec '/usr/bin/diff -x --normal' as a whole which is kind of expected. For the present, I have created a shell alias for the svn diff command, but I am curious what the correct ~/.subversion/config syntax is to achieve what I want? This looks like http://subversion.tigris.org/issues/show_bug.cgi?id=2930 i.e., you've found the current status quo; there is no better method currently available.
Re: diff-cmd =
Ryan Schmidt wrote: [dd] This looks like http://subversion.tigris.org/issues/show_bug.cgi?id=2930 i.e., you've found the current status quo; there is no better method currently available. I have always been told that I am a good tester (i.e. have the ability to come across bugs), but my rate of tripping on all the subversion rakes is alarming. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru
Re: Combining public and private paths
What the anon-access = none option does is remove the ANONYMOUS mech from the list of SASL mechs offered by svnserve (I see this in tcpflow). If this mech is present in the mech list, the svn client does not bother to authenticate even if a valid Kerberos ticket is available. If the svn client had an option to enforce authentication even if offered the ANONYMOUS mech by the server, the problem would be solved IMHO. Which boils down to another problem I stated here about SASL mech selection: http://tinyurl.com/4ntesca John Conrad wrote: For what it's worth, I have run into the same problem and the only solution I have found is to switch to a different access method. As best as I can tell svnserve is simply not an option when trying to set up a repository with path based authentication when select areas are flagged inaccessible to anonymous users. I have recently switched from a svnserve to apache based setup and using the exact same authz-db file, svnserve failed to return svn log results for protected paths while apache worked correctly. The below issue on the SVN tracker I think refers to this issue and it has been open since Oct. 2009: http://subversion.tigris.org/issues/show_bug.cgi?id=3516 Anyway, I could be totally wrong here, but I do not think what you want to do is possible with svnserve. I hope I am mistaken, but if not, sorry to be the bearer of bad news. On Thu, Feb 10, 2011 at 9:30 PM, Victor Sudakov suda...@sibptus.tomsk.ru wrote: The problem is probably in the following. When anon-access is other than none, svnserve does not request authentication for some important operations like svn log, and I have found no way to force it to request authentication. This effectively breaks path based authorization. I have found some tricky solutions for the http access method (like defining two aliases for the same repository), but none for the svnserve method. Any help? Victor Sudakov wrote: I am trying to setup the following policy: a private repository with some public paths. Is such configuration supported at all? The following configuration: == conf/svnserve.conf: anon-access = read auth-access = write authz-db = authz == conf/authz: [/] @noc = rw [/foo] $anonymous = r $authenticated = rw does not work. A valid user from the noc group receives the following reply: $ svn diff -c2237 www.txt svn: Unreadable path encountered; access denied If I change anon-access = read to anon-access = none, it begins to work for the valid user, but there is no anonymous access to anyone even to svn://myserver/foo despite the $anonymous = r clause. What am I doing wrong? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru
Re: svnadmin create repo/path - Error
Hi I was trying to create a repository with this command. svnadmin create --fs-type fsfs newrepo But, it is giving error as follows. svnadmin: Repository creation failed svnadmin: Creating db lock file svnadmin: Can't open file 'newrepo/locks/db.lock': Permission denied My SVN version is 1.5.6. The OS is Solaris 8 Anybody have any idea/resolution ? Thanks in advance, Rajesh
RE: svnadmin create repo/path - Error
-Original Message- From: Rajesh Saha [mailto:rajeshsaha...@gmail.com] Sent: Thursday, February 10, 2011 10:46 PM To: users@subversion.apache.org Subject: Re: svnadmin create repo/path - Error Hi I was trying to create a repository with this command. svnadmin create --fs-type fsfs newrepo But, it is giving error as follows. svnadmin: Repository creation failed svnadmin: Creating db lock file svnadmin: Can't open file 'newrepo/locks/db.lock': Permission denied My SVN version is 1.5.6. The OS is Solaris 8 Anybody have any idea/resolution ? Thanks in advance, Rajesh Hi, According to 'Version Control with Subversion', chapter 5, section 'Creating and Configuration Your Repository', the command should resemble: svnadmin create --fs-type fsfs /var/svn/repos Where you specify the path to your repository in place of /var/svn/repos. It does not understand your current location. HTH, John
Re: svnadmin create complains about subrepositories
On Thursday 10 February 2011, Stefan Sperling wrote: On Thu, Feb 10, 2011 at 07:02:18PM +0100, Fabian Richter wrote: Am Thu, 10 Feb 2011 11:24:09 -0600 schrieb Ryan Schmidt subversion-20...@ryandesign.com: On Feb 10, 2011, at 09:59, Stefan Sperling wrote: and can you please add an --force switch to still being able to create Repositories within the path of another? That's a reasonable request, I think. Not a usual use case but why not? Really? What possible reason could exist for doing this? :) I have no idea, to be honest. But then again I'm not going to guess. Maybe someone can present a good use case for this? Dunno. The only reason I'm aware of is that you want to make browsing easier when you have multiple repositories, as there is otherwise no way to do that. The idea is that you have a parent FS-dir that contains the parent repo. The parent repo FS-contains the child repos. Further, it has repo-directories for each child repository, too. Since SVN tries to walk the FS-path as far as possible for locating the repository. Therefore, a svn ls parent will show the repo-content of the parent's root but a svn ls parent/child-x will not show the repo-content of the parent's child-x subdir but show the root of the parent/child-x repository. In that light, I support the suggested --force option for people that really, really need it. Uli -- ML: http://subversion.apache.org/docs/community-guide/mailing-lists.html FAQ: http://subversion.apache.org/faq.html Docs: http://svnbook.red-bean.com/ ** Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932 ** Visit our website at http://www.dominolaser.com/ ** Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden. E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich. **
