Subversion check in issues

[NeilS]

We're using
7.5 (844) of EA
6.1 of subversion client and server

We are getting major problems on checking in - ea is reporting
"Subversion reports the following error.  svn: commit failed (details follow). svn server sent unexpected return value (423 locked) in response to PUT request for....)"

I own the lock.

I have had to change my windows password recently.  I used tortoise to clear my authentication details and used svn update to update.

Still no joy.  

We are guessing that ea is holding some authentication information.

Any ideas?  (I've contacted ea support but nothing as yet)

Neil

[Martin Terreni]

7.5 assumes that you only lock\unlock through EA, so you must take care that the status is the same in both -meaning both Ea thinks you checked it out and SVN status is locked on the same computer your are trying to check in. You can try right click>package control>file properties to see what is the status of the lock in SVN (as EA gets it form it).

[NeilS]

Hi Martin

Thanks for the swift reply.  Judging from what you said in a previous thread:

http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1239201770

the data is also being held in the EA db.

Is there any way of remedying the situation where ea is out of sync with subversion?

We only started clearing authentication through tortoise as we were failing to start ea at one point.

At the moment I am thinking that I have to export the troublesome packages as xmi.  Break the locks in tortoise, delete the packages and re-import.  This does not strike me as a good long term solution!

Neil

[Martin Terreni]

Well lets think it by alternatives:
1) EA thinks the package is checked in but it is actually locked by you - just unlock file through Tortoise
2) EA thinks the package is checked out by you but you don't own lock on the specific machine - just steal lock through Tortoise to the respective machine, or if not locked then lock it.
3) EA thinks the package is checked in but it is actually locked by someone else - still the lock and then release it

Hope it gices you a solution.

[NeilS]

Hi Martin

Unfortunately I have an option 4!

4) EA and subversion/ tortoise both think I own the lock - which I can see through repo-browser and the file properties in ea.  I can check in from svn/ tortoise, but not through EA.  If I check in from tortoise/svn EA still thinks I have it checked out.  We came to the conclusion that EA must be holding some authentication information beyond the lock own.  Your comments in a previous thread indicated that certainly the lock holder was being held by EA - I suspect the password is also being held but currently this is just a supposition.

Neil

[Martin Terreni]

I guest that first a(just to check that all works) I would try to check out and in another package) and I would export the data not to loose it.
If I manage to do it then the only problem is the synch between EA and SVN.
If this is the problem you will need to release lock from SVN and then do some hacking in EA.
Open the EAP file in Access and open the t_package table looking for the relevant package (do not transform to new access version, leave as is). You will find it is not that easy to change data of and old access version (98 I think), but don't give up .
In the table you will find something like "Lock = true" and some user name, I think it is in "style" column (or something like this) - just delete it and then delete the ""checked out..." string pat from packageflags column.
reopen EA, perform "put latest" and you are all synched.
If the problem is different than the best way is as you stated.

[NeilS]

Hi Martin

I'm not about to claim awards for the elegance of this but the following procedure is working for now at leastL

1. Export offending package to xmi (being of a paranoid disposition)
2. Break the lock using repo-browser
3. Get the lock in svn "Get Lock" option in windows explorer
4. Check in branch in ea

I was getting the same locking message as per start of this thread when I did an svn commit.

Neil