Re: [fossil-users] Version 1.28 release?
2014/1/13 Mark Janssen mpc.jans...@gmail.com: I am not sure if this is an issue with my MinGW install, but latest trunk fails to build on MinGW. I think it's useful if the official release can also be built on MinGW. http://fossil-scm.org/index.html/info/354288db9c Thanks! Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] How to re-open a closed leaf
Hallo to the list. I am a newby and not sure, this is the right place to ask my question. Anyway my problem is, I have closed a leaf, which I did not have to close. Now if I try to commit against my repository, I get the message: cannot commit against a closed leaf. Is there a way to re-open the leaf? I tried to edit the item in the timeline where Closed-leaf is shown, but I did not find any command to set the leaf to open again. Thank you all in advance ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Version 1.28 release?
On Tue, Jan 14, 2014 at 9:36 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2014/1/13 Mark Janssen mpc.jans...@gmail.com: I am not sure if this is an issue with my MinGW install, but latest trunk fails to build on MinGW. I think it's useful if the official release can also be built on MinGW. http://fossil-scm.org/index.html/info/354288db9c Thanks! Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users With that commit, build still fails on sqlite.c: src/sqlite3.c:34515: warning: implicit declaration of function 'winShmMutexHeld' This function is only defined with -DSQLITE_DEBUG but used without ifdef in winShmPurge. There are many other issues with building without -DSQLITE_DEBUG. I am not sure if the proper fix is to define this in the Makefile or to build without DEBUG. Defining -DSQLITE_DEBUG gives a warning about %lld: src/sqlite3.c:5: warning: unknown conversion type character 'l' in format src/sqlite3.c:5: warning: too many arguments for format src/sqlite3.c:7: warning: unknown conversion type character 'l' in format src/sqlite3.c:7: warning: too many arguments for format Mark BTW you are referring to old MinGW in your commit message. I have installed mingw using the installer. How do you get a newer version? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Version 1.28 release?
2014/1/14 Joseph R. Justice jayare...@gmail.com: (I also note from the timeline that the prospective 1.28 does appear to have a release version of SQLite embedded.) Actually, branch-1.28 doesn't contain a release version of SQLite either, it contains the most stable version. This is almost the same, but not 100%. I'll try to explain (my personal view, but I'm sure I'm not the only one). The most stable version at 2013-12-06 was SQLite 3.8.2, there is no question about it. Proof: http://www.sqlite.org/checklists/3080200/index What does it actually mean, the most stable SQLite? Most people would say, the SQLite version which the least number of bugs. Well, no-one know how much bugs SQLite has, we only know how much bugs are reported and how many are found during testing. There are 6 known bugs in SQLite 3.8.2 (that I am aware of), all of them are fixed in SQLite trunk. Only one of them can cause an exception while executing certain SQL queries: http://www.sqlite.org/src/info/520070ec7fbaac There are 3 bug-fixes in shell.c. Since shell.c is not actually part of SQLite there is actually no issue here. SQLite trunk's shell.c contains only bug-fixes, so the shell.c from there is the most stableone. For those who are interested: http://www.sqlite.org/src/info/5e239ecda0 http://www.sqlite.org/src/info/96397263f9 http://www.sqlite.org/src/info/ac15455abc The two remaining are minor. One that only affects Cygwin: http://www.sqlite.org/src/info/c43b59dac1 And the last one which doesn't affect fossil at all because fossil doesn't use fork(): https://www.mail-archive.com/sqlite-users@sqlite.org/msg81284.html Branch branch-1.28 currently contains SQLite 3.8.2 with 5 additional bug-fixes: All the ones mentioned above except the last one. Of course, this needs approval from Richard. Any more bug-fixes that should go in the branch? Any bug-fixes that I missed? Thank you very much for your attention! Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Version 1.28 release?
2014/1/14 Mark Janssen mpc.jans...@gmail.com: With that commit, build still fails on sqlite.c: src/sqlite3.c:34515: warning: implicit declaration of function 'winShmMutexHeld' Should be fixed now in branch-1.28. In trunk it should be fixed as soon as a new SQLite amalgamation appears there. (Already fixed by Joe in SQLite trunk, I just cherry-picked it) Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Version 1.28 release?
Thus said Jan Nijtmans on Tue, 14 Jan 2014 10:33:57 +0100: And the last one which doesn't affect fossil at all because fossil doesn't use fork(): https://www.mail-archive.com/sqlite-users@sqlite.org/msg81284.html Technically it does use fork() for SSH sync operations but I don't believe it fits the description in the above mentioned mailing list post because the forked process is an SSH process, not another process with sqlite code running in it (well, ok, it forks SSH which then runs fossil, but clearly the sqlite code running in that process is unrelated). Andy -- TAI64 timestamp: 400052d55469 ___ fossil-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 re-open a closed leaf
Thus said Pierluigi Moschetti on Tue, 14 Jan 2014 10:01:18 +0100: I get the message: cannot commit against a closed leaf. Is there a way to re-open the leaf? I tried to edit the item in the timeline where Closed-leaf is shown, but I did not find any command to set the leaf to open again. There is an option open the leaf in the web UI (fossil ui). Find the checkin in the timeline, click on it and then click edit. There should be a checkbox that says: Cancel special tag closed If you check it and save the changes, the leaf will no longer be closed. What version of fossil does ``fossil version'' report? Andy -- TAI64 timestamp: 400052d5554c ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tree view and browser back button
Joel - thanks for trying to fix this problem. But your patch doesn't work. On Chrome Version 31.0.1650.63 (the default on Ubuntu 13.10) pressing the back button returns to a collapsed tree. And on IE10, it no longer expands when clicking on a directory. (Firefox and Safari work in all cases that I tested, but they worked before too, so no change there.) I've moved your changes into a branch until we can get them 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] Tree view and browser back button
Richard Hipp wrote: Joel - thanks for trying to fix this problem. But your patch doesn't work. On ChromeVersion 31.0.1650.63 (the default on Ubuntu 13.10) pressing the back button returns to a collapsed tree. And on IE10, it no longer expands when clicking on a directory. (Firefox and Safari work in all cases that I tested, but they worked before too, so no change there.) I've moved your changes into a branch until we can get them working. Sorry, I shouldn't have committed it to trunk in the first place. I'll let you know when I've got it working better. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tree view and browser back button
Joel Bruick wrote: Sorry, I shouldn't have committed it to trunk in the first place. I'll let you know when I've got it working better. Should be working properly now. Tested on Firefox, Chrome, and IE10/11. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tree view and browser back button
On Tue, Jan 14, 2014 at 8:42 PM, Joel Bruick j...@joelface.com wrote: Joel Bruick wrote: Sorry, I shouldn't have committed it to trunk in the first place. I'll let you know when I've got it working better. Should be working properly now. Tested on Firefox, Chrome, and IE10/11. Brilliant! Thanks, Joel. The latest code has been merged to trunk and is now in the server. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Database locked, but which?
Hello,
While attempting to pull the Fossil repository, I saw this error:
$ fossil up
Autosync: https://www.fossil-scm.org/
Round-trips: 2 Artifacts sent: 0 received: 0
Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT m1
FROM time_fudge WHERE mid=objid) WHERE objid IN (SELECT mid FROM time_fudge);}
Round-trips: 2 Artifacts sent: 0 received: 0
Pull finished with 1346 bytes sent, 1866 bytes received
Autosync failed
Rerunning the command was successful. Is this normal? I have no other
fossil command running, so the error must have come from remote.
$ fossil version
This is fossil version 1.28 [4699f8d919] 2014-01-14 10:43:23 UTC
Thanks,
Andy
--
TAI64 timestamp: 400052d60237
___
fossil-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 locked, but which?
On 1/14/14, Andy Bradford amb-fos...@bradfords.org wrote:
Hello,
While attempting to pull the Fossil repository, I saw this error:
$ fossil up
Autosync: https://www.fossil-scm.org/
Round-trips: 2 Artifacts sent: 0 received: 0
Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT
m1 FROM time_fudge WHERE mid=objid) WHERE objid IN (SELECT mid FROM
time_fudge);}
Round-trips: 2 Artifacts sent: 0 received: 0
Pull finished with 1346 bytes sent, 1866 bytes received
Autosync failed
Rerunning the command was successful. Is this normal? I have no other
fossil command running, so the error must have come from remote.
$ fossil version
This is fossil version 1.28 [4699f8d919] 2014-01-14 10:43:23 UTC
No pending commits in other windows? (ie: waiting for you to enter
password for gpg key) ?
-bch
Thanks,
Andy
--
TAI64 timestamp: 400052d60237
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Brad Harder
Method Logic Digital Consulting
http://www.methodlogic.net/
http://twitter.com/bcharder
___
fossil-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 locked, but which?
Thus said B Harder on Tue, 14 Jan 2014 19:38:55 -0800: No pending commits in other windows? (ie: waiting for you to enter password for gpg key) ? No, and in fact, this was the first time I ran any fossil command after logging in and ps did not show any other fossil commands. I wonder if I hit one of the scheduled syncs between the various hosted sites? Andy -- TAI64 timestamp: 400052d6093b ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
