Re: [fossil-users] Bug: Unable to clone

2017-06-12 Thread Richard Hipp
On 6/13/17, Roy Keene  wrote:
> Richard,
>
>   No change.
>

I checked in a change (to trunk) that seems likely to fix this.
Please try yet again using the latest trunk.
-- 
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: Unable to clone

2017-06-12 Thread Richard Hipp
On 6/13/17, Roy Keene  wrote:
>
> 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.
>

That can be your work-around until I get to the bottom of this.  I'm
currently in Budapest for an important couple of days of meetings, and
I have https://www.sqlite.org/src/tktview/cfa2c908f218254 to deal with
first, so there might be a little delay until I can get to this.

-- 
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: Unable to clone

2017-06-12 Thread Roy Keene

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: 699fca172dbd5820bce79a76d0eeb0d5fc52 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  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


Re: [fossil-users] Bug: Unable to clone

2017-06-12 Thread Richard Hipp
On 6/12/17, Roy Keene  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] Bug: Unable to clone

2017-06-12 Thread Roy Keene

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 ?

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


[fossil-users] Patch: Doctype for HTML5

2017-06-12 Thread Johan Kuuse
Hi,

A patch to include DOCTYPE html (HTML5) in web GUI where missing.
Also deleted  tags (which are XHTML specific, and invalid in HTML5).

Best Regards,
Johan
Index: ajax/index.html
==
--- ajax/index.html
+++ ajax/index.html
@@ -1,11 +1,11 @@
-http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
-http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+
+
 
 
 Fossil/JSON raw request sending
-
+
 http://ajax.googleapis.com/ajax/libs/jquery/1.6.4/jquery.min.js";>
 
 
 
 

[fossil-users] src/blob.c : blob_read_from_file overflow int size

2017-06-12 Thread kowlsd3pw23s
src/blob.c : blob_read_from_file
https://www.fossil-scm.org/index.html/artifact?ln=795&name=141d4f5494ed6d1a
795    int size,
801    size = file_wd_size(zFilename);
803    if( size<0 ){

It will not function normally if the file size is larger than INT_MAX.

file size is i64.
file_wd_size return i64.
but size is int.___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users