On 9/3/2014 9:39 PM, Richard Hipp wrote:
On Wed, Sep 3, 2014 at 3:23 PM, Philip Bennefall <phi...@blastbay.com
<mailto:phi...@blastbay.com>> wrote:
Hi all,
I am having a strange problem with Fossil. I and a friend are
collaborating on a project together, and everything has been
working just fine up until now. Today when I tried to grab the
latest commit which I knew he had made, it told me that I already
have the latest version. However when I check the website, I can
see the new version which is the leaf of trunk, and is one child
after my own. I tried both fossil update, sync, pull, and even
rebuild and then the other commands again.
To be clear. When I update I do not get an error, rather I see the
log entry for my own last commit and am told that this is the
latest one even though the web interface on the remote server says
otherwise.
I should mention that the version of Fossil that is on the server
is about 10 months older than the one we both have locally on our
machines. Can that be a problem?
Please try "fossil sync --verily" and see if that clears the problem.
There was a sync problem that has been fixed in trunk, but not (yet)
in the latest release.
Hi Richard,
That fixed the problem immediately. Thanks! I only have one question.
Was this a problem that could be said to be on the server side or the
client side? In other words, if I were running the latest version on my
local machine but an older version without this bugfix on the machine
acting as server, would I experience this problem? And how about the
other way around (old client and new server version)?
Kind regards,
Philip Bennefall
--
D. Richard Hipp
d...@sqlite.org <mailto:d...@sqlite.org>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
