[fossil-users] moving repository

[Altu Faltu]

Is following sequence supposed to work for moving repository?

C:\test>fossil new test.fsl

C:\test>fossil open test.fsl

C:\test>ren test.fsl new.fsl

C:\test>fossil test-move-repository new.fsl

C:\test\fossil.exe: repository does not exist or is in an unreadable directory: C:/test/test.fsl

 

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

- Altu

[Konstantin Khomoutov]

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.
_______________________________________________
fossil-users mailing list
fossil...@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[Bill Burdick]

What about copying the repository, doing a test-move-repository, and then removing the original?

Bill

[Bill Burdick]

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).

[Konstantin Khomoutov]

On Wed, 21 Mar 2012 10:08:58 -0500
Bill Burdick <bill.b...@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...@lists.fossil-scm.org/msg06792.html

P.S.
Please don't top-post.

[Altu Faltu]

I formatted my system and the drive my original repository refers to doesn't exist any more. I can still use subst but following SQL fixed my problem:

C:\test> sqlite3 _FOSSIL_
sqlite> UPDATE vvar SET value='new.fsl' WHERE name='repository';

Unfortunately, fossil sqlite3 command also requires the main repository.
I guess it is a bug that these commands (sqlite3, test-move-repository) require access to repository. They could (and should) operate independent of it.

- Altu