--"Murray @ PlanetThoughtful" <lists@ulblog.org> wrote:
> On 27/12/2005 11:01 PM, Andy Levy wrote:
>> On 12/27/05, Murray @ PlanetThoughtful <lists@ulblog.org> wrote:
>>
>>> Hello All,
>>>
>>> I think I may have stuffed up my repository.
>>>
>>> Today I upgraded my local copy of wordpress, which I have been using
>>> subversion to version control as I tweak it prior to releasing to my web
>>> host. In doing so, it seems that I have caused subversion to have a
>>> nervous breakdown as to the state of the repository.
>>>
>>> When I try to commit (using SVN 1.2.3, TotoiseSVN 1.2.6, on WinXP SP2) I
>>> get the error: wp-admin is not a working copy.
>>>
>>> This is one of a number of directories and files I replaced using a copy
>>> operation.
>>>
>>> Is there any way to resolve this issue, without losing the upgrade
>>> changes I made today?
>>>
>>
>> When you "replaced" things, did you overwrite/modify/destroy the .svn
>> directories?
>>
> Ah, yes, I probably did, come to think of it. I do have a zip of the
> entire project prior to the upgrade available. It's going to be a little
> bit of a pain restoring the files, then copying the upgrades back across
> them, but I *can* do it.
If you committed to the SVN repository prior to the upgrade, you can create
a new empty directory somewhere and do a checkout from the repository. This
will create a new working copy, and you can then apply the upgrade to that.
Prior to doing the upgrade it may also be a good time to create a tag
directory in the repository, since this represents your wordpress site on a
given version.
Good luck,
--
Bruce Webber
brucewebber@fastmail.us
http://brucewebber.us
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 27 16:53:20 2005