Re: [fossil-users] Chiselapp status

[Roy Keene]

It's still me -- though I don't check email that often, and when I do I 
don't read all of it, normally just the subject and sometimes the From.


Upgrading from Fossil 2.1 to something more recent hasn't been a 
priority;  I have to go through the versions and verify no new features 
will cause problems when hosting untrusted repositories, and I haven't 
done that.


If you would like to volunteer to do that then it'll go faster !  :-D

Thanks,
Roy Keene

P.S., I'm usually on the Tcl IRC or Slack ( https://slack.tcl-lang.org ).

On Fri, 13 Jul 2018, Andy Goth wrote:

Whom should I be talking to regarding Chiselapp questions?  I want to know if 
there's a reason why it uses Fossil version 2.1 [83e3445f67] and if there are 
any plans to upgrade.


I've not gotten any email replies from Roy Keene in a long time, neither 
regarding Tcl nor Chiselapp, though I know he's out there because of recent 
commits to his kitcreator project.  Perhaps I just don't have the right 
address.


--
Andy Goth | 
___
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] [sqlite] Mailing list shutting down...

[Roy Keene]

Yes.  Quite a lot.

On Thu, 14 Jun 2018, Thomas wrote:


On 2018-06-14 22:21, Warren Young wrote:

I expect to have no Internet access in the plane I will be aboard shortly.


I'm not aware of any airline that doesn't provide internet access on 
long-haul flights. Is there still one left?

___
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] [sqlite] Mailing list shutting down...

[Roy Keene]

http://rkeene.org/viewer/tmp/email.png.htm

:-)

And yes, this is my primary MUA -- not something I setup to reply to this 
email.


On Thu, 14 Jun 2018, Thomas wrote:


On 2018-06-14 20:51, John Long wrote:

A decent email client can run on a terminal, over ssh or telnet, etc.
and can handle all sorts of filtering and searching. Most mailing lists


I just checked the calendar. It's the 21st century here. Not sure how many 
terminals, telnets or SSH sessions average users got open but I reckon that a 
good guess of less than a promille might be more precise than you may 
imagine...



___
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] [sqlite] Mailing list shutting down...

[Roy Keene]

As someone who rarely posts messages and mostly reads the posts, I 
wouldn't be affected by requiring posts be done via an authenticated 
web-based system.  RSS may even be an option over email for consuming and 
it can have links for authenticated posting.  I haven't read all the 
emails on this thread so sorry if this is already been hashed out.


On Thu, 14 Jun 2018, Richard Hipp wrote:


On 6/14/18, Roy Keene  wrote:

If it's any conideration, if it's not a mailing list or something else
pushed to me, I'll never see it.


I agree.  Any solution must support email notification.  Am working on
that now.  But, given all the security constraints surrounding email
these days, it is a tough problem.
--
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] [sqlite] Mailing list shutting down...

[Roy Keene]

If it's any conideration, if it's not a mailing list or something else 
pushed to me, I'll never see it.  A fossil users' forum will never get 
checked (pulled) by me since I am just too lazy to remember to do so on 
any regular frequency.  There may be others like me who are busy but can 
occasionally check email.


On Thu, 14 Jun 2018, Warren Young wrote:


On Jun 14, 2018, at 4:29 AM, Dominique Devienne  wrote:


Last discussion/thread on moving away from MLs on the SQLite list showed a 
clear bias
against using a forum over a ML IMHO, especially from long time contributors. 
My $0.02... —DD


I was one of those arguing in favor of mailing lists.

To me, the question comes down to two key questions:

1. Which gets us back into operation faster?  If the effort to maintain a 
mailing list in today’s inimical environment is greater than the effort to 
develop an alternate solution that would sidestep these problems, it’s really 
hard to justify sticking with mailing lists.

2. Does switching add important and valuable new capabilities?

Note the qualifiers.  Animoji are not important to the SQLite or Fossil 
development projects, and their value is very low.  Integration with the Fossil 
DVCS may be very valuable and could become important if it helps win converts.


One new thought since my prior post: many projects (including Fossil and 
SQLite) have separate user and developer communication channels.  It might be 
that the internal developer discussions use this proposed Fossil Forum feature 
and the user discussions are held elsewhere.

In one of my Fossil-based projects, we have a public Google Group for 
discussions that may not even touch on the software development project, with 
developer discussions hidden away in private email, even though there’s nothing 
particularly personal about the discussions.

I mentioned Fossil artifact links in a prior email.  I’m frequently 
hand-crafting these in emails to other developers on the project to refer to 
some checkin, wiki edit, etc.  It’s annoying.
___
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] Show time...

[Roy Keene]

The other thing to keep in mind is that I want Fossil reposistories from 
the same user to be able to access the user's other repositories, since 
they could be part of a login group.


On Tue, 5 Jun 2018, Eduard wrote:


1. Enable Safe interpreters for Tcl

How did you do that? The flint repository doesn't seem to include the
fossil build script.


2. Enforce that the SSH program cannot be run (by patching popen2()
to return an error)

Are you not using chroot to protect repositories from each other?


3. (Not complete, but started) run each instance of Fossil as a
different UID based on their Flint UID+131072

That's actually the next thing on my TODO list -- I think it's a good
idea!


1. Need to add the domain to the Public Suffix List (otherwise,
you haven't mitigated the issue completely)

I think the only security issue left vis-a-vis untrusted subdomains is
that a malicious repository can insert thousands of junk cookies,
displacing the login cookie on the secure subdomain and thus logging
the user out. I think it's a mild annoyance at most. Feel free to
contradict me on this.


2. Getting a wildcard cert

I also put it off for the longest time. It turned out to be
surprisingly easy to do, and in fact less annoying than http
validation.

Cheers,
Eduard

On 06/04/2018 10:37 PM, Roy Keene wrote:

Other things we do at ChiselApp:
 1. Enable Safe interpreters for Tcl
 2. Enforce that the SSH program cannot be run (by patching
    popen2() to return an error)
 3. (Not complete, but started) run each instance of Fossil as a
    different UID based on their Flint UID+131072

I thought about putting each repo under their own domain, but doing so 
requires a bit more work:

 1. Need to add the domain to the Public Suffix List (otherwise,
    you haven't mitigated the issue completely)
 2. Getting a wildcard cert

On Mon, 4 Jun 2018, Eduard wrote:


I was planning on making a more official announcement, but here goes.

I'm the developer of Hydra, a single-sign-on and manager for fossil 
repositories. https://hydra.ecd.space/f/hydra/wiki/hydra


I think this is relevant as people may be looking to GitHub alternatives 
for multiproject hosting.


I've recently fixed the XSS/CSRF vulnerabilities inherent to hosting 
multiple repositories on the same domain (which also affect chiselapp), 
when setup privilege is given to malicious users (for the repositories 
they create) and they convince other people to visit their malicious 
repository while logged in. I've done this by using a separate subdomain 
for each repository, and by patching Fossil itself to receive the CSRF 
token from Hydra. More details here: 
https://static.ecd.space/x/hydra/doc/build/html/subdomains.html


I've also done some security hardening by dropping each repository in a 
separate chroot (to contain damage from a potential arbitrary code 
execution vulnerability in fossil itself).


(Sorry drh, I accidentally replied only to you instead of the mailing 
list.)


On 06/03/2018 09:28 PM, Richard Hipp wrote:

There is suddenly a big uptick in traffic to fossil-scm.org,
apparently due to the recent GitHub rumor.  Unlike that traditional
"slashdot effect", though, the referrals seem to be coming for a large
variety of sources.

So, if anybody sees any last minute tidying up that we need to do to
the website in anticipation of a huge influx of first-time visitors,
please speak up.  Quickly.



___
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 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] Show time...

[Roy Keene]

The patch #1 is not a part of Flint, just ChiselApp -- Flint users supply 
their own Fossil with their specific requirements, which may not include 
safe Tcl.


Attached are the two patches in question.

On Tue, 5 Jun 2018, Eduard wrote:


1. Enable Safe interpreters for Tcl

How did you do that? The flint repository doesn't seem to include the
fossil build script.


2. Enforce that the SSH program cannot be run (by patching popen2()
to return an error)

Are you not using chroot to protect repositories from each other?


3. (Not complete, but started) run each instance of Fossil as a
different UID based on their Flint UID+131072

That's actually the next thing on my TODO list -- I think it's a good
idea!


1. Need to add the domain to the Public Suffix List (otherwise,
you haven't mitigated the issue completely)

I think the only security issue left vis-a-vis untrusted subdomains is
that a malicious repository can insert thousands of junk cookies,
displacing the login cookie on the secure subdomain and thus logging
the user out. I think it's a mild annoyance at most. Feel free to
contradict me on this.


2. Getting a wildcard cert

I also put it off for the longest time. It turned out to be
surprisingly easy to do, and in fact less annoying than http
validation.

Cheers,
Eduard

On 06/04/2018 10:37 PM, Roy Keene wrote:

Other things we do at ChiselApp:
 1. Enable Safe interpreters for Tcl
 2. Enforce that the SSH program cannot be run (by patching
    popen2() to return an error)
 3. (Not complete, but started) run each instance of Fossil as a
    different UID based on their Flint UID+131072

I thought about putting each repo under their own domain, but doing so 
requires a bit more work:

 1. Need to add the domain to the Public Suffix List (otherwise,
    you haven't mitigated the issue completely)
 2. Getting a wildcard cert

On Mon, 4 Jun 2018, Eduard wrote:


I was planning on making a more official announcement, but here goes.

I'm the developer of Hydra, a single-sign-on and manager for fossil 
repositories. https://hydra.ecd.space/f/hydra/wiki/hydra


I think this is relevant as people may be looking to GitHub alternatives 
for multiproject hosting.


I've recently fixed the XSS/CSRF vulnerabilities inherent to hosting 
multiple repositories on the same domain (which also affect chiselapp), 
when setup privilege is given to malicious users (for the repositories 
they create) and they convince other people to visit their malicious 
repository while logged in. I've done this by using a separate subdomain 
for each repository, and by patching Fossil itself to receive the CSRF 
token from Hydra. More details here: 
https://static.ecd.space/x/hydra/doc/build/html/subdomains.html


I've also done some security hardening by dropping each repository in a 
separate chroot (to contain damage from a potential arbitrary code 
execution vulnerability in fossil itself).


(Sorry drh, I accidentally replied only to you instead of the mailing 
list.)


On 06/03/2018 09:28 PM, Richard Hipp wrote:

There is suddenly a big uptick in traffic to fossil-scm.org,
apparently due to the recent GitHub rumor.  Unlike that traditional
"slashdot effect", though, the referrals seem to be coming for a large
variety of sources.

So, if anybody sees any last minute tidying up that we need to do to
the website in anticipation of a huge influx of first-time visitors,
please speak up.  Quickly.



___
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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
diff -uNr fossil-2.1.orig/src/th_tcl.c fossil-2.1-safeinterp/src/th_tcl.c
--- fossil-2.1.orig/src/th_tcl.c2017-03-10 11:07:08.0 -0600
+++ fossil-2.1-safeinterp/src/th_tcl.c  2017-03-16 10:34:59.922893000 -0500
@@ -148,6 +148,9 @@
 #  ifndef TCL_CREATEINTERP_NAME
 #define TCL_CREATEINTERP_NAME "_Tcl_CreateInterp\0"
 #  endif
+#  ifndef TCL_MAKESAFE_NAME
+#define TCL_MAKESAFE_NAME "_Tcl_MakeSafe\0"
+#  endif
 #  ifndef TCL_DELETEINTERP_NAME
 #define TCL_DELETEINTERP_NAME "_Tcl_DeleteInterp\0"
 #  endif
@@ -180,6 +183,7 @@
 */
 typedef void (tcl_FindExecutableProc) (const char *);
 typedef Tcl_Interp *(tcl_CreateInterpProc) (void);
+typedef int (tcl_MakeSafeProc) (Tcl_Interp *interp);
 typedef void (tcl_DeleteInterpProc) (Tcl_Interp *);
 typedef void (tcl_FinalizeProc) (void);
 
@@ -405,6 +409,7 @@
   void *hLibrary; /* The Tcl library module handle. */
   tcl_FindExecutableProc *xFindExe

Re: [fossil-users] Show time...

[Roy Keene]

Other things we do at ChiselApp:
1. Enable Safe interpreters for Tcl
2. Enforce that the SSH program cannot be run (by patching
   popen2() to return an error)
3. (Not complete, but started) run each instance of Fossil as a
   different UID based on their Flint UID+131072

I thought about putting each repo under their own domain, but doing so 
requires a bit more work:

1. Need to add the domain to the Public Suffix List (otherwise,
   you haven't mitigated the issue completely)
2. Getting a wildcard cert

On Mon, 4 Jun 2018, Eduard wrote:


I was planning on making a more official announcement, but here goes.

I'm the developer of Hydra, a single-sign-on and manager for fossil 
repositories. https://hydra.ecd.space/f/hydra/wiki/hydra


I think this is relevant as people may be looking to GitHub alternatives for 
multiproject hosting.


I've recently fixed the XSS/CSRF vulnerabilities inherent to hosting multiple 
repositories on the same domain (which also affect chiselapp), when setup 
privilege is given to malicious users (for the repositories they create) and 
they convince other people to visit their malicious repository while logged 
in. I've done this by using a separate subdomain for each repository, and by 
patching Fossil itself to receive the CSRF token from Hydra. More details 
here: https://static.ecd.space/x/hydra/doc/build/html/subdomains.html


I've also done some security hardening by dropping each repository in a 
separate chroot (to contain damage from a potential arbitrary code execution 
vulnerability in fossil itself).


(Sorry drh, I accidentally replied only to you instead of the mailing list.)

On 06/03/2018 09:28 PM, Richard Hipp wrote:

There is suddenly a big uptick in traffic to fossil-scm.org,
apparently due to the recent GitHub rumor.  Unlike that traditional
"slashdot effect", though, the referrals seem to be coming for a large
variety of sources.

So, if anybody sees any last minute tidying up that we need to do to
the website in anticipation of a huge influx of first-time visitors,
please speak up.  Quickly.



___
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] Show time...

[Roy Keene]

Is ChiselApp not serious enough for you ?

On Sun, 3 Jun 2018, Joseph R. Justice wrote:


On Sun, Jun 3, 2018, 9:33 PM Richard Hipp  wrote:
  On 6/3/18, Richard Hipp  wrote:
  >
  > So, if anybody sees any last minute tidying up that we need to do...

  For example, on the front page
  (https://fossil-scm.org/index.html/doc/trunk/www/index.wiki), what if
  I add some text to item 8 to talk about how Fossil is "Independent and
  not beholden to venture capitalists".  Too snarky?


Neither is Git.

The Fossil-based competition to GitHub would be, for instance, Chiselapp (IIRC).

I dare say that the greatest beneficiary of this stuff is likely to be Gitlab.  
Is anybody doing any serious for-profit Fossil repository
hosting yet?



Joseph


___
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] Setting up an internet Fossil server

[Roy Keene]

ChiselApp also uses Let's Encrypt

On Tue, 27 Feb 2018, Warren Young wrote:


On Feb 27, 2018, at 8:37 AM, Roy Keene <fos...@rkeene.org> wrote:


You don't lose support for TLS, since Apache supports TLS.  It's just running 
Fossil as a CGI -- this is exactly how ChiselApp works.


Compare Thomas? post to the HOWTO I linked in my first post in this thread.  
The largest part of the difference between them is that my HOWTO gives you a 
Let?s Encrypt setup as well as a Fossil server.  Since Thomas doesn?t describe 
how to configure TLS on Apache, I?d say that it?s fair to say that?s one big 
reason why Thomas? configuration is simpler than mine.

A much smaller part of the delta is plain old CGI vs ?fossil server --scgi?, 
which I think is well worth the minor complexity to avoid the CPU and disk hits 
of repeated Fossil launches.
___
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] Setting up an internet Fossil server

[Roy Keene]

You don't lose support for TLS, since Apache supports TLS.  It's just 
running Fossil as a CGI -- this is exactly how ChiselApp works.


On Tue, 27 Feb 2018, Warren Young wrote:


On Feb 26, 2018, at 3:33 PM, Thomas Levine <_...@thomaslevine.com> wrote:


Since it seems that the only dynamic stuff is in PHP and fossil,
I suggest using Apache mod_php and mod_cgi (contrary to Warren's
suggestion), as I think the configuration will be easier.


Of course, but then you lose HTTPS, which is the only reason my configuration 
is difficult at all.  If all you wanted is reverse proxying, you?d do away with 
steps 1-6, simplifying the HOWTO considerably.

I don?t view TLS as optional for password-protected public web resources in 
these post-Firesheep days.

Even if you don?t care about your own Fossil repo?s security, Google has been 
punishing sites that are not available via HTTPS for a couple of years now, 
both through reduced rankings in the search engine and through increasingly 
strident warnings in Chrome.

That?s not speculation, Google?s been announcing these things publicly:

  https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html
  https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn

There may come a day when going to an HTTP-only web site will require multiple 
affirmations asymptotically approaching ?Yes, I?m really quite certain I want 
my face eaten by a rabid grue.  Just let me look at this one web site first, 
please.?
___
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] Setting up an internet Fossil server

[Roy Keene]

Scott,

	Fossil can be run in any URL suffix on an existing domain.  This 
is how, for example ChiselApp.com works -- each user*repo is a different 
URL and they run their own repositories, while the rest of the site runs 
PHP.


Thanks,
Roy Keene

On Mon, 26 Feb 2018, Scott Doctor wrote:



Going to give this a try. (also busy with other pay-the-bills work so I tend 
to do this one in my spare (ha) time).


The issue I am trying to figure out is that it seems it is an all or nothing 
setup. Either the website is using fossil as the website or not at all. Most 
of the website is HTML5 and php pages that have nothing to do with the fossil 
archive. It is the functionality of the random number generator, api, and 
website UI I designed that I am packaging up as an open source project. Hence 
the use of fossil.


What I want is for fossil to activate when I access a specific directory to 
use fossil.


https://nousrandom.net/code/

But it appears I am going to have to make a sub-domain to do this.

I put the fossil program in that folder, and through the command line 
interface (via putty) created a new archive in that folder. However, when I 
issue the command


fossil server --scgi

the program runs in the foreground and the command line control is unusable 
until I ctrl-c.


So I guess I need to create a sub-domain to use fossil.

Still have not yet got it to work even as a stand-alone.

To be continued...


-
Scott Doctor
sc...@scottdoctor.com
-

On 2/26/2018 05:17, Warren Young wrote:

On Feb 24, 2018, at 11:57 AM, Scott Doctor <sc...@scottdoctor.com> wrote:


Is there a step-by-step how to get fossil to work from an internet page?

I?ve posted this here several times now:

https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg22907.html

Since you?ve already got Let?s Encrypt working with nginx, you can skip all 
of that.  The HOWTO was written before Let?s Encrypt had built-in support 
for nginx.


___
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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Restoring previous timeline look

[Roy Keene]

Verbose view restores most, but not all, of the look.  Here are two 
otherwise identical repos:

1. Fossil 2.5 (wrong): 
https://core.tcl.tk/tcltls/timeline?ss=v=50=ci=0
2. Fossil 2.4 (right): http://tcltls.rkeene.org/timeline

That said, to me the Fossil 2.5 one in verbose mode looks better so I 
might change my CSS to match that


--
Roy Keene

On Sat, 10 Feb 2018, Richard Hipp wrote:


On 2/9/18, Chris Rydalch <cryda...@gmail.com> wrote:


Is this behavior hard-coded in newer versions of Fossil, or can it be
changed in a skin's css? I thought I'd followed that discussion close
enough, but I expected the skins to control the behavior so I'm clearly
missing something...


Did you change to "Verbose View" on the timeline menu?  Is it still
not doing what you want after that?

--
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] fossil-users Digest, Vol 120, Issue 2

[Roy Keene]

Stephan,

	You need to quote the argument to "echo", otherwise the whitespace 
is collapsed by the shell.


For example:
echo "$(echo -e "1\n2\n3")"

On Tue, 2 Jan 2018, Stephan Beal wrote:


(this time back to the list)
On Tue, Jan 2, 2018 at 3:43 AM, Andy Bradford  wrote:
  Thus said Stephan Beal on Tue, 02 Jan 2018 03:07:20 +0100:

  > That will  still strip  any newlines from  his input,  though, because
  > that's how $(...) works.

  It actually only strips the trailing newline. Any newlines in the middle
  of the file are fine.


That's not what i'm seeing:

[stephan@host:~]$ echo -e "1\n2\n3"
1
2
3
[stephan@host:~]$ echo $(echo -e "1\n2\n3")
1 2 3 

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

Re: [fossil-users] Replacing subversion revision number... by what?

[Roy Keene]

Mark,

	The main thing that a hash doesn't give you is ordering -- you 
don't know if aed2 is before or after f9a2, c93a, etc.


When I migrated from Subversion to Fossil, I just used the datecode for 
this value since that preserves ordering.  On other projects I moved to 
explicit version numbers tagged with a release since the tag already had 
to be coordinated.


Thanks,
Roy Keene

On Fri, 29 Dec 2017, Mark Janssen wrote:


All of this will fail in the case of private branches (or other DAG
differences) between different repositories, unless you special case
private branches.
And how will you handle diverging repos so that my version 12 is not
your version 12, because I didn't sync after commit 10?
I wouldn't be surprised if it's mathematically provable that to create
a unique id for a distributed DAG, the only way is to make one
repository special (e.g. the centralized SVN scenario)

Which begs the question, why all this effort to create something which
already is there?

Is stating version 1245 really that much easier than stating version aed2 ?

On Fri, Dec 29, 2017 at 11:12 AM, Olivier Mascia <o...@integral.be> wrote:

Le 28 déc. 2017 à 23:58, Joerg Sonnenberger <jo...@bec.de> a écrit :


I'm considering replacing the subversion revision ID, for the purpose of 
defining the file version ID (as above) at release-external build time, by the 
count of check-ins in the root repository.  That is the count returned by 
'fossil info' in one of the multiple lines of output (for instance 'check-ins: 
8801').


My 'count of check-ins' is your 'length of the commit chain to the root', or 
are we talking of something else here?


If you have a commit graph like:

A
|
B
| \
C D
| |
E F

Both E and F have a LoCC of 4, but the count f check-ins would depend on
the order of commits?


That I don't know yet for sure.

I just want an integer, always increasing, even though not by one, from a specific 
branch, from a specific repository (the branch/repository from which I compile released 
code). And that value seems to fit that need perfectly.  It does not need to allow me 
backward lookups (finding a check-in from that number). That sequential number could even 
be managed outside by my build system. But it is interesting that it be linked with the 
count of check-ins, because somehow it gives an empiric sense "of the distance" 
of code between to release builds. Which we had before through the subversion revision ID.

Upon build I will derive the trailing version number of my executables from 
that integer. And my build system will auto add a tag with the full constructed 
version number to the top check-in of that same branch. I can also store that 
top check-in ID (hash) somewhere else (than in the version number) so it could 
be displayed on request. And there, thanks to the auto-added full version 
number tag upon successful release build, I get an easy way to locate the exact 
source code that was part of that build. It's easier for users to tell support 
people their version number than a hash code, even shortened.  And 
setup/distribution is easier thanks to an ever increasing full version number, 
even between patch builds of a same release.

--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia


___
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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Digital signatures on check-ins. Was: tangent vs. wyoung on recent commti

[Roy Keene]

For what it's worth, I submitted a patch a while back to add S/MIME 
support to Fossil's signature scheme.  I still apply this patch to Fossil 
when I use it.  S/MIME uses PKI and is primarily used for non-repdudiation 
or encryption in email (every major email client supports it out of the 
box).  PKI is also used for HTTPS.


On Thu, 21 Dec 2017, Richard Hipp wrote:


On 12/21/17, jungle Boogie  wrote:


How are the signatures verified?


Signatures are not verified, at the moment.

Probably each repository would have a set of trusted public keys.
Then as each check-in is received via push (or during a rebuild) those
with signatures have the signatures verified using the set of trusted
keys.  Those for which the keys are unknown get marked as signed but
unverified.

The signatures are currently generated by running gpg in a separate
process.  I suppose the verification step could do something similar.

Hey - I suppose there is a fourth state:  (4) Forgery: The signature
does not match.
--
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] Fossil vs. GitHub

[Roy Keene]

One thing I often wish Fossil did was show other things (tickets, wiki 
pages) that reference tickets rather than just checkins -- I often have a 
mess of tickets that refer to other tickets and no place to generate a 
list of them, or reverse them.


On Wed, 13 Dec 2017, Richard Hipp wrote:


On 12/13/17, jungle Boogie  wrote:

On 13 December 2017 at 09:07, Warren Young  wrote:

On Dec 13, 2017, at 9:55 AM, Richard Hipp  wrote:


Would Git or GitHub have told me about those prior tickets?


GitHub is pretty good about surfacing such information, as long as the
ticket references the checkin ID.


Yep. With most projects I follow on github, the commiter includes the
referenced issue number in the description or somewhere in the commit
message.


Is the ticket number included in the check-in that *fixed* the issue,
or in the check-in that *caused* the issue.  Therein lays the
difference.  I wasn't looking that one of the check-ins that fixed the
bug - I was looking at the check-in that caused the bug, and it
referred me forward to issues that happened in the future.

Maybe GitHub will do that?  Do you have an example?
--
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] Fossil in Debian

[Roy Keene]

-- Forwarded message --
Date: Tue, 5 Dec 2017 15:20:48 +
From: Barak A. Pearlmutter <ba...@pearlmutter.net>
To: Roy Keene <rke...@rkeene.org>
Subject: Re: Fossil in Debian

Version 2.2 is in Debian testing, has been for a while.
Been meaning to upgrade to 2.3 ... wait now it's 2.4 ...
(But upstream doesn't make it easy, with their download page that uses
javascript to mangle the URLs, thus confounding Debian's automatic
monitoring tools.)

Anyway, until the next stable release, the only real way to get a
newer fossil is to either install it from testing, or for someone to
put together a jessie-backports package.
Which I could do if there is sufficient demand.

Cheers,

--Barak.
___
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] web UI for a working checkout?

[Roy Keene]

On Fri, 29 Sep 2017, Andy Goth wrote:


On 9/29/2017 4:43 PM, Steve Schow wrote:

On Sep 29, 2017, at 2:46 PM, Andy Goth <andrew.m.g...@gmail.com> wrote:
Who is hosting that and what is the longevity compared to github and
others?


Roy Keene can answer these questions.



Roy Keene is hosting it... though, of course, so is everyone who clones 
their repos periodically.  Additionally, the source is hosted in 
ChiselApp.com in a repo called "flint".


It'll probably be around for a while, since I use it quite a bit... it was 
created and originally hosted by James Turner and I took it over from him 
when he was looking to move on to other things.

___
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] Using Fossil with Apache Proxy

[Roy Keene]

On Thu, 28 Sep 2017, Mark Janssen wrote:




On 28 Sep 2017 13:37, "David Mason"  wrote:



I have all the logic I need I just want fossil to behave like it would at a 
terminal prompt, rather than acting like a CGI... the complication is that I am 
calling it from a CGI!  But removing all the environment
variable mostly solves the problem.



To get the commandline behavior of fossil in a CGI context use the --nocgi flag.





For what it's worth, this is how Flint (which powers ChiselApp.com) does 
it:


http://chiselapp.com/user/rkeene/repository/flint/artifact?ln=33-37=1eb0582d234199bc
___
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] Continued issues with read-only repository

[Roy Keene]

Quit using Windows ?

On Wed, 20 Sep 2017, Andy Goth wrote:


I'm fine in Linux working from a loopback-mounted ISO9660 disc image,
but in Windows 8.1 doing the same nets me the following:

SQLITE_NOTE: delayed 1375ms for lock/sharing conflict at line 43312
SQLITE_CANTOPEN: os_win.c:43319:(5) winOpen(E:\repo.fossil) - Access is
denied.

Followed by what appears to be normal operation.  I get my web pages,
and it seems good, except for three problems.

One, page generation is a lot slower since I'm guessing it's having to
wait a few seconds each request for some timeout.

Two, the errors themselves appear at the top of every page.

Three, the errors also appear in HTML format at the start of style.css,
corrupting the first definition and messing up the page style.

What can be done about this?

--
Andy Goth | 



___
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] uv add dir/filename

[Roy Keene]

Andy,

Why add this restriction to the "--as" switch ?

I currently use "fossil uv add  --as release-/"

Thanks,
Roy Keene

On Tue, 19 Sep 2017, Andy Goth wrote:

Currently the "fossil uv add" command rejects filenames containing directory 
components.  I suggest instead applying this restriction only to the value of 
the "-as" switch, with "-as" defaulting to the filename sans directory 
components.


--
Andy Goth | 
___
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] Shameless self-promotion

[Roy Keene]

$ ls -lh ~autobuild/aurae.fossil
-rw-r--r-- 1 autobuild users 11G Sep 15 12:05 /home/autobuild/aurae.fossil

On Fri, 15 Sep 2017, Thomas wrote:


On 2017-09-14 23:43, Richard Hipp wrote:

On 9/14/17, Thomas  wrote:


The biggest disadvantage - as my coworkers pointed out - is that the
downloadable executables do not come with https enabled.


At one time that was true.  But I think all of the precompiled
binaries on the site now have https enabled by default, don't that?
Have you tried the recent once?  I pretty sure the Windows binaries in
particular support https out of the box.


Uhm, no, I hadn't. I just downloaded the latest Windows executable and it 
came with https enabled.


Thanks! That's a great leap forward! In my opinion, there's now in my opinion 
nothing left that'd make Git superiour to Fossil unless you got a huge amount 
of contributors (according to the Fossil documentation), or a project 
spanning several gigabytes. I'll certainly pass this on.


But I won't let you off like that nonetheless. :)
Why hasn't this been announced properly, or have I overslept it? ;-)


Cheers
Thoas


___
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] 500 errors on Chisel.

[Roy Keene]

Jacob,

	I've had to put it off to work on other issues.  I may have time 
to do it this weekend.


Thanks,
Roy Keene

On Fri, 11 Aug 2017, Jacob MacDonald wrote:


Any update on the migration?
Thanks,

Jacob.

On Sat, Jun 3, 2017 at 11:22 AM Jacob MacDonald <jaccar...@gmail.com> wrote:
  Appreciate the update!

On Sat, Jun 3, 2017 at 11:16 AM Roy Keene <fos...@rkeene.org> wrote:
  Jacob,

          This is caused by Fossil using a newer version of SQLite3 than the
  system SQLite3 which "Edit" uses.  The system SQLite3 DB can't open the
  Fossil repository to make some modifications due to the schema being
  unsupported on some repositories.

  I can't make Fossil use the system SQLite3 since it requires newer
  versions (presumably to support this schema).

  I plan to upgrade the SQLite3 used by Flint/PHP next week as I migrate to
  a new host which should address the issue.

  A better fix would be to not talk directly to the SQLite3 DB but make the
  changes by calling the Fossil binary, but that hasn't been investigated
  too closely.

  Thanks,
          Roy Keene

  On Sat, 3 Jun 2017, Jacob MacDonald wrote:

  > For the past few weeks, I've been unable to edit my repositories on
  > Chisel (page throws a 500). Unfortunately, since I only have access to
  > my account password and not each repo's password, that means I can't get
  > write access to any of my hosted code.
  > Is this a known issue/something I'm doing wrong?
  >
  > I've seen a bit of chatter re: Chisel on the list, but if there's a
  > better place for the question, please let me know.
  >
  > Thanks!
  >
  > Jacob.
  >
  >
  ___
  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] backing out an incorrect commit?

[Roy Keene]

Steve,

	Usually what is done here is the incorrect commit is moved to a 
different branch, which is typically hidden.  This can be done using 
"fossil amend".  Then you update to the new head of your branch (the 
previous commit) using "fossil update" and retry your commit.


It's also possible to shun the commit artifact on every system that has 
learned of it (given that no new commits are based off it) and a rebuild 
will drop the un-referenced data artifact.  This is not recommended in the 
normal case of a simple error being made, since you'll have to touch every 
clone that has the commit artifact.


Thanks,
Roy Keene

On Wed, 16 Aug 2017, Steve Schow wrote:

I know the fossil paradigm generally frowns on the idea of undoing 
commits.  Please tell me your thoughts about the best approach to handle 
the following situation.


a few file is added to the checkout and committed.  So the commit has 
one new file, nothing else.  It is later determined that the entirely 
wrong version of that file was committed for the first version of the 
file and we?d like to back it out to do it properly?


Is that possible at all or if not, what is the best way to handle that 
kind of situation with fossil?



___
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] Two easy questions

[Roy Keene]

I have not read all this thread, but it seems to be centered around 
release engineering.  The goal, as I understand it, is to create a release 
and when that release is installed somewhere be aware of what release it 
is.


For this kind of thing I use a release engineering script called 
"makearch":  https://chiselapp.com/user/rkeene/repository/makearch/artifact/6250403d86ce0f58


In addition to being able to replace keywords in files (specified in 
makearch.info), it will attempt to ensure that the release is consistent, 
and basically working.


I use this for all my software releases.  Here are some example 
makearch.info files:

1. KitCreator: 
https://kitcreator.rkeene.org/fossil/artifact/2d5da9bed6be27de
2. Build-CC: http://build-cc.rkeene.org/fossil/artifact/2503d2429f6aab44
3. tcc4tcl: 
https://chiselapp.com/user/rkeene/repository/tcc4tcl/artifact/f99b7196f56e6f83
4. AppFS: http://appfs.rkeene.org/web/artifact/41bb149458ce926b
5. Tcl Web App Framework: 
https://chiselapp.com/user/rkeene/repository/webapp/artifact/d9bd7447b870ca6a
6. TUAPI: 
https://chiselapp.com/user/rkeene/repository/tuapi/artifact/587f2c762e4b94fa
7. makearch itself: 
https://chiselapp.com/user/rkeene/repository/makearch/artifact/1d478f607dd5f327

(I use it for a lot more projects, but that's a pretty good sampling of 
different kinds)


Thanks,
    Roy Keene

On Wed, 16 Aug 2017, Stephan Beal wrote:


On Wed, Aug 16, 2017 at 7:17 PM, David Mason <dma...@ryerson.ca> wrote:
  Wow... longest thread I've ever seen.


Naw - there've been a few longer ones.
 
  Then go to 
localhost:8081/artifact/1bea11bf4a97b012e7d8b17c71a7d444f0b5a5aa
and you'll get the exact file you're looking for.  Of course, if someone edited 
the file you're SOL. There may be a command-line way to do
this, but I can't find it.


[stephan@host:~]$ f help whatis
Usage: f whatis NAME

Resolve the symbol NAME into its canonical artifact hash
artifact name and provide a description of what role that artifact
plays.

Options:

   --type TYPE          Only find artifacts of TYPE (one of: 'ci', 't',
                        'w', 'g', or 'e').
   -v|--verbose         Provide extra information (such as the RID)



But, correct: if someone edits the file (i.e. changes the hash) then this is 
useless.

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

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

[Roy Keene]

Victor,

	No message appears to have been included in this email... was that 
intentional ?


Thanks,
Roy Keene

On Tue, 8 Aug 2017, Victor Wagner wrote:


On Tue, 13 Jun 2017 06:34:20 -0500 (CDT)
Roy Keene <fos...@rkeene.org> wrote:


Richard,

That seems to have fixed it:


$ cd ~/devel/aurae
$ /home/rkeene/devel/fossil/fossil version
This is fossil version 2.3 [3200a7c72e] 2017-06-13 05:12:55
UTC $ /home/rkeene/devel/fossil/fossil rebuild
  100.0% complete...
rebuilding the search index... done
$ rm -f /tmp/x.repo; /home/rkeene/devel/fossil/fossil clone
~/devel/aurae/.repo /tmp/x.repo Repository cloned into /tmp/x.repo
Rebuilding repository meta-data...
  100.0% complete...
Extra delta compression...
Vacuuming the database...
project-id: 6f28ae81cd49eaeaa8d55ac7bd1bad5ef71c4ad4
server-id:  09c7831f6f8b06a5dc2497431444a4f3961ffec2
admin-user: rkeene (password is "010b01")
$ /home/rkeene/devel/fossil/fossil fts
check-in search: on
document search: on
ticket search:   on
wiki search: on
Porter stemmer:  on
full-text index: enabled
documents:   3515
$

Thanks,
    Roy Keene


On Tue, 13 Jun 2017, Richard Hipp wrote:


On 6/13/17, Roy Keene <fos...@rkeene.org> 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


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

[Roy Keene]

Richard,

That seems to have fixed it:


$ cd ~/devel/aurae
$ /home/rkeene/devel/fossil/fossil version
This is fossil version 2.3 [3200a7c72e] 2017-06-13 05:12:55 UTC
$ /home/rkeene/devel/fossil/fossil rebuild
  100.0% complete...
rebuilding the search index... done
$ rm -f /tmp/x.repo; /home/rkeene/devel/fossil/fossil clone 
~/devel/aurae/.repo /tmp/x.repo
Repository cloned into /tmp/x.repo
Rebuilding repository meta-data...
  100.0% complete...
Extra delta compression...
Vacuuming the database...
project-id: 6f28ae81cd49eaeaa8d55ac7bd1bad5ef71c4ad4
server-id:  09c7831f6f8b06a5dc2497431444a4f3961ffec2
admin-user: rkeene (password is "010b01")
$ /home/rkeene/devel/fossil/fossil fts
check-in search: on
document search: on
ticket search:   on
wiki search: on
Porter stemmer:  on
full-text index: enabled
documents:   3515
$

Thanks,
    Roy Keene


On Tue, 13 Jun 2017, Richard Hipp wrote:


On 6/13/17, Roy Keene <fos...@rkeene.org> 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


___
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

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

[fossil-users] Bug: Unable to clone

[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] Bug: Ticket formatting breaks if you enable HTML as wiki markup language

[Roy Keene]

There is a bug in Fossil (v2.2) that breaks the formatting of tickets if 
you enable the Configuration option "Use HTML as wiki markup language".


With this option off, tickets get formatted correctly, like:
	Debugging information taken at the time the 
issue was on-going:


With this option on, tickets get formatted incorrectly, like:
	Debugging information taken at the 
time the issue was on-going:


From a quick look at the source it looks like the ticket formatting system 
ONLY outputs Fossil Wiki and relies upon the Fossil Wiki formatting engine 
to be aware of these weird formatting rules and translate them into HTML, 
but enabling "Use HTML as wiki markup language" disables that.

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

[fossil-users] Improvements to the /reports page

[Roy Keene]

All,

	I would benefit from some improvements to the /reports page, such 
as the ability to restrict the dates upon which are being reported and the 
ability to restrict the report to certain tags.


I've started on the former change here:

https://chiselapp.com/user/rkeene/repository/fossil/vdiff?from=6419592d65=stats-with-date-boundaries=0

Let me know if this has a chance of being improved and merged upstream and 
I'll work on improving it and adding more functionality.


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] Make two fossil repositories "friends" ?

[Roy Keene]

All,

	I have two Fossil repositories hosted on the same server and 
serving related projects so it would be helpful to me to make them 
"friends" somehow...


Probably as an extension of the login-group functionality (and depndant 
upon it) would be some way to make Fossil look into its friends 
repositories for artifacts that are referenced that are not part of the 
current repository -- it could then just link to the other web interface 
for the other repository (meaning, that part of becoming friends would be 
identifying what the fossil URL prefix is for that peer).


Or something similar.  Right now for example, I have tickets and commits 
that I would like to use the "bracket" notation to refer to tickets and 
commits in other repositories but they are unknown in this repository.


Is such functionality already present in some way that I've missed, or has 
anyone investigated it ?


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

Re: [fossil-users] 500 errors on Chisel.

[Roy Keene]

Jacob,

	This is caused by Fossil using a newer version of SQLite3 than the 
system SQLite3 which "Edit" uses.  The system SQLite3 DB can't open the 
Fossil repository to make some modifications due to the schema being 
unsupported on some repositories.


I can't make Fossil use the system SQLite3 since it requires newer 
versions (presumably to support this schema).


I plan to upgrade the SQLite3 used by Flint/PHP next week as I migrate to 
a new host which should address the issue.


A better fix would be to not talk directly to the SQLite3 DB but make the 
changes by calling the Fossil binary, but that hasn't been investigated 
too closely.


Thanks,
    Roy Keene

On Sat, 3 Jun 2017, Jacob MacDonald wrote:

For the past few weeks, I've been unable to edit my repositories on 
Chisel (page throws a 500). Unfortunately, since I only have access to 
my account password and not each repo's password, that means I can't get 
write access to any of my hosted code.

Is this a known issue/something I'm doing wrong?

I've seen a bit of chatter re: Chisel on the list, but if there's a 
better place for the question, please let me know.


Thanks!

Jacob.



___
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] [8c22e1bbcd8ec048] Regression: "fossil amend" no longer works unless operating from within an open checkout

[Roy Keene]

Andy,

	Sorry -- the actual command had the UUID in there, it got stripped 
out during sanitization:

$ fossil amend -R ~autobuild/aurae.fossil 
0fb28f59263f1a0c547c9abebeb69d2da67d3f17 --tag build-pass --tag tests-fail
the "amend" command only work from within an open check-out

The fossil checkin I linked to ([8c22e1bbcd8ec048]) has the change in 
src/info.c that enforces this for all cases.


Thanks,
    Roy Keene


On Thu, 25 May 2017, Andy Bradford wrote:


Thus said Roy Keene on Thu, 25 May 2017 21:17:15 -0500:


$ fossil amend -R ~autobuild/aurae.fossil --tag build-pass --tag 
tests-fail
the "amend" command only work from within an open check-out


What particular checkin are you trying to amend here?

Seems like the error really should be a usage statement.

Try:

fossil amend -R ~autobuild/aurae.fossil UUID --tag build-pass --tag tests-fail

Where UUID is the checkin that you want to amend.

Andy
--
TAI64 timestamp: 4000592791c4



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

[fossil-users] [8c22e1bbcd8ec048] Regression: "fossil amend" no longer works unless operating from within an open checkout

[Roy Keene]

All,

Per the change made here:
http://fossil-scm.org/index.html/info/8c22e1bbcd8ec048

Attempts to add tags to a repository using "-R" now returns an engrish 
error message:


$ fossil amend -R ~autobuild/aurae.fossil --tag build-pass --tag 
tests-fail
the "amend" command only work from within an open check-out

Given that this worked, why was it broken ?   And can the error message be 
converted to something that is actually coherent ?  And can it be unbroken ?


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

Re: [fossil-users] How to transfer/move/upload local repository to chiselapp.com

[Roy Keene]

There is a way to upload the repository -- what you are probably doing now 
is creating a new repo with the same project code then pushing to that, 
which won't work out great.


When you go to "Create Repository" there are 3 options: 1. Create a 
new repository; 2. Pull a repository from somewhere; 3. Upload a 
repository file -- pick the last one.


Thanks,
    Roy Keene

On Sun, 14 May 2017, The Tick wrote:

Hmmm. I now see on the timeline that there are two users and the last leaf is 
unconnected to the timeline entries from my local repository. There are two 
users: my windows user name (which I guess I now want to get rid of) and the 
username that I use on chiselapp.com


The chiselapp.com username is the one with the "empty" checkin
My windows username is now there on chiselapp.com after my 'push'

47 timeline items

2017-05-14
21:03 
[7a7ff8235f] Leaf: initial empty check-in (user: iamdave, tags: trunk)

20:59   ? Deleted wiki page CWind 1.4 (user: imdave) [details]
20:57   ? Changes to wiki page CWind (user: imdave) [details]
20:56   ? Changes to wiki page CWind (user: imdave) [details]
20:35   ? Changes to wiki page CWind 1.4 (user: imdave) [details]
20:31   ? Changes to wiki page manpage (user: imdave) [details]
20:20   ? Changes to wiki page manpage (user: imdave) [details]
20:04   ? Changes to wiki page CWind 1.4 (user: imdave) [details]
19:56 
[0d276cd236] Leaf: Rename all files from .cpp to .c -- there is no reason to 
use C++ (user: imdave, tags: trunk)

19:28   ? Changes to wiki page CWind 1.4 (user: imdave) [details]
05:39   ? Changes to wiki page CWind 1.4 (user: imdave) [details]

The 21:03 and the 19:56 leaf's are not connected with the little arrow lines.

I'm probably really messing this up.

Is there a way to upload my local repository (created on windows and which is 
using my windows user name) to chiselapp.com and somehow create an 
equivalence to the username on chiselapp and my windows username?



___
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] How to transfer/move/upload local repository to chiselapp.com

[Roy Keene]

I run ChiselApp.com now and have no plans to stop doing so -- it's viable 
I'd say !


On Sun, 14 May 2017, The Tick wrote:


Sorry for all these questions.

I ran across an exchange from 2013 (I think) that talked about chiselapp.com 
shutting down. Obviously it has not done so.


What is the status of chiselapp.com and is it a viable place to put an open 
source repository as of 2017?

___
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] /dev/null and /dev/urandom not available ?

[Roy Keene]

Maybe it should open /dev/null and /dev/urandom before chroot()'ing ?

On Sat, 13 May 2017, Richard Hipp wrote:


On 5/13/17, Olivier R.  wrote:

Hello,

I?m running Fossil on Debian Jessie 8.2
(x86_64-debian-jessie-2016-04-06_15:26) at Scaleway.com (VC1S).

In the admin panel, Fossil says:

   WARNING: Device "/dev/null" is not available for reading and writing.
   WARNING: Device "/dev/urandom" is not available for reading. This
means that the pseudo-random number generator used by SQLite will be
poorly seeded.

fossil is in usr/bin.
repo.fossil is in /root/repo.

To launch the server, I simply type:

   fossil open repo.fossil
   nohup fossil server &


Are you running the commands above as root?  If so, Fossil will
automatically put itself in a chroot jail on the directory containing
the repository and drop root privileges before doing anything else.
This is a security feature.

If you are going into a chroot jail, probably /dev/null and
/dev/urandom are no longer in that chroot jail.  You can fix that by
running:

  mkdir dev
  mknod dev/null c 1 3
  mknod dev/urandom c 1 9

See also the "managing server load" heading of
http://fossil-scm.org/fossil/doc/trunk/www/server.wiki where it talks
about the importance of making /proc available inside the chroot jail
so that Fossil can determine the load average.

Or, you can use the --nojail option on the "fossil server" command, in
which case Fossil will still drop its root privilege but will not
attempt to form a chroot jail.  This is less secure, but probably
still plenty safe.





In /dev, there is:

   crw-rw-rw- 1 root root 1, 3 Apr 8 2016 null
   crw-rw-rw- 1 root root 1, 9 Apr 8 2016 urandom


If I clone the repository, modify something, commit the modification,
fossil says when trying to sync:

   Autosync:  http://xxx.xxx.xxx.xxx:8080
   Round-trips: 1  Artifacts sent: 0  received: 0
   Pull done, sent: 312  received: 328  ip: xxx.xxx.xxx.xxx
   New_Version: _hash_code_x
   Autosync:  http://xxx.xxx.xxx.xxx:8080
   Round-trips: 1  Artifacts sent: 2  received: 0
   Error: not authorized to write
   Round-trips: 1  Artifacts sent: 2  received: 0
   Sync done, sent: 759  received: 355  ip: xxx.xxx.xxx.xxx
   Autosync failed.

The repository has not been updated.

How to solve these problems?

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




--
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] [PROPOSED FEATURE] Fossil commands output sent through a pager

[Roy Keene]

I vote that the pagination be off by default to preserve the existing 
behaviour -- terminals have been able to scroll for decades now so I don't 
know why systemd/git like to do this by default but it is REALLY annoying 
having to pipe EVERYTHING through "cat" to defeat it.


(Also, even better than scrolling -- my terminal can search 
forwards/backwards/copy/paste, etc, it's real handy.)


On Thu, 23 Mar 2017, Christophe Gouiran wrote:


Good morning,

I would like to implement the feature given in the title.
I'm inspired by what Git (by default ?) and Mercurial (with Pager extension 
activated) do.

I'd like to avoid typing "fossil  | less" everytime I notice it 
produces an output which doesn't fit in a single screen.

Find below my ideas (in no particular order).
Settings :
 1. Add a new boolean setting "Paginates commands" (it is true by default)
 2. Add a new string setting "pager-command" (it is empty by default)
 3. Add a new string setting "Commands to paginate" (default value to be 
defined)

If pager-command is empty then following pager command will be used:

 1. "more" under Windows.
 2. "less -FRSX" under any other OS.

When Fossil writes something to its standard output, then it is sent through 
the pager if (and only if) all following conditions are met:

 1. Fossil standard output is a real terminal.
 2. "Paginates commands" setting is true.
 3. Executed command is indicated in "Commands to paginate" setting.

Fossil standard error must not be paginated.


Now I'm waiting for your advices/improvements/feedbacks.

For example:

 1. Should the settings be versionnable ?
 2. Which commands to be put by default in "Commands to paginate" ?


Many thanks in advance for taking the time to participate.





___
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] Unversioned files not accessible from Web interface

[Roy Keene]

ChiselApp runs Fossil 1.36 currently, not 1.34.

On Wed, 22 Feb 2017, Martin Gagnon wrote:



Le mer. 22 févr. 2017 à 03:33, Tony Papadimitriou  a écrit :
  I placed some unversioned file to a chiselapp repo I maintain and then 
from the Web UI tried to locate the file but without luck.
There isn?t even a hint that some unversioned file is in the repo, so that one 
can try to UNV SYNC from the command line (after cloning).
 
Maybe the FILES tab should have an additional option (next to All, Tree-View, 
etc.) for Unversioned?  And from there process them (e.g., download, hex) 
exactly the same.
 


Hi Tony, 

To see the list of unversionned files on a repo, use the /uvlist page: 

 example: https://www.fossil-scm.org/index.html/uvlist

But in your case, I'm afraid that Chiselapp use a too old version of fossil 
(1.34). unversionned files feature appear in 1.36.

May be "unver sync" command could return an error in that case? 

Regards,

-- 
Martin G.

___
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] Linux binary downloads

[Roy Keene]

I'd vote for x86_64 or amd64 (or even EM64T), but not "x64" (which is 
gibberish).


On Mon, 20 Feb 2017, Richard Hipp wrote:


On 2/20/17, Emil Totev  wrote:

Hi

There are still inconsistencies in the binary downloads for linux at
fossil's web site.

File fossil-linux-x86-1.37.tar.gz contains a x64 (64-bit) executable.
There seems to be no 32-bit linux executable download.

Could someone please fix that for this and future builds?


I suspect that the Mac and OpenBSD builds are 64-bits too.  I suppose
we could produce 32-bit binaries, but I worry that they would be
largely untested, since I use 64-bit machines almost exclusively, as I
suspect most of the other Fossil developers do as well.  If you really
need a 32-bit binary, you can always build your own use the source
tarball, right?

Or, perhaps you are simply asking that the downloads be relabeled from
"x86" to "x64"?

--
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] Bug report: fossil clean follows symlinks

[Roy Keene]

All,

	Running "fossil clean -x -v" appears to follow symlinks, which 
means it will go delete data outside of your repository path -- 
recursively.


Example:
$ mkdir /tmp/a
$ touch /tmp/a/one
$ touch /tmp/a/two
$ touch /tmp/a/three
$ ln -s /tmp/a .
$ fossil clean -x -v
Removed unmanaged file: a/one
Removed unmanaged file: a/three
Removed unmanaged file: a/two
Could not remove directory: a
$

Now imagine that symlink went to "/etc" or "/home" or "/"... :-(

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] Bug report: fossil settings/unset no longer supports "-R"

[Roy Keene]

To whom it may concern,

I would like to report a bug introduced in Fossil 1.36.

In previous versions of Fossil one could do "fossil unset -R  
ssh-command", however Fossil 1.36 added a call to verify_all_options() 
in src/db.c:settings_cmd ( 
http://fossil-scm.org/index.html/info/816bc43b8064bf4d ).


This function notices the "-R" option is present and not previously 
removed and causes an error to be printed.


The "fossil all unset" and "fossil all setting" command use this 
functionality and are now subsequently broken (a regression):


[rkeene@kps-rsk-laptop pipethread]$ fossil all unset ssh-command
fossil unset -R /home/rkeene/.repos/home.fossil ssh-command
unrecognized command-line option, or missing argument: -R
[rkeene@kps-rsk-laptop pipethread]$

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