Blog

svn: The repository at ‘‘ has uuid ‘‘, but the WC has ‘

If you’ve ever tried to switch your current working copy to a new SVN URL with ‘svn switch –relocate [old_repo] [new_repo]‘ command you may run into an error message similar to this: svn: The repository at ‘[new_repo]‘ has uuid ‘[new_uuid]‘, but the WC has ‘[old_uuid]‘ The reason for this is that Subversion expects the same [...]

Continue reading →

svn: Failed to add directory ‘foo/foo’: an unversioned directory of the same name already exists

Ever gotten this Subversion checkout/update operation error message? svn: Failed to add directory ‘foo/foo’: an unversioned directory of the same name already exists You can fix this problem by applying an extra option of “–force” to the SVN’s checkout/update command.  This will mark the folder in question as updated and the subfolder files as versioned [...]

Continue reading →

p4:// “no permission for operation on files(s)” Problem?

If you ever tried to do an integration activity in Perforce and have gotten a similar error message such as “no permission for operation on files(s)” then these are the steps you can do to resolve the problem: Check to make sure your branch spec or the source/target does not have any typo. Check to [...]

Continue reading →

Perforce password (P4PASSWD) invalid or unset error

If you have gotten “Perforce password (P4PASSWD) invalid or unset” error message when you’ve switched to the ticket based authentication, here’s what you can do to fix the problem: p4 login -p -a Simple. Straight forward.

Continue reading →

Importing a new Project in Perforce

I ran into another not-so-clear Perforce error message today while trying to import a new project to an existing depot.  I had a new project1 which I wanted to import into the existing // depot, but when I tried to add via P4V or ‘p4 add’ in the command line, I kept getting this message: [...]

Continue reading →

//projectfoo/bar/… – must refer to client ‘p4_client’.

Ever run into this error with Perforce’s ‘p4 changes’ or any other similar command? //projectfoo/bar/… – must refer to client ‘some_p4_client’.? I ran into this exact problem today.  I was trying to do a ‘p4 changes //projectfoo/bar/…@xxxxxx,yyyyyy’ to get a history of the changelist and got that error. The symptoms were that doing the same [...]

Continue reading →