Re: [fossil-users] Purging data from Fossil
On 7/26/16, David Mason wrote: > I have a problem. > > I use fossil for my courses - one I've used for 4 years. In each year > there are grades files (with student names, student numbers and grades), > and they get changed and committed over the semester, so there are many > versions in the fossil (hundreds of checkins). > > I want to share these fossils with some people who cannot be allowed to see > the grades files. So I need to remove the data. I could shun the artifacts > and rebuild (and, in fact that's what I started to do), but finding all the > versions of the files seems rather daunting, and it appears I can only shun > from the UI, so I can't even write a script to do it. > > Any ideas on how to clean this up? fossil purge looked like it might help, > but then not so much... It is theoretically possible to do this with the current data design. It would really just be a few SQL statements, with the corresponding C code to handling the user interface. But that code does not currently exist. Adding code to do this would make a good student project. Do you have any students willing to undertake it? :-) > > BTW, on the shun page, when it lists pending shuns at the bottom of the > page, it would be very convenient if it listed the files that correspond to > that hash (probably only 1, modulo renaming, but useful regardless). The "shun" table currently has the "scom" field which is intended to be human-readable text that explains why the shun occurred. Probably you would want to add another field to be the filename of the object shunned. This is doable. But, again, the code is not yet in place. -- 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] Purging data from Fossil
Further thoughts: With shunning, Fossil remembers the SHA1 hashes of the shunned artifacts so that they can never again be received by subsequent pulls. It seems like this is more than you need. Suppose we created a new command "fossil trim ARGS..." This new command would remove selected artifacts from the local copy of the repository, but the removal would be temporary. The artifacts would reappear the next time the local repository is synced with some other repo that holds the artifacts. (The removal would, of course, be permanent if there were no other copies of the repo to sync with.) It seems like the "trim" command might serve several purposes: (1) Allow the creation of a repo that omits selected historical information that one does not want to share. (2) Allows putting Fossil into a weird state in order to stress the sync logic for testing purposes. I could have made use of this feature for purpose (1) last week, had it been available. So I am now officially interested in adding it. The ARGS part would embody several options for doing things like removing all instances of a specific file, or all check-ins within a range of dates, all tickets matching some criteria, all wiki pages whose names match a GLOB pattern, etc. The problem I had last week was I needed a cut-down instance of a repository that only contained data for two specific check-ins out of around 3000. Community members, I want your help as follows: (A) Suggest a better name than "fossil trim" (B) Define the syntax of ARGS. (C) Define a safety mechanism that allows content to be restored if it is accidentally trimmed when there are no other repos available with which to sink. Perhaps the trimmed content gets written into a separate "trash-can" database? On 7/26/16, David Mason wrote: > I have a problem. > > I use fossil for my courses - one I've used for 4 years. In each year > there are grades files (with student names, student numbers and grades), > and they get changed and committed over the semester, so there are many > versions in the fossil (hundreds of checkins). > > I want to share these fossils with some people who cannot be allowed to see > the grades files. So I need to remove the data. I could shun the artifacts > and rebuild (and, in fact that's what I started to do), but finding all the > versions of the files seems rather daunting, and it appears I can only shun > from the UI, so I can't even write a script to do it. > > Any ideas on how to clean this up? fossil purge looked like it might help, > but then not so much... > > BTW, on the shun page, when it lists pending shuns at the bottom of the > page, it would be very convenient if it listed the files that correspond to > that hash (probably only 1, modulo renaming, but useful regardless). > > Thanks for any help! > > ../Dave > -- 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] Purging data from Fossil
On 7/26/16, David Mason wrote: > Is there any way to find all the artifacts that correspond to a given > pathname? Then I could shun those. SELECT DISTINCT uuid FROM blob, mlink, filename WHERE blob.rid=mlink.fid AND mlink.fnid=filename.fnid AND filename.name=$NAME; Fill in $NAME appropriately, of course. -- 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] Purging data from Fossil
On 7/27/16, David Mason wrote: > On 26 July 2016 at 17:13, Richard Hipp wrote: > >> SELECT DISTINCT uuid >> FROM blob, mlink, filename >> > > Works a charm (18 UUIDs show up). Now if there were a way to shun from the > command line, I'd be golden. The entry box on the /shun webpage allows you to past all 18 SHA1 hashes in a single go. BTW: Be sure to "fossil rebuild" after shunning. That extra step is necessary to fully purge the unwanted artifacts. Also look into using the "fossil scrub" command on any repo that you want to send to unprivileged users. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] basic usage question - empty directories
On 8/1/16, Adam Jensen wrote: > Is there a way to > commit empty directories to the repository so the project's directory > structure can be preserved and reconstructed? No, sadly, there is not. Fossil versions only files. Directories exist only if they contain a file. -- 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] Compiler warnings
Please try again with the latest code from trunk. On 8/2/16, Johan Kuuse wrote: > Hi, > > In trunk (f475b943eb), I get a compiler warning when I use clang with the > default Makefile: > > > cc -I. -I./src -Ibld -DFOSSIL_DYNAMIC_BUILD=1 -I/usr/local/include-g > -O2 -DHAVE_AUTOCONFIG_H -D_HAVE_SQLITE_CONFIG_H -O2 -pipe -o bld/fshell.o > -c bld/fshell_.c > ./src/fshell.c:109:7: warning: implicit declaration of function 'waitpid' > is invalid in C99 [-Wimplicit-function-declaration] > waitpid(childPid, &status, 0); > ^ > > I don't get that warning by default using gcc. Anyway, I can reproduce it > with the added flag -Wall, which also gives the following warning: > > gcc -I. -I./src -Ibld -DFOSSIL_DYNAMIC_BUILD=1 -I/usr/local/include -Wall > -g -O2 -DHAVE_AUTOCONFIG_H -D_HAVE_SQLITE_CONFIG_H -O2 -pipe -o > bld/user.o -c bld/user_.c > ./src/user.c: In function 'prompt_for_passphrase': > ./src/user.c:191:15: warning: unused variable 'zSecure' [-Wunused-variable] >const char *zSecure; >^ > > 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] How to host fossil repositories on web server that supports only FastCGI interface?
On 8/2/16, John Found wrote: > I have to move my web site on a server that supports only FastCGI interface. > Is there an easy way to host fossil repositories on it? Fossil only support CGI and SCGI. What web server are you running that has only FastCGI support. When I was looking into alternatives to plain old CGI, I found that the FastCGI protocol was very complex and hard to implement, whereas SCGI was quite simple. So I took the simpler approach. Are there some advantages to FastCGI that I am unaware of? -- 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] How to host fossil repositories on web server that supports only FastCGI interface?
On 8/2/16, Stephan Beal wrote: > > As i recall (but it's been 6 or 8 years), FastCGI works by starting a > single app instance and piping CGI data through it multiple times (for > multiple requests). If that's the case... Fossil relies on the app shutting > down to free memory, and would be incompatible with such a mechanism. Also, > IIRC, FastCGI provides drop-in "replacements" of the read() and write() > calls via macros, but use the wrong signature for (IIRC) the write() > routine (they use a non-const pointer for the source memory, whereas the > real API uses a const one). SCGI works the same way - it opens a socket to a persistent process and sends multiple requests over to the process. Fossil handles this the same way it handles the "fossil server" command. There is one persistent process that does nothing but accept SCGI requests. For each request, that process forks a separate child to service that request. You can see this better by noting that there is no "fossil scgi" command, but rather a "--scgi" switch on the "fossil server" command. The same logic that deals with HTTP requests also deals with SCGI requests - it just understands a different protocol. Were we to add FastCGI capabilities to Fossil, no doubt there would be yet another "--fastcgi" option on the "fossil server" command. -- 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] Compiler warnings
On 8/2/16, Johan Kuuse wrote: > > I would suggest adding the -Wextra flag > anyway, to trap a lot of other existing warnings, and more important, > future warnings. > I care more about bugs than warnigns. Has -Wextra ever found a bug in Fossil? -- 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] Compiler warnings
On 8/2/16, Ron W wrote: > > Are there really still compilers in use > that don't implement C99? > I still build Fossil on a circa-2002 iBook. (See section 4 of http://fossil-scm.org/fossil/doc/trunk/www/build.wiki). I do not know if it implements C99 or not, but if I had to guess I would say "not". -- 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] How to host fossil repositories on web server that supports only FastCGI interface?
On 8/2/16, John Found wrote: > So, is it possible to use fossil in CGI mode without wrapping it with bash > CGI script? > Simply run "fossil cgi FILE" where FILE is the name of a configuration file. FILE should look like this: repository: /home/of/your/repository.fossil Other lines are possible, but the above is sufficient to get you started. Probably this deserves to be better documented.... -- 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] How to host fossil repositories on web server that supports only FastCGI interface?
On 8/2/16, Richard Hipp wrote: > > Simply run "fossil cgi FILE" where FILE is the name of a configuration > file. FILE should look like this: > > repository: /home/of/your/repository.fossil > > Other lines are possible, but the above is sufficient to get you > started. Probably this deserves to be better documented Slightly improved documentation here: https://www.fossil-scm.org/fossil/help?cmd=cgi -- 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] How to host fossil repositories on web server that supports only FastCGI interface?
On 8/2/16, John Found wrote: > > But how to make web server run fossil with command line arguments? > Some wrapper is still needed, or I am missing something? > I'm trying to come with documentation to better explain how that works. My *first draft* is currently up at https://www.fossil-scm.org/fossil/doc/trunk/www/aboutcgi.wiki and let me know if it helps any. Remember that the document is a work-in-progress. -- 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] tags manifest
On 8/3/16, Jan Danielsson wrote: >We've been using a version of the branch for a pretty long time now, > and I'm starting to feel that it's ready for trunkification. > >Thoughts? I am not completely happy with the format of the manifest.tags file. The current format is: branch=jan-manifest-tags jan-manifest-tags I think it should be: branch jan-manifest-tags tag jan-manifest-tags Furthermore, it appears the "branch" line is only written for the manifest.tags of a local checkout and is omitted for tarballs and zip archives. Why is that? Should we move this discussion to fossil-...@lists.fossil-scm.org? -- 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] change sync URL
On 8/10/16, jungle Boogie wrote: > > I received 4-5 spam emails when posting this message. > Yes, I'm very sorry. I wish there was something I could do about that. I tried configuring the mailing list so that it obscured the poster's email address, but that change was not well received and so it has been undone. I have found that spam filters quickly learn the pattern of the porn-spam that results from posting to this list and will reliably filter it after very little training. Just press the Spam button on your email reader for one or two of the porn-spam replies and that should take care of the problem. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] some interesting (db)stat
Methinks you have some highly compressible text in that repo :-) On 8/12/16, Gour wrote: > Hello, > > today Fossil surprised me when showing me dbstat output for one of my > private repos: > > repository-size: 2480128 bytes (2.5MB) > artifact-count:621 (stored as 312 full text and 309 delta blobs) > artifact-sizes:4374330 average, 9758918 max, 2716458939 bytes > (2.7GB) total compression-ratio: 1095:1 > check-ins: 311 > files: 1 across all branches > > > Not bad, right. ;) > > > Sincerely, > Gour > > -- > Thus the wise living entity's pure consciousness becomes covered by > his eternal enemy in the form of lust, which is never satisfied and > which burns like fire. > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fix for stash-next pointer
On 8/13/16, Kain Abel wrote: > > after > $ fossil stash pop > or > $ fossil stash rm > is the pointer for the next stash id (stash-next in table vvar) untouched. And thus each new stash has a unique id. Is that a problem? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fix for stash-next pointer (fix for the fix)
On 8/13/16, Kain Abel wrote: > The next try: another version. > > (Prevents the growth from stash id after many push and pop operations.) But you still have not made your case for why growth of the stash id is a bad thing. > > Just for the sake of completeness, > Kain > -- 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] /test_env page outputs headers
On 8/23/16, Svyatoslav Mishyn wrote: > Hi all, > > "Environment Test" page outputs HTTP headers, > when "Show Cookies" option is enabled, > and when `fossil ui` or `fossil server` is running. This is a deliberate feature. Perhaps you can suggest a way to document it 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] /test_env page outputs headers
On 8/23/16, Svyatoslav Mishyn wrote: > (Tue, 23 Aug 16:38) Svyatoslav Mishyn: >> It's not affected when fossil is run as a CGI program. > > Oops, sorry for the noise. > > I just didn't get those headers, when I tested it, > and I thought that there was some inconsistency. The HTTP header is not shown in CGI mode (or SCGI mode) because Fossil does not have access to the information then. Only in HTTP mode (from the "fossil ui" or "fossil server" commands) does Fossil have access to the HTTP headers and hence only then is it able to show the headers. -- 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] Pie Chart: two items are not very readable
On 8/24/16, Svyatoslav Mishyn wrote: > Hello, > > on the page /repo-tabsize I got two items that are not very readable > see screenshot (items "event" and "delta"): > https://cloud.openmailbox.org/index.php/s/WYyIi5ZNpfuMpfY Test case: https://www.fossil-scm.org/fossil/test-piechart?data=50+a%0A3+bbb%0A3+c%0A2+d%0A2+e%0A43+f%0A -- 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] Pie Chart: two items are not very readable
On 8/24/16, Richard Hipp wrote: > On 8/24/16, Svyatoslav Mishyn wrote: >> Hello, >> >> on the page /repo-tabsize I got two items that are not very readable >> see screenshot (items "event" and "delta"): >> https://cloud.openmailbox.org/index.php/s/WYyIi5ZNpfuMpfY > > Test case: > https://www.fossil-scm.org/fossil/test-piechart?data=50+a%0A3+bbb%0A3+c%0A2+d%0A2+e%0A43+f%0A > A fix is now checked in, and installed on the server. -- 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] Pie Chart: two items are not very readable
On 8/24/16, Richard Hipp wrote: > On 8/24/16, Svyatoslav Mishyn wrote: >> Hello, >> >> on the page /repo-tabsize I got two items that are not very readable >> see screenshot (items "event" and "delta"): >> https://cloud.openmailbox.org/index.php/s/WYyIi5ZNpfuMpfY > > Test case: > https://www.fossil-scm.org/fossil/test-piechart?data=50+a%0A3+bbb%0A3+c%0A2+d%0A2+e%0A43+f%0A > In case anybody is reading this on an archive: I have changed the way the test-piechart page works, so the link above no longer functions. -- 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] Pie Chart: two items are not very readable
On 8/24/16, Svyatoslav Mishyn wrote: > (Wed, 24 Aug 11:25) Richard Hipp: >> In case anybody is reading this on an archive: I have changed the way >> the test-piechart page works, so the link above no longer functions. > > Floating-point numbers are allowed..? > Try this: > https://www.fossil-scm.org/fossil/test-piechart?data=50,3,3,2,2,43,9,99.99 > Yes, floating-point is allowed. But not scientific notation. The link above looks to be correctly formatted. Do you see a problem that I am missing? -- 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] How to import a few commits from a git mirror?
On 8/27/16, Natacha Porté wrote: > Hello, > > Short version: I have a git repository built a mirror of a main > repository, a few changes happened to the git repository, and I would > like to find a way to bring these changes back to the fossil repository > so that the git repository can again be a simple mirror. One of my long-term goals is to enhance Fossil so that it can push/pull from a git mirror, or so that a git mirror can push/pull from the main Fossil repository. Unfortunately, that isn't going to help you now. Or this week. -- 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] Small tweak to fix compilation issue (at least on Solaris 11)
On 8/29/16, Warren Young wrote: > > That’s only a partial fix. You also need to add a prototype for > uvstat_page() to one of the header files that src/doc.c includes, so the > compiler would catch that. The header files in Fossil are automatically generated. (See the description of "makeheaders" at https://www.fossil-scm.org/fossil/doc/trunk/www/makefile.wiki) Sometimes the makefile gets confused and it is necessary to do "make clean fossil" in order to regenerate the header files correctly. Probably this is a bug in the makefile, but the problem comes up so rarely and the workaround so easy that nobody has taken the time to track down the bug and fix it. -- 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] Small tweak to fix compilation issue (at least on Solaris 11)
On 8/29/16, Karel Gardas wrote: > Hmm, conversation suggest that this is not bug in the code but trivial > user error. OK! Half-true. Your original bug report was correct. And that problem should be fixed with the most recent Fossil check-in. The subsequent report that your patch was incomplete was the incorrect part. Please update to the latest "trunk" Fossil check-in and verify that the problem is now fixed. -- 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] Small tweak to fix compilation issue (at least on Solaris 11)
On 8/29/16, Warren Young wrote: >> >> The header files in Fossil are automatically generated. > > Okay, in that case, the problem is that doc.c doesn’t include unversioned.h, That's not how makeheaders works. The prototype for the uvstat_page() function should be included in the *.h file for any module that invokes that function. So, the uvstat_page() function should appear, automatically, in the doc.h file. And, that is exactly what happens on my system. drh@bella:~/fossil/m1$ grep uvstat_page bld/*.h bld/doc.h:void uvstat_page(void); bld/unversioned.h:void uvstat_page(void); Notice that the uvstat_page() prototype appears in the header file of every module that uses that routine. -- 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] Do, fossil, when running in cgi mode, compress the response body?
On 8/29/16, John Found wrote: > I am running fossil in cgi mode on an experimental web server. The web > server supports only FastCGI interface, so the fossil is spawned using > "fcgiwrap" tool. Anyway, we are hunting for a problem. > > When requesting the main page "/fossil/repo/name/", fossil returns 302 and > redirects to "/fossil/repo/name/index". > The 302 response, contains some message body "Moved" which is ignored by the > browser. > > But if the request contains the header "Accept-Encoding: gzip", the response > contains the header "Content-Encoding: gzip" and > it seems that fossil compresses the response body. Is this the case, or the > mess happens somewhere else. Yes, Fossil compresses the reply in CGI mode. > IMHO, the cgi script should not return "Content-Encoding" header, because > this is the function of the web server. > I have never before encountered that opinion. It would be a problem for me, because my bespoke webserver used on the www.fossil-scm.org website does NOT attempt to compress CGI content. -- 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] Unversioned files.
A new feature of Fossil (currently unreleased and only available to people who are willing to recompile the code on trunk) is "unversioned files". https://www.fossil-scm.org/fossil/doc/trunk/www/unvers.wiki The "Download" page on the canonical Fossil website is now implemented using these unversioned files, which means that mirrors that sync with the -u option also mirror the Download page content. Your feedback on this new feature is appreciated. -- 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] Unversioned files.
On 9/2/16, Gour wrote: > On Tue, 30 Aug 2016 14:31:06 -0400 > Richard Hipp wrote: > >> Your feedback on this new feature is appreciated. > > I've added one whole directory with several subfolders (via shell > scripting) and an see them with 'fossil unver ls'. > > However, the same set of files is also listed as output of 'fossil > extras'. Is it afeature that one has to explicitly ignore them not to be > shown with 'extras' or do I miss something? At the moment, unversioned files are not part of the check-out. So this is a feature. I have the request to optionally include unversioned files in the check-out. But that is not yet implemented. -- 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] Infinite loop on merge
On 9/6/16, Andy Goth wrote: > > Today I upgraded from Fossil 1.34, and it > looks like I'm going to have to switch back. > Try using trunk before you downgrade to 1.33 or 1.32. -- 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] Infinite loop on merge
On 9/6/16, Andy Goth wrote: > The latest trunk is broken (w.r.t. the merge in question), as is apparently > everything starting with 41c2220934. Version 1.34 is good, as is the > version immediately before 41c2220934. I see no reason to downgrade to > anything before 1.34, since that's what I've been using successfully since > its release. I misunderstood. So apparently the problem is in the merge-renames branch. Joel? -- 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] Infinite loop on merge
On 9/6/16, Andy Goth wrote:
>
> The repository is private, sorry, but I should be able to help with
> debugging.
>
Just a guess:
Index: src/merge.c
==
--- src/merge.c
+++ src/merge.c
@@ -395,11 +395,11 @@
}
if( zPivot ){
vAncestor = db_exists(
"WITH RECURSIVE ancestor(id) AS ("
" VALUES(%d)"
- " UNION ALL"
+ " UNION"
" SELECT pid FROM plink, ancestor"
" WHERE cid=ancestor.id AND pid!=%d AND cid!=%d)"
"SELECT 1 FROM ancestor WHERE id=%d LIMIT 1",
vid, nid, pid, pid
) ? 'p' : 'n';
--
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] Unversioned files.
On 9/9/16, Adam Jensen wrote: > On 09/05/2016 05:23 PM, Adam Jensen wrote: >> B. I suspect the storage requirement will be twice (2x) the data size - >> the data is stored once in the Fossil database and another copy would >> exist in the file-system [as a check-out]. > > I wonder if it would be nifty if Fossil could export a set (or several > sets) of files as a FUSE[1] file-system? Already does that. https://www.fossil-scm.org/fossil/help?cmd=fusefs -- 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] feature requests
On 9/14/16, Aldo Nicolas Bruno wrote: > > Another question... there is a way to link to a directory of the latest > check-in? > by example this link points to directory cairo, but of a particular > check-in... > https://pizzahack.eu/fossil/thunderchez/dir?ci=3c717fb0e55501e7&name=cairo > https://pizzahack.eu/fossil/thunderchez/dir?ci=trunk&name=cairo In other words, change the ci= value to the name of any branch and it uses the most recent check-in on that branch. Or make it ci=tip and it will use the most recent check-in on any branch. -- 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] feature requests
On 9/14/16, Aldo Nicolas Bruno wrote: > Il 14/09/2016 18:33, Richard Hipp ha scritto: >> https://pizzahack.eu/fossil/thunderchez/dir?ci=trunk&name=cairo >> >> In other words, change the ci= value to the name of any branch and it >> uses the most recent check-in on that branch. Or make it ci=tip and >> it will use the most recent check-in on any branch. > Thanks for the reply ;) > This is also possible with files? Anywhere you can put a SHA1 hash prefix for a version name, you can also supply a branch name (which will resolve to the most recent check-in on that branch) or a tag (which will resolved to whatever check-in is tagged with that tag) or "tip" to mean the lastest check-in. There are other options too, like "trunk:2005-01-17" which means the last checkin on the branch "trunk" before 2005-01-17. > > https://pizzahack.eu/fossil/thunderchez/?ci=trunk&name=cairo/cairo-functions.ss > Whether or not this works for a specific webpage depends on whether or not that webpage lest you specify a version number. Which webpage did you have in mind? -- 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] feature requests
On 9/15/16, Martin Gagnon wrote: > > Hints: For all fossil web pages usage information, (and cli usage). You can > go on the '/help' page of any fossil repo. > > E.g. https://pizzahack.eu/fossil/thunderchez/help > That documentation exists, but it is incomplete and not well formatted. It is on my to-do list to improve it. You may have noticed some recent check-ins on trunk relating to refactoring the help-text logic. More of that is planned. But, as Martin says, there is *some* information there already. It just needs to be improved. -- 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] Compilation error with latest trunk
On 9/19/16, Tony Papadimitriou wrote:
> manifest_.c:2631: extra '#endif'.
> tar_.c:708: Unterminated "{"
> Errors while processing "tar_.c"
> NMAKE : fatal error U1077: '.\makeheaders.exe' : return code '0x2'
> Stop.
I'm unable to reproduce the problem on Windows10.
* Fresh Fossil checkout
* cd win
* nmake /f makefile.msc fossil.exe
Compiles without error or warnings. Resulting binary works great.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil server not reliably serving css and js
On 9/26/16, Warren Young wrote: > On Sep 25, 2016, at 11:27 PM, Maninder Singh Suri > wrote: >> >> >> Now when I open any page, these js and css files being served are a hit >> and miss. >> Sometimes, these laod up fine, but other times, the js or the css fails to >> load. > > I think I’ve seen the same thing under different circumstances. A doc URL > in a wiki document pointing at an SVG graphic I want displayed inline in the > wiki article doesn’t always load on the first try. > > I haven’t bothered reporting it because I can just reload to fix it, but for > files critical to the skin, I can see that that would be more burdensome in > your case. I need a way to reproduce the problem in order to fix it. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil server not reliably serving css and js
On 9/26/16, Warren Young wrote: > > I don’t recall seeing inline images in any of the SQLite embedded docs. The Fossil homepage (https://www.fossil-scm.org/) is an embedded document and it has the lizard embedded image. -- 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] Files named "AUX" on Windows
See https://www.fossil-scm.org/aux-test/doc/trunk/aux.md Apparently if a Fossil repository contains a file whose basename is "aux", then an attempt to open or check-out that repo fails with an error. Only the basename needs to be "aux". The full name can be things like "src/aux.c" or "doc/aux.txt". Does anybody know of a reasonable work-around? -- 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] Next Fossil release
I'm thinking we should cut a new Fossil release shortly after the SQLite 3.15.0 release (which should be out in less than two weeks). Key feature for Fossil 1.36 is the addition of unversioned content. -- 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] Files named "AUX" on Windows
On 10/5/16, Warren Young wrote: > > Agreed. If your repository has such file names in it, working around the > Windows limitation in Fossil just boots the problem a few squares down the > sidewalk, where it will be stumbled upon shortly by some other tool. For this reason, the current fix is simply to output a more helpful error message that tries to explain the situation. Probably we also need to also fix Fossil so that it doesn't give up and die when it encounters an error like this but instead at least tried to check out all the other files. Perhaps there should also be warnings when one does "fossil add" or "fossil mv" to create a disallowed filename on unix - a warning to say that this will work fine on unix but will fail when you move the change to windows. > > That said, if y’all decide to support AUX and such on Windows anyway, I > wrote some code to do this recently, just to prove a point on > unix.stackexchange.com. :) > > http://pastebin.com/rTs88KmD > > The code is written for the NUL case, but it’s the same for AUX, CON, etc. > > If someone wants to use that as a basis for a Fossil patch, the code is > currently licensed under cc-by-sa 3.0. That may be liberal enough to > include it in Fossil as-is. > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] visual studio solution and project file for fossil
On 10/5/16, arnoldemu wrote: > > I see that fossil can be built with a batch file "buildmsvc.bat" which uses > the command-line visual studio compiler. It uses some kind of custom build > where the headers which are needed are added to the files and output into a > separate directory. I don't really understand fully how this works and is a > guess from what I have seen so far. To build using msvc from the command-line: cd win nmake /f makefile.msc A description of the build process is found in https://www.fossil-scm.org/fossil/doc/trunk/www/makefile.wiki Fossil uses a great deal of generated code. IDEs such as Visual Studio, on the other hand, are usually built around the assumption that all code is hand-written. Generated code is a more powerful concept, and ultimately makes development easier and less error prone. But since IDEs do not support it well, I think you will have difficulty putting together a "solution" for Fossil. You can run Fossil in the visual studio debugger. Joe showed me how to do that once. I could probably fumble my way through doing it again, but I'm not comfortable trying to describe the process. But basically, you build the fossil.exe using nmake, then you fire up Visual Studio to single-step through the code. This gives you the best of both worlds. You can use powerful generated code techniques from the command-line to construct the executable. Then you can use your nice GUI interface for single-stepping through the code to figure out why it isn't working. > > I want to make a solution for fossil so I can build fossil under visual > studio itself from the IDE itself. I can then use the IDE's debugger. I > tried to add all the source files from inside the src directory but that > didn't work. So I then ran the batch file, waited for it to build and then > used the source files from the msvcbld and that didn't seem to work either. > > So I have failed so far and wondered if anyone has made a solution and if > they did, how did they do it? > > The second question was: > - Is there a way I can modify (or pass a parameter) to the buildmsvc.bat to > make a "debug" build without the compiler doing optimisations and with it > generating a debug pdb. I could also debug fossil from within visual studio > this way. > > Thanks > > Kevin > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] visual studio solution and project file for fossil
On 10/5/16, Ross Berteig wrote: > > Note that building for 64-bit needs something trickier than just > following that recipe from a 64-bit VisualStudio prompt. Really? Because just typing "nmake /f makefile.msc" from a 64-bit VisualStudio prompt works fine for me on Windows10 with VS2012. -- 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] Cutting fossil repository
Maybe you could make a copy of the repo then "purge" all those check-ins and files you don't want from the copy: https://www.fossil-scm.org/fossil/help?cmd=purge On 10/7/16, Zeev Pekar wrote: > Hello, > > if one needs to provide a partial repo (from the beginning till certain > date/commit) to a third party - how should he generate this new partial > repo from the existing full one? > > 1) is there a way to "cut" a repo till certain date/commit? if yes - > how? > > 2) is it possible to delete all the commits (which were made later than > the required date) by hand, one by one? if yes - how? > > Thank you in advance, > Zeev > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Cutting fossil repository
On 10/7/16, sky5w...@gmail.com wrote: > Cool. > How does 'fossil purge obliterate' differ from 'fossil shun'? "shun" rmembers the SHA1 hash and will never again accept that SHA1 hash on a sync. "fossil purge whatever" simply deletes the artifacts from the local repo. They will be restored on a sync from another repo that holds them. I think. Double-check before relying on what I said above. :-) > Is shun obsoleted or superseded by purge now? > Can I achieve the obliteration entirely from the cmd line? > > Thanks! > -- 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] Cutting fossil repository
On 10/8/16, Zeev Pekar wrote: > Could somebody, please, provide an example of deleting a commit, using > a) purge > b) shun > If you need an example in order to pull this off, then it is not something you should attempt. The use of purge and shun is for experts only. If you do not have a full understanding of what you are doing, you will likely end up making a mess. Fossil is designed to never forget things. You are asking it to forget, which goes against its very nature. Some provisions are made for this, for exceptional circumstances. But those provisions are very seldom used, and are not novice-friendly. -- 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] Cutting fossil repository
On 10/8/16, Zeev Pekar wrote: > Ok. I understood the consequences - I'll operate on a copy of a repo. So > could you, please, provide the two examples anyway? > I do not know how to improve upon https://www.fossil-scm.org/fossil/help?cmd=purge If you can explain what part of the documentation is unclear, perhaps we can clarify it for you. -- 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] Cutting fossil repository
On 10/8/16, Zeev Pekar wrote: > > 2) using shun: > > fossil shun 86848307235407 (this is just a guess since this one I > couldn't find in docs) > > Am I right? There is no "shun" command. Shunning must be done from the web interface. -- 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] Cutting fossil repository
On 10/8/16, Adam Jensen wrote: > > The reluctance of some programmer communities to provide examples has > always surprised me. In this case, the documentation (https://www.fossil-scm.org/fossil/help?cmd=purge) consists of a series of examples, each followed by an explanation of what that example does. I do not know how to make the documentation any clearer. Contributions from others who do know how to make better documentation will be greatly appreciated. -- 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] Cutting fossil repository
On 10/9/16, Zeev Pekar wrote: > I sent two examples and asked whether they were correct. A simple "yes" > or "no" would be enough... I don't know. I don't remember. In order to find out, I would either (1) consult the documentation or (2) try the commands out to see what happened, or (3) both. But you can do that as easily as I can. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fossil on HN
https://news.ycombinator.com/item?id=12673229 -- 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] How to use login-group
On 10/11/16, John P. Rouillard wrote: > > Hi all: > > I am trying to set up a series of fossil repos for a volunteer coding > project. > > I have a script that I can use to set up the repos, and the plan is to > have the developers self register at the event. > > I would like to have the sign up once and get access to multiple > repos. > > It seems that login group shoud be able to do this, but I haven't > found any documentation on how it should work. > > Reading through emails, it looks like I need to: > >Choose one repo to be the master > >Enter the server side path to the repo as: >Repository filename in group to join > > Then provide admin credentials on the master repo (I assume > so it can modify the login group config on the master repo). > > Then choose a name for the group. > > Once I have done that I need to have the developers register on the > master repo. > > To allow them to log into the web or clone/push/pull I need to: > > fossil config pull -R museum/repo.fossil user museum/master.repo > > to copy all the users from the master to each repo. > > Is this correct? > I think that is all correct, yes. -- 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] fast-export to git produces unimportable dump
On 10/12/16, Svyatoslav Mishyn wrote: > (Thu, 13 Oct 00:19) Osamu Aoki: >> I have no idea for "error: Multiple updates for ref ..." but at least >> git repo is usable one after executing "git checkout trunk". > > to reproduce that error: > /home/juef/fossil/test: f co trunk > /home/juef/fossil/test: date >> z && f ci -m t1 --tag one --tag two > /home/juef/fossil/test: date >> z && f ci -m b1 --tag one --tag two --branch > br > /home/juef/fossil/test: f2g test > Unpacking objects: 100% (7/7), done. > error: multiple updates for ref 'refs/tags/one' not allowed. My guess: Git does not allow more than a single instance of the tag named "one". In other words, all tags must be unique in Git. -- 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] andygoth-circa
On 10/12/16, Andy Goth wrote: > I recently created a branch called andygoth-circa which adds a "circa" link > to the info web page. This link shows timeline events near the selected > check-in even if they're not ancestors or descendents. It's just for > showing context of what was happening around the same time. Did you know you can already get that on trunk by clicking on the Date: value? > Sorry I haven't been involved in email much lately. Work has been > incredibly busy. I'm using Fossil every day, and it's been very helpful. > People on my team tell me it's a massive timesaver compared to what we > would have been stuck doing. > Glad to you have you around. And glad Fossil is working well for you! -- 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] Errors trying to compile
On 10/12/16, Dan Raymond wrote: > Thanks. > > What is best environment etc to compile under windows? mingw/msys works. Also MSVC. I build the precompiled binaries for the Fossil homepage using mingw/msys. > > > > 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 > 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 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 >> >> > -- 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] www.fossil-scm.org down?
On 10/15/16, Johan Kuuse wrote: > Hi, > > I cannot acces www.fossil-scm.org > Anyway, www.fossil-scm.org:8080 responds, so it seems to be a problem > with the web server. xinitd, which manages inbound connections on port 80, had crashed. I restarted it. Things should be working again. Thanks for the report. I had not noticed it before because I always use https instead of http. https on port 443 is managed by stunnel4. It was still running. Apache manages port 8080 and it was still running. Backup servers at http://www2.fossil-scm.org/ and http://www3.fossil-scm.org/ were both still running. -- 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] www.fossil-scm.org down?
FWIW, sqlite.org was also down (since it is on the same machine and uses the same xinetd process to respond to requests, but nobody bother to report that On 10/15/16, Richard Hipp wrote: > On 10/15/16, Johan Kuuse wrote: >> Hi, >> >> I cannot acces www.fossil-scm.org >> Anyway, www.fossil-scm.org:8080 responds, so it seems to be a problem >> with the web server. > > xinitd, which manages inbound connections on port 80, had crashed. I > restarted it. Things should be working again. Thanks for the report. > I had not noticed it before because I always use https instead of > http. > > https on port 443 is managed by stunnel4. It was still running. > Apache manages port 8080 and it was still running. Backup servers at > http://www2.fossil-scm.org/ and http://www3.fossil-scm.org/ were both > still running. > > -- > D. Richard Hipp > d...@sqlite.org > -- 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] www.fossil-scm.org down?
On 10/16/16, Johan Kuuse wrote: > El 16 oct. 2016 11:08, "Johan Kuuse" escribió: > >> Are you running any supervisor process for xinetd? >> >> I used to run "daemontools" in the passed, worked quite well, but >> nowadays, "runit" seems to be a common alternative. >> >> Or maybe you could just run a cron job for alerts, to keep the downtime >> to >> a minimum. xinetd has never given trouble before... -- 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] disabled due to excessive bounces (again?)
I was just now booted from my own mailing list for excessive bounces. ;-) Dunno what that is about... It was easy enough to click on the link in the notification message to resubscribe. -- 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] Repository question
On 10/18/16, Scott Doctor wrote: > > Assume many check-ins occurred with many changes over many > files. Seems that if something glitches everything can become > out of sync and hard to recover. My question, is there is a way > to tell fossil to store the complete versions of the documents > instead of it recreating the documents by piecing all those > fragments together. My concern is that something goes wrong, > perhaps a bad disk sector not necessarily a software issue, that > would further complicate recover. > Content is checked to make sure it is recoverable prior to running the COMMIT that stores it in the database. If any content is not recoverable, Fossil runs a ROLLBACK instead. See https://www.fossil-scm.org/fossil/doc/trunk/www/selfcheck.wiki for further information. To guard against hardware bugs damaging the database, clone the database on multiple machines and keep them in sync automatically. You are more likely to have a complete disk failure or some other local disaster (a fire or flood) and loss everything than a single bad sector. Turning off the delta compression will not save you from a flood or fire. So if you have important content, be sure to clone the repo to multiple geographic locations. The Fossil self-hosting repositories are stored on leased servers located in three different data centers, each at least 500 miles distant from the others. Server space is leased from two different companies to prevent a common-mode failure at a single ISP. All content is kept in sync using cron jobs that runs "fossil sync -u" very hour or so. And, of course, there are countless private clones of Fossil that can also be used for recovery. There was once a double-bug in Fossil and stunnel that corrupted the canonical Fossil repository database, breaking the delta chain, and making downstream content unrecoverable. The first problem was that stunnel was launching Fossil without opening file descriptor 2 (stderr). The database was opened on the first available file descriptor, which was 2. Then a bug in Fossil caused an assert() to fire which did write(2,...) to put an error message smack in the middle of the database file. All content was recovered using one a clone. SQLite was subsequently enhanced to never open a database using a file descriptor less than 3 so this error can never happen again. But who knows what other subtle problems lurk undetected. Also clone data you care about. -- 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] Can fossil bind to a single address?
I think it is reasonable to request a new option to 'fossil server" to bind to a single address (other than loopback). But I'm unwilling to make that change until the next release cycle. So are there any objections now to taking trunk as the 1.36 release so that we can move forward on these kinds of things? -- 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] features I'd like to have in fossil
On 10/22/16, Nikita Borodikhin wrote: > > What I expected from this post is, well, to share my problems with the > community. There was a chance I could get a discussion on the problems > to better understand what people think and whether they find it > important or not. That could help me to set the right priority to my work. And your input is greatly appreciated. Thank you for contributing. I'm sure your ideas will have at least some influence on future directions. -- 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] windows compiling with MS VC
On 10/24/16, jungle Boogie wrote: > Hi All, > > So I installed Microsoft Visual Studio and within that toolkit, I need > to use VC to build the fossil.exe file, right? Yes, except that Andy broken the build while we were in the quiet period leading up to the 1.36 release and I failed to notice the problem. Hence, the 1.36 tarball will not build (without patching) using MSVC. Bummer. Maybe 1.37 will go better. If you want to build Fossil from sources on windows using MSVC, then use the trunk. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] windows compiling with MS VC
On 10/24/16, jungle Boogie wrote: > > So did you patch prior to making the Windows build and that's how you > have Windows binary? The binary for 1.36 is built using mingw+msys. -- 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] windows compiling with MS VC
On 10/24/16, Andy Bradford wrote: > Thus said Richard Hipp on Mon, 24 Oct 2016 14:17:37 -0400: > >> Yes, except that Andy broken the build while we were in the quiet >> period leading up to the 1.36 release and I failed to notice the >> problem. > > My apologies. Such an obvious C89 problem too, I'm not sure why I didn't > even notice. Sorry. I should have testing on MSVC before tagging the release -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil rebuild on new version(s)?
On 10/26/16, Kain Abel wrote: > Dear readers, > > after a new release is the task 'fossil rebuild $existing_repro' a > SHOULD, a MUST or is it not necessary? There have been no database schema changes, so a rebuild is not necessary. You might want to run "fossil rebuild --compress-only" if you want to minimize the size of your repository/ Also, if you have an older repository, running "fossil rebuild --pagesize 8192 --wal" might give you a small performance increase. But all of this is entirely optional. -- 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] OT: Facebook engineers preferring hg to Git
On 10/27/16, David Mason wrote: > Fossil seems pretty robust in C, but Rust would increase safety confidence. Many people do believe that just because an application is written in Rust rather than in C that it must be "safer". But it is a logical fallacy. You should avoid falling into that trap. Rust helps at preventing certain kinds of bugs (null pointer dereferences, use after free). But those have never been an issue with Fossil. Fossil uses the transactional guarantees of the underlying SQL database engine to ensure the safety of user data. Perhaps Rust might be helpful in systems like Git or Hg which depend on the integrity of the application-level code for data correctness and safety. But as Fossil has no such dependency, rewriting Fossil in Rust would not help in any way. Rather than making Fossil "safer", rewriting it in Rust would simply introduce a bunch of new bugs cause by the inevitable translation errors. See https://www.fossil-scm.org/fossil/doc/trunk/www/selfcheck.wiki for background information. Irony: Isn't Rust heavily dependent upon Git for its package management? So if Hg is written in Rust, does that mean that Hg has a dependency on Git? -- 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] OT: Facebook engineers preferring hg to Git
On 10/27/16, David Mason wrote: > > However, the value of Rust is not simply memory management. The > *considerably* more expressive type system, and the much more robust type > checking can reduce LOC while improving both readability and safety. Perhaps true. But in my brief look at Rust I observed that you really cannot use it effectively without also having to use Git. The two seem closely linked. Is that incorrect? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil check-in [a4bb89ba081e29c5]...
"fossil clean -x" works better than "make clean" or "make distclean". It seems to clear the problem. On 10/27/16, Andy Bradford wrote: > Thus said "Andy Bradford" on 27 Oct 2016 21:42:34 -0600: > >> I always run ``make distclean'' not ``make distclean'' but since you >> suggest it, here's the difference on my system: > > Minor correction, I always run ``make clean'' not ``make distclean'' > > At any rate, this happens on a system that supports FuseFS (at least on > my system) because FOSSIL_HAVE_FUSEFS gets defined in autoconfig.h, but > if there is an #ifdef surrounding the option to include "config.h" inf > fusefs.c, then autoconfig.h will never get sourced, and neither will > FOSSIL_HAVE_FUSEFS when fusefs.c is built. So other parts of Fossil > think that the command is enabled, but fusefs.c itself does not, so it > doesn't get built. Hence the linker error. > > Thanks, > > Andy > -- > TAI64 timestamp: 40005812cb7e > > > _______ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil diff: extra empty lines in non-console output on Windows
On 10/31/16, Artur Shepilko wrote: > I would've > gladly fixed it myself, but have not mailed yet the Contributor Agreement.. > (I have signed it though :) > Please do mail in your CLA. And maybe also post a patch to this mailing list. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil diff: extra empty lines in non-console output on Windows
On 10/31/16, Adam Jensen wrote: > > Would a GPG signed statement suffice? (It doesn't apply to me; I'm just > generally curious). How attached to paper and scribbling is the legal > system? I am attached to dead-tree documents. With prior approval, an email scan can be used instead of sending the original paper via post. -- 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] Is FOSSIL supposed to compile with MSVC14?
On 10/31/16, Tony Papadimitriou wrote: > I can compile fossil just fine (with or without SSL) with MSVC12 > I just installed MSVC14 and I get errors when compiling with the SSL option > (no errors without it). I don't own a copy of MSVC14, so I cannot really say. (Aside: Earlier today, I got work from the repair shop that my win10 machine is dead and too expensive to fix. So I don't even have a Windows10 platform at the moment.) Perhaps you can figure out a work-around or a fix and post patches here, Tony? > > (BTW, SQLite3 also compiles OK with MSVC14). > > So, I wonder if this is normal, or if I should be looking for installation / > configuration problems in my setup. > > Here’s the warnings/errors I get: > > zlib.lib(zutil.obj) : warning LNK4217: locally defined symbol _free imported > in function _zcfree > zlib.lib(gzlib.obj) : warning LNK4049: locally defined symbol _free > imported > zlib.lib(zutil.obj) : warning LNK4217: locally defined symbol _malloc > imported in function _zcalloc > zlib.lib(gzlib.obj) : warning LNK4049: locally defined symbol _malloc > imported > zlib.lib(gzlib.obj) : warning LNK4217: locally defined symbol > ___stdio_common_vsprintf imported in function __snprintf > zlib.lib(gzlib.obj) : warning LNK4217: locally defined symbol __wopen > imported in function _gz_open > zlib.lib(gzlib.obj) : warning LNK4217: locally defined symbol __lseeki64 > imported in function _gz_open > OLDNAMES.lib(open.obi) : warning LNK4049: locally defined symbol __open > imported > libeay32.lib(pem_lib.obj) : error LNK2001: unresolved external symbol > ___iob_func > libeay32.lib(txt_db.obj) : error LNK2001: unresolved external symbol > ___iob_func > libeay32.lib(ui_openssl.obj) : error LNK2001: unresolved external symbol > ___iob_func > ssleay32.lib(t1_enc.obj) : error LNK2001: unresolved external symbol > ___iob_func > ssleay32.lib(d1_both.obj) : error LNK2001: unresolved external symbol > ___iob_func > ssleay32.lib(s3_srvr.obj) : error LNK2001: unresolved external symbol > ___iob_func > libeay32.lib(cryptlib.obj) : error LNK2001: unresolved external symbol > ___iob_func > libeay32.lib(dso_win32.obj) : error LNK2019: unresolved external symbol > _sprintf referenced in function _win32_name_converter > zlib.lib(gzlib.obj) : error LNK2019: unresolved external symbol > __imp__wcstombs referenced in function _gz_open > zlib.lib(gzlib.obj) : error LNK2019: unresolved external symbol __imp__open > referenced in function _gz_open > OLDNAMES.lib(open.obi) : error LNK2001: unresolved external symbol > __imp__open > .\fossil.exe : fatal error LNK1120: 4 unresolved externals > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio > 14.0\VC\BIN\link.EXE"' : return code '0x460' > Stop. > > Thanks. > -- 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] revert of missing files using wildcard not possible.
On 10/31/16, arnoldemu wrote: > > But still it's not possible to revert missing files using a wildcard. I > guess because the shell doesn't know about them and doesn't expand them and > fossil considers the * to be a valid character in a filename. That is correct. That is the unix way. I suppose this is so obvious to people who grew up with Unix that we don't even think about it. Are you coming from a windows background? -- 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] revert of missing files using wildcard not possible.
On 11/1/16, arnoldemu wrote: > > I don't know how shells handle things because I'm not exposed to it > that much and I guess the GUIs I use must "iron-out" some of these > command-line "wrinkles" which I see. Your input is valuable because you see things differently. I have your request to do internal glob expansion for "fossil revert" -- 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] Error compiling FOSSIL trunk
On 11/2/16, jungle Boogie wrote: > On 2 November 2016 at 09:33, Tony Papadimitriou wrote: >> c:\fossil\win\winhttp.h(24) : error C2004: expected 'defined(id)' >> c:\fossil\win\winhttp.h(24) : fatal error C1012: unmatched parenthesis : >> missing ')' >> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual >> Studio >> 12.0\VC\BIN\cl.EXE"' : return code '0x2' >> Stop. >> > > getting the same failure with MSVC 2010 but unix builds pass fine. > Should be fixed now. -- 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] Error compiling FOSSIL trunk
On 11/2/16, Scott Doctor wrote: > Seems to be more problems than usual with this release. That was not a "release" problem. That was a check-in from yesterday. -- 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] More compilation problems with latest trunk
Works fine for me.
https://www.fossil-scm.org/fossil/info/9c211011190bde9a compiled with
either mingw32 or msvc2015.
Maybe you have a bad merge in your check-out. What does "fossil
changes" or "fossil diff" show?
On 11/5/16, Tony Papadimitriou wrote:
> ..\src\sqlite3.c(132731) : error C2143: syntax error : missing ';' before
> '<<'
> ..\src\sqlite3.c(132758) : error C2143: syntax error : missing ')' before
> '->'
> ..\src\sqlite3.c(132758) : error C2143: syntax error : missing '{' before
> '->'
> ..\src\sqlite3.c(132758) : error C2059: syntax error : '->'
> ..\src\sqlite3.c(132758) : error C2059: syntax error : ')'
> ..\src\sqlite3.c(132760) : error C2059: syntax error : 'type'
> ..\src\sqlite3.c(132761) : error C2059: syntax error : 'for'
> ..\src\sqlite3.c(132761) : error C2143: syntax error : missing '{' before
> '<'
> ..\src\sqlite3.c(132761) : error C2059: syntax error : '<'
> ..\src\sqlite3.c(132761) : error C2143: syntax error : missing '{' before
> '++'
> ..\src\sqlite3.c(132761) : error C2059: syntax error : '++'
> ..\src\sqlite3.c(132761) : error C2059: syntax error : ')'
> ..\src\sqlite3.c(132850) : error C2143: syntax error : missing '{' before
> '->'
> ..\src\sqlite3.c(132850) : error C2059: syntax error : '->'
> ..\src\sqlite3.c(132851) : error C2371: 'whereInfoFree' : redefinition;
> different basic types
> ..\src\sqlite3.c(129702) : see declaration of 'whereInfoFree'
> ..\src\sqlite3.c(132852) : error C2059: syntax error : 'return'
> ..\src\sqlite3.c(132853) : error C2059: syntax error : '}'
> ..\src\sqlite3.c(133154) : error C2079: 'yy354' uses undefined struct
> 'LimitVal'
> ..\src\sqlite3.c(135436) : error C2224: left of '.pLimit' must have
> struct/union type
> ..\src\sqlite3.c(135436) : error C2224: left of '.pOffset' must have
> struct/union type
> ..\src\sqlite3.c(135436) : error C2198: 'sqlite3SelectNew' : too few
> arguments for call
> ..\src\sqlite3.c(135652) : error C2224: left of '.pLimit' must have
> struct/union type
> ..\src\sqlite3.c(135652) : error C2224: left of '.pOffset' must have
> struct/union type
> ..\src\sqlite3.c(135655) : error C2224: left of '.pLimit' must have
> struct/union type
> ..\src\sqlite3.c(135655) : error C2224: left of '.pOffset' must have
> struct/union type
> ..\src\sqlite3.c(135658) : error C2224: left of '.pLimit' must have
> struct/union type
> ..\src\sqlite3.c(135658) : error C2224: left of '.pOffset' must have
> struct/union type
> ..\src\sqlite3.c(135661) : error C2224: left of '.pOffset' must have
> struct/union type
> ..\src\sqlite3.c(135661) : error C2224: left of '.pLimit' must have
> struct/union type
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio
> 12.0\VC\BIN\cl.EXE"' : return code '0x2'
--
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] Database corruption when interrupting 'status'
I don't think "fossil status" writes to the database, so I do not see how it is possible for it to corrupt the database. My guess is that the database was corrupt before. Please send me your repository by private email. On 11/24/16, Ron Aaron wrote: > I did a 'fossil status' on a smallish repo of mine. While it was > running, I did Ctrl+C to stop it. > > When I did 'status' again, it reported a corrupt database. I tried > 'fossil rebuild', and get: > > 76.8% complete... > SQLITE_CORRUPT: database corruption at line 60013 of [bee2859b95] > SQLITE_CORRUPT: database corruption at line 60055 of [bee2859b95] > SQLITE_CORRUPT: statement aborts at 23: [SELECT rid, size FROM blob > /*scan*/ WHERE NOT EXISTS(SELECT 1 FROM shun WHERE uuid=blob.uuid) > AND NOT EXISTS(SELECT 1 FROM delta WHERE rid=blob.rid)] database > disk image is malformed > fossil: SQL error: database disk image is malformed > > I've seen this various times, but only now have seen a particular repro > step. I'm running on Linux (Mint 17.3) with the latest fossil. > > Question: beside simply re-cloning the repo, is there a way to recover > from this? > > > -- > Ron Aaron, CTO > Aaron High-Tech, Ltd. > +1 425.296.0766 > +972 52.652.5543 > GPG Key: 91F92EB8 > <https://pgp.mit.edu/pks/lookup?op=get&search=0xC90C1BD191F92EB8> > <http://8th-dev.com> > -- 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] Sync doesn't include non-artifact changes?
On 11/28/16, Warren Young wrote: > I’ve noticed that if I make a change to a non-artifact setting in the > repository on a different machine that re-syncing does not give me a copy on > my machine. > > Examples: > > - Skin changes > - Ticket tracker customizations > - Everything in Admin > Settings > > If I close the repo, re-clone, and reopen it on my local machine, Fossil UI > locally matches what I see via “fossil server” on the remote machine, so it > must be sending all of these things with the clone. > > Is this intentional or just an oversight waiting for someone to fix it? > This is by design. The idea is that there might be multiple clones of a project that are under different administrative domains where the various administrators want different configuration settings. For example, somebody might want to set up a clone of the Fossil self-hosting repository that used a different skin. And so the settings are not synced automatically. To pull configuration changes use: fossil configuration pull all You can substitute various other keywords for "all" to pull only those parts of the configuration you care about: email, project, shun, skin, ticket, or user. To sync up everything on all your repositories, run: fossil all config pull all -- 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] New "fossil all ui" command
There is now a "fossil all ui" command that pops up a list of all known repositories. It appears to work on both unix and windows. But I had to do a lot of cleanup to the --baseurl logic in order to get this working. I *think* the --baseurl option still works as it used to, but I am not completely certain. If you are using --baseurl, I would appreciate it if you could try out the latest trunk version of fossil and let me know whether or not it is still working. -- 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] download compressed tarball from repository
On 12/10/16, Will Parsons wrote: > In one of my projects using Fossil, I wish to provide the software both as a > zip file and a compressed tarball. In fact, I thought I'd already done this > and it was working by providing the following links: > > Current trunk (zip file) > > Current trunk (compressed tar > file) The name of the page is /tarball not /tar See https://www.fossil-scm.org/fossil/help for a complete list of supported web pages and see https://www.fossil-scm.org/fossil/help?cmd=/tarball for the sketchy documentation on the /tarball page. (If you want to contribute, a good starting point might be to update some of the documentation for the various webpages that Fossil generates. :-)) -- 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] db errors after Ctrl-C
On 12/13/16, rosscann...@fastmail.com wrote: > SNIPPET 1 > C:\Users\Ross\src>fossil commit -m "created" > ./math/src/transforms.rs contains mixed line endings. Use --no-warnings > or the "crnl-glob" setting to disable this warning. > Commit anyhow (a=all/c=convert/y/N)? > *** I hit Ctrl-C here *** > Abandoning commit due to mixed line endings in ./math/src/transforms.rs > SQLITE_MISUSE: API call with invalid database connection pointer > SQLITE_MISUSE: misuse at line 138842 of [707875582f] > ^C Can you run fossil in a debugger - set a breakpoint on the fossil_sqlite_log() function, then provoke the behavior above. When you hit the breakpoint, capture a stack trace and post it to the list. That will probably make the problem obvious. -- 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] Timeline bug: horizontal merge arrow without vertical
On 12/11/16, Andy Goth wrote: > http://core.tcl.tk/tcl/timeline?a=b40778af44&m=7054e2f2eb Fixed. > > The marked check-in merges from trunk, but trunk is not visible on the > timeline. In similar situations in the past I believe there were merge > arrows coming from the bottom of the timeline, but in this instance > only the horizontal line is shown. > > Fossil version 6f3ec1bef6. > > Also, yeah, I've gone back to being too busy to do Fossil development. > Sorry about that. > > -- > Andy Goth | > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Merge failed with SQL error
On 12/18/16, Thomas Bilk wrote: > I have had the same issue with a merge with versions 1.35, 1.36 and a > recent trunk build. I finally managed to merge my branches with > version 1.34 of Fossil. So I guess the problem might stem from the > `merge-renames` branch > (http://fossil-scm.org/index.html/timeline?t=merge-renames), that > happened in May 2016. > > What's odd is that my merge did not contain any renames. However > before I had the SQLITE_CONSTRAINT error, the merge tried to delete a > file that existed in both branches. > > I guess I can offer access to the afflicted repository if someone > wants to peek into it. > I won't have an opportunity work on this until Thursday. But I'd like to have a look then, if you can send the repo via private email (or some other mechanism). -- 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] Adding binary files to fossil
On 1/3/17, Martin S. Weber wrote: > On 2017-01-03 10:08:40, Scott Doctor wrote: >> What is the proper way to add binary files to a repository? > > Follow the following steps: > > (1) (fossil) add the files. > (2) you're done. > (3) No, really, you're done. > (4) Enjoy. As just one of many examples, https://www.fossil-scm.org/fossil/artifact/0fa38d60655faf3d in Fossil's self-hosting repository is a binary file. There are many others. I have entire projects consisting of *only* binary files - for example my collection of OpenOffice presentations. The only restriction with binary files is that if you make independent changes in separate branches, those changes cannot be merged. > > fossil will warn you that these files look binary. Read the warning > and answer accordingly. > > With fossil settings you can specify the binary-glob which will allow > you to circumvent the warning. > > With versioned settings (create a .fossil-settings directory in your > top-level checkout directory and create a, say, binary-glob file in > it which contains a comma-or-newline separated list of glob patterns > describing your binaries) you can make sure this setting propagates > properly to other clones. > > cf. (4) above > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Bug report. fossil changes --differ does not work
On 1/18/17, Anton Polonskiy wrote:
> Hi Richard! I have found a bug in fossil 1.37.
Glad to see the mailing list is going again. My reboot must have worked.
Thanks for the bug report. Now fixed on trunk.
>
> Steps to reproduce:
>
> $ fossil version
> This is fossil version 1.37 [1669115ab9] 2017-01-16 20:58:54 UTC
>
> $ fossil new bug.fossil
> project-id: 1757131b1f9f02f15008d7ec1a8f75f4c4955762
> server-id: 08494d364af82b49b5cb72f81d5933e2f5716327
> admin-user: xxx (initial password is "xxx")
>
> $ fossil open bug.fossil
> project-name:
> repository: /tmp/tmp.s6XePikF0Z/bug.fossil
> local-root: /tmp/tmp.s6XePikF0Z/
> config-db: /home/xxx/.fossil
> project-code: e569a99dd4830a3ca443d3d8fe8a2f56b43c6e28
> checkout: 9b7ff3a1bbafc8f89caad0b2a698ea2ffbbf4260 2017-01-17 13:21:43 UTC
> tags: trunk
> comment: initial empty check-in (user: xxx)
> check-ins: 1
>
> $ fossil changes --differ
> SQLITE_ERROR: SELECTs to the left and right of UNION ALL do not have the
> same number of result columns
> fossil: SELECTs to the left and right of UNION ALL do not have the same
> number of result columns
> SELECT pathname, '' as mtime, 0 as size, deleted, chnged, rid,
> coalesce(origname!=pathname,0) AS renamed, 1 AS managed FROM vfile LEFT
> JOIN blob USING (rid) WHERE is_selected(id) AND (chnged OR deleted OR rid=0
> OR pathname!=origname) UNION ALL SELECT pathname, '', 0, 0, 0, 0, 0, 0, 0
> FROM sfile WHERE pathname NOT IN
> ('_FOSSIL_','_FOSSIL_-journal','_FOSSIL_-wal','_FOSSIL_-shm','.fslckout','.fslckout-journal','.fslckout-wal','.fslckout-shm','.fos','.fos-journal','.fos-wal','.fos-shm','bug.fossil','bug.fossil-journal','bug.fossil-wal','bug.fossil-shm')
> ORDER BY pathname
>
--
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] Feature request - SEARCH to honor the -R option
On 1/19/17, Tony Papadimitriou wrote: > Would it be possible for SEARCH to honor the –R option (just like TIMELINE > does) so that one can search without having to open the repo? Now on trunk. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Using Fossil SCM with Master Repositories held on a Flash Drive ?
On 1/20/17, Martin Irvine wrote: > > I am hoping that Fossil will assist me in making it as simple as > possible for me to ensure I always have all versions of the code for every > project accessible to me when I sit down to work at any particular PC. > Lots of good answers already on how to do this with flash drives But have you considered doing it using your network? Are all of your machines at least intermittently connected to a network? So on some central machine that is usually accessible to the others, put all of your master repositories in a folder named (for example) C:\fossils. Then on that machine run the command "fossil serve c:\fossils" and leave it running. Or you can set up a windows service using the "fossil winsrv" command - I normally run on Unix so I'm not as familiar with that approach, but is well documented and might work better for you. On all other machines do: "fossil clone http://first.machine.ip.addr/name-of-repo.fossil ." - this will clone the repositories on the other machines. They will autosync back to the master. Before going off-network, do "fossil all pull". Then you can work off network for a while, using the --nosync option when you commit. Then when you go back on network, just run "fossil all push" to transmit all changes from all repositories back to the masters. -- 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] Using Fossil SCM with Master Repositories held on a Flash Drive ?
On 1/20/17, Javier Guerra Giraldez wrote: > On 20 January 2017 at 13:08, Richard Hipp wrote: >> But have you considered doing it using your network? Are all of your >> machines at least intermittently connected to a network? >> >> So on some central machine that is usually accessible to the others, >> put all of your master repositories in a folder named (for example) >> C:\fossils. > > > chiselapp.com offers private repositories. Or you can get a $10/month Linode (https://www.linode.com/pricing) and set it up as your private server. That gives that added advantage of being an off-site backup in case a disaster (ex: fire) destroys your whole lab. -- 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] Using Fossil SCM with Master Repositories held on a Flash Drive ?
On 1/20/17, Artur Shepilko wrote: > > If I understood it correctly, your main criteria are: > 1) One flash drive -- use of flash drive to keep all "master" project > repos on it > 5) Keep it tidy :) -- leave no project files behind on the PCs > Let's keep in mind that flash drives are notoriously unreliable. They will wear out and fail suddenly and catastrophically. They are great for transferring information from one machine to another, but you should never keep valuable information only on a flash drive. Always assume that your flash drive will whip itself clean the next time you plug it in, and have a suitable recovery plan. -- 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] Using Fossil SCM with Master Repositories held on a Flash Drive ?
On 1/23/17, Warren Young wrote: > > Digital Ocean has a $5/month option that should be ridiculously overkill > (512 MB of RAM, 20 GB SSD) and since they do hourly pricing and have a > remote API, you could bring it up and down at need. If you just schedule it > 8 hours a day 5 days a week, it would come to about $1.25 a month. I don't know about Digital Ocean, but other ISPs charge you by the amount of time that your disk image exists, not the amount of time your VM is actually running. So I'm not sure about the $1.25/month option. I suspect you'd need to pay the full $5/month. > > That’s around the cost of the USB sticks you’re going to wear through with > the other plan. > Good point about comparing the cost to that of a USB stick. For the price of 3 or 4 USB sticks, you could buy a Raspberry PI (or equivalent), stick it on your local network, and run a Fossil server on that! -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Feature Request: Search Technotes
On 1/24/17, Chris Rydalch wrote: > Is this a complicated issue? Haven't had any luck in this thread, or > another technote-related email I sent to the group. > > I'm not sure if the lack of responses is because the emails aren't actually > making it to the group, I was having issues with fossil-users list a while > back. Either way, it'd be good to know if the email is at least making it > to the list. Thanks! :) > Your emails are getting through. But I've been busy with other things. Do you have patches? -- 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] Feature Request: Search Technotes
On 1/24/17, Chris Rydalch wrote: > > I started by trying to combine them, mainly because I'm not a very good > programmer (most of my experience is with Python), and I was thinking this > would be the easiest way. > I agree that combining tech-notes with wiki seems like the best approach. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Bug Candidate: wall Clock as a show Stopper at Cloning
On 1/24/17, Martin Vahi wrote: > > > I believe that this is a flaw/bug, because > it is obvious that clocks of different computers > can differ for various reasons. A value of a clock > should not be a stopper at cloning a repository. > If the difference between the clocks of 2 computers > is also known, then one time is even convertible > to another time and vice versa. > > -citation---start--- > *** time skew *** server is slow by 2.0 minutes > Clone done, sent: 1262 received: 1121 ip: 195.250.189.35 > server returned an error - clone aborted The differences in the clocks on the two systems is just a warning. The clone aborted because of some other error on the server. The bug is that the client is not giving better error diagnostics... Is this reproducible? > -citation---end--- > > > This is fossil version 1.35 [3aa86af6aa] > > Thank You :-) > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] A way to relative link to other fossil repositories
On 1/25/17, john lunzer wrote:
>
> I would like to create a homepage for all of my repos by using another
> fossil which is also in my fossils directory, lets call that
> homepage.fossil for now. I'm looking for a way to link to the other fossils
> be served in the wiki/homepage of homepage.fossil in a relative way.
>
> I envision something like:
>
> [${server}/another_repo|Repo1]
>
I did some experimenting in the Sandbox wiki page and found that links
like this seemed to work:
[/../otherrepo/home | The otherrepo repository]
In other words, start the link with "/" (which tells Fossil to base
the link at the root of the current repository) then follow that by
"../" to move up one level, then insert the other repository name.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil 1.37 segfault, web interface "Login" as nobody with "a" capabilities
On 1/28/17, Lonnie Abelbeck wrote:
> I recently upgraded fossil to 1.37 for our project (cross-compiled from
> source).
>
> In our case the "nobody" user has "a" Capabilities. This is desired since
> fossil (listening on 127.0.0.1) is accessed via an authenticated HTTPS proxy
> using lighttpd.
>
> In the web interface, click on "Login" and while not logged in, the "Change
> Password" appears.
I'm having trouble reproducing this. Can you go into more details
about your unusual setup?
> --
> Change Password for user :
> --
> If the {Change Password} button is clicked, fossil segfaults.
>
> Lonnie
>
> fossil version -v
>
> This is fossil version 1.37 [1669115ab9] 2017-01-16 20:58:54 UTC
> Compiled on Jan 28 2017 10:53:10 using gcc-4.8.3 (64-bit)
> Schema version 2015-01-24
> zlib 1.2.11, loaded 1.2.11
> SSL (OpenSSL 1.0.2k 26 Jan 2017)
> UNICODE_COMMAND_LINE
> DYNAMIC_BUILD
> SQLite 3.16.2 2017-01-06 16:32:41 a65a62893c
> 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
>
>
>
> _______
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil 1.37 segfault, web interface "Login" as nobody with "a" capabilities
On 1/28/17, Joe Mistachkin wrote: > > 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. x-ed the reason I had trouble reproducing the problem is because Joe had already fixed it on trunk. :-\ -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
