NuSphere Forums Forum Index
NuSphere Forums
Reply to topic
CVS Commit Does Not Lock File


Joined: 04 Feb 2004
Posts: 8
Reply with quote
Sometimes when I "commit" a CVS file that has been unlocked "using CVS edit command", the lock does not re-appear next to the file. If I unlock the file (using CVS edit) and make a change to the file, then issue another "cvs commit" command, the file becomes locked again. It seems as if phpEd does not think the file has been changed.
View user's profileFind all posts by clintSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7887
Reply with quote
It may happen if cvs hasn't restored R/O flag(s) because of a reason.
Check logs shown after you run commit to see what's wrong.


Last edited by dmitri on Thu Feb 12, 2004 7:07 am; edited 1 time in total
View user's profileFind all posts by dmitriSend private messageVisit poster's website
So I should Try Refresh Then Blame My CVS Server?


Joined: 04 Feb 2004
Posts: 8
Reply with quote
Thanks for the speedy reply! Next time this happens I will try to refresh my list of files and let you know if the lock magically appears or not.
View user's profileFind all posts by clintSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7887
Reply with quote
make also sure that commit, update and unedit commands are with -r argument (see cvs manual for details)
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 04 Feb 2004
Posts: 8
Reply with quote
where do I make sure of that?
View user's profileFind all posts by clintSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7887
Reply with quote
Depends on phped version you run.
If you run 3.3 you'd check settings on Customization tab.
If you run 3.2 you'd check settings on CVS tab.
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 04 Feb 2004
Posts: 8
Reply with quote
Okay, it seems as if I have -r set for checkout and commit, but not unedit.

checkout: -z3 -r @Repository@ checkout @Sticky@ -d @Path@ @FName@
commit: -z3 -r @Repository@ commit @Comment@ @FName@
update: -z3 @Repository@ update -d -P @FName@
edit: -z3 @Repository@ edit @FName@
unedit: -z3 @Repository@ unedit @FName@
diff: -z3 @Repository@ diff -u @Sticky@ @FName@
add: -z3 @Repository@ add @FName@
status: -z3 @Repository@ status @FName@

These would be the default options for v3.2.1 build 3239eval, as I have not changed them. Are you recommending that I add a -r to the unedit line so that it looks like this?

unedit: -z3 -r @Repository@ unedit @FName@
View user's profileFind all posts by clintSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7887
Reply with quote
yes, exactly.
View user's profileFind all posts by dmitriSend private messageVisit poster's website
Site Admin

Joined: 13 Jul 2003
Posts: 7887
Reply with quote
and you didn't say if "Refresh" on the directory restored the lock sign.
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 04 Feb 2004
Posts: 8
Reply with quote
No, the refresh did not, but an unedit (before the -r was added) seemed to lock the file again. Does that many any sense?
View user's profileFind all posts by clintSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7887
Reply with quote
Yes that makes.
Seems CVS was unable to finish the command and didn't change the flag. You'd inspect CVS logs shown. See log window in the right bottom corner.
BTW, what exactly did you run ? checkin or update ?
Did anybody else make any changes to the same files ?
In that case you might get rejection. See CVS manual for further details on how it handles checkin command (nor checking, check-in!).
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 04 Feb 2004
Posts: 8
Reply with quote
Quote:
BTW, what exactly did you run ? checkin or update?


I ran commit, that's what you meant by checkin right?

Quote:
Did anybody else make any changes to the same files?


No, i'm the only developer using CVS in my company right now, so there is no chance of confliting commits in my particular case.

I will check the log next time this happens and let you know what it says.

I can tell you one thing for sure, it always happens on commit, and either changing the file and then issuing a commit command again will lock the file. Also an unedit command accomplishes the same thing.

... i'll post again in this thread when I have some log data to share ...
View user's profileFind all posts by clintSend private message
CVS Commit Does Not Lock File
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT - 5 Hours  
Page 1 of 2  

  
  
 Reply to topic