Re: [fossil-users] Bug Report Update 1: Failure to Recover when Previous Fossil Process got Killed

2017-07-11 Thread Richard Hipp 
On 7/11/17, Martin Vahi  wrote:
>
> The cloning of the remote repository does not
> give me all of the files that the remote repository
> Web GUI shows to be present. The remote repository URL is:

It seems to work when I try this.  What files are you missing?

>
>
> https://www.softf1.com/cgi-bin/tree1/technology/flaws/silktorrent.bash/home
>
>
> Could someone please write,
> how can I get the cloning to properly work again?
>


-- 
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

Re: [fossil-users] Bug Report Update 1: Failure to Recover when Previous Fossil Process got Killed

2017-07-11 Thread Richard Hipp 
On 7/11/17, Martin Vahi  wrote:
>
> If I log into the web GUI of the remote Fossil repository
> and use the
>
> Admin -> Shunned -> Rebuild
>
> then the web GUI shows me:
>
> ---citation--start
>
> SQLITE_ERROR: no such table: ftsidx_segments

I think that bug was fixed here:
https://www.fossil-scm.org/fossil/timeline?y=ci=3200a7c72e41e783a16f

The repository should have recovered automatically.  To work around
the problem, disable full-text search for the repository prior to
running the rebuild.  Or (better) upgrade to the latest trunk version
of Fossil.

-- 
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

Re: [fossil-users] Bug Report Update 1: Failure to Recover when Previous Fossil Process got Killed

2017-07-11 Thread Stephan Beal 
On Tue, Jul 11, 2017 at 11:25 AM, Martin Vahi 
wrote:

>
> If I log into the web GUI of the remote Fossil repository
> and use the
>
> Admin -> Shunned -> Rebuild
>
> then the web GUI shows me:
>
> ---citation--start
>
> SQLITE_ERROR: no such table: ftsidx_segments
>
> Database Error
>
> no such table: ftsidx_segments:
> { DROP TABLE "ftsidx_segments"; DROP TABLE "ftsidx_segdir";
> DROP TABLE "ftsidx_docsize"; DROP TABLE "ftsidx_stat"; }


i'm fairly certain that that was fixed recently:

http://fossil-scm.org/index.html/info/3200a7c72e41e783


-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Bug Report Update 1: Failure to Recover when Previous Fossil Process got Killed

2017-07-11 Thread Martin Vahi 

If I log into the web GUI of the remote Fossil repository
and use the

Admin -> Shunned -> Rebuild

then the web GUI shows me:

---citation--start

SQLITE_ERROR: no such table: ftsidx_segments

Database Error

no such table: ftsidx_segments:
{ DROP TABLE "ftsidx_segments"; DROP TABLE "ftsidx_segdir";
DROP TABLE "ftsidx_docsize"; DROP TABLE "ftsidx_stat"; }

---citation--end-


The cloning of the remote repository does not
give me all of the files that the remote repository
Web GUI shows to be present. The remote repository URL is:


https://www.softf1.com/cgi-bin/tree1/technology/flaws/silktorrent.bash/home


Could someone please write,
how can I get the cloning to properly work again?

Thank You.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users