JJ> Hi, JJ> We had a vendor turnover a Perforce server to us with multiple depots. I
have set it up, we changed some things, and now have an empty depot to delete.
I cannot delete this depot! It had some files, etc. in it, but is now empty.

JJ> I cannot determine what remains that prevents Perforce from deleting the
depot. For example:

JJ> [c033633 at stplw054 c033633]$ p4 depot -d thedepot JJ> Depot thedepot isn't empty; clear it with 'p4 obliterate' first. JJ> [c033633 at stplw054 c033633]$ p4 obliterate -y //thedepot/... JJ> No records to delete.

JJ> Do changelists, other metadata affect the delete depot command? Anyone JJ> experienced this and can tell me what task(s) to do to delete this depot, JJ> or how to investigate what is preventing its deletion?

ISTR having a problem with obliterate once, which was simply that my client view didn't include the part of the depot I was trying to clobber. You might want to check that the permissions table isn't hiding anything from you either.

Failing that, ask perforce support, they're generally lovely :-)

--Simon