The problem is with the client side, server is not contacted at this stage. Your local repository checkout might have been silently upgraded by another svn client you use. Or it might also be damaged and Subclipse errorneously reports it as an upgrade it doesn't understand.
If you don't want to upgrade Subclipse, your only way is to do a fresh checkout from server, and copy over your changes from this upgraded repository.