Release Engineering is always eager and willing to support our Development and QA user communities. Send email to Release Engineering to add your question to the FAQ.
By default, Perforce won't remove empty directories as it goes, but you can change that behavior.
Do 'p4 client clientname' to bring up the client spec form in notepad or vi, then change 'normdir' to 'rmdir' on the Options line, then save and exit the editor.
That will clean up empty directories once the last file is removed from the directory, either via 'p4 delete' or even 'p4 sync ...#0'. It will only clean up completely empty directories, so it only works if there aren't any view private files (e.g. *.o files or other derived objects) sitting around in the directory structure. You can think of it as doing a safe 'rmdir', not an '/bin/rm –rf'.
Bad parameters passed to mangler"?
p4 -u ylegere client -o', generated this output:
Date 2004/12/17 11:13:41: Operation: user-client Operation 'user-client' failed. Bad parameters passed to mangler!
This indicates that the password field in the user spec somehow contained an invalid character, perhaps a Unicode character. To fix it, delete and then recreate the user's account. Do the following as a P4 super user:
p4 user –o ylegere > user.txt
Edit the user.txt file; delete the Update:, Access:, and Password: fields. Then, delete and recreate the user's account like this:
p4 user –d –f ylegere p4 user –I < user.txt p4 passwd –P hello ylegere
Note: Do NOT use the RemoveUsers.pl utility, since this will cause Perforce to forget what groups the user has access to.
So far, this has been reported only once, and on Windows.
Last updated Mon, 21 Feb 2005, 19:13:33 ET