blocks|key|4914225|text|实际上，svnsync+(从v1.7开始)中内置了一些可以“窃取”锁的功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4914226|svnsync+help+sync|code-block|syntax|javascript|4914227|显示：|4914228|--steal-lock+++++++++++++:+Steal+locks+as+necessary.++Use,+with+caution,
+++++++++++++++++++++++++++if+your+mirror+repository+contains+stale+locks
+++++++++++++++++++++++++++and+is+not+being+concurrently+accessed+by+another
+++++++++++++++++++++++++++svnsync+instance.|4914229|当我运行它的时候，我得到了一个很好的：|4914230|Stole+lock+previously+held+by+'[hostname]'|4914231|所以，你根本不需要propdel这个东西|4914232|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Actually, there is some functionality built into svnsync (since v1.7) that can &quot;steal&quot; the lock.
<pre><code>svnsync help sync
</code></pre>
shows:
<pre><code>--steal-lock : Steal locks as necessary. Use, with caution,
 if your mirror repository contains stale locks
 and is not being concurrently accessed by another
 svnsync instance.
</code></pre>
and when I run it, I get a nice:
<pre><code>Stole lock previously held by '[hostname]'
</code></pre>
So, you don't need the propdel thing after all

blocks|key|4914059|text|您必须通过远程站点上的svn命令行删除远程存储库上的lock属性，该属性是在同步过程中因故障而遗留下来的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4914060|svn+propdel+--revprop+-r0+svn:sync-lock+file:///path/to/the/repository|code-block|syntax|javascript|4914061|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You have to remove the lock property on the remote repository via svn command line on the remote site which has been left over from a failure during synchronization.

<pre><code>svn propdel --revprop -r0 svn:sync-lock file:///path/to/the/repository
</code></pre>

blocks|key|4914193|text|从技术上讲，您需要删除属性的是目标存储库，而不一定是远程存储库，因为目标可以是本地的。因此，对于这个特定的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4914194|svn+propdel+--revprop+-r0+svn:sync-lock+${REPO}|code-block|syntax|javascript|4914195|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Technically, it is the destination repository that you need to delete the property from, not necessarily the remote repository, as the destination could be local. So for this specific question:

<pre><code>svn propdel --revprop -r0 svn:sync-lock ${REPO}
</code></pre>

blocks|key|4914104|text|解锁对我来说很有效。然而，我不得不使用一个稍微不同的命令，因为我需要发送帐户的用户名和密码来解锁帐户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4914105|svn+pdel+--revprop+-r+0+--username+???+--password+???+svn:sync-lock+file:///path/to/the/repository|code-block|syntax|javascript|4914106|我还必须从存储库所在的驱动器运行此命令。(如果我的存储库在d:上，请在运行命令之前在命令提示符中更改为d:)|4914107|在输入用户名和密码之前，当我运行该命令时，我得到了以下错误：|4914108|revprop+change+blocked+by+pre-revprop-change+hook+(exit+code+255)|4914109|我找到并打开了pre-revprop-change钩子文件，其中的代码只列出了可以进行所需更改的某个用户名。在上面的命令中使用该用户名和密码删除了挂钩。|offset|length|style|CODE|4914110|entityMap^0|0|0|0|0|0|7|I|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|Z|8|@$O|10|P|11|Q|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Removing the Lock worked for me. However, I had to use a slightly different command, as I needed to send the username and password of the account to use to unlock the account.

<pre><code>svn pdel --revprop -r 0 --username ??? --password ??? svn:sync-lock file:///path/to/the/repository
</code></pre>

I also had to run this command from the drive that the repository was on. (change to d: in the command prompt before running the command, if my Repository was on d:)

Prior to entering the username and password, when I ran the command I got the following error:

<pre><code>revprop change blocked by pre-revprop-change hook (exit code 255)
</code></pre>

I found and opened the <code>pre-revprop-change</code> hook file, and it had code in there listing only a certain username that could make the required changes. Using that username and password in the above command removed the hook.

blocks|key|4914254|text|要确认锁的存在(尽管错误很明显地说明了这一点)，请使用-verbose运行proplist|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4914255|svn+pl+--revprop+-v+-r+0+file:///svn/slave|code-block|syntax|javascript|4914256|然后根据需要删除道具！|4914257|entityMap^0|R|8|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

To confirm the presence of lock(although the err obviously tells it), run proplist with <code>-verbose</code>

<pre><code>svn pl --revprop -v -r 0 file:///svn/slave
</code></pre>

then delete the prop as necessary!

blocks|key|2017673|text|你必须做两件事来解决这个问题。一个是删除如上所述的锁。然后，您必须将pre-revprop-change.tmpl文件编辑为空，并使其可执行。在Linux/Unix/Mac上使用chmod+%2Bx，但在Windows上将文件名更改为pre-revprop-change.bat。在此之后，您可以将转储文件加载到您的存储库中，然后在需要的任何地方镜像它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2017674|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You have to do two things to solve the problem. One is deleted the lock as noted above. Then you have to edit the pre-revprop-change.tmpl file to be empty, and make it executable. Use chmod +x on Linux/Unix/Mac but change the file name to pre-revprop-change.bat on Windows. After this you can load dump files into your repository and then mirror it where ever you need.

Using svnsync 

<pre><code>$ svnsync --non-interactive sync ${REPO}
</code></pre>

after an abort of the process there was this error message with retry 

<pre><code>Failed to get lock on destination repos, currently held by 'svn.test.com:0e4e0d98-631d-0410-9a00-9330a90920b3' 
... 
Failed to get lock on destination repos, currently held by 'svn.test.com:0e4e0d98-631d-0410-9a00-9330a90920b3' 
svnsync: Couldn't get lock on destination repos after 10 attempts 
</code></pre>

Is there a way to fix this problem?

svnsync - couldn't get lock on destination repos

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

使用svnsync$ svnsync --non-interactive sync ${REPO}进程中止后，重试时出现以下错误消息Failed to get lock on destination repos, currently held by 'svn.test.com:0e4e0d98-631d-0410-9a00-9330a90920b3'  ...  Failed to get loc

问svnsync -无法锁定目标存储库
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问svnsync -无法锁定目标存储库EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问svnsync -无法锁定目标存储库
EN