Build and Release Management » Source Control

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

admin — Thu, 04 Aug 2011 19:03:16 +0000

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 repository from the svn switch command and you wouldn’t run into this problem if you had done an svnsync on it.

At any rate, to solve the above error, you must do an svnadmin setuuid [path/to/new/repo] ‘[old_uuid]‘ on your new repo so that the uuid matches. Hope that solves your problem.

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

admin — Sat, 18 Sep 2010 00:42:46 +0000

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 but will not overwrite any of YOUR files in there.

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

admin — Mon, 13 Sep 2010 23:04:33 +0000

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 make sure you are branching within a source tree such as //softwareX/branches/1.0/… //softwareX/branches/1.1/… and NOT //softwareX/branches/1.0/… to //softwareY/branches/1.1/…
Check p4 protect to make sure your account has write permission within that code line.

Perforce password (P4PASSWD) invalid or unset error

admin — Mon, 28 Jun 2010 19:58:11 +0000

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.

Importing a new Project in Perforce

admin — Wed, 20 Jan 2010 20:22:21 +0000

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:

D:\Work\P4>p4 client myproject_foo
Error in client specification.
Mapping ‘//some_directory/…’ is not under ‘//some_other_directory/…’.
Hit return to continue…

After fumbling around, I found that I had to create a depot first as the superuser in the command line before I can import/add the new project:

p4 depot new_project

Then now I can add new project to my clientspec in the command line like this:

p4 client (it will open a notepad window, just add your new project under the ‘View:’ section, save, and close)

Now you can do ‘p4 add’ or using P4V to import your new project.

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

admin — Fri, 03 Apr 2009 23:01:35 +0000

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 command on other projects within the depot worked perfectly fine as well as trying it on another platform and system.

After googling and running into a brick wall, I started to scrutinize the depot and the naming convention then bam! I Found the solution!

Turns out that inside the depot, “projectfoo” is actually “ProjectFoo.” Do you see the difference yet? Now I tried ‘p4 changes //ProjectFoo/bar/…@xxxxxx,yyyyyy’ and it magically worked.

In short, Perforce is extremely case sensitive when it comes to the command operations. Generally, its a good practice to keep everything within the depot as lower case to avoid unique problems like these.