So I upgraded to MacOS Sierra and now whenever I try to do anything in my working copy I get the error that it
"is too old (format 29) to work with client version '1.9.4 (r1740329)' (expects format 31). You need to upgrade the working copy first."
When I run svn upgrade, as it suggests it says
"Can't open file /.svn/entries: No such file or directory"
Any suggestions will be greatly appreciated!
Open Terminal
go to error folder. ex : cd svn/project/game
command write only "svn upgrade"
Your problem is that the version of the SVN client got upgraded locally; whereas your local working copy (and the server) didn't change! Now the new client is unable to work with the existing working copy.
Now you have three choices:
You can try to get your new SVN client to accept the existing working copy
You downgrade your local SVN client to the previous version
You throw your existing repositories away and start with fresh checkouts
For option 1, you might look here or there.
For option 2, this might help.
Option 3; I guess, is the one-line-no-brainer which maybe costs you download time, but should come with the least amount of "you spending your time" debugging this (unless you got a ton of uncommitted changes sitting in your current repositories). But of course, you would first try to create a new checkout with the new client, before throwing the old directory away.
I solved my problem by doing the 'svn upgrade' on the 'cd' of root folder of the project
Related
Could anyone please help me with steps to upgrade "My WebMethods Server" from 10.1 to 10.5 using/applying patches/fixes?
Upgrade document is clear enaough if you read it all but just in case you want to play safe, this is how I’ve done it:
1- Install DBConfigurator to new location (If you are performing upgrade on the same machine).
2- Install Update Manager.
3- Install latest fixes for DBConfguratior.
4- Run the latest db scripts. (If you installed the scripts already, perform migrate operation after installing fixes for DBConfguratior).
5- Perform Installation of the new version.
6- Shutdown both old and new instances. Run the migrate utility from the new installation.
7- Migration utility will ask for old version installation directory. (Or you can have an export of the old version as a zip file).
8- Follow the steps guided by migration utility, It will ask couple of questions which you can answer by typing Y or N.
9- If everything goes OK, you should be getting the message below. (Might be different for newer versions.)
Failed migrations
None
Migration successful. Exiting the migration utility.
*** End Integration Server Migration ***
10- Validate the scripts you are using for startup have the new installation directory. I faced a couple of problems with that.
Bonus : Make sure the extendend setting about java compiler have the right path for the jvm. watt.server.compile=…\jvm\jvm\bin\javac -classpath {0} -d {1} {2}
An update was downloaded automatically by my 2.6.3.RELEASE Build 201411281425.
STS (Spring Tool Suite) asks to install it and when I click on the pop-up window it does some things and then stops with the following message which seem to indicate that it wants to delete itself.
I can understand why this fails but I am not sure why STS would think that this was possible.
I could not find any instructions about manually installing the zip file that is available as a download as an alternative way to upgrade my installation.
How do I fix the automatic install or manually install the zip?
(I am on Windows 7)
Error message:
An error occurred while uninstalling
session context was:
(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall,
operand=[R]org.springsource.sts.ide.executable.win32.win32.x86_64
3.6.3.201411281415-RELEASE-e44
--> null,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction).
Backup of file C:\RAMDrive\spring\STS.exe failed.
File that was copied to backup could not be deleted: C:\RAMDrive\spring\STS.exe
Start the STS you want to upgrade and before you click on "Check for Upgrades", with STS still running, rename the STS.exe file you just started, to something else, like "STS_old.exe". That should do it.
The message sounds strange, I've never seen this before. To install a fresh copy of STS, just download the ZIP file from the download page (the one that matches your operating system and pick the right 32bit or 64bit one, depending on your OS and the JDK you are using). Then unzip, and start STS.exe. That's it.
I am using Dreamweaver CS5 and Apache Subversion. Until today, the setup had been error-free. However, when I attempted to check in a file I had revised, I got the following error message from Dreamweaver:
SVN: #160024, Commit failed (details follow): File or directory ‘about.html’ is out of date; try updating
resource out of date; try updating
Background: I am the only user. SVN is hosted on another Mac on my home network running OS X 10.7. I set it up this way because I could never get SVN working on my MacBook Pro, which is running Mavericks. I have tried getting the current version, re-editing, then checking back in, but I have the same problem. Reverting the file and re-editing also fails on check-in.
In Terminal on the Mac running svn, I tried svn cleanup (& sudo svn cleanup), both of which produced the following response: svn: '.' is not a working copy directory. SVN update produces but one message: Skipped '.'
I have used Dreamweaver regularly for over 15 years, but I just started using svn a couple of months ago. I am a svn novice and just followed some very great and detailed instructions on the Adobe website to get it up and running and connect Dreamweaver. Other than this one file, the check-in/out process works fine. When I right-click on the problem file in Dreamweaver's file list, go to version control, and select "Show Revisions," it is up to date; that is, it shows all revisions up to the last one I was able to successfully check in.
This particular file has few revisions to date, so if it is easier and quicker to somehow kick it out of svn altogether and just save the current version back, that would be fine. However, I do need to be able to save version changes of it going forward, as I anticipate significant changes in the future.
Any help would be appreciated!
I've had these errors before. select the file and get the latest version from the server. The commit should work fine again.
Don't know what causes it but this has worked for me several times.
I got error when execute 'svn upgrade'.
I had used svn 1.6 in Mac OS Lion. And i updated to Mac OS Mountain Lion few days ago.
so i have to upgrade svn.
I usually use Terminal application and execute svn command in CUI.
when i execute 'svn update'
$ svn update svn:
E155036: Please see the 'svn upgrade' command svn: E155036: Working
copy 'xxxxx' is too old
(format 10, created by Subversion 1.6)
when i execute 'svn upgrade'
$ svn upgrade
...
Upgraded
'aaaaa'
Upgraded
'bbbbb'
Upgraded
'ccccc'
Upgraded
'ddddd'
svn: E155016: This working copy is corrupt and cannot be upgraded.
Please check out a new working copy. svn: E155016: The file
'eeeee'
has no checksum
BY the way, the error file has Japanese Character in file name.
Maybe this is cause.
So How should i resolve this problem?
Thanks.
Looks like you've switched from 1.6 to 1.7 or 1.8. You don't mention where you got your copy of svn 1.6 you're using but it's possible you were using one that was patched with the fix for the unicode composition issue. Specifically there is a patch that's floating around that's in common usage but hasn't been applied to the project as a whole since it is not a complete solution. I'm not sure if Japanese would run into these problems since I don't know much about Japanese but it seems plausible.
I'd suggest that you create a new checkout from the working copy with your new Subversion client. I'm not sure if there is a good way to recover from this situation. In particular I'm not sure if the patch is capable of ensuring that svn upgrade executes properly.
On the other hand this might have nothing to do with the unicode issues on OS X and your working copy might just have been corrupted in a way that didn't turn up until recently. The upgrade command needs to touch everything in order to convert from the old flat file system to sqlite. So it often turns up corrupted working copies. It's usually not worth the effort to try to debug the corruption when you can do a new checkout.
If you have uncommitted changes you want to preserve in your working copy I'd suggest that you checkout the same revision(s) of the contents of your working copy with the new version. You ought to be able to figure out the version with an old 1.6 svnversion command or by manual inspection of the .svn/entries files. Once you've done that, rsync the contents of the old working copy over the new working copy while ignoring the .svn directories. Then run an svn update. If you don't get the versions of the working copy checkout exactly right you might have some additional issues when you run update. But hopefully you don't have too many uncommitted changes to clean up.
Alternatively you can try installing a 1.6 copy of Subversion and seeing if you can diff your changes out and determine the correct versions. But I'm not sure what the state of the working copy databases will be during an interrupted upgrade. This might be the best way to go since I believe we're really careful about not botching things.
I try to check out the repo to a new computer but Smart SVN on mac os x claims that working copy format of ~/ProjectPath is too old '0'.I tried everththing that i found on the web.I upgraded svn to 1.7.6 and i also downloaded the lastest version of smart SVN but it really did not help.
svn upgrade says the following
svn: E155019: Can't upgrade '/Users/ilker/Desktop/CallingCard_v2.0' as it is not a pre-1.7 working copy directory
and svn cleanup says
svn: E200030: sqlite: no such table: wcroot
the only difference that i have on this machine is that i have mac os x 10.6.8 while other clients have at least 10.7.I think but it should not matter.
Did you try the svn checkout command to get a new working copy instead of trying to svn upgrade your current one ?
I have faced the slightly different situation that resulted in the same error.
I made checkout on a server that had almost 0% space free. The checkout downloaded the parent directory from SVN but not the content. When I freed disk space and made check out the issue was still there.
When I deleted the parent directory and made checkout again the issue disappeared.
So you may try deleting the checked out content and checkout again.