Another MP game??

Yup, that's the right one. And of course it's just my luck that as soon as he got that posted, they take down this server for a migration. Sigh. Ah well, at least it's up again now.

Turn done, Thunderbrd is up.

While the svn is up again, the file "C2C SVN MP" appears to have a lock on it so that I cannot write over it with the new version of the file. Thus posting here until that gets fixed. The error messages I get on attempting to Commit:
Commit failed (details follow):
Working copy 'C:\C2C SVN MP\Save+TurnList' locked.
'C:\C2C SVN MP' is already locked.

The odd thing is that I'm not even trying to commit the turn list. It is not checked.
 

Attachments

To help get the svn back up to where it needs to be the person who made the commit after RF's July 14th entry will need to recommit that save and then everyone that followed will need to do the same until it get caught up. Revisions 3609 thru 3615 will all need to be re committed.

Or we can continue to post the saves here (in both threads).

JosEPh
 
So you are saying we will have to re-play all turns since the SVN went down? That seems a bit inefficient. Are you sure there is no other way for someone to fix this?

EDIT: Well, I guess we won't have to re-play all the turns. Just those that may have been deleted from here since being posted.
 
How is the game file affected and why does it have to be restored?. updating the svn doesn't seem to affect the turns. I'm sure it can't have changed much, I have a recent sync of the mp svn. I'm only sure of the saves I attached. I think everything else is regularly deleted.

Glad this is back btw.
 
Unless you've deleted the pbem saves found in the Saves\pbem folders all your saves are stored there. Example my directory; C:\Users\PawPaw\Documents\My Games\Beyond the Sword\Saves\pbem .

Now if you've deleted the saves from there then we/you will need to do a new checkout of the C2C MP SVN.

JosEPh
 
Actually, I do delete those as I go. I save the files from just before my turn though, so replaying any given one is not a problem.

Also, you don't seem to be understanding the problem JosEPh. The problem is that, for whatever reason, the "Save+Turn List" folder on the SVN is LOCKED. Someone needs to unlock it. I poked around in the Help menu in the SVN Commit window, and that seems to be what the message is saying. I'm hoping that Koshling (or someone with root access to the SVN) can unlock it, so we can just get on with it.

In any event, what good would doing a checkout do? I already have the SVN installed and working. There is no need to reinstall the whole thing.

The first savegame file affected for this game was rightfuture's from July 17. I tried to download that so as to Commit it myself, but all I get from clicking on the attachment is a "Clear.gif" that is 1 by 1 pixel. If rightfuture would be so kind as to attempt to Commit the save from that date again, we could see for certain what the issue is.

The first savegame that would have to be Commited for the Massive game was Thunderbrd's and it appears that he removed the attachment, so he will have to Commit that savegame himself.
 
Actually, I do delete those as I go. I save the files from just before my turn though, so replaying any given one is not a problem.

Also, you don't seem to be understanding the problem JosEPh. The problem is that, for whatever reason, the "Save+Turn List" folder on the SVN is LOCKED. Someone needs to unlock it. I poked around in the Help menu in the SVN Commit window, and that seems to be what the message is saying. I'm hoping that Koshling (or someone with root access to the SVN) can unlock it, so we can just get on with it.

In any event, what good would doing a checkout do? I already have the SVN installed and working. There is no need to reinstall the whole thing.

The first savegame file affected for this game was rightfuture's from July 17. I tried to download that so as to Commit it myself, but all I get from clicking on the attachment is a "Clear.gif" that is 1 by 1 pixel. If rightfuture would be so kind as to attempt to Commit the save from that date again, we could see for certain what the issue is.

The first savegame that would have to be Commited for the Massive game was Thunderbrd's and it appears that he removed the attachment, so he will have to Commit that savegame himself.

Actually I do understand MagnusIlluminus.

Because Sourceforge had a problem there are commits (in C2C MP case revisions 3609 thru 3615) that were not saved to the "Fixed" SVN. Sourceforge only "knows" about 3608. Therefore a New Checkout is needed. Forget about the saves being recommited. I did not need to post that route as it's more complicated to do.

Do a new Checkout of the C2C MP svn and delete the Old C2C MP svn. And it's not an installation but a Checkout. That old one is no longer a viable copy for any of us to use. Once that is done by everyone then the current players, whose turn it is in Both games, can take the last posted saves and play them and then Commit their saves back to the New C2C MP svn as we have done in the past.

This is not hard to do and unless you have an IP provider that only gives you less than 3MB Down load speed it does not take very long. I have a 12MB DSL and I did it in about an hour (actually less as i did it while getting ready for Church This morning).

https://svn.code.sf.net/p/c2cmp/code/trunk c2cmp-code this is what you use for the Checkout url.

If you need a refresher on how to do a checkout go to the OP of C2C's SVN thread. Just use the above url instead of C2C's listed one.

JosEPh
 
Ugh... this is KILLING my download limit this month!

I've got the last save here. Will checkout a new MP svn and my next commit will have the new save in it when Whispy and I have taken our turns.

To reiterate, all are going to need a fresh checkout of the repository. Then update when its your turn. In the other game, Praetyre needs to fresh checkout, play the save he was given, then commit the fresh save. Then we proceed as normal. Simple but time consuming and data consuming. Urgh.
 
The New Checkout is ~1.7GB in size and then deleting the old svn will free up about ~4 GB on your HD.

For a new Checkout of C2C you will clear almost 6GB from your HD. Deleting both the old C2C and C2C Mp combined I cleared almost 10GB from my HD.

JosEPh
 
Well, then I guess I really don't understand. The error message said it is locked, therefore, it needs to be unlocked. It did not say that I need to do a checkout, therefore I am not doing a checkout - as a checkout is what one does when installing. You are not making any sense.
 
Well, then I guess I really don't understand. The error message said it is locked, therefore, it needs to be unlocked. It did not say that I need to do a checkout, therefore I am not doing a checkout - as a checkout is what one does when installing. You are not making any sense.

What is the problem? Even the Modders for C2C have to do a new checkout for C2C!

You are Locked because Sourceforge did Not include the revisons from 3609 thru 3615. They were submitted during the period Sourceforge had their major hiccup before they had to shut down to fix everything! What does it take for you to understand and just do as directed? Do you need to hear it from koshling because you refuse to believe me? Go the Sourceforge amd pm koshling there. That is where I talked with him. And where I got my info (from Sourceforge not koshling) to do a new Checkout. Now you can continue to be stubborn that is solely your choice. But you hold everyone up in the process.

I have done a new checkout on both C2C and C2C MP and have full access again. I'm not locked like you. But you are because you refuse to listen to me. Truly sad that you would disrespect me so blatantly, when I offer a simple solution. :shake:

JosEPh:sad:
 
Well, then I guess I really don't understand. The error message said it is locked, therefore, it needs to be unlocked. It did not say that I need to do a checkout, therefore I am not doing a checkout - as a checkout is what one does when installing. You are not making any sense.

Sourceforge crashed. When they brought things back up they strongly suggested that all repositories be re-checked out before proceeding. You MIGHT be able to figure out a way around that but it's not advised. It is Sourceforge telling us to do a fresh checkout. The lock itself is usually resolvable by way of a cleanup command. Even if it works it's still advised to get a fresh checkout.
 
Ah, well, that makes the difference then. The problem I was having, that I apparently didn't explain well, was that I could not see how you could logically get that a checkout was needed from that error message. What you hadn't explained until just above (or if you had, I'd missed it) was that doing a checkout was not a conclusion drawn from the error message but rather was suggested directly by Sourceforge in response to the crash itself. That makes logical sense.

Disrespecting you? That's a stretch. Only as much as you were disrespecting me by not explaining things clearly and just demanding compliance. I'm not stupid, I just didn't see the connection. If you had explained things clearly in the first place... and I'm probably just making things worse now. Right, the point has been made. I'll have to do a Checkout.
 
In my mind and posting I considered everything explained well enough. I don't always write tomes like T-brd so excuse me.

Okay 1 down and more to go. Hope Hydro has it figured out.

JosEPh
 
RF next

JosEPh
 
Back
Top Bottom