[fossil-users] 'test-page++.wiki' in release-checklist not accessible atm

2014-07-25 Thread Michai Ramakers
Hello,

while browsing fossil's docs, I noticed the 'test-page++.wiki' in item #4 on

https://fossil-scm.org/index.html/doc/trunk/test/release-checklist.wiki

is not accessible. I don't really understand why - building that
version locally and running using 'server' works ok.

Probably known / work in progress / whatever, but just for info.

Michai
___
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] 'test-page++.wiki' in release-checklist not accessible atm

2014-07-25 Thread Stephan Beal
On Fri, Jul 25, 2014 at 2:58 PM, Michai Ramakers m.ramak...@gmail.com
wrote:


 https://fossil-scm.org/index.html/doc/trunk/test/release-checklist.wiki

 is not accessible. I don't really understand why - building that
 version locally and running using 'server' works ok.


The trunk works for me locally, too.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
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


Re: [fossil-users] 'test-page++.wiki' in release-checklist not accessible atm

2014-07-25 Thread Richard Hipp
On Fri, Jul 25, 2014 at 8:58 AM, Michai Ramakers m.ramak...@gmail.com
wrote:

 Hello,

 while browsing fossil's docs, I noticed the 'test-page++.wiki' in item #4
 on


 https://fossil-scm.org/index.html/doc/trunk/test/release-checklist.wiki

 is not accessible. I don't really understand why - building that
 version locally and running using 'server' works ok.


The web server on the https://www.fossil-scm.org/ machine filters URLs that
contain characters other than [a-zA-Z0-9_/].  Any characters not in that
set are converted into _.  This is a security feature of that web
server.  But as it blocks + symbols (even those encoded as %2B) it also
blocks the link above.

This is, therefore, a feature, not a bug.


-- 
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] Fossil is now 7 years old

2014-07-25 Thread Richard Hipp
The seventh anniversary of the first self-commit of Fossil source code was
this past Monday.  Time flies.

The logical predecessor of Fossil was CVSTrac (http://www.cvstrac.org/)
which was a wiki and trouble-ticket system built atop CVS.  CVSTrac became
the inspiration for Trac (http://trac.edgewall.org/wiki/CvsTrac) which is a
similar tool for SVN that became far more popular than CVSTrac and which is
still in active use.  Fossil was originally created to provide features
needed in SQLite development, features that I couldn't get with
CVS+CVSTrac, or with Monotone or Git or Mercurial or any other
configuration management system available at the time.  I worked on
prototypes of Fossil for a year or more prior to the first self-commit on
2007-07-21, but none of those early prototypes survive.

Code archeologists will be able to find a lot of commonality between the
CVSTrac and Fossil source codes.  There is a clear genetic relationship
between the two systems.

Fossil was created for the purpose of aiding in the development of SQLite.
(Other uses for Fossil, though welcomed, are secondary.)  The SQLite
documentation sources (http://www.sqlite.org/docsrc/timeline?a=2000-01-01)
were split off from the SQLite source tree in CVS on 2007-11-12, just a few
months after Fossil began self-hosting.  But the core SQLite source code
did not move to Fossil until 2009-08-11, just after the release of SQLite
version 3.6.17, over two years after Fossil became self-hosting.  The move
from CVS to Fossil has proven to be a boon for SQLite development.

CVSTrac was in active use by SQLite for a little over 7 years.  To my
knowledge, nobody uses CVSTrac any more.  (OpenSSL was the last known user
of CVSTrac and they switched over to Git at the beginning of 2013.) Fossil
will soon overtake CVSTrac in terms of years of use, and Fossil has a great
deal more momentum and a much larger user base than CVSTrac ever had.

-- 
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] Fossil is now 7 years old

2014-07-25 Thread Stephan Beal
Congratulations on an undisputably successful project :)

On Fri, Jul 25, 2014 at 5:57 PM, Richard Hipp d...@sqlite.org wrote:

 CVSTrac was in active use by SQLite for a little over 7 years.  To my
 knowledge, nobody uses CVSTrac any more.  (OpenSSL was the last known user
 of CVSTrac and they switched over to Git at the beginning of 2013.) Fossil
 will soon overtake CVSTrac in terms of years of use, and Fossil has a great
 deal more momentum and a much larger user base than CVSTrac ever had.


With libfossil slowly taking shape, i think there's still a lot more
momentum to build...

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
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


Re: [fossil-users] Fossil is now 7 years old

2014-07-25 Thread Gour
Richard Hipp d...@sqlite.org writes:

 The seventh anniversary of the first self-commit of Fossil source code was
 this past Monday.  Time flies.

Congratulations, Richard!!

The (D)VCS world would be much poorer without existance of Fossil: ;)


Sincerely,
Gour

-- 
Everyone is forced to act helplessly according to the qualities 
he has acquired from the modes of material nature; therefore no 
one can refrain from doing something, not even for a moment.

___
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] Fossil is now 7 years old

2014-07-25 Thread Miles Fidelman

Happy Birthday to Fossil and congratulations to Richard!

Miles Fidelman

Richard Hipp wrote:
The seventh anniversary of the first self-commit of Fossil source code 
was this past Monday.  Time flies.


The logical predecessor of Fossil was CVSTrac 
(http://www.cvstrac.org/) which was a wiki and trouble-ticket system 
built atop CVS. CVSTrac became the inspiration for Trac 
(http://trac.edgewall.org/wiki/CvsTrac) which is a similar tool for 
SVN that became far more popular than CVSTrac and which is still in 
active use.  Fossil was originally created to provide features needed 
in SQLite development, features that I couldn't get with CVS+CVSTrac, 
or with Monotone or Git or Mercurial or any other configuration 
management system available at the time.  I worked on prototypes of 
Fossil for a year or more prior to the first self-commit on 
2007-07-21, but none of those early prototypes survive.


Code archeologists will be able to find a lot of commonality between 
the CVSTrac and Fossil source codes. There is a clear genetic 
relationship between the two systems.


Fossil was created for the purpose of aiding in the development of 
SQLite.  (Other uses for Fossil, though welcomed, are secondary.)  The 
SQLite documentation sources 
(http://www.sqlite.org/docsrc/timeline?a=2000-01-01) were split off 
from the SQLite source tree in CVS on 2007-11-12, just a few months 
after Fossil began self-hosting.  But the core SQLite source code did 
not move to Fossil until 2009-08-11, just after the release of SQLite 
version 3.6.17, over two years after Fossil became self-hosting.  The 
move from CVS to Fossil has proven to be a boon for SQLite development.


CVSTrac was in active use by SQLite for a little over 7 years. To my 
knowledge, nobody uses CVSTrac any more.  (OpenSSL was the last known 
user of CVSTrac and they switched over to Git at the beginning of 
2013.) Fossil will soon overtake CVSTrac in terms of years of use, and 
Fossil has a great deal more momentum and a much larger user base than 
CVSTrac ever had.


--
D. Richard Hipp
d...@sqlite.org mailto: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



--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra

___
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] Fossil is now 7 years old

2014-07-25 Thread Philip Bennefall
I only discovered Fossil about 3 months ago, but I'm already very 
comfortable using it and have switched all my projects to it. I came 
from SVN and haven't looked back once.


Kind regards,

Philip Bennefall
On 7/25/2014 5:57 PM, Richard Hipp wrote:
The seventh anniversary of the first self-commit of Fossil source code 
was this past Monday.  Time flies.


The logical predecessor of Fossil was CVSTrac 
(http://www.cvstrac.org/) which was a wiki and trouble-ticket system 
built atop CVS. CVSTrac became the inspiration for Trac 
(http://trac.edgewall.org/wiki/CvsTrac) which is a similar tool for 
SVN that became far more popular than CVSTrac and which is still in 
active use.  Fossil was originally created to provide features needed 
in SQLite development, features that I couldn't get with CVS+CVSTrac, 
or with Monotone or Git or Mercurial or any other configuration 
management system available at the time.  I worked on prototypes of 
Fossil for a year or more prior to the first self-commit on 
2007-07-21, but none of those early prototypes survive.


Code archeologists will be able to find a lot of commonality between 
the CVSTrac and Fossil source codes. There is a clear genetic 
relationship between the two systems.


Fossil was created for the purpose of aiding in the development of 
SQLite.  (Other uses for Fossil, though welcomed, are secondary.)  The 
SQLite documentation sources 
(http://www.sqlite.org/docsrc/timeline?a=2000-01-01) were split off 
from the SQLite source tree in CVS on 2007-11-12, just a few months 
after Fossil began self-hosting.  But the core SQLite source code did 
not move to Fossil until 2009-08-11, just after the release of SQLite 
version 3.6.17, over two years after Fossil became self-hosting.  The 
move from CVS to Fossil has proven to be a boon for SQLite development.


CVSTrac was in active use by SQLite for a little over 7 years. To my 
knowledge, nobody uses CVSTrac any more.  (OpenSSL was the last known 
user of CVSTrac and they switched over to Git at the beginning of 
2013.) Fossil will soon overtake CVSTrac in terms of years of use, and 
Fossil has a great deal more momentum and a much larger user base than 
CVSTrac ever had.


--
D. Richard Hipp
d...@sqlite.org mailto: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] 'open --nested', quick poll

2014-07-25 Thread Warren Young

On 7/22/2014 08:38, Michai Ramakers wrote:


I was wondering how many of you use 'open --nested' to have nested workdirs?


Thanks to this thread, I became aware of open --nested, and promptly 
found a use for it.  So thank you. :)


Here's the problem that open --nested solved for us:

We keep two main lines of development open on our main Fossil repo: the 
development trunk and the stable branch.  Bug fixes made on the trunk 
get backported to stable.  Sometimes we backport features, too.


As it happens, there is one small section of the trunk that works better 
if it is shared exactly between trunk and the stable branch, rather than 
participate in the code fork set up by the branch.


Prior to learning about open --nested, we coped with this by ignoring 
the stable branch's fork of that piece of the code repository.  All 
changes had to be made on trunk only.  This was awkward, and sometimes 
led to people making the change on the branch instead of on the trunk.


open --nested let us move this logically separate section of the tree 
out into a separate Fossil repo, but then reattach it at its old 
position within the trunk and branch checkouts.


Except for the fact that fossil ci can mean two different things now, 
depending on your working directly, no one can tell that anything has 
changed.  It appears that the stable branch and the development trunk 
simply share a common subset.


Actually, there is *one* other difference.  Checkins on the extracted 
repository run a lot faster, due to it being a lot smaller. :)

___
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] Fossil is now 7 years old

2014-07-25 Thread Ron W
On Fri, Jul 25, 2014 at 1:38 PM, Michai Ramakers m.ramak...@gmail.com
wrote:

 (one
 CVSTrac thing which I still miss in some more fancypants
 issue-trackers is the concept of ticket-groups).


You could probably do that in Fossil by adding additional ticket fields and
customizing the TH1 ticket handling code.

Shortly after I discovered Fossil, I customized the ticket handling to work
with our process flow. I posted an early version of that to this list -
about 2.5 years ago.
___
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] Fossil is now 7 years old

2014-07-25 Thread Joe Prostko
Congratulations!   I must say that Fossil is the best thing to happen
to my development workflow this year, as I am pretty sure that using
Git has resulted in the premature death of too many of my brain cells.
I'm glad to be able to replace Git in every place that I possibly can
with Fossil.

The occasion of the seven year anniversary reminds me of something
I've been meaning to ask on the list.  It has been asked in the past
according to my check of the archives, but is there any chance you
would be willing to go on Floss Weekly and talk about Fossil?  I know
that you were on there to talk about SQLite quite some time ago, but I
would love for there to be a show featuring Fossil.  I know that
Randal's current way for projects to get on the show is that he will
only schedule a time if the project leader(s) contacts him directly.
In any case, I hope you will consider going on the show (alone or with
another core committer), as it would be a great way to let more people
know about the awesomeness that is Fossil.

- joe

On Fri, Jul 25, 2014 at 11:57 AM, Richard Hipp d...@sqlite.org wrote:
 The seventh anniversary of the first self-commit of Fossil source code was
 this past Monday.  Time flies.

 The logical predecessor of Fossil was CVSTrac (http://www.cvstrac.org/)
 which was a wiki and trouble-ticket system built atop CVS.  CVSTrac became
 the inspiration for Trac (http://trac.edgewall.org/wiki/CvsTrac) which is a
 similar tool for SVN that became far more popular than CVSTrac and which is
 still in active use.  Fossil was originally created to provide features
 needed in SQLite development, features that I couldn't get with CVS+CVSTrac,
 or with Monotone or Git or Mercurial or any other configuration management
 system available at the time.  I worked on prototypes of Fossil for a year
 or more prior to the first self-commit on 2007-07-21, but none of those
 early prototypes survive.

 Code archeologists will be able to find a lot of commonality between the
 CVSTrac and Fossil source codes.  There is a clear genetic relationship
 between the two systems.

 Fossil was created for the purpose of aiding in the development of SQLite.
 (Other uses for Fossil, though welcomed, are secondary.)  The SQLite
 documentation sources (http://www.sqlite.org/docsrc/timeline?a=2000-01-01)
 were split off from the SQLite source tree in CVS on 2007-11-12, just a few
 months after Fossil began self-hosting.  But the core SQLite source code did
 not move to Fossil until 2009-08-11, just after the release of SQLite
 version 3.6.17, over two years after Fossil became self-hosting.  The move
 from CVS to Fossil has proven to be a boon for SQLite development.

 CVSTrac was in active use by SQLite for a little over 7 years.  To my
 knowledge, nobody uses CVSTrac any more.  (OpenSSL was the last known user
 of CVSTrac and they switched over to Git at the beginning of 2013.) Fossil
 will soon overtake CVSTrac in terms of years of use, and Fossil has a great
 deal more momentum and a much larger user base than CVSTrac ever had.

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


[fossil-users] Issue compiling with 16f1076334 and newer revisions

2014-07-25 Thread Joe Prostko
Using the handy `fossil bisect`, I found that this revision is causing
me problems while compiling Fossil from within Haiku.

This revision brought in -D_HAVE_SQLITE_CONFIG_H and in theory should
work on platforms that support utime() and usleep().  In any case, I
have found that for Haiku anyway, the build fails with this revision
or better, unless I get rid of -D_HAVE_SQLITE_CONFIG_H in Makefile.in.

I admit I didn't really dig into this at all yet, but in any case, the
build fails with both GCC 2.95.3 and GCC 4.8.3 on Haiku.  I'm not sure
why it is happening as of yet.  I suspect it will come down to the
compiler not liking something with respect to typedef'ing structs
though, as I admit this failure seems familiar to me.

Below is the output from revision ffef4edceb with GCC 4.8.3 (since it
is more verbose) in case Jan or anyone else can make sense of it
before I get a chance to try to dig deeper into the situation.


cc -I/packages/openssl-1.0.0m-2/.self/develop/headers-g -O2
-DHAVE_AUTOCONFIG_H -D_HAVE_SQLITE_CONFIG_H  -I. -I./src -Ibld
-DSQLITE_OMIT_LOAD_EXTENSION=1 -DSQLITE_ENABLE_LOCKING_STYLE=0
-DSQLITE_THREADSAFE=0 -DSQLITE_DEFAULT_FILE_FORMAT=4
-DSQLITE_OMIT_DEPRECATED -DSQLITE_ENABLE_EXPLAIN_COMMENTS  -c
./src/sqlite3.c -o bld/sqlite3.o
In file included from ./src/config.h:55:0,
 from ./src/sqlite3.c:7635:
./src/sqlite3.c: In function 'pcache1TruncateUnsafe':
./src/sqlite3.c:38822:26: error: 'nPage' undeclared (first use in this function)
   assert( pCache-nPage==nPage );
  ^
./src/sqlite3.c:38822:26: note: each undeclared identifier is reported
only once for each function it appears in
./src/sqlite3.c: In function 'sqlite3WalFindFrame':
./src/sqlite3.c:49527:36: error: 'Wal' has no member named 'lockError'
   assert( pWal-readLock=0 || pWal-lockError );
^
./src/sqlite3.c: In function 'sqlite3WalExclusiveMode':
./src/sqlite3.c:50265:36: error: 'Wal' has no member named 'lockError'
   assert( pWal-readLock=0 || pWal-lockError );
^
./src/sqlite3.c: In function 'cellSizePtr':
./src/sqlite3.c:52346:18: error: 'debuginfo' undeclared (first use in
this function)
   assert( nSize==debuginfo.nSize );
  ^
./src/sqlite3.c: In function 'autoVacuumCommit':
./src/sqlite3.c:54514:11: error: 'nRef' undeclared (first use in this function)
   assert( nRef=sqlite3PagerRefcount(pPager) );
   ^
./src/sqlite3.c: In function 'balance':
./src/sqlite3.c:58117:18: error: 'balance_deeper_called' undeclared
(first use in this function)
 assert( (balance_deeper_called++)==0 );
  ^
./src/sqlite3.c:58156:20: error: 'balance_quick_called' undeclared
(first use in this function)
   assert( (balance_quick_called++)==0 );
^
./src/sqlite3.c: In function 'sqlite3_backup_step':
./src/sqlite3.c:60361:15: error: 'rc2' undeclared (first use in this function)
   assert( rc2==SQLITE_OK );
   ^
./src/sqlite3.c: In function 'sqlite3VdbeSorterWrite':
./src/sqlite3.c:75447:31: error: 'nExpect' undeclared (first use in
this function)
 assert( rc!=SQLITE_OK || (nExpect==pSorter-iWriteOff) );
   ^
./src/sqlite3.c: In function 'sqlite3ExprCodeTarget':
./src/sqlite3.c:80833:36: error: 'iCacheLevel' undeclared (first use
in this function)
|| pParse-iCacheLevel==iCacheLevel );
^
./src/sqlite3.c: In function 'sqlite3DeleteTable':
./src/sqlite3.c:86185:15: error: 'pOld' undeclared (first use in this function)
   assert( pOld==pIndex || pOld==0 );
   ^
./src/sqlite3.c:86208:11: error: 'nLookaside' undeclared (first use in
this function)
   assert( nLookaside==0 || nLookaside==db-lookaside.nOut );
   ^
./src/sqlite3.c: In function 'sqlite3InitCallback':
./src/sqlite3.c:100108:25: error: 'rcp' undeclared (first use in this function)
 assert( (rc0xFF)==(rcp0xFF) );
 ^
./src/sqlite3.c: In function 'execSql':
./src/sqlite3.c:108467:11: error: 'rc' undeclared (first use in this function)
   assert( rc!=SQLITE_ROW || (db-flagsSQLITE_CountRows) );
   ^
make: *** [bld/sqlite3.o] Error 1
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users