On 6/12/17, Roy Keene <fos...@rkeene.org> wrote: > All, > > I've run into a bug with Fossil 2.2 where I am unable to clone my > current repository. Instead of cloning I get: > > $ mkdir /tmp/fossil-2.2-upstream > $ cd /tmp/fossil-2.2-upstream/ > $ wget http://fossil-scm.org/index.html/uv/fossil-linux-x86-2.2.tar.gz > fossil-linux-x86-2.2.tar.gz > $ tar -xf fossil-linux-x86-2.2.tar.gz > $ readlink -f fossil > /tmp/fossil-2.2-upstream/fossil > $ /tmp/fossil-2.2-upstream/fossil rebuild > 100.0% complete... > rebuilding the search index... done > $ rm -f /tmp/x.repo; /tmp/fossil-2.2-upstream/fossil clone > ~/devel/aurae/.repo /tmp/x.repo > Repository cloned into /tmp/x.repo > Rebuilding repository meta-data... > 0.0% complete... > SQLITE_ERROR: no such table: ftsidx_segments > /tmp/fossil-2.2-upstream/fossil: no such table: ftsidx_segments: { > DROP TABLE "ftsidx_segments"; > DROP TABLE "ftsidx_segdir"; > DROP TABLE "ftsidx_docsize"; > DROP TABLE "ftsidx_stat"; > } > > > Is this a known bug ? Is there any resolution ?
I don't recall anything like this. Have you tried using the latest trunk version of Fossil (which is to say, the version of Fossil being used on Fossil's self-hosting website)? -- D. Richard Hipp 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
