Re: [fossil-users] Checkin [a9578f7870] freezes Windows server

[Joe Mistachkin]

Richie Adler wrote:
> 
> Compiling checkin a9578f7870 in Windows 7 freezes the server; whatever
task is
> running, it never ends, and the timeline does not update, neither does the
> files list. 
> 

I'm unable to reproduce the issue here (also Windows 7).  Do you have any
further
details on how to see the problem?  Does it (eventually) stop after 120
seconds?

--
Joe Mistachkin

___
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] The legacy of FOSSIL_ENABLE_LEGACY_MV_RM

[Joe Mistachkin]

To help those that always wanted the —hard option behavior to be he default for 
their custom compiled binaries.

Sent from my iPhone

> On Jun 20, 2018, at 9:59 PM,  
>  wrote:
> 
> That makes sense, but what I'm saying is, why bother with the
> compile-time flag?
> 
> It seems desirabe to allow the user to configure this behavior with
> repository settings, rather than using a flag to determine if it is
> hard-coded or not.
> 
> Are there a lot of legacy scripts out there that are difficult to
> modify? Perhaps keeping the new behaviour (overridden with --soft) is
> worth it at this stage. 
> 
> On Wed, 20 Jun 2018 21:49:18 -0400
> Richard Hipp  wrote:
> 
>> It ought to be the case that the default action of "fossil rm" and
>> "fossil mv" is to actually change the filesystem, in addition to
>> changing the way files are stored in the repository.  But early
>> versions of Fossil did not behave that way.  They required you to do
>> it in two steps:
>> 
>> fossil rm abc.c
>> rm abc.c
>> 
>> We talked about fixing Fossil so that "fossil rm abc.c" actually
>> removed the file.  But the feeling was that would break too many
>> legacy scripts.  So the less desirable legacy behavior remains, to
>> this day.
>> 
>>> On 6/20/18, bytevolc...@safe-mail.net  wrote:
>>> Hello,
>>> 
>>> I am trying to understand the idea behind FOSSIL_ENABLE_LEGACY_MV_RM.
>>> 
>>> It has been around for a while, and it is the only compile-time flag that
>>> determines if a setting is hard-coded or if it is obtained from the
>>> repository config.
>>> 
>>> It appears that if this is not defined, the "mv" and "rm" commands will
>>> modify the file system under all circumstances.
>>> 
>>> Given the "--hard" option in these commands anyway, this seems superfluous.
>>> So what is the idea behind the FOSSIL_ENABLE_LEGACY_MV_RM flag?
>>> 
>> 
>> 
> 
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> 

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

Re: [fossil-users] Action-based automation and scripting

[Joe Mistachkin]

Damien Garwood wrote:
> 
> 1. TH1Hooks
> In the Fossil TH1 documentation, I can find nothing regarding hooks. I
also 
> can't seem to find anything regarding the sort of things I might want to
do 
> after a commit, such as email, writing to files etc. I'm assuming TH1
can't 
> do this automatically and you've got to do some hackery to get that to
work? 
> Especially if you want to send it to somewhere like Twitter like GitHub
can 
> do. 
> 

The following pages may be of help to you:

https://www.fossil-scm.org/fossil/doc/trunk/www/th1.md

https://www.fossil-scm.org/fossil/doc/trunk/www/th1-hooks.md

TH1, by itself, cannot do things like send mail, write files, etc.

However, Fossil can be compiled with "full" Tcl integration support using
something like the following:

./configure --with-tcl=1 and --with-tcl-private-stubs=1

Then, once the "tcl" setting is enabled on the target repository, you can
use
the [tclEval] command (and related commands) in TH1 to interact with full
Tcl,
which can do practically anything you would like.

--
Joe Mistachkin 

___
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] zStopperFile / main.c / win32_http_server

[Joe Mistachkin]

I added it.  It’s needed to make various server aspects of Fossil testable on 
Windows.

Sent from my iPhone


___
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

[Joe Mistachkin]

Richard Hipp wrote:
>
> "Verbose" mode now looks like legacy.
>

Thank you, much appreciated.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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

[Joe Mistachkin]

Richard Hipp wrote:
>
> Maybe "Verbose" should be modified to include the hash up front 
>

Yeah, something like that would be cool.  Also, having the "Leaf" indicator,
et al, up front as well (like before)?

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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

[Joe Mistachkin]

Richard Hipp wrote:
> 
> (1) You have a selection of styles:  Normal, Compact, Verbose,
> Columnar.  Each can be styled separately. 
> 

Pretty please, can we have a "Legacy" style that gives the old look?

I think not having the check-in at the front of the line is going to
be a huge pain for me to adapt to.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Building with Tcl?

[Joe Mistachkin]

Please try this:

./configure --with-tcl=1 --with-tcl-private-stubs=1
--with-th1-hooks=1

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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 as an app server?

[Joe Mistachkin]

If you compile Fossil with TH1 docs & hooks support and with Tcl integration
enabled (like I compile it), it makes quite a reasonable server for running
server-side scripts written in TH1/Tcl.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Bugs in file_wd_isdir()

[Joe Mistachkin]

Perhaps changing the exec-rel-paths setting might impact this?  Not sure 
without further research.

Sent from my iPhone
https://urn.to/r/mistachkin

> On Mar 21, 2017, at 12:50 PM, Reimer Behrends  wrote:
> 
> Richard Hipp wrote:
>> I wonder if you could provide a more concrete example of the problem,
>> perhaps in a the form of a "fossil test-file-environment" command that
>> gives an incorrect answer?
> 
> I'm afraid not. As I recall, the reason I ran into this originally was 
> because "fossil diff --checkin ..." blew up on my Mac in file_mkfolder() with 
> an "unable to create directory" error. The reason was that on macOS, /tmp is 
> a symlink to private/tmp; rather than resolving to /private/tmp, Fossil 
> resolved it to private/tmp (without a leading slash). The presence of the 
> bugs should be obvious from a code inspection, however.
> 
> Reproducing it can be a bit tricky, because "fossil diff --checkin ..." does 
> not always seem to trigger it, but providing a --command option does seem to 
> cause it fairly reliably for checkins other than the current one. Example:
> 
> [/tmp/fossil]$ ./fossil version
> This is fossil version 2.0 [1d407cff32] 2017-03-03 12:00:30 UTC
> [/tmp/fossil]$ ./fossil up version-2.0
> ---
> checkout: 1d407cff32978b6ed57138da36787d547ce6887d 2017-03-03 12:00:30 UTC
> tags: trunk, release, version-2.0
> comment:  Version 2.0 (user: drh)
> changes:  None. Already up-to-date
> [/tmp/fossil]$ ./fossil diff --checkin prev --command "diff"
> Index: src/shell.c
> ==
> unable to create directory /var
> 
> The problem is that after blob_read_link() is called, even if the result is a 
> relative path, it is directly passed to file_is_wdir() again without 
> appending it to the link's directory. This means that the code will 
> (inaccurately) try to use it relative to the current directory.
> 
> The infinite recursion occurs if there's an absolute link that links to 
> itself along the path, simply because file_wd_isdir() will call itself over 
> without having a way to terminate.
> 
> Also, the !db_allow_symlinks(1) check can prevent the code from even 
> following the /tmp -> private/tmp link in the first place, even though the 
> setting is meant only for working tree directories and files.
> 
>Reimer Behrends
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> 

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

Re: [fossil-users] Help with Fossil and Tcl integration

[Joe Mistachkin]

Perhaps they are "customizing" the Tcl library in some way that is 
fundamentally incompatible, e.g. changing some fundamental data type, like int 
to size_t?  Jan Nijtmans might know more about what the various Linux 
distributions are doing.

Sent from my iPhone
https://urn.to/r/mistachkin
___
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 with Fossil and Tcl integration

[Joe Mistachkin]

How was the Tcl library built?  Are you able to step through Fossil in gdb to 
see why tclInvoke is not getting added to the TH1 interpreter?

Sent from my iPhone
https://urn.to/r/mistachkin


___
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 with Fossil and Tcl integration

[Joe Mistachkin]

That's really odd.  I've run Tcl-enabled Fossil on multiple flavors of Linux, 
both statically and dynamically linked to Tcl and never seen this crash or 
failure.

It should be noted that simply using "fossil version --verbose" actually loads 
and uses Tcl from TH1 (and that appears to work on your machine?).

Sent from my iPhone
https://urn.to/r/mistachkin

> On Mar 16, 2017, at 9:29 PM, Ryan Dingman  wrote:
> 
> I’m having trouble with Fossil and Tcl integration. At a high level, I have 
> two main problems:
> 
> Problem 1. When I configure Fossil to build as a dynamically linked binary, 
> the build succeeds and loads the Tcl library. However, when I run a TH1 
> script that uses a command requiring Tcl integration (e.g. tclInvoke) it 
> fails.
> 
> Problem 2. When I configure Fossil to build as a statically linked binary, 
> the build either fails or the Fossil crashes when loading the Tcl library.
> 
> Here’s a summary of what I’ve tried on a machine running Ubuntu 16.04.
> 
> 1. I’ve successfully built Fossil with Tcl integration as a dynamically 
> linked binary using:
> 
> ./configure --json --with-tcl --with-tcl-stubs --with-tcl-private-stubs
> make
> 
> I can see that the Tcl library is getting loaded by running ‘fossil version 
> -v’ and getting the following output:
> 
>  Begin 'fossil version -v' output 
> This is fossil version 2.1 [4fa4c0218f] 2017-03-13 01:12:30 UTC
> Compiled on Mar 16 2017 17:33:43 using clang-3.8.0 (tags/RELEASE_380/final) 
> (64-bit)
> Schema version 2015-01-24
> zlib 1.2.8, loaded 1.2.8
> hardened-SHA1 by Marc Stevens and Dan Shumow
> SSL (OpenSSL 1.0.2g  1 Mar 2016)
> TCL (Tcl 8.6.0, loaded TH_OK: 8.6.5)
> USE_TCL_STUBS
> FOSSIL_ENABLE_TCL_PRIVATE_STUBS
> JSON (API 20120713)
> UNICODE_COMMAND_LINE
> FOSSIL_DYNAMIC_BUILD
> SQLite 3.18.0 2017-03-10 17:03:11 f8560c60d1
> SQLITE_ENABLE_DBSTAT_VTAB
> SQLITE_ENABLE_FTS3
> SQLITE_ENABLE_FTS3_PARENTHESIS
> SQLITE_ENABLE_FTS4
> SQLITE_ENABLE_FTS5
> SQLITE_ENABLE_JSON1
> SQLITE_LIKE_DOESNT_MATCH_BLOBS
> SQLITE_OMIT_DECLTYPE
> SQLITE_OMIT_DEPRECATED
> SQLITE_OMIT_LOAD_EXTENSION
> SQLITE_OMIT_PROGRESS_CALLBACK
> SQLITE_OMIT_SHARED_CACHE
> SQLITE_SYSTEM_MALLOC
> SQLITE_THREADSAFE=0
> SQLITE_USE_ALLOCA
>  End 'fossil version -v' output 
> 
> However, when I try to test a TH1 script that uses a command that requires 
> Tcl integration, it doesn’t work. For example, I tried this with the 
> following:
> 
> fossil test-th-source -th-trace ~/test.th1 
> Has TCL
> TCL Not Ready
> TH_ERROR: no such command:  tclInvoke
> 
> -- BEGIN TRACE LOG --
> th1-init 0x0 => 0x0
> th1-setup {} => TH_OK
> [hasfeature tcl] => 1
> [tclReady] => 0
> 
> --- END TRACE LOG ---
> 
> I’ve included test.th1 in case I’m doing something wrong there. I’ve also 
> tried the same script from the the Fossil UI page Admin -> TH1. I’ve verified 
> that Tcl is enabled with 'fossil settings tcl’ which gives the following 
> output:
> 
>  Begin 'fossil settings tcl’ output 
> tcl  (local)  1
> tcl-setup   
>  End 'fossil settings tcl’ output 
> 
> I’m not sure what I’m missing here. If anyone has guidance here, any help 
> would be appreciated. I’m happy to provide any relevant information that I 
> may be missing here.
> 
> 2. To build Fossil as a statically linked binary, I first tried just using 
> the Tcl stubs that come with Fossil.
> 
> ./configure --static --json --with-tcl --with-tcl-stubs 
> --with-tcl-private-stubs
> 
> After configuring Fossil in this way, the build succeeds. However, Fossil 
> crashes when loading the Tcl library. For example, Fossil crashes when I run:
> 
> ./fossil version -v
> Segmentation fault (core dumped)
> 
> I’ve attached a stack trace of the crash if that’s useful to anyone.
> 
> Next, I tried to build Tcl as a static library first and then build Fossil 
> using that library. I configured and built Tcl 8.6.6 from source with:
> 
> ./configure --disable-shared
> make
> sudo make install
> 
> Then, configure and build Fossil with:
> 
> ./configure --static --json --with-tcl=/usr/local
> make
> 
> The build fails during linking with the following error:
> 
> /usr/bin/ld: dynamic STT_GNU_IFUNC symbol `sin' with pointer equality in 
> `/usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.0/../../../x86_64-linux-gnu/libm.a(s_sin.o)'
>  can not be used when making an executable; recompile with -fPIE and relink 
> with -pie
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> src/main.mk:591: recipe for target 'fossil' failed
> make: *** [fossil] Error 1
> 
> Again, if any one has guidance on how to properly build Fossil with Tcl 
> integration as a statically linked binary, any help would be appreciated.
> 
> Thanks,
> 
> Ryan
> 
> 
> 
> 
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> 

Re: [fossil-users] Directory symlinks...

[Joe Mistachkin]

Martin Gagnon wrote:
>
> I'm not sure if this protection is necessary, but if it is, it doesn't
> get triggered if the symlink point directly to "../../dir3/other_ckout"
> since the "top of a checkout" check only happens for the recursive call.
> 

I believe this may be to protect against file system loops?

>
> I don't know if the top of a checkout *must* be skipped or not, but
> right now there's something inconsistent with this rule.  
> 

I think it's by design.  It does not appear to be directly related to
the symlinks issues.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Directory symlinks...

[Joe Mistachkin]

Martin Gagnon wrote:
> 
> Strange, "fossil add a_dir_symlink" doesn't works for the case #2 on my
> actual repository, but if I try to reproduce the problem on a brand new
> repo, everything works.. Probably I hit a strange corner case. I will
> try to investigate a bit more.. 
> 

I've added the 'test-file-environment' command to Fossil to help with
figuring this stuff out.  Also, it has an --open-config option which
is useful.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Directory symlinks...

[Joe Mistachkin]

Martin Gagnon wrote:
>
> But if I do:
>   $ fossil add a_dir_symlink/*
>
> It add the content.
>
> Actually, may be it was intended ?
>

The way it should work (on the branch) is:

1. With allowSymlinks ON, symlinks to both files and
   directories are always treated as "normal" content
   files.  In this case, the --no-dir-symlinks flag
   has no effect because they are already disabled.

2. With allowSymlinks OFF and WITHOUT the --no-dir-symlinks
   flag, symlinks to files refer to the linked file and
   symlinks to directories are traversed into.

3. With allowSymlinks OFF and WITH the --no-dir-symlinks
   flag, symlinks to files refer to the linked file and
   symlinks to directories are NOT traversed into.

Given the above, my local testing seems to confirm that it
works as intended, including the "add" command.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Directory symlinks...

[Joe Mistachkin]

Martin Gagnon wrote:
>
>   $ fossil add a_dir_symlink
> 
> Nothing happens... 
> 

It was a bit more complex than I thought, made a couple more changes.

Hopefully, it will work better now.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Directory symlinks...

[Joe Mistachkin]

Changes on the "symlinks" branch prevent directory symlinks
from being traversed into if the "allow-symlinks" setting is
enabled or the "--no-dir-symlinks" flag is specified.

Making this change work correctly also required removing the
forced override of the cached "allow-symlinks" setting from
the "clean" and "extras" command implementations.  This will
probably increase the need for thorough testing.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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 export handling of trunk differs from import

[Joe Mistachkin]

Roy Marples wrote:
> 
> fossil import --rename-master trunk
> fossil export --rename-trunk master 
> 

As a matter of my personal preferences and taste, I really like the
idea of NOT doing "magic branch renaming" by default and adding the
above new options.

What kind of backward compatibility issues might we face with those
changes?

--
Joe Mistachkin @ https://urn.to/r/mistachkin

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

Re: [fossil-users] Bug report: fossil clean follows symlinks

[Joe Mistachkin]

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

I've figured out the issue.  Can you confirm that the "noSymlinks"
branch corrects the issue you were seeing?

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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 1.37 segfault, web interface "Login" as nobody with "a" capabilities

[Joe Mistachkin]

Lonnie Abelbeck wrote:
>
> BTW, this also segfaults in Fossil 1.35, only discovered it by
> randomly clicking, testing 1.37. 
>

Thanks for the report.  The issue should now be fixed on trunk.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

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

Re: [fossil-users] Bug report: fossil clean follows symlinks

[Joe Mistachkin]

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

Out of curiosity, why are you using the "-x" option?

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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 crashes with PDFs!!!

[Joe Mistachkin]

Artur Shepilko wrote:
>
> The problem stems from db.c::db_database_slot() function that is
> called in the context of db.c::db_force_rollback(), as part of
> reporting the fossil db error (SQLITE_NOTADB) from db.c::db_err().
>

Thanks for the details.  This particular issue should now be fixed
on trunk.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] compile fossil with-tcl on openbsd

[Joe Mistachkin]

I recommend the following Tcl related arguments to ./configure:

--with-tcl=1 --with-tcl-private-stubs=1

Sent from my iPhone
https://urn.to/r/mistachkin

> On Jan 1, 2017, at 5:46 PM, jungle boogie  wrote:
> 
> Hi All,
> 
> Happy New year! Best wishes in 2017 for all of you.
> 
> I'm running openbsd -current and attempting to configure fossil from trunk to
> compile with --with-tcl=/usr/local/bin but I get this:
> 
> $ ./configure --with-tcl=/usr/local/bin/
> Host System...amd64-unknown-openbsd6.0
> Build System...amd64-unknown-openbsd6.0
> C compiler... cc -g -O2
> C++ compiler... c++ -g -O2
> Build C compiler...cc
> Checking for stdlib.h...ok
> Checking for uint32_t...ok
> Checking for uint16_t...ok
> Checking for int16_t...ok
> Checking for uint8_t...ok
> Checking for pread...ok
> Checking for tclsh...no
> Checking for zlib.h...ok
> Checking for inflateEnd in z...-lz
> Checking for ssl via pkg-config...ok
> HTTPS support enabled
> Error: Cannot find Tcl at /usr/local/bin/
> Try: 'configure --help' for options
> 
> The find-tclsh script finds it:
> $ sh autosetup/find-tclsh
> /usr/local/bin/tclsh8.6
> 
> Without specifying a directory:
> $ ./configure --with-tcl
> Host System...amd64-unknown-openbsd6.0
> Build System...amd64-unknown-openbsd6.0
> C compiler... cc -g -O2
> C++ compiler... c++ -g -O2
> Build C compiler...cc
> Checking for stdlib.h...ok
> Checking for uint32_t...ok
> Checking for uint16_t...ok
> Checking for int16_t...ok
> Checking for uint8_t...ok
> Checking for pread...ok
> Checking for tclsh...no
> Checking for zlib.h...ok
> Checking for inflateEnd in z...-lz
> Checking for ssl via pkg-config...ok
> HTTPS support enabled
> Error: Cannot find Tcl on your system
> Try: 'configure --help' for options
> 
> 
> I thought I had previously tclsh compiled with fossil, but I can't confirm 
> that
> and I don't recall 100%.
> 
> What's fossil looking for and how do I get it compiled with tcl?
> 
> Thanks!
> 
> If this matters, here's the config.log:
> $ cat config.log
> Invoked as: ./configure --with-tcl
> Failed: cc -g -O2 conftest__.c -o conftest__
> /tmp//cciPpc4x.o: In function `main':
> /home/jungle/fossil-repos/Fossil-e38d5e1c/conftest__.c:3: undefined reference 
> to `inflateEnd'
> collect2: ld returned 1 exit status
> child process exited abnormally
> 
> The failed code was:
> extern void inflateEnd(void);
> int main(void) {
> inflateEnd();
> return 0;
> }
> 
> 
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> 

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

Re: [fossil-users] Bug report: fossil settings/unset no longer supports"-R"

[Joe Mistachkin]

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

I see the logic in what you are saying; however, so far, I'm unable to
reproduce the error message on Windows or Unix when using set/unset with
the -R option.

What build configuration/options are you using for Fossil?

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] OpenSSL in the source tree

[Joe Mistachkin]

Adam Jensen wrote:
>
> But that results in:
> ---
> Checking for ssl in source tree...no
> Error: OpenSSL not found. Consider --with-openssl=none to disable HTTPS
> support
> --- 
> 

I think using OpenSSL 1.1 will only work on the "openssl-1.1.0" branch.

Here are the commands I generally use to get things all working in the
source tree:

cd compat/zlib && ./configure && make
cd ..
wget -4 https://www.openssl.org/source/openssl-1.0.2j.tar.gz
tar -zxvf openssl-1.0.2j.tar.gz
mv openssl-1.0.2j openssl
cd openssl
./config --with-zlib-include=../compat/zlib --with-zlib-lib=../compat/zlib
make depend
make
cd ../..
./configure --with-zlib=tree --with-openssl=tree
make

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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 check-in [a4bb89ba081e29c5]...

[Joe Mistachkin]

I was unable to reproduce the stated linker error even without this change.
Given
that the generated header files all seem to wrap references to "fusefs_cmd"
in #if
blocks, I'm not sure how it's possible unless maybe the linker error was
caused by
something like not using "make distclean"...?

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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 trying to compile

[Joe Mistachkin]

That largely depends on what your existing development environment is.  Good 
choices are MinGW (not MinGW64) or MSVC.  Proper makefile are provided for both 
of these options.

Sent from my iPhone
https://urn.to/r/mistachkin

> On Oct 12, 2016, at 6:38 PM, Dan Raymond <d...@ecourban.com.au> wrote:
> 
> Thanks.
> 
> What is best environment etc to compile under windows?
> 
> 
> 
> 
> Level 19 Waterfront Place, 1 Eagle Street Brisbane Qld 4000 Australia
> Mail:   PO Box 7815 Waterfront Place, Brisbane 4001
> Tel:+61 733 600 255
> Mob:  +61 400 551 920
> Fax:   +61 733 600 222
> Web:  http://ecourban.com.au
> 
>> On Thu, Oct 13, 2016 at 11:28 AM, Joe Mistachkin <sql...@mistachkin.com> 
>> wrote:
>> 
>> Using that makefile with Cygwin is untested, unlikely to work, and 
>> unsupported.
>> 
>> Sent from my iPhone
>> https://urn.to/r/mistachkin
>> 
>>> On Oct 12, 2016, at 5:55 PM, Dan Raymond <d...@ecourban.com.au> wrote:
>>> 
>>> I am getting the following errors when trying to compile: What do I need to 
>>> do?
>>> 
>>> 
>>> 
>>> $ make -f win/Makefile.mingw
>>>
>>> gcc -Wall -Os -Lsrc/../compat/zlib -Isrc/../compat/zlib 
>>> -DBROKEN_MINGW_CMDLINE=1 -c
>>>  -o src/../compat/zlib/match.o -DASMV 
>>> src/../compat/zlib/contrib/asm686/match.S
>>> match.S: Assembler messages:
>>>
>>> match.S:94: Error: invalid instruction suffix for `push'
>>>
>>> match.S:96: Error: bad register expression  
>>>   
>>> match.S:97: Error: invalid instruction suffix for `push'
>>>
>>> match.S:99: Error: invalid instruction suffix for `push'
>>>
>>> match.S:101: Error: invalid instruction suffix for `push'   
>>>
>>> src/../compat/zlib/contrib/asm686/match.S:348: Error: invalid instruction 
>>> suffix fo
>>> r `pop' 
>>>
>>> src/../compat/zlib/contrib/asm686/match.S:350: Error: invalid instruction 
>>> suffix fo
>>> r `pop' 
>>>
>>> src/../compat/zlib/contrib/asm686/match.S:352: Error: invalid instruction 
>>> suffix fo
>>> r `pop' 
>>>
>>> src/../compat/zlib/contrib/asm686/match.S:354: Error: invalid instruction 
>>> suffix fo
>>> r `pop' 
>>>
>>> make: *** [win/Makefile.mingw:994: src/../compat/zlib/match.o] Error 1  
>>>
>>> 
>>> 
>>> 
>>> I am, trying to compile under CYGWIN on windows 
>>> 
>>> ___
>>> fossil-users mailing list
>>> fossil-users@lists.fossil-scm.org
>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>> 
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> 
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to make post-commit hook?

[Joe Mistachkin]

Svyatoslav Mishyn wrote:
>
> but it looks like a commit script is executed before commit:
> 

The script specified on the "xfersetup_commit" page should run right
after the database transaction is committed.  However, this will not
necessarily be after each Fossil commit.

Admittedly, the TH1 hooks documentation could stand to be improved.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Directory symlinks...

[Joe Mistachkin]

Warren Young wrote:
>
> Well, that's a tricky one, innit?  Fossil manages files, not directories,
> but Fossil's view of symlinks is file-like.  So is it an apple or an
> orange?
>
 
I've checked in a fix on the dirSymlinks branch that appears to completely
fix the issue I personally encountered.

I would appreciate wider testing of it.

--
Joe Mistachkin @ https://urn.to/r/mistachkin


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

[fossil-users] Directory symlinks...

[Joe Mistachkin]

Are having directory symlinks (on Unix) supposed to be supported?
If not, is anybody willing to help me add support for them?

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] TH1 and/or Tcl

[Joe Mistachkin]

Adam Jensen wrote:
> 
> Is TH1 required to run Tcl scripts?
> 

Yes, which should be fine since it is always included when building
Fossil.

>
> Are there any examples of Tcl use-with/extensions-of Fossil?
>

Examples, yes.  Public examples, I'm not so sure about.

> 
> "To enable the native Tcl integration feature feature, add the
> --with-tcl=1 and --with-tcl-private-stubs=1 options."
> 

These should be fine.  The other options control other features (related
to TH1), which are not strictly necessary for Tcl integration.

>
> Does this mean that '--with-th1-hooks' is needed to access a full Tcl
> implementation? (Is the TH1 interpreter required to invoke the Tcl
> interpreter?)
> 

No.  Also, TH1 itself is always included when building Fossil.

Being able to have a TH1 script "hook" commands and/or web pages requires
the --with-th1-hooks option.

Similarly, being able to have a TH1 script be evaluated in response to an
embedded documentation page requires the --with-th1-docs option.

Neither of these options are required simply to enable Tcl integration.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Openssl 1.1.0 [Was:Objections to merging stash-fixes branch?]

[Joe Mistachkin]

 
Jan Nijtmans wrote:
>
> That's your decision (or .. actually Richard's ???) 
> In my view, openssl-1.1.0 has a larger user base
> than SQLite 1.15, so it should be OK for fossil
> trunk. I didn't find anything wrong with it so far.
> (I wouldn't recommend it - yet - as default
> for the 1.35 branch)
> 

I simply moved the changes to a branch for further review, partially because
there are incompatible changes to the MSVC build system (which is
technically
a build break).

Meanwhile, the 1.0.2 branch of OpenSSL has a much longer support end-date
(since it's "LTS") than the 1.1.0 branch, e.g.:

https://www.openssl.org/policies/releasestrat.html

Version 1.1.0 will be supported until 2018-08-31.
Version 1.0.2 will be supported until 2019-12-31 (LTS).

Given that information, I don't see any urgent need to migrate to the
1.1.0 branch of OpenSSL, especially considering the major, incompatible
differences present there.

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Double forward slash when using --baseurl

[Joe Mistachkin]

Zombies wrote:
> 
> For the main web page links it is working fine, however on some of the
pages,
> I am getting links to pages with an extra '/' being inserted. It happens
with
> all of the links from the 'Admin' tab, e.g-
>

What is the full command line being used?

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] Objections to merging stash-fixes branch?

[Joe Mistachkin]

Andy Bradford wrote:
>
> Any objections to merging the stash-fixes branch?
> 

Andy,

FYI, I've modified your branch to re-merge changes from trunk without
the changes for OpenSSL 1.1.0, which is not quite ready for primetime
yet.

Jan, 

I think the MSVC makefile needs updating for the OpenSSL 1.1.0 changes
to work.  Also, maybe we should wait for 1.1.0 to mature a bit prior
to migrating Fossil to it?  Technically, their 1.0.2 branch is still
listed as "stable" and "supported" (until 2019-12-31).

--
Joe Mistachkin @ https://urn.to/r/mistachkin

___
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] basic usage question - empty directories

[Joe Mistachkin]

Adam Jensen wrote:
>
> So neither the TH1 or the embedded Tcl engine have typical shell-like
> access the OS?
>

If the Tcl integration features of Fossil are enabled, the Tcl interpreter
will have full access to the Tcl command set, including any packages that
happen to be installed.

By default, Fossil will attempt to load the "best" Tcl library found in the
PATH; however, this behavior can be overridden using the FOSSIL_TCL_PATH
environment variable (which can point to a file or directory).  Supported
versions of Tcl are 8.4, 8.5, and 8.6.

--
Joe Mistachkin

___
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 clean' should clean extra folders

[Joe Mistachkin]

You should be able to use the
 --emptydirs or --dirsonly options to do that.

Sent from my iPhone

> On Jul 29, 2016, at 12:43 AM, Ronald  wrote:
> 
> 'fossil clean' should clean extra folders, folders can also be extra, and 
> empty extra folder will be confusing.
> 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Windows 1.35 binary does not know about mv-rm-filessetting

[Joe Mistachkin]

Steve Stefanovich wrote:
>
> It looks like it has not been compiled with the correct flag. Can this be
> amended and correct version posted?‎ It is confusing. Summarised here: 
> 

You can obtain the "all features enabled", signed Fossil 1.35 binary for
Windows here:

http://urn.to/r/fossil_3

--
Joe Mistachkin

___
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] TH1 Work - May be of interest to others

[Joe Mistachkin]

David Simmons wrote:
>
> While doing other work in fossil, I've made a few enhancements to TH1.
>

Is the code posted somewhere we can look at it?  I'm not sure if you
intended
to attach it to your message; however, these mailing lists strip
attachments.

--
Joe Mistachkin

___
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 report bug in fossil

[Joe Mistachkin]

Scott Robison wrote:
>
> Okay, thanks for all the help. I've committed some new test cases that
> demonstrate errors in the trunk invalid_utf8. 16 tests fail on trunk,
> none fail on invalid_utf8_table branch (which of course doesn't mean
> there aren't bugs, just that the sample data doesn't exercise a buggy
> path, or that I did something wrong in adding the tests).

Thanks for the new tests.

>
> But seriously, take a look at the new test cases. Let me know whether
> you want to tweak your function or want me to merge mine to trunk.
>

Sure, I'll look at it.  I'm pretty sure we'll go with your function as
it seems easier to understand and maintain.  Thanks for the bugfixes.

--
Joe Mistachkin

___
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 report bug in fossil

[Joe Mistachkin]

Scott Robison wrote:
>
> So my expectation that it would automatically update the utf.test file is
> incorrect? I'm supposed to manually integrate that file back to utf.test?
>

Yes and yes.

>
> If I want to specify a new test that should fail but does not currently,
> am I just supposed to manually tweak the desired expected output of
> utf-check.txt before integration? That's how it is looking to me at the
> moment.
>

Yes.

--
Joe Mistachkin

___
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 report bug in fossil

[Joe Mistachkin]

Scott Robison wrote:
>
> Also: Simply uncommenting the "createTestResults $tempPath 100" call
doesn't
> seem to be doing anything for me. Here is what I'm doing:
>

Here are the steps I just used here locally:

1. Uncomment the "createTestResults" line.
2. Run "tclsh test\tester.tcl fossil.exe utf" from the checkout.
3. Results are located in "%TEMP%\utf-check.txt".

If you add extra entries to the array prior to these steps, those new
results
should appear in the "utf-check.txt" file as well.

--
Joe Mistachkin

___
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 report bug in fossil

[Joe Mistachkin]

Scott Robison
>
> Glad to be able to get to something before everyone else for a change. :)
> 

Yes, thank you very much.

Also, I know it's not a lot of fun, but...

It would be nice if some new tests covering these edge cases were added to
the "utf.test" file.  The "generated section" in the file can be created by
uncommenting the "createTestResults $tempPath 100" call.

--
Joe Mistachkin

___
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 report bug in fossil

[Joe Mistachkin]

rosscann...@fastmail.com wrote:
>
> The bug:
> In lookslike.c, invalid_utf8() returns 'invalid' for the input 0xE0,
> 0xB8, 0x94, which is the Thai character 'do dek' (U+0E14). This can be
> easily reproduced by trying to commit a file that contains those three
> bytes and nothing else - you will get the "this file contains invalid
> UTF-8..." warning.
> 

Thanks for the report.  Jan, any hints on this one?

--
Joe Mistachkin

___
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 2.0: rethinking extras, addremove, and clean

[Joe Mistachkin]

Andy Goth wrote:
>
> My recommendation is to keep the promise made by the current addremove
> documentation.  That is to say, make extras and adds be equal.  This
> means changing the extras command to also ignore files matched by
> clean-glob: extras = adds = tree - managed - ignore-glob.
> 

I do not recall the exact rationale behind the existing semantics;
however, I'm pretty sure there was a length discussion (or two) on the
mailing list at some point.

> 
> The clean command has gotten very complicated, so I further advocate
> removing the -emptydirs and -dotfiles options and making them always be
> in effect.  Empty directories requiring preservation should be listed in
> the empty-dirs setting.  Likewise, dotfiles should be checked in or put
> in ignore-glob.  I also advocate removing -keep and keep-glob since I
> really don't know what they do that isn't done better by ignore-glob.
> 

Unfortunately, most of the complexity is necessary and removing or changing
the semantics would risk breaking existing repositories, including some of
the ones I use on a daily basis.

--
Joe Mistachkin

___
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] Detection of OpenSSL sources in the tree(--with-openssl=tree)

[Joe Mistachkin]

Kain Abel wrote:
>
> The detection of OpenSSL sources in the fossil tree will only pass after:
> ./config and make (in compat/openssl), but not on a clean OpenSSL source
tree
> (or after 'make clean').
> 

Yes, that is the current design. 

However, if there is a clean, portable, robust, and maintainable way to make
it more automatic, I think we would be open to doing that.

--
Joe Mistachkin

___
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 actually >use< TH1?

[Joe Mistachkin]

The Tick wrote:
>
> I guess this answers the question that I did not know how to
> ask precisely:
> 
> Can TH1 be used on the wiki pages (such as the "home" page)?
> Answer: no
> 
> I wonder why TH1's use is excluded for all these pages.
> 

Primarily for reasons of repository security.  Allowing anybody
with wiki editing permissions to execute arbitrary TH1 scripts
might pose a (small?) risk.

--
Joe Mistachkin

___
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 actually >use< TH1?

[Joe Mistachkin]

The Tick wrote:
>
> I spent an hour or so googling "how to use th1 in fossil". I got a ton 
> of links for the language spec but I could not find a single real, live 
> example of how to actually use it. 
> 

There are various ways to use it, depending on context:

1. It can be used via the Fossil command line, e.g. using the
   "test-th-eval" and "test-th-source" commands.

2. It can be used via the "TH1 docs" feature.  Wwhen enabled, this
   feature enables embedded documentation files with a ".th1" file
   extension to execute TH1 scripts).  The "th1-docs" setting must
   be manually enabled for this to work.

3. It can be used to customize the ticket system (e.g. the web
   pages "tktsetup_com", "tktsetup_change", "tktsetup_newpage",
   etc).

4. It can be used within the custom skin headers and footers.

5. It can be used to customize the post-transfer behavior for
   artifacts, commits, and ticket changes (e.g. the web pages
   "xfersetup_com", "xfersetup_push", "xfersetup_commit", and
   "xfersetup_ticket").

6. Finally (I think?), it can be used to setup hooks (pre) and
   notifications (post) for any command or web page, even ones
   that do not actually exist.  Also see the "th1-setup" setting.

Another thing to remember is that when Fossil is compiled with support
for "full Tcl" integration, you can use the TH1 commands "tclEval",
etc to interact with full Tcl scripts, in both directions.  Full details
are available here:

    https://www.fossil-scm.org/index.html/doc/trunk/www/th1.md

Examples of all functionality described in this email are available in
the Fossil test suite.

--
Joe Mistachkin

___
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-dev] Call for review / testing...

[Joe Mistachkin]

> 
> Or if /tmp floats your boat, then do nothing at all and let tester.tcl 
> use it by default. Set TEMP (first found of FOSSIL_TEST_TEMP, 
> FOSSIL_TEMP, TEMP, or TMP with each checked as all caps, all lowercase, 
> and initial caps) to force it to land somewhere known. Also use -keep 
> (which certainly should cause it to print the location of the clutter) 
> to keep the clutter around for post-mortem fussing with the test cases 
> themselves. 
> 

Yes, using the default (/tmp on POSIX) should be fine, because all files
are created within sub-directories of it anyhow (home_ and repo_).

Also, I've just added the -keep option (on the branch).

--
Joe Mistachkin

___
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-dev] Call for review / testing...

[Joe Mistachkin]

Andy Bradford wrote:
> 
> I think this will  work, but I still wonder if it used  to work this way
> before (e.g.  test results  ended up in  current working  directory, not
> elsewhere), why it should not continue  to work that way? The reason why
> I suggested [pwd] is because that is how it currently works (on trunk). 
> 

The way trunk works is probably not the best model.  It requires the user
running the test to actively take steps to avoid polluting/mangling the
Fossil checkout while testing.

> 
> Also, I  look at it  from a different  perspective. Having a  tool write
> things in a magical location that  is *not* my current working directory
> is odd behavior.  For example, if I type ``vi  somefile.txt'', I know it
> will  produce that  file  in my  current working  directory.  If I  type
> ``fossil --httptrace sync'' it it will produce HTTP request/reply things
> in  my current  working directory,  etc... Why  would tester.tcl  behave
> differently?
> 

Lots of tools on both Windows and Unix (including 'vi'?) write temporary
files (and folders) to a temporary directory.

With the new handling on the testerCleanup branch, these files and folders
are written and cleaned up for each test file, in a "fail-safe" manner.

--
Joe Mistachkin

___
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-dev] Call for review / testing...

[Joe Mistachkin]

Andy Bradford wrote:
> 
> I  think  a safer  default  for  tempPath is  [pwd]  and  not where  the
> tester.tcl is found. The following  change permits the testing to resume
> for me:
> 

Slightly different solution checked-in.  I'm not really a fan of relying on
[pwd] in tests.  Instead, we can just use the system temporary file location
-OR- force the user to set FOSSIL_TEST_TEMP.

--
Joe Mistachkin

___
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-dev] Call for review / testing...

[Joe Mistachkin]

Andy Bradford wrote:
>
> $ tclsh $SRC/test/tester.tcl $FOSSIL
> * amend **
> already within an open tree rooted at /tmp/fossil-test/
> 

My guess is that you had a pre-existing checkout recorded for that
directory.  Please "fossil all ignore" that checkout manually and
then try again. 

--
Joe Mistachkin

___
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-dev] Call for review / testing...

[Joe Mistachkin]

Ross Berteig wrote:
> 
> My Ubuntu VM saw this exact message. I was running tester.tcl in a 
> testing folder that is neither the build nor source tree.
> 

My guess is that you had a pre-existing checkout recorded for that
directory.  Please "fossil all ignore" on that checkout manually
and then try again.

--
Joe Mistachkin

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

[fossil-users] Call for review / testing...

[Joe Mistachkin]

Please review and/or run tests against the test suite changes on the
"testerCleanup" branch.  It's designed to give each test file its very
own isolated set of test directories (one for each call to repo_init).
It's also designed to cleanup after itself.  Finally, it is designed
so that it no longer matters if it's run from an open checkout.  For
now, I've left the "no open checkout" restrictions in place for the
specific test files that have it; however, technically it no longer
matters.

--
Joe Mistachkin
 

___
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] possible bug in dc72fd9624 whenadding--with-th1-hooks

[Joe Mistachkin]

Alexandru Birsanu wrote:
>
> HOME=/root and FOSSIL_HOME is not set. It still doesn't work if I set
> FOSSIL_ROOT to /root before make clean && ./configure
> --with-th1-hooks. I've also tested it with a non-root user, and that
> works fine.
> 

IIRC, the "fossil server" command runs in a chroot jail.  You'll need
to take that into consideration when setting the FOSSIL_HOME variable.

--
Joe Mistachkin

___
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] possible bug in dc72fd9624 when adding--with-th1-hooks

[Joe Mistachkin]

Alexandru Birsanu wrote:
> 
> ./fossil server repo.fossil
> results in an "invalid home directory: /root" error when using a
> browser to connect.
> 

What are your FOSSIL_HOME and HOME environment variables set to?  Can
you try setting FOSSIL_HOME to the right home directory prior to running
with TH1 hooks enabled?

--
Joe Mistachkin

___
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-dev] Request for merge

[Joe Mistachkin]

Baruch Burstein wrote:
>
> I would like to suggest these branches for merging into trunk:
>
> https://www.fossil-scm.org/index.html/info/cfd3a5b944ea15f4

> 
> https://www.fossil-scm.org/index.html/info/50d81f95041f631e
> 
> https://www.fossil-scm.org/index.html/info/26fc65f99c035dac
> 

I've reviewed these changes briefly and I do not see anything
obviously wrong with them; however, can other people with deeper
knowledge of the web interface code please review them as well?

--
Joe Mistachkin

___
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] Recent breakage on Mac OS X

[Joe Mistachkin]

Andy Bradford wrote: 
>
> I see similar errors with gcc on OpenBSD.
>

Sorry about that, should be fixed now.

--
Joe Mistachkin

___
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 build improvements...

[Joe Mistachkin]

I've made some enhancements to the standard Fossil build process using
configure and make.  I would appreciate feedback and testing for the
tip of the "mingwConfigure" branch, on whatever platform(s) you have
handy.  A quick summary of the enhancements is:

1. Add the "tree" option to --with-openssl to build using OpenSSL
   source code contained in the "compat/openssl" sub-directory of
   the tree (i.e. it must be manually downloaded, extracted, and
   built there first).

2. Make it possible to use vanilla configure and make on MinGW.

Again, any feedback and/or testing for these changes would be greatly
appreciated.

--
Joe Mistachkin

___
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] Empty files in fossil-generated zip archives

[Joe Mistachkin]

Florian Balmer wrote:
> 
> 7-Zip lists "D" as the attributes for empty files in the
> fossil-generated zips, and `zipinfo' on my FreeBSD web server lists
> "drwxr-xr-x". 
> 

Thanks for the report.  Should be fixed, here:

https://www.fossil-scm.org/index.html/vinfo/18607?sbs=0

Please let us know if this clears the issue for you.

--
Joe Mistachkin

___
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] server returned an error - clone aborted

[Joe Mistachkin]

I've seen these types of errors from both "fossil clone" and "fossil update"
where the response was truncated.  It seemed to be an issue with the VPS I
was using at the time.

Perhaps the issue is a subtle interaction between Fossil and how some
VPS'es handle SSL connections?

--
Joe Mistachkin

___
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] Can't build Fossil 1.34 with Tcl 8.5

[Joe Mistachkin]

Piotr Orzechowski wrote:
> 
> Trying "make distclean" did not help, the error persisted.
> 

Odd, it did work here (i.e. adding "--with-tcl-private-stubs=1"
to configure after "make distclean").

> 
> #define Tcl_Canceled(a,b) TCL_OK did its job well. :)
> 

Glad to hear it.

--
Joe Mistachkin

___
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] symlinks (was Re: xkcd on git)

[Joe Mistachkin]

David Mason wrote:
>
> Exactly.  Please fix symlinks so that if you live only on Unix you get
seamless
> support.  If you work back and forth between Windows and Unix then you
probably
> just don't use symlinks, so it won't be a problem for you! 
>

To All:

Just to clarify, what are the behavioral changes needed on the Unix side to
make
things work seamlessly?

Are there differing opinions on the changes needed (i.e. and not just
whether or
not there should be any changes in the current behavior)?

--
Joe Mistachkin

___
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] symlinks (was Re: xkcd on git)

[Joe Mistachkin]

Eric Rubin-Smith wrote:
>
> (1) Default allow-symlinks to true
> (2) Fix bug in which the allow-symlinks setting is not honored while
> opening a repository
>

Please try the latest Fossil trunk and let us know if that fixes all the
issues you were seeing.

--
Joe Mistachkin

___
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] symlinks (was Re: xkcd on git)

[Joe Mistachkin]

Eric Rubin-Smith wrote:
>
> (2) Fix bug in which the allow-symlinks setting is not honored while
> opening a repository
>

Did the following changes (a while back) not address this?

https://www.fossil-scm.org/fossil/vinfo/010451e7a5fe116a?sbs=0

If not, in what way are they not adequate?

--
Joe Mistachkin

___
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] symlinks (was Re: xkcd on git)

[Joe Mistachkin]

Eric Rubin-Smith wrote:
>
> Version [aa92270fe9] seems to have regressed the case of opening a
repository with a
> .fossil-checkout/allow-symlinks file set to 'on'.  See the transcript
below.  Note
> that I had created the repository earlier (I assume this does not matter
for the
> purposes of this test).

This issue was more subtle than it originally appeared.  I think the current
trunk
changes should make it work right for both versioned and non-versioned
allow-symlinks
settings.

--
Joe Mistachkin

___
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] Can't build Fossil 1.34 with Tcl 8.5

[Joe Mistachkin]

Piotr Orzechowski wrote:
>
> /fossil-src-1.34/./src/th_tcl.c:1069: undefined
> reference to `Tcl_Canceled'
> collect2: error: ld returned 1 exit status
> make: *** [fossil] Error 1
> 

Thanks for the report.  There are a couple workarounds:

1. use "--with-tcl-private-stubs=1" with configure.
2. #define Tcl_Canceled(a,b)  TCL_OK

--
Joe Mistachkin

___
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] Can't build Fossil 1.34 with Tcl 8.5

[Joe Mistachkin]

Piotr Orzechowski wrote:
> 
> Adding --with-tcl-stubs and --with-tcl-private-stubs did not help.
> 

Did you try "make distclean" first?

>
> That #define looks scary, to be honest. ;) 
>

I wrote both the Tcl and Fossil code in question and I can personally assure
you that it is safe (also I just tried it myself).  Simply run "./configure"
with the desired arguments and then add the necessary line to "autoconfig.h"
before running "make".  You may need to run "make distclean" first if there
are compiled files from a previous attempt around.

--
Joe Mistachkin

___
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 gdiff shows diffs on ADDED_BY_INTEGRATE files

[Joe Mistachkin]

Noam Postavsky wrote:
> 
> It doesn't for ADDED or ADDED_BY_MERGE (which is good because seeing
> every line added in a diff viewer isn't so helpful). I'm sure this is
> just a missing clause in an if somewhere.
> 

Thanks for the report.  Should be fixed on trunk.

> 
> Also, my fossil clone with remote "http://fossil-scm.org; seems to be
> stuck at 975600dd599fff84 (i.e. fossil update does not advance it any
> further). Am I using the wrong remote or something?
> 

What version of Fossil are you using?  Does it give an error message of
any kind?  What does 'fossil status' say?  Also, can you try running
'fossil test-integrity'?

--
Joe Mistachkin

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

[fossil-users] The "exec-rel-paths" branch...

[Joe Mistachkin]

I would like to get this merged prior to the 1.34 release.

Are there any objections?

--
Joe Mistachkin

___
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] Questions about wiki linking to non-branch artifact IDs/images

[Joe Mistachkin]

On trunk, in contexts where TH1 is allowed (not wiki?), you should now be
able to do:

set image [encode64 [artifact trunk path/to/some.png]]


--
Joe Mistachkin

___
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] Time to release Fossil version 1.34?

[Joe Mistachkin]

Jan Nijtmans wrote:
> 
> It turns out that the cause of this problem is the following commit:
> <http://www.fossil-scm.org/index.html/info/9431fec1ea098fea>
> so I backed it out. My local trunk build doesn't show the problem
> any more.
> 

Actually, it appears you backed out two check-ins.  The original one and
the follow-up that fixed the timeline issue it had.

I've moved the backout off trunk so the issues that remain, if any, can
be fixed prior to the release.

--
Joe Mistachkin

___
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] Time to release Fossil version 1.34?

[Joe Mistachkin]

There seems to be a timeline issue:

https://system.data.sqlite.org/index.html/timeline?n=50=all=1

The [2c6bdf20ea] merge check-in has two entries for each of the modified
files.

--
Joe Mistachkin

___
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] Trying to compile fossil with TCL integration

[Joe Mistachkin]

The tclReady command does not create the Tcl interpreter on-demand, which is 
unlike the other Tcl integration commands.  Use tclEval at least once before 
using tclReady and it should return 1.

As far as the Tcl library loading error goes, it's probably either a naming 
scheme mismatch (Fossil wants literally "libtcl8.6.so") or an inability to find 
the Tcl library along the shared library path (or the LD_LIBRARY_PATH).

Sent from my iPhone

> On Sep 2, 2015, at 5:51 AM, Remco Schoen  wrote:
> 
> 
>> Op 2 sep. 2015, om 13:17 heeft Jan Nijtmans  het 
>> volgende geschreven:
>> 
>> You can check whether your fossil is compiled correctly with:
>>$ fossil version -v
>>   TCL (Tcl 8.6.0, loaded TH_OK: 8.6.4)
> 
> Okay, I see I have my first challenge there:
> TCL (Tcl 8.6.4, loaded TH_ERROR: could not load any supported Tcl 8.6, 8.5, 
> or 8.4 shared library "libtcl8.x.so”)
> 
> I downloaded the source from TCL and compiled and installed it, but 
> apparently that is not enough in ubuntu. Now compiling again to see what 
> happens on a Raspberry Pi.
> 
> 
>> After that, it should work, but not in the test-th-eval command ;-)
>> You could try "fossil ui" and then go to Admin -> TH1. Typing
>> the command "tclEval {info tclversion}"  from there works.
> 
> Check, got it to work in the docker image.
> 
> Is there a reason why tclReady returns 0 there as well?
> 
> Kind regards,
> 
> Remco
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

[Joe Mistachkin]

There are docs on --with-tcl and the commands it provides (see th1.md in the 
source tree).  Also, with Tcl enabled the hooks work perfectly for sending mail 
and I've personally been doing so for several years on a repository of mine.

Sent from my iPhone

> On Aug 31, 2015, at 9:40 AM, Warren Young  wrote:
> 
>> On Aug 30, 2015, at 2:27 AM, Stephan Beal  wrote:
>> 
>>> On Sun, Aug 30, 2015 at 10:15 AM, Baptiste Daroussin 
>>>  wrote:
>>> Number #1 is the inhability to run "external" hooks easily
>> 
>> it's difficult to do portably
> 
> system() is ANSI C.
> 
> There are many external programs you can call that way.  All that’s needed is 
> some kind of hook-calling protocol, a la CGI.
> 
>> it opens up many more potential failure cases
> 
> I don’t see what’s difficult about failing a transaction if a hook is defined 
> and the external program call fails.  All the difficult parts are fobbed off 
> on the person writing the hook script.
> 
>> what happens to a commit if an http connection to an external server, used 
>> by a trigger, cannot be established?
> 
> The commit fails, same as if the process of attempting the commit causes any 
> other error, such as a fork without --allow-fork.
> 
>> Many hosting environments do not allow hosted scripts/apps to establish 
>> outbound connections with external servers
> 
> If you’re on such a host, you don’t get to use hooks.  Switch to a different 
> hosting provider if you need hooks.  There are dozens of bare-bones VPS and 
> cloud hosting providers without this restriction.
> 
> Also, this restriction only affects those who go out of their way to use 
> hooks.  If you don’t define any hooks, Fossil will behave the same as it does 
> today.
> 
>> Fossil does have basic hooks support in the form of TH1/TCL scripts,
> 
> You have to configure Fossil with --with-th1-hooks to enable it.
> 
> Also, as far as I can tell, TH1 doesn’t have the power to implement an SMTP 
> client or call out to an external one anyway.  (i.e. no equivalent of 
> connect(2) or system(3).)
> 
> I was curious how Git handles this, and to a first approximation, it doesn’t. 
>  It includes a 1,700 line Perl script which either calls out to sendmail(1) 
> or uses the Perl Net::SMTP library to do all the heavy lifting.
> 
>https://github.com/git/git/blob/master/git-send-email.perl
> 
> My point above is that even these options aren’t available to TH1.
> 
> I see that Fossil has --with-tcl, which might be able to solve this, but I 
> don’t see any documentation explaining it on the Fossil site.
> 
>> There is no _portable_ external provider API for sending mails.
> 
> Not for C, true, but Tcl can do it: http://wiki.tcl.tk/1256
> 
> For platforms where linking to Tcl isn’t suitable, TH1 could add the exec and 
> open commands:
> 
>   https://www.tcl.tk/man/tcl8.5/tutorial/Tcl26.html
> 
> Then Fossil proper wouldn’t have to worry about such things as how to send 
> email.
> 
>> My point was not so much about the multiline support, but the lack (in my 
>> experience) of need for book-length commit messages. Without those, the lack 
>> of multi-line support is moot.
> 
> Straw man.  Adding a small bit of markup to a commit message is not writing 
> books.  And it’s a good thing, since Markdown is not the right formatting 
> system for book production anyway.
> 
> Most of the code needed to do this is in Fossil already.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] check-in-edit branch ready?

[Joe Mistachkin]

Thanks for adding the tests.  I think it looks great.  Does anybody else
have
any feedback on the changes?

--
Joe Mistachkin

___
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] quick poll: do you generally use add/rm or mv

[Joe Mistachkin]

Warren Young wrote:

 Fossil currently forces a two-step mv, which is different from *every
 other popular F/OSS VCS* except for CVS, and that's only because CVS
 doesn't have mv at all.


No, it doesn't.  Fossil now has the --hard option for mv/rm.  Also, it
can be compiled in such a way that --hard is the default.

--
Joe Mistachkin

___
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] 'mv' semantics

[Joe Mistachkin]

Michai Ramakers wrote:
 
 I don't think I understand what goes on here; I can't see the
 difference between filesystem-mv (no fossil involved), and 'fossil mv
 --hard', really.
 

Sometimes, Fossil will show a rename as a delete/add pairing.  I've seen
this happen when I edit the file at the same time I'm renaming it (and in
some other circumstances).  I'm not 100% sure what causes this behavior;
however, it seems mostly harmless.

 
 I looked at some posts w.r.t. mv/rm/extra/changes from the past, and
 some people feel strongly about what should or must not happen - I'm
 not one of those, really, I just don't understand how it works now.
 

Yes, I remember those discussions.  I think most (?) of the underlying
issues in those discussions have largely already been addressed.

--
Joe Mistachkin

___
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] 'mv' semantics

[Joe Mistachkin]

Michai Ramakers wrote:

 I was unclear; this is the corresponding timeline:
 
 === 2015-07-29 ===
 19:58:39 [70b61c707b] *CURRENT* x (user: michai tags: trunk)
DELETED d/dd/f
DELETED d/f
ADDED e/dd/f
ADDED e/f
 19:57:26 [998d26af68] a (user: michai tags: trunk)
ADDED d/dd/f
ADDED d/f
 19:56:53 [07d0f795af] initial empty check-in (user: michai tags: trunk) 
 

Yeah, I've seen that happen to; however, in this case I believe it's a
red herring.  The --hard option makes no different in how the timeline
is presented.

I'm not saying there isn't an issue with the timeline; I'm saying it's
unrelated to the --hard option.

--
Joe Mistachkin

___
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] 'mv' semantics

[Joe Mistachkin]

Michai Ramakers wrote:

 Right... creating the target-dir 'd2' beforehand worked in my case;
 any subdir existing under 'd' seems to be moved under 'd2' afterwards.


I think the following change will fix the issue:

https://www.fossil-scm.org/fossil/info/b86127e187a00bfc

--
Joe Mistachkin

___
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] check-in-edit branch ready?

[Joe Mistachkin]

Andy Bradford wrote:

 I think the changes in the  check-in-edit branch are ready for a broader
 audience and move to have it merged.
 

It might be nice to have test coverage for the new command.

Since the underlying [newly] shared code would end up being tested as well,
it would be even more valuable (and critical?) than normal for a typical
new feature.

--
Joe Mistachkin

___
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] Adding 'undo' support to the 'clean' command...

[Joe Mistachkin]

I considered that out-of-scope for this feature.  You can always use --force to 
avoid those prompts.

Sent from my iPhone

 On Jul 14, 2015, at 1:13 AM, Jan Nijtmans jan.nijtm...@gmail.com wrote:
 
 2015-07-10 12:04 GMT+02:00 Jan Nijtmans jan.nijtm...@gmail.com:
$ ./fossil clean
WARNING: Deletion of this file will not be undoable via the 'undo'
 command because the file is too big.
Remove unmanaged file abc.x (a=all/y/N)? y
 
 Yes, that's exactly how I expect it to work.
 
 Thanks!
   Jan Nijtmans
 
 Trying something else:
 
$ mkdir abc
$ fossil clean --emptydirs
Remove empty directory abc (a=all/y/N)? y
$
 
 If deletion of files is undoable, how about the deletion
 of empty directories? Or am I asking too much?   ;-)
 
 Regards,
 Jan Nijtmans
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Adding 'undo' support to the 'clean' command...

[Joe Mistachkin]

I've come up with an alternative implementation of this feature that I think
is a bit simpler (see the enhancedUndo branch).  It avoids making changes
to anything that is unrelated to the goal at hand.  I would really
appreciate
feedback.

Also, regardless of which implementation is eventually used, we are going to
need tests.

--
Joe Mistachkin

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

[fossil-users] Seeking feedback on the rssTags branch...

[Joe Mistachkin]

I wanted the ability to see the associated branch for each RSS item on a
Fossil feed, so I made the necessary modifications on a branch.  I think
the (quite minor) changes are merge-worthy at this point.

Any objections?  Other feedback?

--
Joe Mistachkin

___
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 enable TH1?

[Joe Mistachkin]

Michael Richter wrote:
 
 What, exactly, does this actually do?  I can't find any information on
this
 whatsoever.


Technically, it is documented in the help for the settings command.

I suppose that I should provide more details on the primary TH1 integration
reference page:

https://www.fossil-scm.org/fossil/doc/trunk/www/th1.md

My conference slides describing how to use this feature (and other Tcl
integration features) are here:

http://eagle.to/tcl2014/fossil-tcl.pdf

Here is the relevant excerpt from the help for the settings command:

   tcl  If enabled (and Fossil was compiled with Tcl support),
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. Default: off.

   tcl-setupThis is the setup script to be evaluated after creating
(versionable)   and initializing the Tcl interpreter.  By default, this
is empty and no extra setup is performed.

   th1-docs WARNING: If enabled (and Fossil was compiled with TH1
support for embedded documentation files), this allows
embedded documentation files to contain arbitrary TH1
scripts that are evaluated on the server.  If native
Tcl integration is also enabled, this setting has the
potential to allow anybody with check-in privileges to
do almost anything that the associated operating system
user account could do.  Extreme caution should be used
when enabling this setting.  Default: off.

   th1-hooksIf enabled (and Fossil was compiled with support for TH1
hooks), special TH1 commands will be called before and
after any Fossil command or web page. Default: off.

   th1-setupThis is the setup script to be evaluated after creating
(versionable)   and initializing the TH1 interpreter.  By default, this
is empty and no extra setup is performed.

   th1-uri-regexp   Specify which URI's are allowed in HTTP requests from
(versionable)   TH1 scripts.  If empty, no HTTP requests are allowed
whatsoever.  The default is an empty string.

--
Joe Mistachkin

___
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 enable TH1?

[Joe Mistachkin]

lz wrote:

 xxx@xxx:~/FossilBook$ fossil settings th1-docs
 no such setting: th1-docs
 

This must be enabled at compile-time as well via the FOSSIL_ENABLE_TH1_DOCS
define.  When using ./configure, you can specify:

--with-th1-docs=1

--
Joe Mistachkin

___
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_ERROR using fossil mv --hard

[Joe Mistachkin]

Taylor C. Venable wrote:

  Error #1: Moving existing files to curdir
 RENAME a dir/a
 RENAME b dir/b
 cannot open /home/taylor/tmp/fossil/move/repo/dir/a for reading
  Error #2: Moving non-existent files to curdir
 SQLITE_ERROR: no such table: fmove
 fossil: no such table: fmove
 SELECT x, y FROM fmove ORDER BY x;
 

Thanks for the report.  These issues should now be fixed on the tip
of the mvRmHardFix branch.

--
Joe Mistachkin
 

___
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 check-ins [46675ed2] and [010451e7] (remove add access-check and andygoth-versioned-open merge)...

[Joe Mistachkin]

I am a fan of both of these changes.  However, does everybody think they
have had enough testing to be included in a release that is imminent?

I just reviewed the changes again and I'm starting to think they are low
risk enough to include in 1.33.  Does anybody disagree?

--
Joe Mistachkin

___
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] Symlink trouble

[Joe Mistachkin]

Andy Goth wrote:
 
 My andygoth-versioned-open branch (just checked in) addresses this
 problem and seems to fix the symlink issue.  However, the Fossil coding
 style is rather alien to me, particularly the way it leaks memory on
 purpose, so the way I'm doing things may not be the best.  Please have a
 look, and feel free to ask questions and make suggestions and further
 changes. 
 

I've made some tweaks on the branch.  Here are the highlights:

1. By changing the return code checking for historical_version_of_file(),
   which apparently returns greater than zero on success.

2. Set noWarn based on the historical version of that file, if it exists.

3. Unrelated: Removed superfluous slash in the .fossil-settings path
   used by print_setting().

--
Joe Mistachkin

___
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] Documenting the TH1 extended commands...

[Joe Mistachkin]

Sergei Gavrikov wrote:

 Also, we would add a bit of self-documentation sugar to TH1 language if we
 provide yet two sub-commands to TH1 [info] command, I mean 'commands' and
 'globals' sub-commands. 
 

You're right, this was sorely needed.

I've added new info commands and info vars sub-commands on trunk.  You
can combine the info vars sub-command with uplevel to get the same
effect
as info globals.

Thanks for the feedback and bug reports...  :)

--
Joe Mistachkin

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

[fossil-users] Documenting the TH1 extended commands...

[Joe Mistachkin]

I've committed an initial draft of the documentation for the TH1
extended commands exposed by Fossil.  Corrections and feedback
are more than welcome.

https://www.fossil-scm.org/fossil/doc/trunk/www/th1.md

--
Joe Mistachkin

___
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 with Tcl support does not work withnginx/xinetd

[Joe Mistachkin]

Piotr Orzechowski wrote:
 
 So the question is, does Tcl support require some special steps or
 environment setup to work? Is there any other thing I should check or
 look at?
 

If Fossil is linked to a Tcl shared library, is it accessible from the
web server process?  In some environments (i.e. jails), you might need
to compile Tcl without shared library support (via --disable-shared) and
then recompile Fossil to use that Tcl.

Once the Fossil repository works when compiled with Tcl support, you'll
need to enable the tcl setting (on the settings page) in order to take
advantage of it.

--
Joe Mistachkin

___
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] RFC regarding short UUID for some command line use.

[Joe Mistachkin]

Andy Bradford wrote:
 
 There  have  recently  been  some  changes  to  make  short  UUIDs  more
 prominent, however, I  think that new checkins should  still display the
 full UUID:
 

Personally, I agree.  I find having the abbreviated UUID displayed in this
particular context to be quite disconcerting.

--
Joe Mistachkin

___
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 repolist argument with winsrv

[Joe Mistachkin]

Petr Ferdus wrote:

 I just realized that fossil winsrv command does not recognize --repolist
 argument. Could winsrv honors this argument as well?


Fixed on trunk.

--
Joe Mistachkin

___
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 repolist argument with winsrv

[Joe Mistachkin]

Richie Adler wrote:
 
 This passes the --repolist parameter to the fossil server command
recorded
 in the registry, but I get a Not found page when I run the service
installed
 or even when I run 
 

Sorry, minor oversight.  It was not setting the right flag bit prior to
calling
into the Win32 HTTP server.  Should work on trunk now.

--
Joe Mistachkin

___
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] configure reset skin resets too much

[Joe Mistachkin]

Andy Bradford wrote:
 
 I don't think  it makes much sense  for the index-page to  be reset with
 ``fossil config reset  skin'' either. Is the  index-page considered part
 of the  skin? Likewise,  it also  seems odd  that ``fossil  config reset
 project'' doesn't reset the index-page.
 

Agreed.  I'm also of the opinion that this is a good change and I have no
objections to it.

--
Joe Mistachkin

___
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] TH1 Hooks.

[Joe Mistachkin]

Andy Bradford wrote:

 If   Iconfigure   the   FOSSIL_ENABLE_TH1_HOOKS(e.g.   configure
 --with-th1-hooks) what does that get me?  I assume from the code that it
 will call Th_CommandHook  passing in the name and flags,  but to what in
 the TH1  environment? My guess  is that I need  a function by  a certain
 name, but what? Is there any documentation on using TH1 hooks? 
 

First, you would need to enable the th1-hooks setting.

Then, you would normally need a th1-setup script, set via the settings
command or a .fossil-settings file.  There would need to be a procedure
defined named command_hook (and/or command_notify), e.g.:

proc command_hook {} {
  if {$::cmd_name eq timeline} {
puts $::cmd_args\n
puts preparing the timeline... [tclEval {info patchlevel}]\n\n
  }
}

proc command_notify {} {
  if {$::cmd_name eq timeline} {
puts $::cmd_args\n
puts timeline completed. [tclEval {info patchlevel}]\n\n
  }
}

The hook procedure is evaluated prior to the actual command and the notify
procedure is evaluated after the command.  In the above example, which was
used for testing, I also made use of the native Tcl integration feature.

--
Joe Mistachkin

___
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] TH1 Hooks.

[Joe Mistachkin]

Ron W wrote:

 What's in $::cmd_args ? Is it just the command line (or command URL)?


The command line arguments, just as they existed in the g.argv field at
that point.  It should be noted that the command line arguments _cannot_
currently be modified by the hook, only inspected.


 In command_notify, after a commit, is the commit ID included? What about
 ticket and wiki writes?


No.  Only the cmd_name, cmd_args, and cmd_flags TH1 variables are
specially set.  However, you are free to use TH1 (and Tcl if enabled) to
determine any additional context information you may need.

--
Joe Mistachkin

___
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] Compilation with SSL option fails on Win7

[Joe Mistachkin]

Tony Papadimitriou wrote:
 
 link /nologo /subsystem:console /opt:ref /debug 
 /out:out32\md4test.exe @C:\Users\Tony\AppData\Local\Temp\nm7D8C.tmp
 LINK : fatal error LNK1181: cannot open input file 'link.obj'
 NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 
 12.0\VC\BIN\link.EXE' : return code '0x49d'
 Stop.
 NMAKE : fatal error U1077: 'pushd' : return code '0x2'
 Stop. 
 

I have not been able to reproduce this error message here.  It might
be useful to know the contents of that temporary file being used by
link.exe.  However, it can be difficult to read those since they
are typically deleted automatically.

 
 But then, I also tried without the new FOSSIL_BUILD_SSL=1 (only the 
 FOSSIL_ENABLE_SSL=1 option), and it built OK.  (I suppose you
 separated the build of SSL from the inclusion of SSL.)
 

I'm confused by this.  You saying that you freshly extract the OpenSSL
source code between attempts, yet you are able to build Fossil with
SSL support enabled without actually being able to build the OpenSSL
libraries?

 
 1. The problem is with the build process of SSL because using pre-built 
 libraries apparently works.
 

Actually, Fossil follows the official OpenSSL instructions for building
with MSVC.


 2. Both 32-bit and 64-bit Win7 behave the same in either case.


Odd, because prior to last night building OpenSSL for 64-bit Windows was
not supported by the Fossil MSVC makefile.

 
 3. Latest trunk version builds FOSSIL executable successfully but only if 
 the FOSSIL_BUILD-SSL is not given.
 

This strongly implies that you have some OpenSSL libraries built and lurking
around somewhere.

 
 So, if you manage to build on your machine with the FOSSIL_BUILD_SSL=1 
 option, then apparently there must be some component(s) missing on mine.
I 
 have:
 

Possibly, but I cannot imagine what components that might be.  I've been
able
to build Fossil with OpenSSL enabled on a completely fresh box using
Visual
Studio 2013 Express, ActivePerl, and the OpenSSL source code.

--
Joe Mistachkin

___
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] Compilation with SSL option fails on Win7

[Joe Mistachkin]

Stephan Beal wrote:
 
 Pure speculation: is it a side-effect of the missing pushd, causing it not
to
 be able to (A) change dirs and (B) find the file(s) it expects in those
dirs
 (because (A) failed)? 
 

Great catch.  The MSVC makefile is designed to be used from the directory it
is
contained in.  This should now be more strongly enforced, here:

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

--
Joe Mistachkin

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