Question

我今天有一个腐败存放处的问题。

尽管Svnadmin核实说所有东西都是K.,但Svnlog给我“Malised file”错误。

当你的渊源历史如此时,它总是坏了,在帮助某人的情况下,也给人留下了答案。

Answer 1

页: 1

请注意,最后一项修订(例如,第99条),后一项修改有错误(例如100)。

如果有香烟或烟,你可以确定:

copy the previous props (99) over the bad one (100)
open the corrected props, set the date to a resonable value (don t edit anything else unless you know the file format)

运行“vnadminump REPOSPATH > nul”

Answer 2

@laktak的解决方案在大多数情况下都是在推进剂被腐蚀的情况下进行的,而不是如@jgifford25所指出的实际更新文件。

理想的解决办法是:

Identify corrupt changes as suggested @laktak, let s say 100
Take the dump till only last valid version from the start as a backup, or skip this if you have backup till valid revision.

    svnadmin dump /path/to/currentrepo -r 0:99 --incremental > svnbackuptillvalid

Take the second backup for version committed after revision 100, till head (only if any, skip this if you are sure there are no commits after corrupted).

   svnadmin dump /path/to/currentrepo -r 101:HEAD --incremental > svnbackupafterinvalid

    svnadmin create /path/to/newrepo

    svnadmin load /path/to/newrepo < svnbackuptillvalid

• 与一个小组分享新的URL,或删除现有的背书,并使用同一途径。

此外,你还可以在印瓦修正后添加有效的改动。

    svnadmin load /path/to/newrepo < svnbackupafterinvalid