Hello Hugh,
please excuse the long delay.
> Two fsvs working trees which I have previously had no problems with now
> no longer respond to fsvs info, status etc.. I get the message "couldn't
> fine working copy with matching base".
Hmmm ... strange.
> What might be the cause of this ? Would sync-repos fix the problem ?
No, not directly; if there's no base found the URLs are unknown, too.
> I have examined the working trees, the FSVS CONF and WAA areas for each
> case and don't see any changes of any kind to the files and directories
> since the last successful commit. In each case, there is a _base link
> below FSVS_CONF which is still correct.
...
> The only thing I can think of that has changed since things were last
> working is the automounter.
...
> I notice now that if I follow the _base link under CONF to the working
> area tree, which is in an automounted folder, then do "pwd" I get
> $FSVS_CONF/.../_base. I am not sure if this is new behavior since the
> AMD change. I am not sure if this different than it was before the
> automounter change. The link is valid in the sense that cd works,
> expected files are seen etc.
Well, yes. It's good to know that.
FSVS determines the CONF and WAA directory by the full pathname - which will be
different if reached via symlinks, so it's normal that it won't work from there.
Could you please do a
realpath $FSVS_CONF/*/_base
and
fsvs info -d
in the WC root, and one directory below, and send me the results?
(Privately, if you prefer.)
Regards,
Phil
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=2807260
To unsubscribe from this discussion, e-mail:
[[email protected]].
