Problem with SVN update from Revision: 6272 to Revision: 6282

I have just tried to run a svn update on my install of revo.

I ran the command as I have always done on every time I have updated.

this time I get the following error
svn: Can’t copy ’public_html/setup/includes/upgrades/.svn/text-base/2.0.0-alpha-1.php.svn-base’ to ’public_html/setup/includes/upgrades/.svn/tmp/2.0.0-alpha-1.php.tmp.tmp’: Success

and whilst it says success at the end the rev no still stays at 6272

is this a problem at my end or modx’s

If mine what do folks suggest.

I’ve just upped my revo 2.0.0 install from r6272 to r6282 with no probs, so I guess that it looks like your end.

The ’Can’t copy’ line suggest either a perms issue or a missing directory etc. although if you do this regularly this shouldn’t be the case.

You could try a clean up i.e. ’svn cleanup’

Thanks for the reply shamblett at first I wondered about permissions but I’m sure none of these have been changed but will take a good look.

tried the cleanup but that didn’t work either.

The ’..tmp/2.0.0-alpha-1.php.tmp.tmp’ looks kind of funny. Is that a real file?

Also, have you updated your SVN client lately? I think the latest TSVN has some checkout bugs, especially under Windows 7.

After having a look around it is the public_html/setup/includes/upgrades/.svn/text-base/2.0.0-alpha-1.php.svn-base file that is missing.

I tried creating a file with this name and several others that throw up similar errors afterwards and eventually got
Checksum mismatch for ’public_html/setup/includes/upgrades/.svn/text-base/2.0.0-beta-5.php.svn-base’; recorded: ’199cefc29a9cc288d90db961d5df1528’, actual: ’d41d8cd98f00b204e9800998ecf8427e’
which i’m guessing is because "that is one of the files that i created" the file contents and size don’t match and so the check sum doesn’t.

I usually always read the logs after did the update.
Some of updates were stamped "[REBUILD/UPGRADE REQUIRED]".

Did you find one?
Did you try to rebuild?

Quote from: goldsky at Jan 14, 2010, 07:39 PM

I usually always read the logs after did the update.
Some of updates were stamped "[REBUILD/UPGRADE REQUIRED]".
Did you find one?
Did you try to rebuild?

That wont have anything to do with his issue; his issue has to do with a corrupted SVN checkout, or file permissions on the server.

Well after lots of hunting and file permission checking the only way I found to solve this was to do a complete fresh check out.