Jump to content


"p4 push" - dvcs

dvcs

  • Please log in to reply
4 replies to this topic

#1 Kei Son

Kei Son

    Advanced Member

  • Members
  • PipPipPip
  • 46 posts

Posted 19 September 2015 - 10:09 AM

I have an error message like this when I hit "p4 push"

//mydepot/main/a/b/c/d.txt - locked by someone@stream.name

Does p4 lock every file down on the remote spec to push it?

#2 P4Sam

P4Sam

    Advanced Member

  • Members
  • PipPipPip
  • 484 posts
  • LocationSan Francisco, CA

Posted 19 September 2015 - 03:20 PM

A file that's locked by another user can't be updated -- this is true whether you're trying to submit a change to that file on the shared server, or push to the shared server from your local server.  You'll need to either wait for them to release the lock (i.e. submit their change or "p4 unlock" the file) or have an admin on the shared server force an unlock with "p4 unlock -f".

#3 Kei Son

Kei Son

    Advanced Member

  • Members
  • PipPipPip
  • 46 posts

Posted 23 September 2015 - 12:37 PM

Sounds like it is not feasible in production.

#4 Patrick B

Patrick B

    Member

  • Members
  • PipPip
  • 29 posts

Posted 23 September 2015 - 01:36 PM

It has nothing to do with the DVCS specifically.  They wouldn't be able to submit from a regular client either.  You presumably set up certain filetypes to lock for reason.  If you don't want that behavior then chante the typemap.  If a user explicitly locked a file, I'm assuming they had a reason.  Speak to that user.

#5 Kei Son

Kei Son

    Advanced Member

  • Members
  • PipPipPip
  • 46 posts

Posted 28 September 2015 - 12:48 PM

When using non-dvcs I can submit any file that isn't locked by another user. Why do `Push` lock every file on a stream?





Also tagged with one or more of these keywords: dvcs

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users