This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
After adding a new svn checkout, any updates done on old svn checkouts from same server but different logins/trunks will result in the following error: org.apache.subversion.javahl.ClientException: E170009: Repository UUID '6273807f-1b75-40b9-beab-73ce2f6d0e6d' doesn't match expected UUID '1f95d0d0-8ef1-4c5a-8924-db3d3658982b'
Attach the messages log. And paste the output of 'svn info' command ran inside the folder with the problematic checkout. Does 'svn update' on commandline works?
Sorry for the slow reply. I am not proficient with svn so I can't locate the message log. 'svn info' gave me the following: svn: The path '.' appears to be part of a Subversion 1.7 or greater working copy. Please upgrade your Subversion client to use this working copy. Note: I am using the SvnKit client as defaulted in Netbeans 7.2. My observation, after trying a few settings, is that the project I am trying to update seems to always use the latest connection added and not the previous connection that is tied to it. This resulted in only the latest project able to access the svn correctly.
The original message '6273807f-1b75-40b9-beab-73ce2f6d0e6d' doesn't match expected UUID '1f95d0d0-8ef1-4c5a-8924-db3d3658982b' means that your local working copy matches the repository with id 1f95d0d0-8ef1-4c5a-8924-db3d3658982b. But that repository does not exist - the repository residing at the URL you originally checked out has probably been replaced. Simply do a new fresh checkout and everything should work again. If you can do the update on the old working copy with another subversion client (as commandline client), reopen.
few hints: 1) how to attach the messages.log: http://wiki.netbeans.org/FaqLogMessagesFile 2) you should upgrade your commandline client to 1.7 version. You're still on 1.6, that's why you're getting: > svn: The path '.' appears to be part of a Subversion 1.7 or greater 3) then you should go to the failing checkout and run: a) svn info . b) svn info URL_OF_THE_REPOSITORY and compare the repository UUIDs
Created attachment 123379 [details] NetBeans 7.2 messages log Attached is my messages log in case someone is interested in. From it you can see that a svn update of an older project 'kopitiam' encountered error while a svn update of the latest project 'biipmi' is okay. Problem will reverse if I checkout 'kopitiam' as the latest and 'biipmi' will encounter error.
Does your checkouts use svn externals? Is there a folder in your local checkout that points to an external repository?
the two repository UUIDs: 6273807f-1b75-40b9-beab-73ce2f6d0e6d' and '1f95d0d0-8ef1-4c5a-8924-db3d3658982b' Do they belong to different repositories you're both using? Because you mentioned in the original post that: > on old svn checkouts from same server but different logins/trunks how should i understand that? That you have a single repository and you checkout two projects from it or that you have actually more than one repository on the server? In case of two repos, what is their URL? And what is the local folder for both the checkouts on disk?
Also please download and install the latest dev build from http://bits.netbeans.org/download/trunk/nightly/latest/ We upgraded the svnkit client to 1.7.5 in dev builds, maybe your issue is already fixed. If not, attach the messages log from the dev build, it will at least contain updated stacktraces. Thanks
Hi, I am using the SvnKit included, not external ones. The server has multiple repositories and the two checkouts are of two different repos. The local folders of the two checkouts are separate. Anyway, I see whether I can install the patch or wait for an update. Thank you very much for your response and help.