On Tue, Nov 28, 2017 at 12:01:45PM -0500, Richard Hipp wrote: > On 11/28/17, Jacob MacDonald <jaccar...@gmail.com> wrote: > > On my end, I added a couple of local files in two commits. Then I ran > > "fossil sync". The commits do not show up on Chisel even though the sync > > command says it succeeds. Furthermore, opening a new clone of the > > repository from Chisel seems to be corrupt: When I try to open it, it tells > > me the manifest is bad and no files get put on the disk. > > Obviously, I cannot test the syncing part because I don't have write > access on your chisel repo. But when I clone and open your repo, it > seems to work fine and report no errors. > > What version of Fossil are you running locally? What does "fossil version" > say? > > Try running: > > fossil sync --httptrace
If it can help, I've tried to clone the repo, and I notice that I got an error on "fossil open" command. Also, there was no file on my checkout. Then, I suspect problem with hash policy, since it involve version 2.1 and 2.4 where default hash-policy change. So here's what I got: $ fossil hash-policy shun-sha1 Since the repository on chisel use only sha1 hash, it's normal that I get nothing. So I change the hash-policy to "sha1", I did fossil up, and all file appear. I'm not sure if the problem is related and why the hash-policy after my clone was set to "shun-sha1". -- Martin G. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users