* Message by -Ph. Marek- from Sun 2010-05-16: > Hello Lasse, > > On Sunday 16 May 2010 Lasse Kliemann wrote: > > This sounds like a really simple issue, but I did not find out > > how to do it. I want to rename a working copy and then continue > > using it with the old URL. There are many ways to change the URL > > of a working copy, but not the other way round. > you are right; as the addressing of the working copy and the properties is > done via MD5 of the pathname, a working copy move is not really supported at > the time. > > > Of course, I can do a fresh checkout in the new location. But > > this working copy is so large that I rather would like to simply > > do a mv or a local rsync to rename it. > Well, the easiest way is to go to the current working copy, do > > old/ # fsvs urls dump > /tmp/fsvs-urls > > and then move or rename the working copy, followed by going into the new path > and starting > > new/ # fsvs urls load < /tmp/fsvs-urls > > to initialize the new path configuration. > > # ls -la /etc/fsvs/ > > shows the new and old config directories - simply move the files from the old > directory into the new one (would be Urls and Ign, I think);
I followed the instructions so far. Since I have no ignores here and the URLs are the same, the two config directories only differ in the README.txt file, where it gives the working copy path (as expected). > then do a > > new/ # fsvs sync-repos > > to fetch current file list and properties for the new paths. This steps fails. There comes a list of (probably all) files in the usual format: [...] N..... 0 2009/tmp/draft.tex N..... 0 2009/tmp/main.tex [...] Then it concludes: An error occurred at 16:53:09.697: No such file or directory (2) in main: action sync-repos failed This is with -vvv. The new working copy was created from the old one by 'rsync -a'. I cannot do mv in the actual application, since the data is on different file systems there. > That way you can at least keep the local data, and save network bandwidth. > > Sorry for the bother; I hope that helps. Thank you for the quick answer. Maybe we can still get this working.
pgpfgsqpqVnUt.pgp
Description: PGP signature
