Perforce edit/open only working via depot name, not local name

perforce

I have my perforce client set up and had a problem trying to simply do a "p4 edit file.txt" from a subdirectory of the client root where file.txt is a checked-in file local to that directory. In other words, if I did "p4 have" I would see "//depot/folder/file.txt#2 – /proj/folder/file.txt" in the list. p4 sync seems fine. However, "p4 edit file.txt" would give the error "File(s) not on client."

I did finally get a p4 edit to work by using the depot name. "p4 edit //depot/folder/file.txt" DID work and strangely enough it modified the local file to have write permissions.

Any idea what the problem is? I have other clients on the same system for different projects that work the way you would expect, by referencing the local file name.

Best Answer

I've encountered problems like this using overlay mappings (entries in the client view with leading plus signs.

I've also encountered problems like this by changing the client view, but not performing a full 'p4 sync' afterwards to re-arrange all the files on my workstation to match the updated view.

Did you, by any chance, fit into either of those scenarios?

Have you tried running 'p4 where file.txt' and 'p4 where //depot/folder/file.txt'? Often that command is very useful for figuring out why the filename syntax on your command line isn't successfully resolving to a repository file name.

Related Solutions

How to convert Perforce depot locations to client view locations

I have always used the p4 where command for this. Here is its description from the built-in help:

where -- Show how file names map through the client view

p4 where [ file ... ]

    Where shows how the named files map through the client view.
    For each argument, three names are produced: the name in the
    depot, the name on the client in Perforce syntax, and the name
    on the client in local syntax.

    If no file is given, the mapping for '...' (all files in the
    current directory and below) is shown.

    Note that 'p4 where' does not determine where any real files are.
    It only computes where they should be according to the client view.

Perforce error – cannot submit from non-stream client

It's possible that P4V has guided you to create a stream depot and a mainline, but has somehow created a non-stream workspace for you. From what I've heard, that's likely to happen for first-time P4V users due to something in the setup.

To see if that's the problem, go to Connection/Edit Workspace and look in the 'Stream' field. Is it empty? If so, use Browse to select the stream. This will turn your current workspace into a stream workspace.

Best Answer

Related Solutions

How to convert Perforce depot locations to client view locations

Perforce error – cannot submit from non-stream client

Related Topic