Re: [fossil-users] Fossil 2.0 (reprise)
On 2/23/15, Richard Hipp d...@sqlite.org wrote: That said, a key feature of Fossil is the ability to operate disconnected - without an internet connection. I'm not an expert on Bootstrap, but I don't think it works that way. Furthermore, Bootstrap pushes itself as mobile first. I think that is at cross-purposes with Fossil which is designed foremost for a developers desktop. -- 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 2.0 (reprise)
On Sun, 15 Feb 2015 23:49:42 -0500 Richard Hipp d...@sqlite.org wrote: Please continue to offer suggestions for improvement. Adding support for plugins/addons, using TH1, TCL, Lua or other embeddable language. Plugin code and data should reside on specific table for each plugin, and passed on push/pull/sync/clone. Examples of plugins/addons: - Project Management (Burnout graphs, TODO lists/check lists, time cost measurements, project statistics, etc...), - Bridges to non-http protocols (mail, p2p, nntp, ...), - Calendar, alarms, notices, - Compilation and test status, import these and other information from other developer tools, - Project specific needs - Cron automatizations, f.ex. deferring hash (md5) or other calculations to idle time. Not everyone will need them and their development can be parallel to fossil-scm, these means that plugins/addons code should not reside inside fossil-scm c code. -- D. Richard Hipp d...@sqlite.org --- --- Eduardo Morras emorr...@yahoo.es ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil 2.0 (reprise)
On 2/23/15, Samuel Debionne samuel.debio...@ujf-grenoble.fr wrote: What about adding javascripts as part of the skin (as it is done for css) ? The current skinning mechanism (https://www.fossil-scm.org/fossil/doc/trunk/www/customskin.md) gives the developers complete control over the header and footer of the document, which means that the skin developer can add as much JS or .less as he wants. That said, a key feature of Fossil is the ability to operate disconnected - without an internet connection. I'm not an expert on Bootstrap, but I don't think it works that way. -- 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 version 1.31 testing
On 2/22/15, Marcel Graf graf.m.ml+sbf...@gmail.com wrote: Hello, I noticed two problems in the web-ui of recent fossil versions: 1. On the timeline, clicking on a tag used to show all checkins related to that tag/branch around that time - but now it only shows the checkins on and after that time, but no older checkins. Example from the fossil repository (svn-import link from c3bcab0f0505eb9a) is http://www.fossil-scm.org/index.html/timeline?r=svn-importndc=2015-02-22+12%3A00%3A49n=200 only shows 5 checkins, using fossil 1.30 it shows about 90 checkins. The problem does not show if the selected branch is trunk or the n=200 parameter is removed - then the checkins before and after are shown. This problem appears first with checkin 45127a7236e4c34ecac670b6ee0645c1bcf77c20 This problem appears to be resolved now. 2. On the Files page, sometimes changing from Flat to Tree view and vice-versa, the references check-in/branch/tag is lost and All Files (Files from all XXX checkins) are shown. It does not happen if fossil ui is called inside a working directory or the repository is in the current directory when fossil ui repo.fossil is called (and probably the same for CGI). It does happen when calling fossil ui /abs/path/to/some/repo.fossil (or using CGI). Then, on the Files page (/dir?ci=tip) the Tab for Tree-View links to /dir?type=tree instead of /dir?ci=tiptype=tree This first appears with checkin 7478f9974c6320e4c942b7808ca393fa1540d871 I was unable to recreate this problem. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] auth failure with fossil server
Hi, first, thank you all for this great piece of software. I used it primary to keep track of my script development for myself, later on tracking my development on work as well. Currently my whole team got used to work with fossil-scm. Thanks for that. Anyway, I encounter a problem with fossil, which I do nowadays use on my Synology-NAS (DS411slim) to host a dozen repos to access them via ddns from anywhere I do need to. All my repos do have the same user config, that is all default users got no rights at all. Then I have to users defined, one with my private username and one with my work username. Both users have differend passwords for sure. Now my problem is, if I connect to a repo via http://my.dyn.dns:8080/myrepo I am able to log in as userA. But if I do a logout, and try to log in as userB, it always refuses the logon and claims that the password is wrong. Trying to log in as userA again works. When I reset the NAS (or restart the init script), and try to logon as userB it works, but logoff and login as userA states the same error as the otherway round. I distributed user settings by manually entering the users on one repo, then do fossil config export user user.config -R myrepo.fossil and imported it via fossil config import user.config -R other.fossil Can anybody experience anything like that, or explain to me, that fossil server is not able to handle different users? Kind regards Oliver ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil 2.0 (reprise)
The current skinning mechanism (https://www.fossil-scm.org/fossil/doc/trunk/www/customskin.md) gives the developers complete control over the header and footer of the document, which means that the skin developer can add as much JS or .less as he wants. Right, that is how I am doing it for lack of an better solution, but find it a bit hackish, especially when the javascript gets large. Moreover the javascript could be cached by the browser if it was not directly inline in the HTML. That said, a key feature of Fossil is the ability to operate disconnected - without an internet connection. I'm not an expert on Bootstrap, but I don't think it works that way. There may be a misunderstanding in my use case : I was talking about javascript that would be served by fossil, not by a CDN or whatever server (so that fossil continues to operate offline). As of Bootstrap, it would be perfectly OK to have Bootstrap css/js served by fossil, there is no requirement to get it from internet. And I am not trying to push for the use of Bootstrap, it's just that it's really hard to get CSS right on multiple browser (at list for a casual stylesheet writer like me) ! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil 2.0 (reprise)
Furthermore, Bootstrap pushes itself as mobile first. I think that is at cross-purposes with Fossil which is designed foremost for a developers desktop. Well, I think mobile first could be read behaves well on mobile devices and as well as usual on desktop ! Any idea about the licensing issue ? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Wiki navigation bar support
On Mon, Feb 23, 2015 at 11:48 AM, Stephan Beal sgb...@googlemail.com wrote: FWIW, frames were (thank goodness) deprecated in HTML5. iframes are still around but work much differently. Been over 10 years since I did any serious web work (was moonlight work I did for a friend). I didn't do the page designs. I just coded around the provided (generated) HTML. I suspect frame support will remain in webbrowsers for years to come. Deprecating frames was probably easy. But it's iframes I've always hated. ___ fossil-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 version 1.31 testing
On Mon, Feb 23, 2015 at 2:22 PM, Richard Hipp d...@sqlite.org wrote: On 2/22/15, Marcel Graf graf.m.ml+sbf...@gmail.com wrote: Hello, I noticed two problems in the web-ui of recent fossil versions: 1. On the timeline, clicking on a tag used to show all checkins related to that tag/branch around that time - but now it only shows the checkins on and after that time, but no older checkins. Example from the fossil repository (svn-import link from c3bcab0f0505eb9a) is http://www.fossil-scm.org/index.html/timeline?r=svn-importndc=2015-02-22+12%3A00%3A49n=200 only shows 5 checkins, using fossil 1.30 it shows about 90 checkins. The problem does not show if the selected branch is trunk or the n=200 parameter is removed - then the checkins before and after are shown. This problem appears first with checkin 45127a7236e4c34ecac670b6ee0645c1bcf77c20 This problem appears to be resolved now. Yes. Thank you. 2. On the Files page, sometimes changing from Flat to Tree view and vice-versa, the references check-in/branch/tag is lost and All Files (Files from all XXX checkins) are shown. It does not happen if fossil ui is called inside a working directory or the repository is in the current directory when fossil ui repo.fossil is called (and probably the same for CGI). It does happen when calling fossil ui /abs/path/to/some/repo.fossil (or using CGI). Then, on the Files page (/dir?ci=tip) the Tab for Tree-View links to /dir?type=tree instead of /dir?ci=tiptype=tree This first appears with checkin 7478f9974c6320e4c942b7808ca393fa1540d871 I was unable to recreate this problem. Maybe I was not too clear in the description. But I was able to recreate it with the following few lines, all using fossil version 1.31 [858dcc2c19]: fossil init -A myself repo/tree-dir-test.fossil mkdir tree-dir-test.fossil cd tree-dir-test.fossil fossil open ../repo/tree-dir-test.fossil echo foo a.txt fossil add a.txt fossil ci --user myself -m 'foo into a.txt' mv a.txt b.txt fossil mv a.txt b.txt fossil ci --user myself -m 'rename a.txt to b.txt' Viewing this by means of CGI like #!/path/to/fossil directory: /abs/path/to/repo-dir/ the Files Tab in the main menu links to /tree?ci=tip, once on that page the [Tree-View]-button links to /dir?type=tree and shows all checkins and files (a.txt and b.txt). Changing the skin to San Francisco Modern, the Files Tab in the main menu links to /dir?ci=tip, but again, once on that page the [Tree-View]-button links to /dir?type=tree, missing something like ci=tip If I use as CGI like #!/path/to/fossil directory: /abs/path/to/repo-dir/tree-dir-test.fossil I have to check for fossil ui with that repository later on ... but the first time I noticed the bad behavior was using fossil ui /abs/path/to/repo.fossil Marcel -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil version 1.31 testing
On 17 February 2015 at 15:55, Richard Hipp d...@sqlite.org wrote: I'd like to release Fossil version 1.31 soon. Before the end of February. See https://www.fossil-scm.org/fossil/doc/trunk/www/changes.wiki for a summary of changes. Please test the latest trunk code as much as possible over the next week. You'll need to recompile fossil yourself in order to do this. Compiling Fossil from sources is not hard. See https://www.fossil-scm.org/fossil/doc/trunk/www/build.wiki for the details. Not a bug but maybe something to consider... https://www.fossil-scm.org/fossil/timeline?u=drhc=2015-02-23+16%3A27%3A34ndn=200 Would it be worthwhile to have older here and the max # to show? Much like on the timeline page: https://www.fossil-scm.org/fossil/timeline?y=ci -- D. Richard Hipp d...@sqlite.org -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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 1.30 : db_record_repository_filename() never writes ckout to REPOSITORY.config
Since Fossil 1.30 the function db_record_repository_filename() in db.c
performs update of config table with two commands:
1. DELETE record to circumvent caseInsensitivity problems:
db_optional_sql(repository,
DELETE FROM config WHERE name %s = %Q;,
filename_collation(), zCkoutSetting
);
2. UPDATE record:
db_optional_sql(repository,
REPLACE INTO config(name,value,mtime)
VALUES(%Q,1,now());,
zCkoutSetting
);
Statements collected by db_optional_sql() are executed in
db_end_transaction() but in REVERSE ORDER. So the DELETE statement will
be the last and withdraws the UPDATE.
I applied the following patch to my fossil.exe, swapping the statements:
Index: db.c
==
--- db.c
+++ db.c
@@ -2138,19 +2138,19 @@
REPLACE INTO global_config(name, value)
VALUES(%Q,%Q);,
zCkoutSetting, blob_str(full)
);
db_swap_connections();
-db_optional_sql(repository,
-DELETE FROM config WHERE name %s = %Q;,
-filename_collation(), zCkoutSetting
-);
db_optional_sql(repository,
REPLACE INTO config(name,value,mtime)
VALUES(%Q,1,now());,
zCkoutSetting
);
+db_optional_sql(repository,
+DELETE FROM config WHERE name %s = %Q;,
+filename_collation(), zCkoutSetting
+);
fossil_free(zCkoutSetting);
blob_reset(localRoot);
}else{
db_swap_connections();
}
==
[Another option would be to execute the db.azBeforeCommit array in
db_end_transaction() in reversed order but maybe there was a reason
other than convenient programming style.]
Now that db_record_repository_filename() works for me I experience
something else -- opening a new repository still doesn't report the
'ckout' to REPOSITORY.config.
Cause: By default there is *no initial commit* in Fossil 1.30.
'open_cmd' calls 'checkout_cmd' which starts a transaction. But since
there are no leaves or events or blobs in a new repository `zVers` is 0
and the transaction isn't commited, discarding the optional sqls from
'db_record_repository_filename'.
Of course the first commit or `init --date-override` will do the trick.
BTW: What's the reason for storing the 'ckout' in the REPOFILE via
'db_optional_sql'? Why not via 'db_multi_exec'?
Tontyna
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil 2.0 (reprise)
Please continue to offer suggestions for improvement. What about adding javascripts as part of the skin (as it is done for css) ? Motivation: skins could be made responsive and/or include more dynamic components and there is no way to do that without a bit of javascript. Large javascript in the header or footer looks a bit hacky (and the javascript cannot be cached). Maybe v2 of the skin system is a good time to add something like this : script type=text/javascript src=/myrepo/script.js?default/script Lately I have proposed a Bootstrap based skin: https://flintcode.com/repo/skin The next step would be to use the .less files (the css source files) from Bootstrap to create a custom tailored version of Bootstrap for fossil, instead of having it the other way around (aka tailoring the generated html of fossil for Bootstrap using hacky javascript). LESS provides functionalities (such as css inheritance) to do that. My question is about the licensing: would it be OK to include a byproduct of Bootstrap (MIT license) in Fossil ? Samuel ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] auth failure with fossil server
Thus said Oliver Friedrich on Mon, 23 Feb 2015 15:17:35 +: Nowmy problemis, ifI connectto arepo via http://my.dyn.dns:8080/myrepo I am able to log in as userA. But if I do a logout, and try to log in as userB, it always refuses the logon and claims that the password is wrong. Trying to log in as userA again works. What is meant by ``connect to a repo'' in this context? Do you mean point your browser to that URL, or do you mean you change the remote-url for a fossil clone? Can anybody experience anything like that, or explain to me, that fossil server is not able to handle different users? Are you running ``fossil server /some/path'' as root, or just normal user? Or some other invocation? What version of fossil on the server? Thanks, Andy -- TAI64 timestamp: 400054ec0143 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] auth failure with fossil server
Nowmy problemis, ifI connectto arepo via http://my.dyn.dns:8080/myrepo I am able to log in as userA. But if I do a logout, and try to log in as userB, it always refuses the logon and claims that the password is wrong. Trying to log in as userA again works. Reading this, I made a mistake. It is not that logon on the same repo does not work, but logon to another repo hostet by the same fossil server instance will deny my credentials, although all repos do share the same user settings. (tested with config export and diff) What is meant by ``connect to a repo'' in this context? Do you mean point your browser to that URL, or do you mean you change the remote-url for a fossil clone? Yes, i meant an connect via http, logon on the webpage of the repository. Can anybody experience anything like that, or explain to me, that fossil server is not able to handle different users? Are you running ``fossil server /some/path'' as root, or just normal user? Or some other invocation? What version of fossil on the server? I run fossil server -P 8080 /some/path on my nas. This is done as root (cause nothing else is possible there). NAS fossil version This is fossil version 1.30 [1df1b41c86] 2015-01-19 11:29:00 UTC This fossil is self compiled from the stable sources of 1.30. Thank you for your time and help. ___ fossil-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 version 1.31 testing
On Mon, Feb 23, 2015 at 1:16 PM, Richard Hipp d...@sqlite.org wrote: New tarball with the missing files has been uploaded. Are you sure about that? I tried buliding on two separate OS's now (Manjaro Linux and Haiku) and it fails to build with either with the same error as previously mentioned. This is the source tar.gz in question: https://www.fossil-scm.org/download/fossil-src-20150223162734.tar.gz Here is the build failure which occurs after ./configure and make: cc -o bld/mkbuiltin ./src/mkbuiltin.c bld/mkbuiltin --prefix ./src/ ./src/../skins/black_and_white/css.txt ./src/../skins/black_and_white/footer.txt ./src/../skins/black_and_white/header.txt ./src/../skins/default/css.txt ./src/../skins/default/footer.txt ./src/../skins/default/header.txt ./src/../skins/eagle/css.txt ./src/../skins/eagle/footer.txt ./src/../skins/eagle/header.txt ./src/../skins/enhanced1/css.txt ./src/../skins/enhanced1/footer.txt ./src/../skins/enhanced1/header.txt ./src/../skins/etienne1/css.txt ./src/../skins/etienne1/footer.txt ./src/../skins/etienne1/header.txt ./src/../skins/khaki/css.txt ./src/../skins/khaki/footer.txt ./src/../skins/khaki/header.txt ./src/../skins/plain_gray/css.txt ./src/../skins/plain_gray/footer.txt ./src/../skins/plain_gray/header.txt ./src/../skins/rounded1/css.txt ./src/../skins/rounded1/footer.txt ./src/../skins/rounded1/header.txt ./src/diff.tcl ./src/markdown.md bld/builtin_data.h cc -o bld/makeheaders ./src/makeheaders.c make: *** No rule to make target 'src/../manifest.uuid', needed by 'bld/VERSION.h'. Stop. - joe ___ fossil-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 version 1.31 testing
On Mon, Feb 23, 2015 at 8:04 PM, Joe Prostko joe.pros...@gmail.com wrote: same error as previously mentioned. This is the source tar.gz in question: https://www.fossil-scm.org/download/fossil-src-20150223162734.tar.gz As an FYI, the sha1sum matches what is reported on the website at http://www.hwaci.com/fossil_download_checksums.html . That said, I still see the build failure. [jprostko@galago Downloads]$ sha1sum fossil-src-20150223162734.tar.gz 8fbde3f48f10cf128c902035aaa6aae06e869098 fossil-src-20150223162734.tar.gz - joe ___ fossil-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 version 1.31 testing
On 2/23/15, Joe Prostko joe.pros...@gmail.com wrote: On Mon, Feb 23, 2015 at 1:16 PM, Richard Hipp d...@sqlite.org wrote: New tarball with the missing files has been uploaded. Are you sure about that? Uploaded yet again. Please retry. -- 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 version 1.31 testing
On Mon, Feb 23, 2015 at 9:09 PM, Richard Hipp d...@sqlite.org wrote: On 2/23/15, Joe Prostko joe.pros...@gmail.com wrote: On Mon, Feb 23, 2015 at 1:16 PM, Richard Hipp d...@sqlite.org wrote: New tarball with the missing files has been uploaded. Are you sure about that? Uploaded yet again. Please retry. Confirmed working. Thank you! - joe ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
