[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: disappearing tags

From: Ryan Schmidt <subversion-2006q2_at_ryandesign.com>
Date: 2006-06-06 15:20:02 CEST

On Jun 6, 2006, at 04:38, Michael P. Soulier wrote:

> I have a project called "rem", with the standard structure.
> rem/trunk
> rem/tags/release-0.3
> rem/tags/release-0.4
> rem/tags/release-0.5
> I just created the 0.5 tag. Now, the project has been renamed, so
> in addition
> to renaming a lot of files, I also renamed the rem directory. Now
> it's...
> MiProf/trunk
> MiProf/tags/release-0.3
> MiProf/tags/release-0.4
> Umm, where did release-0.5 go??
> Help appreciated. I tried an svn up, but it's up to date.

Check the log. If your repository is $REPO, try:

svn log -v $REPO/MiProf --stop-on-copy

Maybe that'll show too much output, I'm not sure... but it should
show you what was copied from where. Presumably you'll see that the
0.5 release tag was not copied.

The reason for this could be that you had a working copy of maybe the
whole repository checked out? And you did this move in that working
copy? And you didn't run "svn up" on the root directory before doing
so? Presumably that would mean that the revision of the rem directory
when you did the move was before the revision in which the 0.5
release tag existed, so it was not copied with the rest of it.

One solution now would be to copy the 0.5 release tag from the old
URL to the new one with something like

svn cp \
$REPO/rem/tags/release-0.5@$FOO \
$REPO/MiProf/tags \
-m "Re-adding 0.5 release tag"

where $FOO is a revision in which the 0.5 release tag still existed.

I'm a little worried though that maybe some other changes weren't
copied either. It could depend on how long ago you last ran "svn up"
on that root directory. It might be better to just delete the entire
MiProf directory and do the copy again, "properly." By "properly" I
don't mean that there was anything wrong with the way you did it,
it's just that you have to make sure the directories are up-to-date
in the working copy before doing so, and as you see that's easy to
forget. I'd try:

svn rm \
$REPO/MiProf \
-m "Deleting incorrectly-copied MiProf project"

svn cp \
$REPO/rem@$BAR \
$REPO/MiProf \
-m "Renaming rem to MiProf"

where $BAR is the last revision in which rem existed.

The recommended practice is not to check out the entire repository --
this gets unwieldy as you start getting a lot of branches or tags.
Usually you should just check out the part of the repository you need
to use -- like the trunk. And if you need to work on a branch, then
you can "svn switch" to it, do the work in the branch, and then
switch back to the trunk.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 6 15:21:33 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.