Open the repository in the SVN service console "SVN cannot read current" --- excerpted from the network wrote
SVN cannot read the current repair method Can't read file : End of file found
files: repository/db/txn_current, repository/db/current
where current records the current latest version number, and txn_current records the folder where the version number file in the repository is stored
Reason: When submitting the file, the svn server was forcibly shut down, resulting in the unsuccessful writing of the version information file, and the version record files txn_current and current became garbled characters.
Solution: Rewrite the correct version information to the current and txn-current files.
Generally, the latest version will be wrong and can only be rolled back to the previous version. Find the latest version, which is usually the one with the error. Assuming that the error is 9010,
you can usually get it from (\Repositories\ProjectName\db\revprops\X), where X is the folder name inside, and almost all version numbers can be Find the corresponding file name in these directories and
find largest version number 9010. If the file is garbled when opened with the record book, it should be an error, then delete the file. Correspondingly, the version number of the previous version is 9009, corresponding to The X is generally the 9 folder.
Update txn-current, write the X folder name "9" in it, and then press Enter! save.
Update current, write 9009 in it, and then press Enter! save.
At this point, the issue should be resolved.
files: repository/db/txn_current, repository/db/current
where current records the current latest version number, and txn_current records the folder where the version number file in the repository is stored
Reason: When submitting the file, the svn server was forcibly shut down, resulting in the unsuccessful writing of the version information file, and the version record files txn_current and current became garbled characters.
Solution: Rewrite the correct version information to the current and txn-current files.
Generally, the latest version will be wrong and can only be rolled back to the previous version. Find the latest version, which is usually the one with the error. Assuming that the error is 9010,
you can usually get it from (\Repositories\ProjectName\db\revprops\X), where X is the folder name inside, and almost all version numbers can be Find the corresponding file name in these directories and
find largest version number 9010. If the file is garbled when opened with the record book, it should be an error, then delete the file. Correspondingly, the version number of the previous version is 9009, corresponding to The X is generally the 9 folder.
Update txn-current, write the X folder name "9" in it, and then press Enter! save.
Update current, write 9009 in it, and then press Enter! save.
At this point, the issue should be resolved.
After the server resource files can be accessed, eclipse synchronization problems follow one after another. The local file version is higher than the server file version. What should I do if the file cannot be synchronized and submitted?
error one wrote
同步 SVNStatusSubscriber 时报告了错误。1 中的 0 个资源已经同步。
同步 /OPRO_IMS-I_Peento/src 时发生错误：Error getting status for resource F/OPRO_IMS-I_Peento/src org.apache.subversion.javahl.ClientException: No error
svn: A reported revision is higher than the current repository HEAD revision.
Error getting status for resource F/OPRO_IMS-I_Peento/src org.apache.subversion.javahl.ClientException: No error
svn: A reported revision is higher than the current repository HEAD revision.
org.apache.subversion.javahl.ClientException: No error
svn: A reported revision is higher than the current repository HEAD revision.
org.apache.subversion.javahl.ClientException: No error
svn: A reported revision is higher than the current repository HEAD revision.
Error two wrote
org.apache.subversion.javahl.ClientException: Invalid filesystem revision number
svn: No such revision 9010
org.apache.subversion.javahl.ClientException: Invalid filesystem revision number
svn: No such revision 9010
Solution:
It's very simple. The entire file that can be submitted is directly submitted to SVN, the project is synchronized again, and the problem is solved. The reason is: the submitted file will add a new version number to the SVN resource.