Hello,
I discovered something strange when moving repositories (I wanted to
consolidate the location of some of mine). After some searching I came
up with three possibilities for a repository relocation:
1) Simple moving the file and then updating the location both in the
global configuration database as well as all checkout databases (which
in my case would've been only one) via raw SQL commands.
2) Closing the checkout(s), moving the repository, and the re-opening
the checkout(s).
3) Using the "test-move-repository" command (which I found in some of
the archived list e-mails).
Is that correct, or are there more ways?
I considered variant 1 as too "manual" and too error-prone, and (despite
the "--force" option for closing and the "--keep" option for re-opening)
variant 2 has its disadvantages as well (like losing the undo history,
the stash etc). Therefore I opted for variant 3.
The move was successful in the end, but after issuing the command, the
repository disappeared from the list of all repositories in the
configuration database, i.e., it was not contained in the "fossil all
list" output anymore. Luckily, after doing the first commit, it
reappeared again…
My questions here are:
• Does this happen on purpose or is this a bug? For me it seems odd that
the repository gets (temporarily) "lost" from the list of all
repositories and thus excluded from all "fossil all" commands until
being added again later.
• If this is bug, why is it resolved by the first commit to the involved
repository? My naive understanding is that a commit only affects the
respective checkout database as well as of course the repository
database itself, but not the global configuration database?
In case this is indeed a bug, I can file a ticket (though the issue is
not critical due to its exceptional nature).
Thanks!
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
