Hi Hugo,
Thank you for your quick reply!
Your idea really sounds good but unfortunately I got the same problem when
one file is backdated to an older revision:
1. Checkout whole project (including trunc and tags):
$ ls
./ ../ myproject/
$ cd myproject
$ ls
tags trunk branches
$ ls tags
[nothing here]
2. Backdating one file in trunc working copy:
$ svn update -r 1 trunc/oracle/directory/perftool.pm
U perftool.pm
Updated to revision 1.
3. Copying modified trunc into tags directory (looks good):
$ svn copy trunk tags/release1
A tags/release1
4. Commit new directory against repository (fails again):
$ svn commit -m "Blah bla"
Adding tags/release1
Adding tags/release1/oracle/directory/perftool.pm
svn: Commit failed (details follow):
svn: Out of date:
'/myproject/tags/release1/oracle/directory/perftool.pm' in transaction '18'
svn: Your commit message was left in a temporary file:
svn: '/DBA/users/kam/svn/myproject/svn-commit.tmp'
I really cannot believe that this does not work. Maybe my repository or my
compiled svn is not ok? But all other things work fine so the binaries seem
to be ok.
Thanks again!
Best Regards
Jens Kammler
-----Original Message-----
From: Hugo Heden [mailto:heden@foi.se]
Sent: Donnerstag, 13. Mai 2004 11:35
To: Jens.Kammler@Bertelsmann.de
Cc: users@subversion.tigris.org
Subject: Re: Creating complex tag with mixed revisions fails
On Thu, 13 May 2004 Jens.Kammler@Bertelsmann.de wrote:
> Hi all,
>
> I am trying to create a complex tag from a working copy where some files
are
> backdated to older revisions. This feature is described in the subversion
> book (chapter 4 "Branching And Merging", section "Tags", subsection
> "Creating a Complex Tag") but it seems not to work. I read the
documentation
> again and again but cannot find a mistake in the way I do it:
I can't see why that wouldn't work. But -
Have you tried doing the copy from WC to WC and then commiting? Something
like
$ ls
./ ../ myproject/
$ cd myproject
$ ls
tags trunk branches
$ ls tags
[nothing here]
$ svn copy trunk tags/release1
$ svn commit -m "Blah bla"
usually works for me. How does that work?
Best Regards
Hugo Heden
>
> 1. Checking out a fresh working copy from repository trunc of my project
> (svn checkout):
> $ svn co svn://myhost/SVNPSNK3/myproject/trunc myproject
> A myproject/orenge
> A myproject/orenge/nestlib
> A myproject/orenge/bin
> ... (many more files here)
> Checked out revision 10.
>
> 2. Verifying the status of the working copy directory where I would like
to
> backdate a file (svn status):
> $ cd directory
> $ svn status -v
> 10 2 kam .
> 10 1 kam splus.pm
> 10 1 kam oracs.pm
> 10 1 kam orasdb.pm
> 10 2 kam perftool.pm
> 10 1 kam execute.pm
>
> 3. Backdating file "perftool.pm" from rev 2 to older revision 1 (svn
> update):
> $ svn update -r 1 perftool.pm
> U perftool.pm
> Updated to revision 1.
>
> 4. Verifying status of the directory again (svn status):
> $ svn status -v
> 10 2 kam .
> 10 1 kam splus.pm
> 10 1 kam oracs.pm
> 10 1 kam orasdb.pm
> 1 1 kam perftool.pm
> 10 1 kam execute.pm
>
> 5. Making a snapshot of the whole working copy by creating a tag (svn copy
> WC -> URL) fails now:
> $ ls
> ./ ../ myproject/
>
> $ svn copy myproject svn://myhost/SVNPSNK3/myproject/tags/release1
> -m "Release 1 with old perftool"
> svn: Commit failed (details follow):
> svn: Out of date:
> '/myproject/tags/release1/oracle/directory/perftool.pm' in transaction
'16'
>
> Of course the file perftool.pm is out of date, it is from an older
revision.
> But this is exactly the snapshot I need and this should be a subversion
> feature.
>
> I also tried to create the directory tags/release1 first in the repository
> before making the snapshot. This did not help.
>
> The svn version I use is 1.0.2 (r9423), self compiled on Linux.
>
>
> I would be very happy if someone could help me in this issue.
>
> Regards
>
> Jens Kammler
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 13 14:11:15 2004