Community
Participate
Working Groups
on debian stable, I installed a recent eclipse luna. So far I used subclipse, but that didn't work anymore, so I switched to subversive2.0.3 that appears to work mostly fine. One no so helpful error I get, however: <<Synchronize operation failed. svn: E155021: Unsupported working copy format>> My suspicion is that in one or a few folders of my directory tree, there is still a .svn/* created by subclipse left. Would it be possible to amend the error message with 1) where the problem is seen (path) 2) a hint how to remedy or at least a link on a faq-/help-page that describes how to proceed? Many thanks in advance!
3) or add a "more" button to see detailed log excerpts. Interestingly, elsewhere the 1) is done: https://netbeans.org/bugzilla/show_bug.cgi?id=226018 but my workspace/.metadata/.log only says: Caused by: org.apache.subversion.javahl.ClientException: svn: E155021: Unsupported working copy format at org.apache.subversion.javahl.ClientException.fromException(ClientException.java:68) at org.tmatesoft.svn.core.javahl17.SVNClientImpl.getClientException(SVNClientImpl.java:1496) at org.tmatesoft.svn.core.javahl17.SVNClientImpl.status(SVNClientImpl.java:211) at org.polarion.team.svn.connector.svnkit.SVNKitConnector.status(SVNKitConnector.java:589) ... 33 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E155021: Unsupported working copy format at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.svn.SVNEditModeReader.driveEditor(SVNEditModeReader.java:248) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.status(SVNRepositoryImpl.java:1446) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetStatus.run(SvnNgGetStatus.java:110) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetStatus.run(SvnNgGetStatus.java:1) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.javahl17.SVNClientImpl.status(SVNClientImpl.java:209) ... 34 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E155021: Unsupported working copy format at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.verifyDirUsable(SVNWCDb.java:4858) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.obtainWcRoot(SVNWCDb.java:6271) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.obtainWcRoot(SVNWCDb.java:6263) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readInfo(SVNWCDb.java:3526) at org.tmatesoft.svn.core.internal.wc17.SVNStatusEditor17.readInfo(SVNStatusEditor17.java:570) at org.tmatesoft.svn.core.internal.wc17.SVNStatusEditor17.getDirStatus(SVNStatusEditor17.java:663) at org.tmatesoft.svn.core.internal.wc17.SVNRemoteStatusEditor17.handleStatii(SVNRemoteStatusEditor17.java:358) at org.tmatesoft.svn.core.internal.wc17.SVNRemoteStatusEditor17.closeDir(SVNRemoteStatusEditor17.java:295) at org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeDir(SVNCancellableEditor.java:102) at org.tmatesoft.svn.core.internal.io.svn.SVNEditModeReader.processCommand(SVNEditModeReader.java:136) at org.tmatesoft.svn.core.internal.io.svn.SVNEditModeReader.driveEditor(SVNEditModeReader.java:231) ... 42 more
see also http://issues.tmatesoft.com/issue/SVNKIT-255?projectKey=SVNKIT
E155021 and E155005 are two different messages and so, they're reported differently. If you haven't got any E155005 errors it just means that your case is different and there wasn't any information that includes the path to resource or anything else. The only idea I've got in mind is to provide a specific page in the Subversive Help (which could be opened directly from an Error Dialog), that will list some typical errors and the ways to solve them. Would that be alright?
Hi Alexander, having a help link i.e. 2) would be a good frist step. 3) it furthermore would be helpul to state in your part of the error whether the error occurred on the local end (client side) or remotely (server-side). Many thanks in advance! Ralf
There is a help button in the bottom of the Error Dialog, which looks like question mark. When the error happens and if you don't know the meaning and what to do, then please press the button and check if there is a solution proposed. Currently there're only two typical errors described. If you want to add more information, please place corresponding requests to the tracker and we'll add more problem solutions.
