On Wed, 21 Mar 2012 10:08:58 -0500 Bill Burdick <bill.burd...@gmail.com> wrote:
[...] > >> > C:\test>fossil test-move-repository c:\test\new.fsl > >> > C:\test\fossil.exe: repository does not exist or is in an > >> > unreadable directory: C:/test/test.fsl > >> > > >> > C:\test>fossil version > >> > This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC > >> Same problem here with 1.21 also on Windows. > >> Not renaming the original repository before running the command > >> complains that the target repository does not exist. > >> So in the end there seems to be no way to actually run this command > >> successfully. > > What about copying the repository, doing a test-move-repository, > > and then removing the original? > Or, you could hard link it, instead of copying it, if the new > location is on the same volume as the old (hard linking works on > windows, too). Following this line of thinking I could as well just run sqlite3 command-line binary on the checkout fossil database and manually hack the necessary entry in an appropriate table. What the OP implied is that that command's implementation probabaly contains a bug and I demonstrated that it indeed seems so. Also see this discussion: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg06792.html P.S. Please don't top-post. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
