Re: [fossil-users] Test From masquerading

[Jungle Boogie]

On Sat 11 Aug 2018 11:47 AM, Andy Bradford wrote:
> Thus said "Andy Bradford" on 11 Aug 2018 11:41:01 -0600:
> 
> > This is just a test.
> 
> Only now at  the end do I realize that  Fossil Users allowed subscribers
> to hide their subscriber email address... pity.
> 

Just curious, how did you masquerade your address? It might still work on other
mailing lists you're subscribed to.

> Andy
> -- 
> TAI64 timestamp: 40005b6f213b
___
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] About to merge the forum-v2 branch

[Jungle Boogie]

On Thu 02 Aug 2018  6:03 PM, joerg van den hoff wrote:
>
> the specific _concern_ here is the contemplated shutdown of this mailing
> list and mandatory(!) migration of all questions/discussions to the
> planned/upcoming fossil-scm forum. if that's what going to happen: so be it.
> but I would prefer otherwise.
> 

Sure, I was providing a little history as of why/how/when the forum discussion
started.

As for migration, I'm sure Dr. Hipp will be a reasonable decision with the input
he's been provided. Ultimately, though, the best way to test the feature out is
to eat your own dog food.

> >
> >> br/joerg
___
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] About to merge the forum-v2 branch

[Jungle Boogie]

On Thu 02 Aug 2018 11:02 AM, joerg van den hoff wrote:
> On 02.08.18 10:38, Steve Landers wrote:> On 31 Jul 2018, 9:47 PM +0800,
> Richard Hipp , wrote:
> >> I am about ready to merge the forum-v2 branch into trunk. If there
> >> are any objections, voice them quickly.
> >
>
> I could easily envision a situation where the forum option would suit me
> fine for personal/small/modest projects where I also would actually _want_
> to keep the whole communication with some colleagues as part of the project,
> and "foreign", bigger ones (fossil, tcl, sqlite, ...) where I most
> definitely would
> not be interested in doing that and also probably would prefer to use a
> mailing list acessed by a reasonable mail client that allows me to
> sort/delete/search/flag (and highlight unread) messages etc. more
> flexible/better (probably...) than what the forum functionality could
> reasonably provide.



If folks will remember back just a couple months ago, this is kind of what
started this discussion. DRH shutdown the sqlite mailing list for a day or two
because of spam. During that time many folks disucssed forums, slack channels,
discord, irc, and of course, mailing lists.

After the mailing list was patched, the discussion continued on about how
fossil, with a forum or some kind of email delivery system, could work better
with push/pull requests. Fossil bundles were discussed, but many folks still
wanted to see a github style pull request system with email notifications and
abilities to make comments within the fossil repo, aside from wikis, tech notes,
and tickets. Dr. Hipp quickly developed email notifications for commits to the
repo, and a few ways to store the emails.

I enjoy mailing lists, having a copy of the mail and being able to reply from
mutt (which I'm doing now), but I think what's been implemented within fossil is
something we can all appreciate and find use of. A small project may not use
tickets, the wiki, or tech notes. That project probably won't have a mailing
list either.
Now there's another feature, for free, that they also may not use - a forum.

> br/joerg



Just my opinion on this subject. Please refer to the mailing list archive for a
more accurate account for the discussion, but this is how I remember it
happening/taking place.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Re-sync skins of remote repo

[Jungle Boogie]

Hi All,

I'd like to know if there's a way to re-sync to the skin of a remote repo, but I
don't know of an option to do so.

If I cloned the sqlite3 repo from long ago, when I run fossil server, I'll see
the former skin. `fossil sync` doesn't seem to care about changes to the skin.

Is the skin something outside the control syncing and updating?

Thanks!


___
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] OT: security/entropy (was Re: New Fossil user experiences)

[Jungle Boogie]

On Fri 13 Jul 2018  4:22 PM, David Mason wrote:
> So I guess this is what Warren had in mind.  Posting this in case it helps
> somebody on the list.
> 

Taking this offtopic a little bit more...let's talk about VPNs.

Don't use PPTP and don't get tangled up in ipsec configuration hell.

Be happy with wireguard! https://www.wireguard.com

It runs on everything but Windows (Linux, *BSD, MacOS, Andriod, iphone). There's
no passwords to share and the public keys are easily, easily distributed.

> Thanks  ../Dave
___
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] /usr/bin/ld: cannot find -ldl

[Jungle Boogie]

On Fri 13 Jul 2018  5:08 AM, Artur Shepilko wrote:
> > openBSD -current x64
> > $ cc -v
> > OpenBSD clang version 6.0.0 (tags/RELEASE_600/final) (based on LLVM 6.0.0)
> > Target: amd64-unknown-openbsd6.3
> > Thread model: posix
> > InstalledDir: /usr/bin
> >
> 
> Ok, I think I found the problem. This info was very helpful.
> 
> Indeed, the *BSD platforms have all the dl functionality in the
> standard C library, so no libdl present.
> This should make the test `[check-function-in-lib dlopen dl]` pass
> without the need for -ldl.
> 
> Corrected it and pushed an update
> [http://fossil-scm.org/index.html/info/7cdb522b42aad6a1]
> Please try if this solves it for you.
> 
> Thank you for catching the bug!


Thank YOU for fixing and pushing it to trunk. I've been able to successfully
build fossil now.

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

[fossil-users] /usr/bin/ld: cannot find -ldl

[Jungle Boogie]

Hi All,

Since commit 9c38803597 I can't build fossil successfully:

.obld/linenoise.o  bld/shell.o  bld/th.o  bld/th_lang.o  bld/th_tcl.o
bld/cson_amalgamation.o -lfuse -lm -lssl -lcrypto -lz -ldl
/usr/bin/ld: cannot find -ldl
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error 1 in /home/jungle/fossil-repos/fossil (./src/main.mk:670 'fossil')

Looks like there was only one minor change to the makemake.tcl file. I can
generate main.mk file without any issues:
 tclsh makemake.tcl
 building main.mk
 building ../win/Makefile.mingw
 building ../win/Makefile.dmc
 building ../win/Makefile.msc
 building ../win/Makefile.PellesCGMake

 Just compiling is failing.


 Any clues?

 Thanks!
___
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] Feature slideshow on fossil homepage

[Jungle Boogie]

On Thu 12 Jul 2018  1:40 PM, Andy Bradford wrote:
> Thus said mario on Mon, 09 Jul 2018 18:06:52 +0200:
> 
> > Our current homepage is  a bit wall of textish /  too bland I'd think.
> > While it already gets all interesting features across, it's not likely
> > enticing to new users.
> 
> Here's a GIF animation of what it looks like in my browser:
> 
> http://fossil.bradfords.org/fossilthings.gif
> 
> Does this look more enticing?
> 

That doesn't appear to establish a connection. Is your server down?

> Thanks,
> 
> Andy
> -- 
> TAI64 timestamp: 40005b47aeee
___
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] Feature slideshow on fossil homepage

[jungle Boogie]

HI Mario,
On 9 July 2018 at 09:06, mario  wrote:
> As followup to last month` Show time.. discussion:
>
> → http://fossilslideshow.tmp.include-once.org/
>
> (Take in mind this ain't a mockup yet; just as example.)
>

I think it's a good first step. Thanks for your efforts!

The carousal might be a little too cookie cutter/modern for
programmers/developers, but might appeal to managers of those people.

What if the current 'What is Fossil' section had small graphical
bullet points, kind of like with git-scm.org's various sections:
https://git-scm.com

I agree that there is a large wall of text - but all very informative
- which would require the visitor to read for an understanding of
Fossil, kind of a large commitment in today's minds IMO.
___
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] branch assistance needed

[jungle Boogie]

On 12:42AM, Wed, Jul 4, 2018 Nicola  wrote:
>
> On 04/07/2018 00:18, Warren Young wrote:> On Jul 3, 2018, at 3:09 PM,
> Dewey Hylton  wrote:
>
>  >> I then attempted to change that latest commit by adding a 'trunk'
> tag and cancelling the new branch tag.
>  >
>  > Ow!
> As a newbie Fossil user, after reading
>
>  https://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki
>
> and, specifically, this sentence:
>
>  > […] check-ins can be freely moved between branches simply by altering
>  > their tags
> I was (mis)lead to believe that what the OP did might somehow work
> (well, actually I was skeptic, so I tried on a test repository).
>
> Maybe, the sentence above could be complemented with an example of how
> to do that and how *not* to do it (e.g., explaining what the effect of
> adding a 'trunk' tag to a random check-in is and why it should not be
> done).

So provide a patch with the enhancement and let's see what happens.

>
> Nicola
>
___
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] Cannot clone sqlite docs repository

[jungle Boogie]

On 2 July 2018 at 09:05, Brian Nguyen  wrote:
>> $ fossil clone https://www2.sqlite.org/docsrc doc.sqlite
>> Round-trips: 2   Artifacts sent: 0  received: 0
>> Error: not authorized to clone
>> Round-trips: 2   Artifacts sent: 0  received: 0
>> Clone done, sent: 537  received: 582  ip: 2.0.1.187
>> server returned an error - clone aborted
>> $ fossil clone https://www.hwaci.com/cgi-bin/docsrc doc.sqlite
>> Round-trips: 3   Artifacts sent: 0  received: 7650
>> Clone done, sent: 821  received: 10881255  ip: 2.0.1.187
>> Rebuilding repository meta-data...
>>   98.0% complete...
>> 7 scan steps for 1 rows in [UPDATE time_fudge SET m1=m2-:incr WHERE m1>=m2
>> AND m1>   100.0% complete...
>> Extra delta compression...
>> 2430 scan steps for 5 rows in [SELECT rid FROM event, blob WHERE
>> blob.rid=event.objid   AND event.type='ci'   AND NOT EXISTS(SELECT 1 FROM
>> delta WHERE rid=blob.rid) ORDER BY event.mtime DESC]
>> 5615 scan steps for 843 rows in [SELECT DISTINCT blob.rid, mlink.fnid FROM
>> blob, mlink, plink WHERE NOT EXISTS(SELECT 1 FROM delta WHERE rid=blob.rid)
>> AND mlink.fid=blob.rid   AND mlink.mid=plink.cid   AND plink.cid=mlink.mid
>> ORDER BY mlink.fnid, plink.mtime DESC]
>> Vacuuming the database...
>> project-id: a49a74a282acfe2f07de91768b854dffd3d783df
>> server-id:  c09ff2f6b492daa621659f4fea82347370fb3343
>> admin-user: root (password is "7653f4")
>> $ fossil sync --unversioned --verily https://www2.sqlite.org/docsrc -R
>> doc.sqlite
>> Round-trips: 2   Artifacts sent: 0  received: 0
>> Server says: pull only - not authorized to push
>> Round-trips: 4   Artifacts sent: 0  received: 1194
>> Sync done, sent: 237087  received: 2094710  ip: 2.0.1.187
>> 8831 scan steps for 431 rows in [  SELECT pid FROM plink WHERE pid>0 AND
>> isprim AND cid IN (SELECT blob.rid FROM blob   WHERE rcvid=:rcvid)]
>
> I don't understand why it is possible to sync a repository but not to clone
> it. Why is the permission system like that?
>

I can:

$ fossil sync --unversioned --verily https://www.sqlite.org/docsrc -R
../docs.fossil
Round-trips: 1   Artifacts sent: 0  received: 0
Sync done, sent: 235039  received: 235667  ip: 45.33.6.223

I imagine DRH doesn't want www2 cloneable, because it's not the
canonical source of truth, only a copy of it.

Try your steps again with the original copy.
___
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 crash with http command

[Jungle Boogie]

Hi All,

I don't know if this has been reported already, but I'm getting a core dump when
running `fossil http` anywhere but within the fossil repo.

#0  sqlite3FindFunction (db=0x0, zName=0x6364d2e0220 "constant_time_cmp",
nArg=2, enc=1 '\001', createFlag=0 '\0') at ./src/sqlite3.c:31156
#1  0x06364d04c1e1 in sqlite3CreateFunc (db=0x0, zFunctionName=0x6364d2e0220
"constant_time_cmp", nArg=2, enc=1, pUserData=Variable "pUserData" is not
available.
)
at ./src/sqlite3.c:148524
#2  0x06364d04bda0 in sqlite3_create_function (db=0x0, 
zFunc=Variable
"zFunc" is not available.
) at ./src/sqlite3.c:148607
#3  0x06364cf7178c in login_check_credentials () at login.c:951
#4  0x06364d001abd in style_header (zTitleFormat=0x6364d394ea8 "Bad
Request") at style.c:394
#5  0x06364cf908fd in fossil_fatal (zFormat=Variable "zFormat" is 
not
available.
) at printf.c:1096
#6  0x06364cf2a7bb in db_must_be_within_tree () at db.c:1737
#7  0x06364cf77b83 in cmd_http () at main.c:2145
#8  0x06364cf74f96 in main (argc=Variable "argc" is not available.
) at main.c:788

Hope this help.

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

[fossil-users] minor grammar suggestions

[Jungle Boogie]

Hi All,

Please see attached patch for your consideration. I found some text for the
various settings that could be updated.

Thanks!
Index: src/db.c
==
--- src/db.c
+++ src/db.c
@@ -15,11 +15,11 @@
 **
 ***
 **
 ** Code for interfacing to the various databases.
 **
-** There are three separate database files that fossil interacts
+** There are three separate database files that Fossil interacts
 ** with:
 **
 **(1)  The "user" database in ~/.fossil
 **
 **(2)  The "repository" database
@@ -2932,19 +2932,19 @@
 ** If enabled, automatically pull the shunning list
 ** from a server to which the client autosyncs.
 */
 /*
 ** SETTING: autosyncwidth=16 default=on
-** This setting can take either a boolean value or "pullonly"
-** If enabled, automatically pull prior to commit
-** or update and automatically push after commit or
-** tag or branch creation.  If the value is "pullonly"
+** This setting can take either a boolean value or "pullonly".
+** If enabled, automatically pull prior to commit,
+** or update and automatically push after commit,
+** tag, or branch creation.  If the value is "pullonly",
 ** then only pull operations occur automatically.
 */
 /*
 ** SETTING: autosync-tries  width=16 default=1
-** If autosync is enabled setting this to a value greater
+** If autosync is enabled, setting this to a value greater
 ** than zero will cause autosync to try no more than this
 ** number of attempts if there is a sync failure.
 */
 /*
 ** SETTING: binary-glob width=40 versionable block-text
@@ -2963,11 +2963,11 @@
 #endif
 #if !(defined(_WIN32)||defined(__CYGWIN__)||defined(__DARWIN__))
 /*
 ** SETTING: case-sensitive  boolean default=on
 ** If TRUE, the files whose names differ only in case
-** are considered distinct.  If FALSE files whose names
+** are considered distinct.  If FALSE, files whose names
 ** differ only in case are the same file.  Defaults to
 ** TRUE for unix and FALSE for Cygwin, Mac and Windows.
 */
 #endif
 /*
@@ -2977,11 +2977,11 @@
 ** delete without prompting or allowing undo.
 ** Example: *.a,*.lib,*.o
 */
 /*
 ** SETTING: clearsign   boolean default=off
-** When enabled, fossil will attempt to sign all commits
+** When enabled, Fossil will attempt to sign all commits
 ** with gpg.  When disabled, commits will be unsigned.
 */
 /*
 ** SETTING: crlf-glob   width=40 versionable block-text
 ** The value is a comma or newline-separated list of GLOB patterns for
@@ -3201,11 +3201,11 @@
 ** password authentication.
 */
 #ifdef FOSSIL_ENABLE_TCL
 /*
 ** SETTING: tcl  boolean default=off
-** If enabled Tcl integration commands will be added to the TH1
+** If enabled, Tcl integration commands will be added to the TH1
 ** interpreter, allowing arbitrary Tcl expressions and
 ** scripts to be evaluated from TH1.  Additionally, the Tcl
 ** interpreter will be able to evaluate arbitrary TH1
 ** expressions and scripts.
 */

___
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] smtp.c build failures

[jungle Boogie]

On 28 June 2018 at 12:07, Richard Hipp  wrote:
> On 6/28/18, jungle Boogie  wrote:
>>
>> Does this help?
>> http://man.openbsd.org/man3/getrrsetbyname.3
>>
>
> That seems to be an OpenBSD-only library function.  So, no, it doesn't
> really help.
>
> Does OpenBSD have req_query() at least?  I suppose I could write my
> own DNS record parser.  (sigh...)
>

https://man.openbsd.org/resolver.3

res_query, res_search, res_mkquery, res_send, res_init, dn_comp, dn_expand —
resolver routines

The res_query() function provides an interface to the server query
mechanism. It constructs a query, sends it to the local server, awaits
a response, and makes preliminary checks on the reply. The query
requests information of the specified type and class for the specified
fully qualified domain name dname. The reply message is left in the
answer buffer with length anslen supplied by the caller. Values for
the class and type fields are defined in .

I think that's what you want!


> --
> D. Richard Hipp
> d...@sqlite.org



---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] smtp.c build failures

[jungle Boogie]

On 28 June 2018 at 11:42, Richard Hipp  wrote:
> On 6/28/18, jungle Boogie  wrote:
>> Hi All,
>>
>> I know it's still very early on to make use of the new smtp logic, but
>> I thought I'd report these issues. Is anyone else experiencing issues
>> with compiling?
>
> Did you rerun ./configure?
>
> fossil clean -x
> ./configure
> make
>

The build took place in a separate directory, outside my trunk version
of Fossil.

> If you still get errors then, please let me know.  But first, figure
> out what library OpenBSD wants to link against in order to pick up the
> DNS parsing routines.

Does this help?
http://man.openbsd.org/man3/getrrsetbyname.3

>
> --
> 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] smtp.c build failures

[jungle Boogie]

Hi All,

I know it's still very early on to make use of the new smtp logic, but
I thought I'd report these issues. Is anyone else experiencing issues
with compiling?

FIG_H -D_HAVE_SQLITE_CONFIG_H -g -O2 -o bld/smtp.o -c bld/smtp_.c
./src/smtp.c:54:3: error: use of undeclared identifier 'ns_msg'
  ns_msg h;   /* DNS reply parser */
  ^
./src/smtp.c:62:8: warning: implicit declaration of function
'ns_initparse' is invalid in C99
  [-Wimplicit-function-declaration]
  rc = ns_initparse(aDns,nDns,);
   ^
./src/smtp.c:62:32: error: use of undeclared identifier 'h'
  rc = ns_initparse(aDns,nDns,);
   ^
./src/smtp.c:64:10: warning: implicit declaration of function
'ns_msg_count' is invalid in C99
  [-Wimplicit-function-declaration]
  nRec = ns_msg_count(h, ns_s_an);
 ^
./src/smtp.c:64:23: error: use of undeclared identifier 'h'
  nRec = ns_msg_count(h, ns_s_an);
  ^
./src/smtp.c:64:26: error: use of undeclared identifier 'ns_s_an'
  nRec = ns_msg_count(h, ns_s_an);
 ^
./src/smtp.c:66:5: error: use of undeclared identifier 'ns_rr'
ns_rr x;
^
./src/smtp.c:69:10: warning: implicit declaration of function
'ns_parserr' is invalid in C99
  [-Wimplicit-function-declaration]
rc = ns_parserr(, ns_s_an, i, );
 ^
./src/smtp.c:69:22: error: use of undeclared identifier 'h'
rc = ns_parserr(, ns_s_an, i, );
 ^
./src/smtp.c:69:25: error: use of undeclared identifier 'ns_s_an'
rc = ns_parserr(, ns_s_an, i, );
^
./src/smtp.c:69:38: error: use of undeclared identifier 'x'
rc = ns_parserr(, ns_s_an, i, );
 ^
./src/smtp.c:71:9: warning: implicit declaration of function
'ns_rr_rdata' is invalid in C99
  [-Wimplicit-function-declaration]
p = ns_rr_rdata(x);
^
./src/smtp.c:71:21: error: use of undeclared identifier 'x'
p = ns_rr_rdata(x);
^
./src/smtp.c:72:10: warning: implicit declaration of function
'ns_rr_rdlen' is invalid in C99
  [-Wimplicit-function-declaration]
sz = ns_rr_rdlen(x);
 ^
./src/smtp.c:72:22: error: use of undeclared identifier 'x'
sz = ns_rr_rdlen(x);
 ^
./src/smtp.c:82:5: warning: implicit declaration of function
'ns_name_uncompress' is invalid in
  C99 [-Wimplicit-function-declaration]
ns_name_uncompress(aDns, aDns+nDns, pBest+2,
^
6 warnings and 10 errors generated.
*** Error 1 in /home/jungle/fossil-repos/smtp (./src/main.mk:1628 'bld/smtp.o')

OpenBSD clang version 6.0.0 (tags/RELEASE_600/final) (based on LLVM 6.0.0)
Target: amd64-unknown-openbsd6.3
Thread model: posix
InstalledDir: /usr/bin

Running openBSD -current

Thanks!



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] email.c typo

[jungle Boogie]

Hi All,

I spotted one small type in the email.c file:

Index: src/email.c
==
--- src/email.c
+++ src/email.c
@@ -2028,11 +2028,11 @@

 /*
 ** WEBPAGE: announce
 **
 ** A web-form, available to users with the "Send-Announcement" or "A"
-** capability, that allows one to to send an announcements to whomever
+** capability, that allows one to send an announcements to whomever
 ** has subscribed to them.  The administrator can also send an announcement
 ** to the entire mailing list (including people who have elected to
 ** receive no announcements or notifications of any kind, or to
 ** individual email to anyone.
 */

I think the rest looks good, but others should feel free to review as well!
___
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] email testing - no subscriber table?

[jungle Boogie]

On 25 June 2018 at 14:51, Richard Hipp  wrote:
> On 6/25/18, jungle Boogie  wrote:
>> If I inadvertently forward my email along
>> to someone/group without modifying the footer, the person/group would
>> be able to alter my subscription.
>
> How can I fix that?
>

I don't know, but maybe that idea of randomizing them every 12-24
hours is a good stop gap?

Perhaps the system be enhanced to randomize the subscriberCodes
periodically - say just before each daily digest is sent out?

> --
> 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] email testing - no subscriber table?

[jungle Boogie]

On 23 June 2018 at 13:07, Richard Hipp  wrote:
> Just FYI:
>
> I have opened up email notifications on the canonical Fossil
> repository.  To subscribe, visit:
>
> https://fossil-scm.org/fossil/subscribe
>
> Your help in finding creative ways of breaking the new system is appreciated.
>

This is already touched on in your email design document, but I'm just
adding another point here.

I really like the idea of the subscriberCode, because passwords are
not needed to be stored or remembered to alter the subscription.
However, the subscriberCode doesn't have to be stolen for the
subscription to be altered. If I inadvertently forward my email along
to someone/group without modifying the footer, the person/group would
be able to alter my subscription.

But as you point out, only the email address is available for the
miscreant and no username/password, etc.
___
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] email testing - no subscriber table?

[Jungle Boogie]

On Sat 23 Jun 2018  4:07 PM, Richard Hipp wrote:
> Just FYI:
> 
> I have opened up email notifications on the canonical Fossil
> repository.  To subscribe, visit:
> 
> https://fossil-scm.org/fossil/subscribe
> 
> Your help in finding creative ways of breaking the new system is appreciated.

Not a way of breaking it, but what do you think about having a link to the rss
feed at the bottom of the horizontal divide? "Follow the project via rss", or
something similar to that?

rss may not be a cool as messages to your slack channel, but it's still quite
reliable and really simple ;).


___
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] email testing - no subscriber table?

[Jungle Boogie]

On Sat 23 Jun 2018 11:26 PM, Svyatoslav Mishyn wrote:
> (Sat, 23 Jun 23:03) Svyatoslav Mishyn:
> > quick typos:
> 
> another one (+ previous one):
> 
> -generated once the email notification systems stablizes.
> +generated once the email notification systems stabilizes.
> 
> and
> 
> -  of the source tree that shows how to this is done.
> +  of the source tree that shows how this is done.
> 
> 
> (I don't know, should I add such small edits in full attachment patch
> file, or is it ok to just inline them?)
> 

Patches are probably easier to add, and I've inlined them in the past.
___
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] email testing - no subscriber table?

[Jungle Boogie]

On Sat 23 Jun 2018  4:07 PM, Richard Hipp wrote:
> Just FYI:
> 
> I have opened up email notifications on the canonical Fossil
> repository.  To subscribe, visit:
> 
> https://fossil-scm.org/fossil/subscribe
> 
> Your help in finding creative ways of breaking the new system is appreciated.
> 

Looks like + signs are not allowed for email addresses.

Without quotes, local-parts may consist of any combination of
alphabetic characters, digits, or any of the special characters

! # $ % & ' * + - / = ?  ^ _ ` . { | } ~

https://tools.ietf.org/html/rfc3696#section-3

> Please note that this is still a work-in-progress.  All subscription
> data may be erased at any time.  Email notifications might be disabled
> at any time, in order to close security holes or otherwise work on the
> system.
> -- 
> 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] email testing - no subscriber table?

[Jungle Boogie]

Hi All,

I think I've brought my repo up to trunk, did a little configuring of the email
page and attempted to add a subscriber, but I have a database error:

 
 SQLITE_ERROR: no such table: subscriber
 Database Error

 no such table: subscriber SELECT 1 FROM subscriber WHERE suname='jungle'


 I don't see the subscriber table at /repo_schema, if that means anything.

 Perhaps someone else can double-check this; I've done a fossil rebuild but no
 change.

The /stat page doesn't show a new schema version:
Schema Version: 2015-01-24, sha3

Should there be a schema version update?

Thanks!
___
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] What should email notifications look like?

[jungle Boogie]

On 22 June 2018 at 11:18, Richard Hipp  wrote:
> Shown below is what I have at the moment.  It is more succinct than
> other examples I've seen, but you can easily follow the link for
> details.


Very nice! I think you're on the right track!
___
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] What should email notifications look like?

[jungle Boogie]

On 22 June 2018 at 07:09, jungle Boogie  wrote:
> On 22 June 2018 at 06:09, Richard Hipp  wrote:
>> You may have noticed that I've been working on adding support for
>> email notifications or alerts to events on a Fossil repository.  But I
>> need your help.
>>
>> When an event occurs (such as a check-in, or wiki-page edit) and a
>> user wants a notification of that event, what should the email look
>> like?
>>
>> Please send me examples.  Pick a timeline event from the Fossil
>> self-hosting repository and send me the actual text of an email that
>> you think should be dispatched to announce that event.
>>
>
> This is an example of what some git client is sending for the chrony project:
> https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-dev/2018/06/msg0.html
>
> I don't mind that format.
>

For an additional example, here's what openBSD cvs posts look like:
https://marc.info/?l=openbsd-cvs=152964678232394=2

That's very simple, but still informative to show what's changed.

I think Philip's format is nice and simple, much of what's above.
___
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] What should email notifications look like?

[jungle Boogie]

On 22 June 2018 at 06:09, Richard Hipp  wrote:
> You may have noticed that I've been working on adding support for
> email notifications or alerts to events on a Fossil repository.  But I
> need your help.
>
> When an event occurs (such as a check-in, or wiki-page edit) and a
> user wants a notification of that event, what should the email look
> like?
>
> Please send me examples.  Pick a timeline event from the Fossil
> self-hosting repository and send me the actual text of an email that
> you think should be dispatched to announce that event.
>

This is an example of what some git client is sending for the chrony project:
https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-dev/2018/06/msg0.html

I don't mind that format.

I'd rather have emails delivered in plain text, bypassing
html/markdown but that's just my preference.

> You can reply to this mailing list, or send examples directly to me.
> --
> 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] Cloning repository with large files very slow

[Jungle Boogie]

On Thu 21 Jun 2018  7:47 PM, E Cruz wrote:
> On 06/21/2018 05:06 PM, Warren Young wrote:
> 
> As mentioned in the original post, the majority of the time taken by the
> clone operation seems to be spent re-calculating the delta encoding of the
> large table definition files.   I do not mind much the time it takes to
> commit changes to the large tables, although if that can be improved it
> would be welcomed.  But once that is done, we have to pay for the delta
> encoding on every future clone operation.  That is the part I would like to
> avoid if possible.
> 

Just curious, how often are you cloning and opening the repo? With git, I've had
it take a little while to expand the repo.

For a comparison, clone the sqlite repo and see if it's quicker/slower/about
the same as your repo clone. I believe the sqlite repo is larger than yours.
___
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] Perception of Fossil

[jungle Boogie]

All very, very lovely thinking! I just have one comment/question...

On 15 June 2018 at 10:35, Richard Hipp  wrote:
> On 6/15/18, David Mason  wrote:
>> I heartily agree with this... A flag to allow a person (including
>> Anonymous) to make a commit that would automatically go into a new branch
>> like "Patch-1" (each one incrementing the branch number) is (a) better than
>> emailed patches, and (b) better than pull requests. Primarily because it
>> puts it into Fossil so you can use all your standard workflows.
>>
>> The "Patch-?" branches should not be automatically synced, and if you do a
>> sync with some special flag, it should offer each of the existing patch
>> branches and allow you to agree to sync it, or not. Then there needs to be
>> a way to delete the patch branches (whether included into the trunk or not)
>
> An alternative design sketch:
>
> (1) Anonymous clones repo CoolApp
>
> (2) Anonymous makes changes to CoolApp and checks those changes into a
> branch named "anon-patch" on her private clone.  Repeat this step as
> necessary to get anon-patch working.
>
> (3) Anonymous runs the command "fossil pullrequest anon-patch"
>
> (4) The pullrequest command creates a "bundle" out of the "anon-patch"
> branch and then transmits that bundle back to the server from which
> the clone originated.
>
> (5) The server accepts the bundle and parks it in a separate holding
> table, but does not merge it or otherwise make it available to average
> passers by.  The server then sends email notifications to developers
> with appropriate privileges to let them know that a pull request has
> arrived.
>
> (6) Developers who receive notification of the pull request can run a
> command that pulls down the bundle and applies it as a private branch
> on their own personal clones of the repo.  Developers can then either
> approve of the pull request by publishing it (marking it non-private)
> and pushing it back to the server.  Or they can reject the pull
> request which erases it from their clone.  They might also cause the
> pull request to be erased from the holding table on the server.
>

Some changes may not need to be tested in a personal repo on their
local machine. Would it be possible to see the changes and approve
within the fossil UI?
For instance, anything involving text can likely be read from a diff -
spelling updates, grammar, more/less word.

I know that might be getting too deep into the centralized view of a
decentralize server, but it's a thought that occurred to me.

> Additional notes:
>
> Prior to step (3), Fossil might require Anonymous to provide contact
> information so that developers can get in touch in case there are
> questions or requests for clarification.  Anonymous might also be
> asked to sign a contributors agreement to be included in the bundle
> (as an entry in the bconfig table).

That's a very nice thought. What is another Anonymous person were to
submit a pull request, would it assume it's the same user and use the
same contact info? I don't think you would want it to have a
confirmation message that displays the previous Anonymous user email
address.

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

[jungle Boogie]

On 14 June 2018 at 13:30, Thomas  wrote:
> Web forums are much more superior than mailing lists, in any possible
> direction.
>

Ah, yes, superior.
https://xkcd.com/979/

At this rate, I suggest we start using reddit more, it's at least more
diverse than a single stand alone forum.
https://www.reddit.com/r/sqlite/
___
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] Back on-line. Was: Mailing list shutting down...

[jungle Boogie]

On 14 June 2018 at 08:58, Richard Hipp  wrote:

>
> So there you have it:  If you want to harass someone by sending them
> thousands of subscription confirmations, there is now a website to
> assist you.  Do we need any further evidence that the heart of man is
> deceitful above all things, and desperately wicked?

You're right - we're born sinners and must practice being good.

> --
> D. Richard Hipp
> d...@sqlite.org


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Mailing list shutting down...

[jungle Boogie]

On 13 June 2018 at 08:11, Warren Young  wrote:
> On Jun 13, 2018, at 8:05 AM, Richard Hipp  wrote:
>>
>> My current tthinking is to use a hybrid approach where subscribers get
>> emails just like ordinary mailing lists, but posting and replying is
>> via web-form only.
>
> If you do this atop Fossil, then you end up inches away from being able to 
> provide an oft-wanted feature: email notifications on checkins, wiki article 
> changes, and other Fossil events.


DRH at least had this concept in mind:
http://www2.alt-mail.net/index.html/doc/trunk/README.md
___
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] Attachment policy

[jungle Boogie]

Hi Andy,

Seeing that you have a Gmail account, you could upload to Google drive and
make public. Then provide the link via email to that file.
___
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...

[Jungle Boogie]

On Sun 03 Jun 2018  9: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.

On the homepage:
Maybe a blurb about using sha3 in light of what happened with sha1.

Link to reports and/or stats page: https://www.fossil-scm.org/index.html/reports
This is not to show off how active fossil itself is, but Github projects have
the insights tab easily available.




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

[Jungle Boogie]

On Sun 03 Jun 2018 11:06 PM, Richard Hipp wrote:
> On 6/3/18, Jungle Boogie  wrote:
> > On Sun 03 Jun 2018 10:47 PM, Richard Hipp wrote:
> >> On 6/3/18, jungle Boogie  wrote:
> >> >
> >> > Since it's linked from the homepage, maybe this can be updated to show
> >> > that
> >> > a) project website is still updated and b) to show fossil is still
> >> > efficient.
> >> >
> >> > http://fossil-scm.org/index.html/doc/trunk/www/stats.wiki
> >> >
> >>
> >> Updated.
> >
> > This line:
> > SQLite project gets excellent 73:1 compression.
> >
> > Chart now shows 80:1! Perhaps just 73:1 or better?
> 
> I got 80:1 on a fresh clone.  You get something different?

No, the text under 'Analysis And Supplemental Data' shows the older 73:1. 

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

[Jungle Boogie]

On Sun 03 Jun 2018 10:47 PM, Richard Hipp wrote:
> On 6/3/18, jungle Boogie  wrote:
> >
> > Since it's linked from the homepage, maybe this can be updated to show that
> > a) project website is still updated and b) to show fossil is still
> > efficient.
> >
> > http://fossil-scm.org/index.html/doc/trunk/www/stats.wiki
> >
> 
> Updated.

This line:
SQLite project gets excellent 73:1 compression.

Chart now shows 80:1! Perhaps just 73:1 or better?

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

[Jungle Boogie]

On Sun 03 Jun 2018  9: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.
> 

Perhaps expand point #2 to talk about themes/skins built into fossil, and a link
to the URL where the user can browse the examples.

You might consider remove or moving the 'Fuel' link down the list. There sadly
hasn't been an update to the repo since Oct 2015.


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

[jungle Boogie]

On 6:28PM, Sun, Jun 3, 2018 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.
>

Since it's linked from the homepage, maybe this can be updated to show that
a) project website is still updated and b) to show fossil is still
efficient.

http://fossil-scm.org/index.html/doc/trunk/www/stats.wiki

> --
> 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] Recently added or enhanced /timeline query parameters

[jungle boogie]

Thus said Warren Young on Sat, 28 Apr 2018 20:24:16 -0600

On Apr 28, 2018, at 1:07 PM, Richard Hipp  wrote:


(1) The new days=N query parameter shows all activity within the
previous N days.


Nice!

I think this will end up being more useful than “max N any type,” as I 
frequently find myself fiddling with N as a project gets busy and then calms 
back down again.  I want it to show me one screen showing everything I want to 
see and no more; days is more likely to get me what I want than guessing at 
values of max N.

What would make it even more useful, though, is if it was part of the page UI 
and participated in the page load cookie, so that you wouldn’t have to keep 
resetting it with manual URL editing.



Yes, I agree with this. Also like the idea of having some generic 
options, 7 days, 2 weeks, 1 month, etc.


Perhaps the UI could even have an empty box that accepts an integer and 
adjacent to that, the user selects days/weeks/months, etc.


___
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] Why SQLite Does Not Use Git

[Jungle Boogie]

On Sat 14 Apr 2018  6:22 AM, Richard Hipp wrote:
> Article:  https://sqlite.org/whynotgit.html
> 
> HN discussion: https://news.ycombinator.com/item?id=16806114
> 
> Reddit discussion:
> https://www.reddit.com/r/programming/comments/8c2niw/why_sqlite_does_not_use_git/
> 

Really good article with lots of good discussions happening. Nice job!

Some other points worth considering:
Since you created Fossil, you can expand it to fit your needs. The majority of
folks find tools that are good enough for their usage, but you have the ability
to enhance Fossil more, not only is this a benefit to you but others who use
Fossil. You also accept patches for Fossil to improve it - not sure how easily
that is on git.

Fossil won't work in every situation (kernel development), and that's fine for
your use case and probably most folks who use git already.


> -- 
> 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] Commit 3e94c7ed7

[jungle boogie]

Thus said Richard Hipp on Sat, 7 Apr 2018 16:12:43 -0400


To get the latest trunk check-in, do this:

https://whatever.dom/fossil/tarball/trunk/download.tar.gz



That's awesome! Thanks for pointing this out and the link to the document!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Commit 3e94c7ed7

[jungle boogie]

Hi DRH,

I think this commit is real useful:
https://www.fossil-scm.org/index.html/info/3e94c7ed74a07741

Thanks!

To enhance it a little more, what do you think about having the latest 
commit on trunk having a generic filename such as trunk.zip/.tar.gz/.sqlar?


In this event, you wouldn't need to know the partial hash to download 
the latest code, and more importantly, the URL wouldn't change from 
commit-to-commit.


Thanks!
___
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] Error on commit

[jungle Boogie]

On 26 March 2018 at 12:27, Scott Doctor  wrote:
>
> A while back I created a new repository for a project I ressurected. Checked
> it after creating with the fossil ui that all files included and such.
> Everything OK.
>
> My project contains many folders and a couple hundred files for a multi
> processor embedded application. Been working on the program for a while. I
> tried to do a commit as I have not done so in a while and I am getting ready
> to do some major work on my program.
>
> Issued the fossil commit command.
>

What was the exact commit command you issued?
___
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] Strange IP address on repository sync report.

[jungle Boogie]

On 2 February 2018 at 07:08, Warren Young  wrote:
> On Sep 16, 2017, at 12:57 PM, John Found  wrote:
>>
>> On Sat, 16 Sep 2017 13:44:51 -0500
>> Andy Goth  wrote:
>>
>>> Please type "openssl version" and let us know what it prints.
>>
>> OpenSSL 1.1.0f  25 May 2017
>
> There’s a known bug in that version of OpenSSL which was fixed in the very 
> next version, 1.1.1.
>
> Quoting from the OpenSSL 1.1.1 ChangeLog:
>
>>  *) Rewrite of BIO networking library. The BIO library lacked consistent
>> support of IPv6, and adding it required some more extensive
>> modifications.  This introduces the BIO_ADDR and BIO_ADDRINFO types,
>> which hold all types of addresses and chains of address information.
>> It also introduces a new API, with functions like BIO_socket,
>> BIO_connect, BIO_listen, BIO_lookup and a rewrite of BIO_accept.
>> The source/sink BIOs BIO_s_connect, BIO_s_accept and BIO_s_datagram
>> have been adapted accordingly.
>> [Richard Levitte]
>
> One solution you have, therefore, is to install the source code for OpenSSL 
> 1.1.1 or 1.0.2n into compat/openssl under the Fossil source tree, build the 
> library, then reconfigure Fossil, adding --with-openssl=tree to whatever 
> other options you’d normally use.
>
> You may need to add this to your ~/.profile:
>
> export SSL_CERT_DIR=/etc/ssl/certs
>
> This non-platform version of OpenSSL will not be able to find your platform 
> CA certificate store otherwise.
>
> Another solution is simply to disable IPv6 everywhere in your system.
>
> A third solution would be to lean on Debian/Raspbian/Ubuntu, etc. to backport 
> this fix from 1.1.1 to 1.1.0f.  I don’t hold out much hope on this since the 
> fix is described as a “rewrite” of a core I/O library.
>
> Therefore, a fourth solution is to simply ignore it until 2020 or so, by 
> which time you should have a new version of your stable OS’s core libraries, 
> as long as you’re willing to upgrade at that time.

Fifth solution: don't use TLS for this repo when you're using that platform.


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Cross-link tech notes to commits

[jungle Boogie]

On 21 December 2017 at 07:34, jungle Boogie <jungleboog...@gmail.com> wrote:
> On 20 December 2017 at 13:13, jungle Boogie <jungleboog...@gmail.com> wrote:
>> Hi All,
>>
>> I know a tech note entry in the timeline can be linked to a specific commit.
>> For example:
>> http://fossil-scm.org/index.html/timeline?ss=m=200=e=0
>>
>> See the top commit by AG.
>>
>> Can a commit message contain the [ID] of a tech note and have it linked to 
>> it?
>>
>
> At this point in reading the documentation, I don't think this is the
> case. Technotes commit messages can contain the [ID] of a check-in,
> though.
>
> https://www.fossil-scm.org/index.html/doc/trunk/www/event.wiki
>
> Is this because of this?
> Because technotes are considered a special kind of wiki, users must have
> permission to read wiki in order read technotes.
>

I know a release is coming up soon, so maybe we can determine if this
is a bug not to cross-link, an enhancement, or as designed.


> Thanks!



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Strange IP address on repository sync report.

[jungle Boogie]

On 24 January 2018 at 13:45, Warren Young  wrote:
> On Jan 24, 2018, at 1:47 PM, Warren Young  wrote:
>>
>> On Sep 16, 2017, at 1:27 PM, Andy Goth  wrote:
>>>
>>> Indeed, 1.1.0f is a version which includes the BIO_ADDR type, which is a 
>>> union containing struct sockaddr_in6 among others. I don't think there's 
>>> any question Fossil is trying to read an IPv6 address structure as if it 
>>> were IPv4.
>>
>> Has anyone tried addressing this?  I still see it on my Raspberry Pi running 
>> a recent version of Raspbian.
>
> In case it’s not clear, I mean that I see it with the tip of trunk.  
> [1cbaf3bdd9]
>
> lsb_release -s says, "Raspbian GNU/Linux 9.3 (stretch)”

I'm using a raspberry pi with raspbian, although I don't think it's stretch.

>
>> Since I haven’t seen it on any of my 64-bit hosts, I’m guessing it has 
>> something to do with a peculiarity on 32-bit Linux.
>
> I’ve poked at it some, and it’s only happening in the HTTPS code path.  If I 
> clone http://fossil-scm.org on the Pi, it shows the correct IP, 45.33.6.223.

Not for me
$ sudo tcpdump port 443
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
14:11:45.030160 IP 192.168.0.7.36828 > sqlite.org.https: Flags [S],
seq 2345998021, win 29200, options [mss 1460,sackOK,TS val 33726945
ecr 0,nop,wscale 7], length 0
14:11:45.095329 IP sqlite.org.https > 192.168.0.7.36828: Flags [S.],
seq 3106903644, ack 2345998022, win 28960, options [mss 1460,sackOK,TS
val 459170829
ecr 33726945,nop,wscale 7], length 0
14:11:45.095647 IP 192.168.0.7.36828 > sqlite.org.https: Flags [.],
ack 1, win 229, options [nop,nop,TS val 33726952 ecr 459170829],
length 0
14:11:45.095949 IP 192.168.0.7.36828 > sqlite.org.https: Flags [P.],
seq 1:317, ack 1, win 229, options [nop,nop,TS val 33726952 ecr
459170829], length 316
14:11:45.157556 IP sqlite.org.https > 192.168.0.7.36828: Flags [.],
ack 317, win 235, options [nop,nop,TS val 459170895 ecr 33726952],
length 0
14:11:45.162647 IP sqlite.org.https > 192.168.0.7.36828: Flags [.],
seq 1:1449, ack 317, win 235, options [nop,nop,TS val 459170896 ecr
33726952], length
1448
14:11:45.163125 IP sqlite.org.https > 192.168.0.7.36828: Flags [.],
seq 1449:2897, ack 317, win 235, options [nop,nop,TS val 459170896 ecr
33726952], length 1448
14:11:45.163187 IP 192.168.0.7.36828 > sqlite.org.https: Flags [.],
ack 1449, win 251, options [nop,nop,TS val 33726959 ecr 459170896],
length 0
14:11:45.163353 IP sqlite.org.https > 192.168.0.7.36828: Flags [P.],
seq 2897:3081, ack 317, win 235, options [nop,nop,TS val 459170896 ecr
33726952], length 184
14:11:45.163468 IP 192.168.0.7.36828 > sqlite.org.https: Flags [.],
ack 2897, win 274, options [nop,nop,TS val 33726959 ecr 459170896],
length 0
14:11:45.164153 IP 192.168.0.7.36828 > sqlite.org.https: Flags [.],
ack 3081, win 296, options [nop,nop,TS val 33726959 ecr 459170896],
length 0
14:11:45.190109 IP 192.168.0.7.36828 > sqlite.org.https: Flags [P.],
seq 317:443, ack 3081, win 296, options [nop,nop,TS val 33726961 ecr
459170896], length 126
14:11:45.242410 IP sqlite.org.https > 192.168.0.7.36828: Flags [P.],
seq 3081:3132, ack 443, win 235, options [nop,nop,TS val 459170979 ecr
33726961], length 51
14:11:45.244928 IP 192.168.0.7.36828 > sqlite.org.https: Flags [P.],
seq 443:642, ack 3132, win 296, options [nop,nop,TS val 33726967 ecr
459170979], length 199
14:11:45.336303 IP sqlite.org.https > 192.168.0.7.36828: Flags [.],
ack 642, win 243, options [nop,nop,TS val 459171075 ecr 33726967],
length 0
14:11:45.336625 IP 192.168.0.7.36828 > sqlite.org.https: Flags [P.],
seq 642:1645, ack 3132, win 296, options [nop,nop,TS val 33726976 ecr
459171075], length 1003
14:11:45.391737 IP sqlite.org.https > 192.168.0.7.36828: Flags [.],
ack 1645, win 259, options [nop,nop,TS val 459171131 ecr 33726976],
length 0
14:11:45.428202 IP sqlite.org.https > 192.168.0.7.36828: Flags [.],
seq 3132:4580, ack 1645, win 259, options [nop,nop,TS val 459171167
ecr 33726976], length 1448
14:11:45.428495 IP sqlite.org.https > 192.168.0.7.36828: Flags [.],
seq 4580:6028, ack 1645, win 259, options [nop,nop,TS val 459171167
ecr 33726976], length 1448
14:11:45.428715 IP sqlite.org.https > 192.168.0.7.36828: Flags [P.],
seq 6028:6345, ack 1645, win 259, options [nop,nop,TS val 459171167
ecr 33726976], length 317
14:11:45.428846 IP 192.168.0.7.36828 > sqlite.org.https: Flags [.],
ack 6028, win 342, options [nop,nop,TS val 33726985 ecr 459171167],
length 0
14:11:45.429000 IP sqlite.org.https > 192.168.0.7.36828: Flags [P.],
seq 6345:6376, ack 1645, win 259, options [nop,nop,TS val 459171167
ecr 33726976], length 31
14:11:45.430025 IP 192.168.0.7.36828 > sqlite.org.https: Flags [P.],
seq 1645:1676, ack 6376, win 364, options [nop,nop,TS val 33726985 ecr
459171167], length 31
14:11:45.430401 IP 192.168.0.7.36828 > sqlite.org.https: Flags [R.],
seq 1676, ack 6376, 

[fossil-users] Sort skins alphabetically patch

[Jungle Boogie]

Hi All,

For your consideration...


Index: src/skins.c
==
--- src/skins.c
+++ src/skins.c
@@ -39,23 +39,23 @@
 static struct BuiltinSkin {
   const char *zDesc;/* Description of this skin */
   const char *zLabel;   /* The directory under skins/ holding this skin */
   char *zSQL;   /* Filled in at run-time with SQL to insert this skin 
*/
 } aBuiltinSkin[] = {
-  { "Default",   "default",   0 },
+  { "Ardoise",   "ardoise",   0 },
+  { "Black & White, Menu on Left",   "black_and_white",   0 },
   { "Blitz", "blitz", 0 },
   { "Blitz, No Logo","blitz_no_logo", 0 },
   { "Bootstrap", "bootstrap", 0 },
-  { "Xekri", "xekri", 0 },
-  { "Original",  "original",  0 },
+  { "Default",   "default",   0 },
+  { "Eagle", "eagle", 0 },
   { "Enhanced Original", "enhanced1", 0 },
-  { "Shadow boxes & Rounded Corners","rounded1",  0 },
-  { "Eagle", "eagle", 0 },
-  { "Black & White, Menu on Left",   "black_and_white",   0 },
+  { "Khaki, No Logo","khaki", 0 },
+  { "Original",  "original",  0 },
   { "Plain Gray, No Logo",   "plain_gray",0 },
-  { "Khaki, No Logo","khaki", 0 },
-  { "Ardoise",   "ardoise",   0 },
+  { "Shadow boxes & Rounded Corners","rounded1",  0 },
+  { "Xekri", "xekri", 0 },
 };
 
 /*
 ** A skin consists of four "files" named here:
 */

Thanks,
j.b.
___
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] New "Ardoise" skin

[jungle Boogie]

On 8 January 2018 at 04:27, Richard Hipp  wrote:
> On 1/8/18, Antoine Chavasse  wrote:
>> I'm not sure I can fix this from the skin, since the background color for
>> ticket reports are configured by the user in the settings.
>>
>
> I might need to enhance Fossil to recognize this situation and make
> automatic adjustments to the background color.
>

If it's not already obvious, the fields on the ticket page are also too bright:
https://www.fossil-scm.org/skins/ardoise/tktview?name=c541b6e734

Thanks for the new skin, Antoine! I appreciate the work.

> --
> D. Richard Hipp
> d...@sqlite.org

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Errors in current trunk (24c2b99d) related to TIMESPEC

[jungle Boogie]

On 9 January 2018 at 06:32, Richard Hipp  wrote:
> A new version of Fossil is now on trunk.
> (https://www.fossil-scm.org/fossil/info/9a33a240a2101ede)  Please try
> again to build on every platform you have at hand, but especially all
> variations of MSVC and MinGW, and let me know whether or not you run
> into build issues.
>

I don't see any build errors when using MS Visual Studio 2017, v15.0.26730.16.
I just performed a fossil up trunk and the make flags.


> --
> 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] HTML instead of fossil sync protocol

[jungle Boogie]

On 28 December 2017 at 12:02, Richard Hipp <d...@sqlite.org> wrote:
> On 12/28/17, jungle Boogie <jungleboog...@gmail.com> wrote:
>> Hi All,
>>
>> I cannot clone a fossil repo running on a reaspberry pi.
>> --fossil-debug was originally used but since then, multiple fossil
>> binaries have been built with it disabled.
>
> Sounds to me like you are still running the older binary that was
> built using --fossil-debug.  Are you 100% certain that you have
> installed the new one?  Have you rebooted the machine to make sure you
> killed off the old one?
>
>

I do believe the wrong binary in the wrong path was the issue. Thanks
for the fast response.

Thanks!
___
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] HTML instead of fossil sync protocol

[jungle Boogie]

>
> Any pointers are appreciated.
>
>

I created a brand new repo with zero commits and I was able to clone
it with fossil server running. So it looks like an issue with the repo
itself, perhaps enabling fossil debug on the binary caused an issue?


>
> --
> ---
> inum: 883510009027723
> sip: jungleboo...@sip2sip.info



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] HTML instead of fossil sync protocol

[jungle Boogie]

Hi All,

I cannot clone a fossil repo running on a reaspberry pi.
--fossil-debug was originally used but since then, multiple fossil
binaries have been built with it disabled.

>fossil clone http://10.7.0.82:8080 cpp_projects.f
Round-trips: 1   Artifacts sent: 0  received: 0
server replies with HTML instead of fossil sync protocol:
cfile bc64ba9aec57c8dc726c7d920b317f2a06080276030b7b2a31339ee822261b0c 161 148

Round-trips: 2   Artifacts sent: 0  received: 11
server replies with HTML instead of fossil sync protocol:
config /reportfmt 579
2440587.5
Round-trips: 2   Artifacts sent: 0  received: 14
Clone done, sent: 513  received: 3344  ip: 10.7.0.82

This is fossil version 2.5 [1fae64de38] 2017-12-28 17:20:14 UTC
for the pi and the windows computer.


fossil 2.4 was downloaded from fossil-scm.org
fossil 2.4 was used to clone trunk
fossil from trunk was compiled --with-openssl=none

In the /setup_ulist page, I do see this:
sort w/o index in [SELECT uid, login, cap, info,
date(mtime,'unixepoch'), lower(login) AS sortkey, CASE WHEN info LIKE
'%expires 20%' THEN substr(info,instr(lower(info),'expires')+8,10) END
AS exp,atime FROM user LEFT JOIN lastAccess ON login=uname WHERE login
NOT IN ('anonymous','nobody','developer','reader') ORDER BY sortkey]

The repo has been rebuilt with the fossil binary disabled for
debugging, but this is still present.

Any pointers are appreciated.



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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 hack: quickly finding the first checkin via the web UI

[Jungle Boogie]

On Thu 21 Dec 2017 11:46 AM, Dominique Devienne wrote:
> 
> Nice tip.
> 
> Since I've seen DRH ask about available features on GitHub since I started
> lurking on this list recently,
> I'd mention the graphs the latter provide which I find useful, in the
> Insights tab of a project.
> The Code Frequency [1] one seems to be since inception, while the Commit
> [2] one is year-to-date.
> I also like the per-user "map" that shows activity of a GitHub user, across
> all projects, but there's
> also a per-project page with contributor graphs [3], also since inception
> it seems.
> 
> I find such graphs useful myself, FWIW. --DD
> 
> [1] https://github.com/rqlite/rqlite/graphs/code-frequency
> [2] https://github.com/rqlite/rqlite/graphs/commit-activity
> [3] https://github.com/rqlite/rqlite/graphs/contributors

Are you familiar with these:
http://www4.fossil-scm.org/stat
http://www4.fossil-scm.org/reports
http://www4.fossil-scm.org/reports?type=ci=bymonth=drh
http://www4.fossil-scm.org/reports?type=g=byfile=drh

Play around with these and other features. My guess is you'll find out
how much is reported. There could be a chance to add more and/or improve
on what is in place, however.

P.s. I'm using www4 because of DRH's request on the other thread.
___
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

[Jungle Boogie]

On Fri 22 Dec 2017  6:13 AM, Warren Young wrote:
> On Dec 21, 2017, at 4:57 PM, jungle Boogie <jungleboog...@gmail.com> wrote:
> > 
> > On 21 December 2017 at 15:03, Warren Young <war...@etr-usa.com> wrote:
> >> On Dec 21, 2017, at 2:58 PM, jungle Boogie <jungleboog...@gmail.com> wrote:
> >>> perhaps left of the username.
> >> 
> >> I think right, simply because it’s currently ordered most-clicked to 
> >> least-clicked, more or less.
> >> 
> > 
> > In between the username and date/time or right of date/time?
> 
> I was thinking far right, after the tag in the Modern view.  I sometimes 
> click on the checkin ID, I almost never click on the user name, and when I 
> click on a tag, it’s generally from some other view than the Timeline.  

Oh, I was thinking in the overview section of a commit, left of the
username:
http://www4.fossil-scm.org/info/8a53d4016ee960ab

Shift what's there down a bit to have the icon line up with the other
records above and below.

With what you said, I do think that placement is nice.
___
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

[jungle Boogie]

On 21 December 2017 at 15:03, Warren Young <war...@etr-usa.com> wrote:
> On Dec 21, 2017, at 2:58 PM, jungle Boogie <jungleboog...@gmail.com> wrote:
>>
>> 3) Small green lock, like you see in your browser for https
>> 2) Unlocked & red
>> 1) Locked, but grey
>
> That’s going to make the red-green color blind unhappy:
>
>
> https://en.wikipedia.org/wiki/Color_blindness#Red%E2%80%93green_color_blindness
>

You're right, I wasn't taking that into account.

>>>  And where would they be placed?  Beside the username?
>
> Works for me.
>
>> I think that's a good starting point, perhaps left of the username.
>
> I think right, simply because it’s currently ordered most-clicked to 
> least-clicked, more or less.
>

In between the username and date/time or right of date/time?

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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

[jungle Boogie]

On 21 December 2017 at 14:16, Richard Hipp <d...@sqlite.org> wrote:
> On 12/21/17, jungle Boogie <jungleboog...@gmail.com> 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.
>

Gotcha. I was assuming this was already implemented and I missed a
feature like this.

I like the idea of the repo keeping track of the keys, rather than a
key server _in this instance_. Fossil, while distributed, can work
where's there's no internet. If that's the case, keys wouldn't be
verified.

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

I like SDR's response!

> --
> D. Richard Hipp
> d...@sqlite.org


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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

[jungle Boogie]

On 21 December 2017 at 13:46, Richard Hipp  wrote:
> Suppose Fossil were enhanced to show an icon beside each check-in that
> indicated whether or not the check-in had been signed and whether the
> signature had been verified.  Thus, there are three states:  (1)
> unsigned, (2) signed but unverified, and (3) signed and verified.
> What would the three icons for these three states look like?  And
> where would they be placed?  Beside the username?

3) Small green lock, like you see in your browser for https
2) Unlocked & red
1) Locked, but grey

I would think hovering over the icon would show some text, such as
"This commit is signed & verified".

>   And where would they be placed?  Beside the username?

I think that's a good starting point, perhaps left of the username.

How are the signatures verified?


> --
> D. Richard Hipp
> d...@sqlite.org



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Cross-link tech notes to commits

[jungle Boogie]

On 20 December 2017 at 13:13, jungle Boogie <jungleboog...@gmail.com> wrote:
> Hi All,
>
> I know a tech note entry in the timeline can be linked to a specific commit.
> For example:
> http://fossil-scm.org/index.html/timeline?ss=m=200=e=0
>
> See the top commit by AG.
>
> Can a commit message contain the [ID] of a tech note and have it linked to it?
>

At this point in reading the documentation, I don't think this is the
case. Technotes commit messages can contain the [ID] of a check-in,
though.

https://www.fossil-scm.org/index.html/doc/trunk/www/event.wiki

Is this because of this?
Because technotes are considered a special kind of wiki, users must have
permission to read wiki in order read technotes.

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

[fossil-users] Cross-link tech notes to commits

[jungle Boogie]

Hi All,

I know a tech note entry in the timeline can be linked to a specific commit.
For example:
http://fossil-scm.org/index.html/timeline?ss=m=200=e=0

See the top commit by AG.

Can a commit message contain the [ID] of a tech note and have it linked to it?

Otherwise, how do you list all tech notes and/or cross-link tech notes
and commits?
AFAIK, the only way to find tech notes is to change the drop down box
from the timeline and see what it lists.

I don't see tech notes in the site map: http://fossil-scm.org/index.html/sitemap

Thanks!

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Automatic update when changing type on timeline?

[jungle Boogie]

On 19 December 2017 at 13:59, Florian Balmer  wrote:
> No, my patches were about intercepting the enter key from text input
> elements to submit the form and update the view.
>
> In my tests, I found that the "onchange" handler worked fine for
> drop-down lists, so you may have detected a new problem.
>

I think I had a bad install of fossil. Going to previous versions and
back to the trunk, the drop down box does change the timeline.

Sorry for the noise...


> --Florian
___
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] Automatic update when changing type on timeline?

[jungle Boogie]

On 19 December 2017 at 13:16, Florian Balmer  wrote:
> As the form has no "submit" element, it works differently in different
> web browsers. I've sent a set of patches directly to Richard Hipp to
> make use of the "onkeydown" ("onkeyup" in the initial version) instead
> of the "onchange" handler for text input elements [0], as in some web
> browsers, the "onchange" handler is only fired after the control lost
> focus. The "onchange" handler usually works better for drop-down
> lists, but obviously not in all cases, and I'm not sure what's the
> solution here.
>

Thanks for the link to the patch.

I find this really peculiar, because:
a) the fossil-scm.org repo functions as I expect on Chrome and Firefox
and I see the URL show this: ?ss=m=100=e=0
b) Using the same version of the browser, my repo doesn't show these
changes or any changes to the URL

So how does this function on the fossil-scm repo? Is your patch being
applied for each build of fossil?


> [0] 
> https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg25061.html
>
> --Florian

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Automatic update when changing type on timeline?

[jungle Boogie]

Hi All,

When I change from Check-ins to tech notes on my personal repo,
there's not an automatic display of the results. I have to enter into
something like the "max" box and press enter to change the tech notes.
I noticed on the fossil-scm repo, there's some update to the page and
it displays the tech notes.

Does something need to be enabled in the admin section for this to happen?

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Please suggest built-in skin fixes and improvements

[jungle boogie]

Thus said Richard Kipp on Sun, 17 Dec 2017 21:11:30 -0500

You can now see the canonical Fossil self-hosting repository using any
of the built-in skins by visiting links from this page:
https://www.fossil-scm.org/skins/


Thanks for the link, this is a very handy way to see all the skins.

This is primarily to Zakero, who's very responsive with my suggestions 
on the cool skin.


https://www.fossil-scm.org/skins/xekri/info/a6c5a4620a5388fd

In the context section of the link above, there's no highlighting around 
the commit text.


This is what it looks like on the default skin:

http://www.fossil-scm.org/index.html/info/a6c5a4620a5388fd

No background color here:

https://www.fossil-scm.org/skins/xekri/timeline?c=2017-12-18+02:06:40

vs.

http://www.fossil-scm.org/index.html/timeline?c=2017-12-18+02:06:40


I'd personally say the background color of the timeline needs a little 
more contrast:


https://www.fossil-scm.org/skins/xekri/timeline

I know drh just committed the css to implement a background color, so a 
more noticeable color is only needed, IMO.


Thanks!

___
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] tangent vs. wyoung on recent commti

[jungle boogie]

Thus said Warren Young on Mon, 18 Dec 2017 17:55:16 -0700

I want to restrict this thread to the technical issues: preventing 
wyoung/tangent confusions, or helping Donny trust Alice, or or giving Donny the 
tools to *not* trust Alice just because Bob trusts Alice.


I can't remember the repo drh mentioned, but he signs commits with a GPG 
key, maybe Th1 repo?. W.r.t. signing commits, I think this information 
is only shown in the  manifest link:

https://www.fossil-scm.org/skins/original/artifact/a6c5a4620a5388fd

I think I asked something to the effect of, can this information be 
shown in the overview section of a commit, but since that hasn't really 
been asked for, it was assumed it wasn't really a needed feature.


And honestly, it would have only provided some assurance if you had 
signed the commit with a gpg key.


So if you committed something as drh with an improved overview section 
showing gpg keys, would this has prevented confusion? Would we have 
easily seen wyoung attempted to commit as drh, because of a missing gpg 
key? I don't even know what happens if the drh has gpg keys setup and 
wyoung attempts a commit. Would the commit work and not be signed?



___
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] tangent vs. wyoung on recent commti

[jungle Boogie]

On 14 December 2017 at 10:07, Richard Hipp <d...@sqlite.org> wrote:
> On 12/14/17, jungle Boogie <jungleboog...@gmail.com> wrote:
>> Hi All,
>>
>> This commit caught my eye:
>> http://fossil-scm.org/index.html/info/ec059849f5c73a43
>>
>> User & Date:wyoung on 2017-12-13 21:37:20
>> Original User & Date:tangent on 2017-12-13 21:37:20
>>
>> So Warren edited a file at the same exact time as tangent?
>>
>
> No.  The commit was originally by a user named "tangent" at the time
> shown.  Then a tag was added
> (http://fossil-scm.org/index.html/info/80f1e8a521518104) that changed
> the username to "wyoung".
>
> I'm guessing that "tangent" is some local username on Warren's
> desktop.  After he committed, he noticed that the commit picked up the
> wrong username and so he changed it to his "public" username "wyoung".
> I don't have any issues with this.  In fact, I think it was the right
> thing to do.

Ah, that's probably what it is. I don't see a notation of an edit. Am
I missing that, or are username changes no recorded?

> --
> D. Richard Hipp
> d...@sqlite.org


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] tangent vs. wyoung on recent commti

[jungle Boogie]

Hi All,

This commit caught my eye:
http://fossil-scm.org/index.html/info/ec059849f5c73a43

User & Date:wyoung on 2017-12-13 21:37:20
Original User & Date:tangent on 2017-12-13 21:37:20

So Warren edited a file at the same exact time as tangent?

Clicking on tangent, I see this:
http://fossil-scm.org/index.html/timeline?c=2017-12-13+21:37:20=tangent

But those both show Warren's name.

I don't mean to call out you, Warren, directly and I certainly am not
pointing a proverbial finger at you.

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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 rm --hard dir1

[jungle Boogie]

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

> I’d feel differently if Fossil owned the directories, but it doesn’t.  
> They’re mine; leave them alone!

Yes, I agree. I think this topic has been raised here in the past,
although that was about removing files. Still, If I created the
directory, I don't want fossil to remove it (even though it would save
me extra typing).
https://en.wikipedia.org/wiki/Principle_of_least_astonishment

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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

[jungle Boogie]

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.

>
> In fact, GitHub can be a bit overeager about cross-linking everything.  Just 
> write “#1” in some bit of Markdown somewhere, and you’ll get linked to issue 
> #1, even if you didn’t mean to refer to it.
>

Agreeded.

> Git wouldn’t, of course, since it doesn’t have a ticket tracker. :)  
> Presumably there are Git + bug tracker lash-ups that will do this 
> bidirectional linking.
>

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Lots of web interface changes

[jungle Boogie]

On 6 December 2017 at 11:22, Richard Hipp  wrote:
> There have been lots of changes (hopefully, "improvements") to the web
> interface of Fossil over the past few days.  If you have not be
> following the developments, I encourage you to visit a few of the main
> sites running the latest code and let me know what you think.  Your
> suggestions and comments are very important.
>
> If you can, please download the latest trunk sources, compile on your
> own systems, and run the tip of trunk there.  Let me know if you run
> into any problems.
>
> If you want to contribute your CSS skills for better styling, that
> would be really great.  Let me know and I will set you up.
>
> Here are some links to try:
>
>  https://www.fossil-scm.org/fossil/timeline

For a comparison:
http://www2.fossil-scm.org/fossil/timeline

I really do like the tags and properties section of a check-in not
being displayed by default. And the reorganization of what's displayed
in the Overview section.

Nice job and thanks for the constant improvements.
___
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] Windows make fail: mkcss.c

[jungle Boogie]

On 30 November 2017 at 10:55, Warren Young <war...@etr-usa.com> wrote:
> On Nov 30, 2017, at 8:16 AM, jungle Boogie <jungleboog...@gmail.com> wrote:
>>
>>mkcss.exe ..\src\default_css.txt default_css.h
>> ..\src\default_css.txt:1: syntax error
>
> Has src/default_css.txt changed?  Try reverting it.
>

Thanks for the pointer! There as an issue with the default_css.txt
file, it has some merge issue and create the _merge _original and had
extra info in the real file. I had to delete it and copy in a new
default_css.txt file.

Fossil successfully built with Visual Studio 2017!
___
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] diff coloring missing?

[jungle Boogie]

On 30 November 2017 at 08:07, Marc Simpson  wrote:
> Re: CSS issues: I think the default skin would be a bit more readable
> with 1 or 2 pixels of space between these newly added commit
> bubbles/boxes.
>
> (Adjacency currently yields a doubly thick shared line.)

Comparing to the sqlite skin, I agree with this improvement:
https://www.sqlite.org/src/timeline
vs.
https://www.fossil-scm.org/fossil/timeline



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Windows make fail: mkcss.c

[jungle Boogie]

On 30 November 2017 at 08:43, Richard Hipp <d...@sqlite.org> wrote:
> On 11/30/17, jungle Boogie <jungleboog...@gmail.com> wrote:
>> On 30 November 2017 at 07:46, Richard Hipp <d...@sqlite.org> wrote:
>>> On 11/30/17, jungle Boogie <jungleboog...@gmail.com> wrote:
>>>>
>>>> Still failing with latest changes and nmake /f Makefile.msc and with
>>>> buildmsvc.bat:
>>>>
>>>
>>> Sorry you are having trouble.  It works for me.  Please suggest a fix...
>>
>> Are you using Microsoft Visual Studio to compile? If so, which version?
>
> MSVC.  I do not know how to determine what version.
>

When I open up the Developer Command Prompt, I see this:

Visual Studio 2017 Developer Command Prompt v15.0.26730.16



> --
> D. Richard Hipp
> d...@sqlite.org

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Windows make fail: mkcss.c

[jungle Boogie]

On 30 November 2017 at 07:46, Richard Hipp <d...@sqlite.org> wrote:
> On 11/30/17, jungle Boogie <jungleboog...@gmail.com> wrote:
>>
>> Still failing with latest changes and nmake /f Makefile.msc and with
>> buildmsvc.bat:
>>
>
> Sorry you are having trouble.  It works for me.  Please suggest a fix...

Are you using Microsoft Visual Studio to compile? If so, which version?

> --
> D. Richard Hipp
> d...@sqlite.org

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] diff coloring missing?

[jungle Boogie]

On 30 November 2017 at 06:36, Martin Gagnon  wrote:
> Do ctrl-f5 to force a full refresh. CSS is cached.
>

Yes, now it back!
___
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] Windows make fail: mkcss.c

[jungle Boogie]

On 29 November 2017 at 15:35, jungle Boogie <jungleboog...@gmail.com> wrote:
> On 29 November 2017 at 15:06, jungle Boogie <jungleboog...@gmail.com> wrote:
>> Hi All,
>>
>> First time to compile Fossil on Windows in awhile, so this might me a
>> fault of my own doing.
>>
>>  ..\src\../skins/original/header.txt
>> ..\src\../skins/plain_gray/css.txt  ..\src\../skins/plain_gr
>> ../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
>> ..\src\../skins/rounded1/details
>> nded1/header.txt  ..\src\../skins/xekri/css.txt
>> ..\src\../skins/xekri/details.txt  ..\src\../skin
>> iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
>> cl /nologo /MT /O2 ..\src\mkcss.c
>> mkcss.c
>> ..\src\mkcss.c(79): warning C4129: '%': unrecognized character escape 
>> sequence
>> mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
>> Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
>> NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
>> Stop.
>>
>
>
> nmake /f Makefile.msc clean
> nmake /f Makefile.msc I get this now:
>
> khaki/footer.txt  ..\src\../skins/khaki/header.txt
> ..\src\../skins/original/css.txt  ..\src\../skins/original/details.txt
>  ..\src\../skins/original/footer.txt
>  ..\src\../skins/original/header.txt
> ..\src\../skins/plain_gray/css.txt
> ..\src\../skins/plain_gray/details.txt
> ..\src\../skins/plain_gray/footer.txt  ..\src\
> ../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
> ..\src\../skins/rounded1/details.txt
> ..\src\../skins/rounded1/footer.txt  ..\src\../skins/rou
> nded1/header.txt  ..\src\../skins/xekri/css.txt
> ..\src\../skins/xekri/details.txt  ..\src\../skins/xekri/footer.txt
> ..\src\../skins/xekri/header.txt  ..\src\d
> iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
> mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
> Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
> NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
> Stop.

Still failing with latest changes and nmake /f Makefile.msc and with
buildmsvc.bat:

mkbuiltin.exe --prefix ..\src/ ..\src\../skins/aht/details.txt
 ..\src\../skins/black_and_white/css.txt
..\src\../skins/black_and_white/details.txt  ..
\src\../skins/black_and_white/footer.txt
..\src\../skins/black_and_white/header.txt
..\src\../skins/blitz/css.txt  ..\src\../skins/blitz/details.txt
..\src\.
./skins/blitz/footer.txt  ..\src\../skins/blitz/header.txt
..\src\../skins/blitz/ticket.txt
..\src\../skins/blitz_no_logo/css.txt  ..\src\../skins/blitz_no_lo
go/details.txt  ..\src\../skins/blitz_no_logo/footer.txt
..\src\../skins/blitz_no_logo/header.txt
..\src\../skins/blitz_no_logo/ticket.txt  ..\src\../skins/bo
otstrap/css.txt  ..\src\../skins/bootstrap/details.txt
..\src\../skins/bootstrap/footer.txt
..\src\../skins/bootstrap/header.txt  ..\src\../skins/default/css.
txt  ..\src\../skins/default/details.txt
..\src\../skins/default/footer.txt  ..\src\../skins/default/header.txt
 ..\src\../skins/eagle/css.txt  ..\src\../skins
/eagle/details.txt  ..\src\../skins/eagle/footer.txt
..\src\../skins/eagle/header.txt  ..\src\../skins/enhanced1/css.txt
..\src\../skins/enhanced1/details.txt
  ..\src\../skins/enhanced1/footer.txt
..\src\../skins/enhanced1/header.txt  ..\src\../skins/khaki/css.txt
..\src\../skins/khaki/details.txt  ..\src\../skins/
khaki/footer.txt  ..\src\../skins/khaki/header.txt
..\src\../skins/original/css.txt  ..\src\../skins/original/details.txt
 ..\src\../skins/original/footer.txt
 ..\src\../skins/original/header.txt
..\src\../skins/plain_gray/css.txt
..\src\../skins/plain_gray/details.txt
..\src\../skins/plain_gray/footer.txt  ..\src\
../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
..\src\../skins/rounded1/details.txt
..\src\../skins/rounded1/footer.txt  ..\src\../skins/rou
nded1/header.txt  ..\src\../skins/xekri/css.txt
..\src\../skins/xekri/details.txt  ..\src\../skins/xekri/footer.txt
..\src\../skins/xekri/header.txt  ..\src\d
iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
cl /nologo /MT /O2 ..\src\mkcss.c
mkcss.c
mkcss.exe ..\src\default_css.txt default_css.h
..\src\default_css.txt:1: syntax error
NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
Stop.

Build failure, errors were encountered.



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] diff coloring missing?

[jungle Boogie]

On Nov 30, 2017 3:35 AM, "Richard Hipp" <d...@sqlite.org> wrote:
>
> On 11/30/17, jungle Boogie <jungleboog...@gmail.com> wrote:
> >>
> >> In previous builds, this commit would certainly have a number of green
> >> lines, but that's not the case anymore.
> >
> > bisect complete
> >   4 BAD 2017-11-29 19:18:45 5c9c51be5f033de2 CURRENT
> >   3 GOOD2017-11-29 16:20:29 f9fc914eaef2c9e7
> >   2 GOOD2017-11-29 16:06:09 5beb3614960f2c3e
> >   1 GOOD2017-11-29 14:05:43 c94f6085489effe6
>
> Thanks for the bisect.  Should be working again, now.  Let me know if
> you spot any other CSS issues.
>
Hmmm, I still don't see it working on the website, and it looks like you're
running the latest code. I'll check more closely if my bisect was wrong.

> --
> 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] diff coloring missing?

[jungle Boogie]

On Nov 29, 2017 9:29 PM, "Jungle Boogie" <jungleboog...@gmail.com> wrote:
>
> Hi All,
>
> I don't think this is just an issue with my browser...
>
> https://www.fossil-scm.org/index.html/info/c94f6085489effe6
>
> In previous builds, this commit would certainly have a number of green
> lines, but that's not the case anymore.
>
> Same with the unified diff version, too:
> https://www.fossil-scm.org/index.html/vinfo/c94f6085489effe6?sbs=0
>
> What's happened?

bisect complete
  4 BAD 2017-11-29 19:18:45 5c9c51be5f033de2 CURRENT
  3 GOOD2017-11-29 16:20:29 f9fc914eaef2c9e7
  2 GOOD2017-11-29 16:06:09 5beb3614960f2c3e
  1 GOOD2017-11-29 14:05:43 c94f6085489effe6

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

[fossil-users] diff coloring missing?

[Jungle Boogie]

Hi All,

I don't think this is just an issue with my browser...

https://www.fossil-scm.org/index.html/info/c94f6085489effe6

In previous builds, this commit would certainly have a number of green
lines, but that's not the case anymore.

Same with the unified diff version, too:
https://www.fossil-scm.org/index.html/vinfo/c94f6085489effe6?sbs=0

What's happened?

Thanks!
___
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] Trolling GitHub for ideas

[Jungle Boogie]

On Sat 25 Nov 2017  9:17 AM, Richard Hipp wrote:
> The SQLite project is mirrored on GitHub (not by me).  This mirror
> provides a good opportunity to compare the interfaces of GitHub and
> Fossil using the same underlying data.
> 
> https://sqlite.org/srcx/timeline?basic
> https://github.com/mackyle/sqlite/commits/master
> 
> Your suggestions for useful features found in GitHub but missing from
> Fossil, or for pages in GitHub that work especially well and that you
> would like to see replicated in Fossil, are greatly appreciated.

It would be nice if, when line numbers are enabled, for there to be a
link on the line number and for that to highlight the line for an easy
way to share links.

https://github.com/mackyle/sqlite/blob/master/src/delete.c#L83

Notice all the line numbers left of the code are links, allowing an easy
way to highlight it.

It's possible to highlight lines (or multiple lines) in fossil, but you
need to manually edit the URL:
https://www.fossil-scm.org/index.html/artifact?ln=45-52=24bd6b806af1782c

It's nice that highlighting is possible, but it's not obvious how to do
it.
___
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] Windows make fail: mkcss.c

[jungle Boogie]

On 29 November 2017 at 15:06, jungle Boogie <jungleboog...@gmail.com> wrote:
> Hi All,
>
> First time to compile Fossil on Windows in awhile, so this might me a
> fault of my own doing.
>
>  ..\src\../skins/original/header.txt
> ..\src\../skins/plain_gray/css.txt  ..\src\../skins/plain_gr
> ../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
> ..\src\../skins/rounded1/details
> nded1/header.txt  ..\src\../skins/xekri/css.txt
> ..\src\../skins/xekri/details.txt  ..\src\../skin
> iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
> cl /nologo /MT /O2 ..\src\mkcss.c
> mkcss.c
> ..\src\mkcss.c(79): warning C4129: '%': unrecognized character escape sequence
> mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
> Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
> NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
> Stop.
>


nmake /f Makefile.msc clean
nmake /f Makefile.msc I get this now:

khaki/footer.txt  ..\src\../skins/khaki/header.txt
..\src\../skins/original/css.txt  ..\src\../skins/original/details.txt
 ..\src\../skins/original/footer.txt
 ..\src\../skins/original/header.txt
..\src\../skins/plain_gray/css.txt
..\src\../skins/plain_gray/details.txt
..\src\../skins/plain_gray/footer.txt  ..\src\
../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
..\src\../skins/rounded1/details.txt
..\src\../skins/rounded1/footer.txt  ..\src\../skins/rou
nded1/header.txt  ..\src\../skins/xekri/css.txt
..\src\../skins/xekri/details.txt  ..\src\../skins/xekri/footer.txt
..\src\../skins/xekri/header.txt  ..\src\d
iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
Stop.
___
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] Windows make fail: mkcss.c

[jungle Boogie]

On 29 November 2017 at 15:06, jungle Boogie <jungleboog...@gmail.com> wrote:
> Hi All,
>
> First time to compile Fossil on Windows in awhile, so this might me a
> fault of my own doing.

I'm using Microsoft Visual Studio 2017, by the way.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Windows make fail: mkcss.c

[jungle Boogie]

Hi All,

First time to compile Fossil on Windows in awhile, so this might me a
fault of my own doing.

 ..\src\../skins/original/header.txt
..\src\../skins/plain_gray/css.txt  ..\src\../skins/plain_gr
../skins/plain_gray/header.txt  ..\src\../skins/rounded1/css.txt
..\src\../skins/rounded1/details
nded1/header.txt  ..\src\../skins/xekri/css.txt
..\src\../skins/xekri/details.txt  ..\src\../skin
iff.tcl  ..\src\markdown.md  ..\src\wiki.wiki > builtin_data.h
cl /nologo /MT /O2 ..\src\mkcss.c
mkcss.c
..\src\mkcss.c(79): warning C4129: '%': unrecognized character escape sequence
mkcss.exe ..\src\default_css.txt ..\src\default_css.txt default_css.h
Usage: .\mkcss.exe INPUTFILE OUTPUTFILE
NMAKE : fatal error U1077: '.\mkcss.exe' : return code '0x1'
Stop.

Any hints on correcting this?

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] A-B comparison of proposed timeline changes

[Jungle Boogie]

On Tue 28 Nov 2017 10:36 PM, Andy Bradford wrote:
> Thus said Richard Hipp on Mon, 27 Nov 2017 17:41:55 -0500:
> 
> > I   have  installed   the   new  look   (temporarily   at  least)   on
> > https://www.fossil-scm.org/fossil so  that we can  live with it  for a
> > while to see how we like it.
> 
> I  tend to  prefer  having more  information to  less,  but the  biggest
> drawback to hiding everything is that  now every commit message seems to
> blend together with all the adjacent commits in the same branch. Before,
> we at least  had all the commit  hashes at the beginning  of each commit
> message which  served as a  natural divider between commits;  also there
> were  some  links  that  were underlined  (tags,  branches,  and  users)
> providing  some level  of distinction  between them,  but now  that this
> information  is hidden,  all the  comments  from a  single branch  blend
> together making it difficult to make sense of it all.
> 

yes, in this view without the spacing or commit IDs, I agree. Would it
look better if the diff buttons were moved over towards the commits, or
would that get too ugly with multiple branches?

When seen in this view, the commits are a easier to follow:
https://www.fossil-scm.org/fossil/timeline?ymd=2017-11-28

The commit IDs are hidden away so we don't have to skip over them with
our eyes, but we're able to expose it if we want by clicking on the
commit.

> Just my $0.02.
> 
> Andy
> --
> TAI64 timestamp: 40005a1e4794
___
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] A-B comparison of proposed timeline changes

[Jungle Boogie]

On Tue 28 Nov 2017 10:40 PM, Andy Bradford wrote:
> Thus said Richard Hipp on Mon, 27 Nov 2017 17:41:55 -0500:
> 
> > The big  down-side is  that less  information is  visible on  a single
> > screen now, so you have to scroll more. But that seems to be the trend
> > with websites these days
> 
> There's another extremely annoying downside  to this as well---I like to
> double-click or triple-click to highlight  words in commit logs, and now
> that  behavior  is  extremely  unpleasant,  if  not  outright  hindered.
> Clicking  anywhere in  the  commit message,  including double-clicks  to
> highlight words makes copy/paste not fun.
> 

In which mode? I think this is only an issue in the compact mode, right?

> More $0.02.
> 
> Andy
> --
> TAI64 timestamp: 40005a1e488b
___
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] Trolling GitHub for ideas

[Jungle Boogie]

On Sat 25 Nov 2017  9:17 AM, Richard Hipp wrote:
> The SQLite project is mirrored on GitHub (not by me).  This mirror
> provides a good opportunity to compare the interfaces of GitHub and
> Fossil using the same underlying data.
> 
> https://sqlite.org/srcx/timeline?basic
> https://github.com/mackyle/sqlite/commits/master
> 
> Your suggestions for useful features found in GitHub but missing from
> Fossil, or for pages in GitHub that work especially well and that you
> would like to see replicated in Fossil, are greatly appreciated.
> 

Often times I like to grab just a single file from someone's repo, i.e.
a .tmux.conf without needing to clone and/or download all their repo.
And I don't need to download the copy to the computer I'm on, but a
remote computer.

I find the file, click raw and see the contents in the browser:
https://raw.githubusercontent.com/mackyle/sqlite/master/src/shell.c.in
Then I can use fetch/ftp/wget/curl to grab the single file.

In Fossil, there is a 'Download' link, and this will actually download
the file locally, but not display in the browser.
https://sqlite.org/src/artifact/c441d7ddfbb8120c

I think there's ways to do show the file with fossil, but it's a little more
complicated, and there doesn't seem to be a button available on the
fossil link above.

tl;dr: Make it easier to show raw file contents on a webpage. Ideally,
the filename will be the suffix of the URL.:
https://sqlite.org/src/artifact/c441d7ddfbb8120c/shell.c.in

Thanks for the consideration!

Best,
j.b.





> -- 
> 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] A-B comparison of proposed timeline changes

[jungle Boogie]

On 27 November 2017 at 14:13, Warren Young  wrote:
> On Nov 24, 2017, at 7:35 AM, Richard Hipp  wrote:
>>
>> Which is better?
>>
>>  A:  https://www.fossil-scm.org/a/timeline
>>  B:  https://www.fossil-scm.org/b/timeline
>
> I prefer A because I don’t like having to dig for details.  Hiding details 
> isn’t the answer to clutter.  Drawing the eye to key details first is the 
> right path.
>
> Here is a few minutes spent with option A’s CSS:
>
> https://imgur.com/a/w0mGF
>
> Key changes:
>
> 1. More “air” around each comment line
> 2 Slight opacity drop and font size drop on details span to deemphasize it
> 3. Details span pushed off to the lower right to visually separate it from 
> the comment
> 4. Extra “air” around details span; ditto
> 5. Borders added to separate timeline elements more clearly
>


I like these changes! I definitely like the horizontal spacing around
the check-ins and the check-in details to be slightly below the single
line check-in information.

Can we see this implemented on a timeline c option?

Thanks for the work, Warren!

best,
j.b.
___
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] More timeline changes

[Jungle Boogie]

On Sat 25 Nov 2017  6:46 PM, Zakero wrote:
> To help make the ellipses more visible, you could put them in their own
>   and let the skin figure out what looks best.  Also, instead of
> using "...", what about "[+]"?
> 

Yes, I support this suggestion. Most sites I've seen that can expand/shrink
info usually wrap it with something like [+] [-] buttons.

> >
> > On Sat, Nov 25, 2017 at 5:51 PM, Marc Simpson  wrote:
> >
> >> One other (potential) problem: without the hash prefix, descriptions
> >> run together.
> >>
> >> Example: http://www.sqlite.org/src/timeline, 2017-11-24. The graph
> >> nodes are flushed to the left, so descriptions appear as:
> >>
> >>   Add the "^" syntax from fts3/4 to fts5. ...
> >>   Enhance the configure script to detect zLib. ...

Yes, this is a good point. Your eyes need to read all the way to the end
of the line with "fts5" and then to the beginning of the next line with
the timestamp to see these are two different check-ins.

> >>
> >>
> >> /M
___
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] A-B comparison of proposed timeline changes

[Jungle Boogie]

On Fri 24 Nov 2017  7:25 PM, sky5w...@gmail.com wrote:
> Wow, #5 is super clean and easy on the eyes!
> And #12 is interesting if I can see it with Per-Item Time Format = (off)?
> 
> Thanks for the changes!

#5 is nice, and especially with the easy option to switch back to
advanced. Perhaps the basic option can include the user as well, that
would probably be my only suggestion.

DRH, thank you for being so willing to listen to the user base and those
who have probably never touched fossil before (such as HN folks).
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Version bump post 2.4 release

[jungle boogie]

Hello All,

I think I've noticed this 'problem' before but I don't know what I did 
about it. It's really just a minor annoyance and not a bug.



$ fossil version
This is fossil version 2.4 [bf69c6enc9] 2017-11-04 14:56:23 UTC

But that hash is from this commit, which is post 2.4 release:
http://www.fossil-scm.org/index.html/info/bf69c6ebc998fe2c

My trunk version of sqlite3 contains the next version, 3.22.0:
$ sqlite3
SQLite version 3.22.0 2017-11-04 08:53:37

Why does fossil still think it's on 2.4? Things don't have to be 
corrected to make this right, just curious why it thinks I'm on version 2.4.


Thanks!
___
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] CI thinks check-in is empty

[jungle Boogie]

On 31 October 2017 at 17:18, Jacob MacDonald  wrote:
> That is indeed the issue. There are command line flags to get Code to behave
> the way you want, but I don't recall them off the top of my head. Try
> searching for how to use Code as Git's editor, and use the same command as
> Fossil's editor setting. That should do it.
>

Solved with the help of this stack overflow:
https://stackoverflow.com/questions/30024353/how-to-use-visual-studio-code-as-default-editor-for-git

fossil set editor "Code --wait"

>fossil set editor
editor   (local)  Code --wait

Thanks,
j.b.
___
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] CI thinks check-in is empty

[jungle Boogie]

Good call, Stephan.

Thanks for the input, Jacob. I'll take a look for the arguments to use.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] CI thinks check-in is empty

[jungle Boogie]

Hi All,

I would like this to be my editor on Windows:
"C:\Program Files\Microsoft VS Code\Code.exe"

I was able to set it up as my editor:
>fossil set editor
editor   (local)  "C:\Program Files\Microsoft VS Code\Code.exe"

I wanted to commit a change:
>fossil ci

This opened VS Code and generated a text file in my project directory.
I typed my message, saved and closed. Fossil had moved on long ago and
assumed my check-in was empty and asked if I wanted to proceed:

>fossil ci
Autosync:  http://localhost:8080
Round-trips: 1   Artifacts sent: 0  received: 0
Pull done, sent: 306  received: 772  ip: 127.0.0.1
"C:\Program Files\Microsoft VS Code\Code.exe" "./ci-comment-636BBE9D36FF.txt"

empty check-in comment.  continue (y/N)? n

Fossil opened VS Code in a couple seconds and I started typing my message.

Is it likely VS code is too slow for fossil before it thinks there's
an empty check-in?

What's an editor Widows folks use? I have gvim installed, so I can
switch to that familiar editor if you folks think VS Code is just a
bit too slow for fossil.

Thanks!

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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

[jungle Boogie]

On 14 September 2017 at 09:12, Johan Kuuse  wrote:
> On Thu, Sep 14, 2017 at 5:55 PM, Richard Hipp  wrote:
>> If you'd like to help promote Fossil to unwashed masses who are still
>> using Git, perhaps like or retweet
>> https://twitter.com/robmurrer/status/908080904781869056 :-)
>
> Working in a 115,000 employers 3G/4G/5G international software
> company, Git all over. (That's a lot of Git.)
> Does anyone who ever have used Fossil (and Git, to be able to compare)
> *not* promoted Fossil for unwashed colleagues?
> I do. ;-)
>

115,000 employees with your employer or 115,000 people using git at
your employer?

> BR,
> Johan
>
>
>
>>
>> --
>> 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] toc.tcl

[jungle Boogie]

On 20 August 2017 at 10:24, Andy Goth  wrote:
> On 08/18/17 07:38, Dewey Hylton wrote:
>>
>> I predict this to be the best email I receive today.
>>
>> My first thought was "This is like paid support!"
>> My second thought was "Wait ... paid support has *never* been this good
>> ..."
>>
>> Thanks for your work!
>
>
> Since you seem to be really interested, have one more improvement.  Now
> there's no need for an  marker.  The table of contents extends
> from  to the first blank line.  Aside from looking cleaner
> overall, this works around a Markdown rendering oddity which required me to
> put a blank line between the last line of the TOC list and the 
> line.
>
>
> https://chiselapp.com/user/andy/repository/brush/file/doc/toc.tcl
>


Any chance of using something like https://www.pastiebin.com to show the code?
chiselapp.com is offline, and it looks like that's been the case of a
few days now.
___
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] Help messages in add.c

[jungle Boogie]

On 15 July 2017 at 03:58, Johan Kuuse  wrote:
> On Fri, Jul 14, 2017 at 9:23 PM, Venkat Iyer  wrote:
>> Consider me old fashioned,  but the current behavior seems more in line with
>> traditional unix (read sysv) commands.
>
> I don't want to make this a big deal, but I don't agree that the
> commands behave the same way as traditional unix commands.
> Examples:
>


fossil ls

This will list all of the files of the repo if no path is specified.
Unix ls will only list files in that directory.

This is the documented behavior or fossil:
List all files in the current checkout.  If PATHS is included, only the
named files (or their children if directories) are shown.

https://www.fossil-scm.org/index.html/help?cmd=ls
___
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 move a check-in from a branch to another one?

[jungle Boogie]

On 14 July 2017 at 08:21, Richard Hipp <d...@sqlite.org> wrote:
> On 7/14/17, jungle Boogie <jungleboog...@gmail.com> wrote:
>>
>> The command to edit commits after they've been commited is amend:
>> https://www.fossil-scm.org/index.html/help?cmd=amend
>>
>> example:
>> fosisl amend abc123 --tag fossiliscool
>>
>>
>> As you see, that command allows you to edit quite a bit from the
>> command line after a commit happened.
>>
>
> But amend will not move a check-in to a different branch.  All amend
> can do is change tags.  Moving a check-in to a different branch
> fundamentally changes the check-in.

Ah, right you are!

>
> Reparenting won't work either.  Reparenting just changes the ancestors
> of the check-in.  It does not change the content of the check-in so
> that it contains the desired content from the other branch where it
> was suppose to occur in the first place.
>
> Cherrypicking the check-in over to the correct branch is the only way
> to do this.
>

All good points.

Sorry to have added confusion to this.

>
> --
> D. Richard Hipp
> d...@sqlite.org


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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 move a check-in from a branch to another one?

[jungle Boogie]

On 14 July 2017 at 03:21, Richard Hipp  wrote:
> On 7/14/17, Olivier R.  wrote:
>> So what is the recipe to move a check-in to another branch?
>
> I (the original author of Fossil) always use web-based UI for this.
> First run "fossil ui" to get the web interface going.  Then find the
> check-in you want to move and click on its link to get to the "/info"
> page.  There is an "Edit" option beside "Other Links:".  Click on the
> Edit option.  On the /ci_edit page, there is a check box "Make this
> check-in the start of a new branch named:".  Enter the name of the new
> branch and click on the box and press "Apply Changes".
>
> There is a way to do this from the command-line, but I never use it
> and so I don't remember what it is.

The command to edit commits after they've been commited is amend:
https://www.fossil-scm.org/index.html/help?cmd=amend

example:
fosisl amend abc123 --tag fossiliscool


As you see, that command allows you to edit quite a bit from the
command line after a commit happened.


> --
> D. Richard Hipp
> d...@sqlite.org


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Help messages in add.c

[jungle Boogie]

On 6 June 2017 at 06:50, Johan Kuuse  wrote:
> Hi,
>
> The following commands, executed without any arguments, are mute:
>
> f add
> f rm
> f delete
> f forget
>
> IMHO, they should show a help message instead.
>

Is it desired to not do anything with the command isn't followed by a
filename/argument?

> Best Regards,
> Johan
___
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] diff for browse.c

[jungle Boogie]

On 10 July 2017 at 16:56, Richard Hipp <d...@sqlite.org> wrote:
> On 7/10/17, jungle Boogie <jungleboog...@gmail.com> wrote:
>> Hi All,
>>
>> One very minor update to browse.c to add a comma:
>
> I don't think that comma is correct.  The most important comma rule I
> was taught in 8th grade was "if in doubt, leave it out".  And I don't
> see a compelling reason to include that comma.
>

Best commit message!
Reword the header to the /fileage page to avoid disputes of commas.
___
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 info on tag & directory: SQLITE_CANTOPEN

[jungle boogie]

On 07/11/2017 06:30 PM, Richard Hipp wrote:

On 7/11/17, jungle Boogie <jungleboog...@gmail.com> wrote:


I don't think the -v works:
https://www.fossil-scm.org/index.html/help?cmd=info



What were you expecting it to do?



Your commit is welcomed!
Just one minor nitpick here:
https://www.fossil-scm.org/index.html/help?cmd=info

I think you want to say:
If the argument is a repository name, then the --verbose option shows
the known

Sorry for the trouble!
___
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 info on tag & directory: SQLITE_CANTOPEN

[jungle boogie]

On 07/11/2017 06:30 PM, Richard Hipp wrote:

On 7/11/17, jungle Boogie <jungleboog...@gmail.com> wrote:


I don't think the -v works:
https://www.fossil-scm.org/index.html/help?cmd=info



What were you expecting it to do?



Well that's a good question.

With and without the -v seem to produce the same output.
I'd either expect: 'fossil info' to show less info or 'fossil info -v' 
to show more info than it currently does.


The help page says "Show extra information".

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