错误:访问“/svn/path/”禁止 - 不是案例问题
我有一个在另一个国家的开发人员从那里访问 svn。 现在我们的防火墙出现了问题,他有一段时间无法访问存储库。防火墙错误现在应该已修复,并且对其他人来说可以再次使用。不过,该开发人员收到错误“错误:禁止访问'/svn/path/lots-of-numbers'”。 当我试图找到原因时,我发现了这个: 类似案例链接 但是,他向我发送了他使用的存储库链接,并且全部都是小写,就像应该的那样。权限也正确,我只是仔细检查了它们。
问题可能出在防火墙上,或者有人有其他建议吗?
I have a developer in another country who is accessing svn from there.
Now we had an issue with the firewall, and he could not access the repository for a while. The firewall error should be fixed now, and it works again for others. This devs gets the error "Error:access to '/svn/path/lots-of-numbers' forbidden" though.
When I tried to find the cause, I found this: link to similar case
However, he sent me the repository link he uses, and it is all in lower case, just as it should be. The permissions are also correct, I just double checked them.
Could the problem lie in the firewall somehow, or does anyone have another suggestion?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
前一段时间就弄清楚了,但我想我也应该在这里发布这个,以防其他人遇到类似的问题。我的问题实际上是权限设置。
我现在所拥有的有效设置与我之前在 svn 服务器中的设置完全相同,只是现在它们是从根继承的。苏……是啊。我不知道为什么这实际上会产生影响。
Figured it out some time ago, but I guess I should post this here too in case someone else has a similar issue. My problem was actually with permission settings.
What I have now that works, are the exact same settings I had in the svn server previously, only now they are inherited from the root. Sooo...yeah. I have no idea why that actually made a difference.
我遇到同样的问题有一段时间了,并找出了问题所在。我有不该有的资本。我的存储库是 svn/dave,但我在 URL 中将其设置为 svn/Dave。它让我登录没有任何问题,但我实际上无法做任何事情。将其更改为小写可以清除所有内容。
I've had the same issue for a while and figured out what was wrong. I had a capital where I shouldn't have. My repository was svn/dave, but i had it in the URL as svn/Dave. It let me log in without any issues, but I couldn't actually do anything. Changing it to lower case cleared everything up.
我遇到了类似的情况,我也将服务器中的权限更改为从根继承。
在发出命令
svn update
后,我的问题得到了解决。通常这是我一直遵循的做法 - 我运行
svn status 。
然后运行 svn update 。 在触发
svn commit
之前。这次我跳过了 svn update 并捕获了错误。
看起来 svn update 所做的不仅仅是更新文件。
I faced similar situation and I also had changed the permission in the server to inherit from the root.
My problem got solved after I issued the command
svn update
Usually it is a practice that I always follow - I run
svn status .
and thensvn update .
before firingsvn commit
.I skipped
svn update
this time and caught the error.It looks like
svn update
does much more than just update the files.