CODEWITHSUNDEEP
perforce
seektrue
seektrue

Reputation: 19

No permission to lock file when attempts to checkin after unshelve

Others has a change list that is shelved for me to checkin. So in my workspace, I first do unshelve:

p4 unshelve -s 111111

Then try checkin but fails:

p4ci -fixed QUEST -cr reviewer -- changedfile.cpp

And received the error:

changedfile.cpp - no permission to lock file

If I unshelve the changed file elsewhere and copy the file then overwrite the original one, checkin works. But his procedure does not seems to be legitimate. So what am I supposed to do after unshelve?

Upvotes: 7

Views: 13618

Answers (1)

Bryan Pendleton
Bryan Pendleton

Reputation: 16389

It sounds like the Perforce protect rules have been defined such that you have open permission for changedfile.cpp, but you do not have write permission.

See: https://www.perforce.com/perforce/doc.current/manuals/cmdref/p4_protect.html

open

This gives the user permission to do everything she can do with read access, and gives her permission to p4 add, p4 edit, p4 delete, and p4 integrate files. However, the user is not allowed to lock files or submit files to the depot.

Versus:

write

The user can do all of the above, and can also write files with p4 submit and lock them with p4 lock.

Your next step should be to contact your Perforce administrator and figure out why you only have open permission, not write permission.

Perhaps your account was not placed in the proper group; protections in the typical Perforce installation are granted to entire groups, not to individual developers, and hence you must be in the proper group to have the desired protections.

Upvotes: 6

Related Questions