views:

580

answers:

2

I am trying to delete an old user from our perforce installation. A previous admin had deleted all their active workspaces / clients so we should be able to now delete the user, however when i run

p4 user -f -d auser
User auser has file(s) open on 1 client(s) and can't be deleted.

However auser no longer has any associated clients, and if I filter the pending changelist view in P4V it shows the user as having one file checked out in the default changelist but no client is specified. Even if I log in as the user I dont seem to be able to revert or do anything with the file. Any hints how I might solve this?

+1  A: 

It would indeed be strange if the following to commands produced zero results:

  1. p4 clients -u auser

  2. p4 changes -s pending -u auser

Can you confirm this?

Scott Saad
Both of these return nothing. The file is still listed under pending changelists for the user.
Toby Allen
A: 

Solved.

A bit weird but this is what I did. I got the details of the default changelist that contained the file. It had the workspace name which was the name of a machine. I logged into the machine and then into perforce as the user. At this point I could see the pending changelist and revert the file. Now I can delete the user.

How did this happen?

I think what must of happened was a confusion of clients. A while back I changed the owner of quite a few clients on that machine (its the build server) and some of these clients must have had open files for the old user. This is the only explanation I can come up with.

Toby Allen