You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Fabian Cenedese <Ce...@indel.ch> on 2005/07/27 14:58:14 UTC
tag moving
Hi
I'm looking for the equivalent of cvs tag -F.
Does svn support the move of a tag? And if so how should this be done?
I know that the creation of a tag is a simple svn copy. And I can merge
differences from another branch/trunk into this branch and therefore
"move" the tag to other versions (as long as there haven't been any
changes in current).
Is this the same as:
svn delete (repo)/tags/current
svn copy (repo)/trunk (repo)/tags/current
Would a checked out working copy get any new files with
svn update?
Thanks
bye Fabi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: tag moving
Posted by David Weintraub <qa...@gmail.com>.
On 7/29/05, Fabian Cenedese <Ce...@indel.ch> wrote:
> Well, it can't be that a user always has to "switch" to the same tag
> he supposedly is already on. I mean, that's what update is for, no?
> I will do some more testing. Thanks for the help though.
There is data stored in the .svn/entries file that tells Subversion
what version the directory is at, the URL the working directory is
attached to, and the UUID of the repository. I have a feeling that
something in this file was losing track of the tag you were using and
its location. I don't know what that could be, but if you still have
the old tag working directory, it would be interesting to compare its
.svn/entries file with the new working directory you just checked out.
So far, I've been unable to successfully duplicate your error, so I
really don't know why Subversion behaved the way it did.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: tag moving
Posted by Fabian Cenedese <Ce...@indel.ch>.
>> That's what I did. The problem is that I had a checked out working
>> copy of the older tag. When I then updated this copy with the now
>> new "current" tag it only updated the existing files. But there were
>> also new files in the new tag and they didn't get created in the
>> existing working copy. Only when I checked out anew I also got
>> the new files (don't know about deleted files, didn't test yet).
>>
>> cvs update had a switch -d to create directories which were new
>> in the repo. But I couldn't find a similar switch for svn update.
>> Anyway, the new files were in an existing directory, so I would
>> have needed a flag to update also new files.
>>
>> So: should it work to update and get new files or do I need to do a
>> new checkout? Updating from the trunk usually also gets new
>> files so it generally works fine.
>
>So, checking out a clean work directory was fine. Doing an "svn
>update" on the old work directory had problems.
>
>You may need to do a "svn switch" even though the URL is actually the
>same. I don't know enough of Subversion's internals to understand how
>it tracks the URL, but I suspect that that the old working directory
>is still pointing to the old tag directory and not the new one.
Well, it can't be that a user always has to "switch" to the same tag
he supposedly is already on. I mean, that's what update is for, no?
I will do some more testing. Thanks for the help though.
bye Fabi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: tag moving
Posted by David Weintraub <qa...@gmail.com>.
So, checking out a clean work directory was fine. Doing an "svn
update" on the old work directory had problems.
You may need to do a "svn switch" even though the URL is actually the
same. I don't know enough of Subversion's internals to understand how
it tracks the URL, but I suspect that that the old working directory
is still pointing to the old tag directory and not the new one.
On 7/28/05, Fabian Cenedese <Ce...@indel.ch> wrote:
>
> >> svn delete (repo)/tags/current
> >> svn copy (repo)/trunk (repo)/tags/current
> >>
> >> Would a checked out working copy get any new files with
> >> svn update?
> >
> >* You have a tag REL1.0 over various versions of your files. However,
> >you decide that the versions tagged as REL1.0 isn't the right version
> >(maybe the release was pulled at the last minute). In this case,
> >simply delete the tag directory REL1.0 and recreate it by copying the
> >correct version of the release..
>
> That's what I did. The problem is that I had a checked out working
> copy of the older tag. When I then updated this copy with the now
> new "current" tag it only updated the existing files. But there were
> also new files in the new tag and they didn't get created in the
> existing working copy. Only when I checked out anew I also got
> the new files (don't know about deleted files, didn't test yet).
>
> cvs update had a switch -d to create directories which were new
> in the repo. But I couldn't find a similar switch for svn update.
> Anyway, the new files were in an existing directory, so I would
> have needed a flag to update also new files.
>
> So: should it work to update and get new files or do I need to do a
> new checkout? Updating from the trunk usually also gets new
> files so it generally works fine.
>
> Thanks
>
> bye Fabi
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
--
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: tag moving
Posted by Fabian Cenedese <Ce...@indel.ch>.
>> svn delete (repo)/tags/current
>> svn copy (repo)/trunk (repo)/tags/current
>>
>> Would a checked out working copy get any new files with
>> svn update?
>
>* You have a tag REL1.0 over various versions of your files. However,
>you decide that the versions tagged as REL1.0 isn't the right version
>(maybe the release was pulled at the last minute). In this case,
>simply delete the tag directory REL1.0 and recreate it by copying the
>correct version of the release..
That's what I did. The problem is that I had a checked out working
copy of the older tag. When I then updated this copy with the now
new "current" tag it only updated the existing files. But there were
also new files in the new tag and they didn't get created in the
existing working copy. Only when I checked out anew I also got
the new files (don't know about deleted files, didn't test yet).
cvs update had a switch -d to create directories which were new
in the repo. But I couldn't find a similar switch for svn update.
Anyway, the new files were in an existing directory, so I would
have needed a flag to update also new files.
So: should it work to update and get new files or do I need to do a
new checkout? Updating from the trunk usually also gets new
files so it generally works fine.
Thanks
bye Fabi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: tag moving
Posted by David Weintraub <qa...@gmail.com>.
The tags directory is simply a regular directory. You can copy it,
change it, or even delete it with the regular svn commands.
In CVS terms, you could be talking about two things:
* You have a tag REL1.0 over various versions of your files. However,
you decide that the versions tagged as REL1.0 isn't the right version
(maybe the release was pulled at the last minute). In this case,
simply delete the tag directory REL1.0 and recreate it by copying the
correct version of the release..
* You have a tag REL1.0 over various versions of your files.
Suddently, a developer comes with "one more change" that you want to
squeeze into your system. In this case, checkout the REL1.0 tag
directory, change the files, and commit your changes.
On 7/27/05, Fabian Cenedese <Ce...@indel.ch> wrote:
> Hi
>
> I'm looking for the equivalent of cvs tag -F.
>
> Does svn support the move of a tag? And if so how should this be done?
> I know that the creation of a tag is a simple svn copy. And I can merge
> differences from another branch/trunk into this branch and therefore
> "move" the tag to other versions (as long as there haven't been any
> changes in current).
>
> Is this the same as:
> svn delete (repo)/tags/current
> svn copy (repo)/trunk (repo)/tags/current
>
> Would a checked out working copy get any new files with
> svn update?
>
>
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org