Richard,
No change.
See below:
$ fossil info
project-name: Fossil
repository: /home/rkeene/devel/fossil/.repo
local-root: /home/rkeene/devel/fossil/
config-db: /home/rkeene/.fossil
project-code: CE59BB9F186226D80E49D1FA2DB29F935CCA0333
checkout: 699fca172dbd5820bce79a76d0eeddddb0d5fc52 2017-06-12
01:23:28 UTC
parent: 1b3fa2610a494166b7ab61c6fd6bfab8b1752be4 2017-06-11
16:25:56 UTC
tags: trunk
comment: Remove another set of extraneous backslash from an error
message in the ticket editing webpage. (user: mistachkin)
check-ins: 10607
$ ./fossil version
This is fossil version 2.3 [699fca172d] 2017-06-12 01:23:28 UTC
$ rm -f /tmp/x.repo; ./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
./fossil: no such table: ftsidx_segments: {
DROP TABLE "ftsidx_segments";
DROP TABLE "ftsidx_segdir";
DROP TABLE "ftsidx_docsize";
DROP TABLE "ftsidx_stat";
}
$
There's nothing particularly special about this repo... I have FTS enabled:
$ fossil fts
check-in search: off
document search: on
ticket search: on
wiki search: on
Porter stemmer: off
full-text index: enabled
documents: 3512
$
I tried "fossil fts-config reindex", but no change.
If I do "fossil fts-config index off" then I can clone, but if I then do
"fossil fts-config index on" I cannot again due to the same error.
Thanks,
Roy Keene
On Tue, 13 Jun 2017, Richard Hipp wrote:
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
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
