CODEWITHSUNDEEP
integrationperforce
ifnull
ifnull

Reputation: 249

Error opening librarian file when trying integration in Perforce

Today I was trying to integrate from a child streamC to a parent streamP (copy-up operation) in Perforce. This operation is performed almost every day and usually we don't experience any issues. But today something went wrong. On a few files Perforce throws an error:

Operation 'rmt-FileFetch' failed.
Librarian checkout /opt/perforce/..../fileA
Error opening librarian file /opt/perforce/..../fileA revision 1.2555519.
RCS checkout 1.2555519 failed!
RCS no such revision 1.2555519!

And the same error is shown on a few other files.

I've checked status of these files in a parent stream streamP and they are all marked for delete by somebody else.

Is it a bug in perforce that you cannot integrate file deletion if it is already marked for delete?

Or is it a perforce infrastructure issue and I need to talk to IT guys?

Upvotes: 0

Views: 4374

Answers (1)

Samwise
Samwise

Reputation: 71464

If the file is deleted in the source there shouldn't be a librarian operation at all. Sounds a lot like this (fixed) bug:

Bugs fixed in 2016.1

    #1378013 (Bug #85458) **
        'p4 copy' could produce a librarian error when attempting to copy
        a source file that was moved and then deleted.  Fixed.

https://www.perforce.com/perforce/doc.current/user/relnotes.txt

Upvotes: 2

Related Questions