Re: [fossil-users] The autosetup, and readline
On Fri, Sep 02, 2011 at 01:13:43PM +1000, Steve Bennett wrote: On 02/09/2011, at 7:43 AM, Lluís Batlle i Rossell wrote: Does the autosetup detect 'readline' for all of you? For me, it says that it cannot find the 'readline' symbol in the lib. In my case, autosetup is even not running the test for the 'readline' symbol in the lib (tested with --debug), so it really looks like something internal to autosetup. Can you send me config.log from running with --debug? Sure. Here you have both the output and the config.log. Looking for sh in /nix/store/49wd5hr0wwac2dnfxcd3q64k2dvp53z7-tcl-8.5.7/bin Looking for sh in /nix/store/42mpg3g8b570pm6v48q3ll2xq0mcg35p-openssl-1.0.0d/bin Looking for sh in /nix/store/pssjwskay00fzfdv0xz1hfg16asc7y47-ncurses-5.7/bin Looking for sh in /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin Looking for sh in /nix/store/7w8b9g33z1vffv6y2swr3dbiddsrysdl-coreutils-8.7/bin Looking for sh in /nix/store/zqzkczyp0pfxi8piw1lszhjnr53p28h5-findutils-4.4.2/bin Looking for sh in /nix/store/4jadx4smsnz92p31v6y4b49lvccf277n-diffutils-3.0/bin Looking for sh in /nix/store/52v147alz9mny3hg5va6y7jfd1rr4rk8-gnused-4.2.1/bin Looking for sh in /nix/store/shjfhj9l4pm317liz9y6ak4ibkpv9vp8-gnugrep-2.7/bin Looking for sh in /nix/store/kdj0y3lbvk6xl175v7xrdfm97drjry7x-gawk-3.1.8/bin Looking for sh in /nix/store/s0cvbvq23hv4xazpl7srpdm04gs1l78j-gnutar-1.25/bin Looking for sh in /nix/store/0x5s5xv0k7w58xvfaqswn80id5b8z2lx-gzip-1.4/bin Looking for sh in /nix/store/6iyhp953ay3c0f9mmvw2xwvrxzr0kap5-bzip2-1.0.5/bin Looking for sh in /nix/store/ahpgr8qzxx7m1khmdp8dhkkn83cdpz82-gnumake-3.82/bin Looking for sh in /nix/store/j8rrk6dkrcaa8r1j5987g94154rkawy9-bash-4.1-p2/bin Found sh - /nix/store/j8rrk6dkrcaa8r1j5987g94154rkawy9-bash-4.1-p2/bin/sh Host System...x86_64-unknown-linux-gnu Build System...x86_64-unknown-linux-gnu Looking for cc in /nix/store/49wd5hr0wwac2dnfxcd3q64k2dvp53z7-tcl-8.5.7/bin Looking for cc in /nix/store/42mpg3g8b570pm6v48q3ll2xq0mcg35p-openssl-1.0.0d/bin Looking for cc in /nix/store/pssjwskay00fzfdv0xz1hfg16asc7y47-ncurses-5.7/bin Looking for cc in /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin Found cc - /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin/cc Looking for c++ in /nix/store/49wd5hr0wwac2dnfxcd3q64k2dvp53z7-tcl-8.5.7/bin Looking for c++ in /nix/store/42mpg3g8b570pm6v48q3ll2xq0mcg35p-openssl-1.0.0d/bin Looking for c++ in /nix/store/pssjwskay00fzfdv0xz1hfg16asc7y47-ncurses-5.7/bin Looking for c++ in /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin Found c++ - /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin/c++ Looking for ld in /nix/store/49wd5hr0wwac2dnfxcd3q64k2dvp53z7-tcl-8.5.7/bin Looking for ld in /nix/store/42mpg3g8b570pm6v48q3ll2xq0mcg35p-openssl-1.0.0d/bin Looking for ld in /nix/store/pssjwskay00fzfdv0xz1hfg16asc7y47-ncurses-5.7/bin Looking for ld in /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin Found ld - /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin/ld Looking for cc in /nix/store/49wd5hr0wwac2dnfxcd3q64k2dvp53z7-tcl-8.5.7/bin Looking for cc in /nix/store/42mpg3g8b570pm6v48q3ll2xq0mcg35p-openssl-1.0.0d/bin Looking for cc in /nix/store/pssjwskay00fzfdv0xz1hfg16asc7y47-ncurses-5.7/bin Looking for cc in /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin Found cc - /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin/cc Looking for ccache in /nix/store/49wd5hr0wwac2dnfxcd3q64k2dvp53z7-tcl-8.5.7/bin Looking for ccache in /nix/store/42mpg3g8b570pm6v48q3ll2xq0mcg35p-openssl-1.0.0d/bin Looking for ccache in /nix/store/pssjwskay00fzfdv0xz1hfg16asc7y47-ncurses-5.7/bin Looking for ccache in /nix/store/2yghakb86zfivd2da4x1ipcz03xmz6rd-gcc-wrapper-4.5.1/bin Looking for ccache in /nix/store/7w8b9g33z1vffv6y2swr3dbiddsrysdl-coreutils-8.7/bin Looking for ccache in /nix/store/zqzkczyp0pfxi8piw1lszhjnr53p28h5-findutils-4.4.2/bin Looking for ccache in /nix/store/4jadx4smsnz92p31v6y4b49lvccf277n-diffutils-3.0/bin Looking for ccache in /nix/store/52v147alz9mny3hg5va6y7jfd1rr4rk8-gnused-4.2.1/bin Looking for ccache in /nix/store/shjfhj9l4pm317liz9y6ak4ibkpv9vp8-gnugrep-2.7/bin Looking for ccache in /nix/store/kdj0y3lbvk6xl175v7xrdfm97drjry7x-gawk-3.1.8/bin Looking for ccache in /nix/store/s0cvbvq23hv4xazpl7srpdm04gs1l78j-gnutar-1.25/bin Looking for ccache in /nix/store/0x5s5xv0k7w58xvfaqswn80id5b8z2lx-gzip-1.4/bin Looking for ccache in /nix/store/6iyhp953ay3c0f9mmvw2xwvrxzr0kap5-bzip2-1.0.5/bin Looking for ccache in /nix/store/ahpgr8qzxx7m1khmdp8dhkkn83cdpz82-gnumake-3.82/bin Looking for ccache in /nix/store/j8rrk6dkrcaa8r1j5987g94154rkawy9-bash-4.1-p2/bin Looking for ccache in /nix/store/h6p4p5pyybqiic0hhpqnhsw0ndp6w61w-patch-2.6.1/bin Looking for ccache in /nix/store/7pfrbs0y30xi28wg73yzadv1dcjqp3l4-replace-2.24/bin Looking for ccache in /nix/store/jdppx3yhx1lbxl01asplmil8jm0lqn82-patchelf-0.5/bin
Re: [fossil-users] The autosetup, and readline
On Fri, Sep 02, 2011 at 06:15:54PM +1000, Steve Bennett wrote: Thanks. Can you test this patch for me it see if it helps? Now it outputs: Checking for zlib.h...ok Checking libs for inflateEnd...-lz Checking for system ssl...ok HTTP support enabled Checking for readline/readline.h...Checking libs for gethostbyname...none needed Checking libs for socket...none needed Checking for getpassphrase...not found Checking libs for getpass...none needed It looks like it is not testing the symbol anymore. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] The autosetup, and readline
On 02/09/2011, at 6:24 PM, Lluís Batlle i Rossell wrote: On Fri, Sep 02, 2011 at 06:15:54PM +1000, Steve Bennett wrote: Thanks. Can you test this patch for me it see if it helps? Now it outputs: Checking for zlib.h...ok Checking libs for inflateEnd...-lz Checking for system ssl...ok HTTP support enabled Checking for readline/readline.h...Checking libs for gethostbyname...none needed Checking libs for socket...none needed Checking for getpassphrase...not found Checking libs for getpass...none needed It looks like it is not testing the symbol anymore. Ahh, I see. Ignore that patch. It is because you are using Tcl rather than Jim Tcl. I can reproduce it here. Will work on a fix. Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Silencing warnings about deprecated OpenSSL on OS X
Well, you could just do this (see attached patch). Thanks! But should it be restricted to when compiling http_ssl? To Mac OS X? To 10.7? I think restricting it to just Mac OS X is okay. We know that they deprecated OpenSSL, and we don't have any plans to do something with it apart from making OS X users compile their own OpenSSL once Apple removes it, do we? The probability that there be something else deprecated (zlib? functions from libc?) is tiny. -- Dmitry Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Problem after 'make clean'
After doing 'make clean', './configure' complains that 'Makefile.in' doesn't exist (and indeed it doesn't) Seem to be deleted by merge here: http://www.fossil-scm.org/index.html/info/e4f1c1fe95 -- Dmitry Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Silencing warnings about deprecated OpenSSL on OS X
I was curious about this too. Seems they're replacing it with Common Crypto: http://ludovicrousseau.blogspot.com/2011/08/mac-os-x-lion-and-openssl.html Yeah, the big warnings are mostly for App Store developers. They (including me :) have to statically compile OpenSSL or use Common Crypto, or else the reviewers won't approve apps. -- Dmitry Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] The autosetup, and readline
On 02/09/2011, at 6:24 PM, Lluís Batlle i Rossell wrote: On Fri, Sep 02, 2011 at 06:15:54PM +1000, Steve Bennett wrote: Thanks. Can you test this patch for me it see if it helps? Now it outputs: Checking for zlib.h...ok Checking libs for inflateEnd...-lz Checking for system ssl...ok HTTP support enabled Checking for readline/readline.h...Checking libs for gethostbyname...none needed Checking libs for socket...none needed Checking for getpassphrase...not found Checking libs for getpass...none needed It looks like it is not testing the symbol anymore. OK. Try this fix instead. -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 fossil-autosetup-tclsh-fix.patch Description: Binary data ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Silencing warnings about deprecated OpenSSL on OS X
On 02/09/2011, at 7:27 PM, Dmitry Chestnykh wrote: Well, you could just do this (see attached patch). Thanks! But should it be restricted to when compiling http_ssl? To Mac OS X? To 10.7? I think restricting it to just Mac OS X is okay. We know that they deprecated OpenSSL, and we don't have any plans to do something with it apart from making OS X users compile their own OpenSSL once Apple removes it, do we? The probability that there be something else deprecated (zlib? functions from libc?) is tiny. OK. So this should do then. -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 fossil-deprecated-decl-v2.patch Description: Binary data ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Problem after 'make clean'
On Sep 2, 2011, at 11:28 AM, Dmitry Chestnykh wrote: After doing 'make clean', './configure' complains that 'Makefile.in' doesn't exist (and indeed it doesn't) Seem to be deleted by merge here: http://www.fossil-scm.org/index.html/info/e4f1c1fe95 I'm wrong, earlier: http://www.fossil-scm.org/index.html/info/2b8cbf3c41 -- Dmitry Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Silencing warnings about deprecated OpenSSL on OS X
OK. So this should do then. Thank you! -- Dmitry Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Diff after move
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/01/2011 06:17 PM, Stephan Beal wrote: Regarding the comparison with git: git tracks changes differently, and can even tell you that a given commit moved X lines of code from file A to file B (it's pretty f-ing smart that way). Fossil tracks whole files only. i unfortunately don't understand the internal details of how fossil tracks lineage and changes well enough to explain/justify fossil's behaviour, but this topic as come up before and IIRC (which i won't guaranty!) the consensus was that fossil's design doesn't immediately lend well to solving that. Or maybe it's just that nobody's pitched in yet to do it. AIUI, both git and fossil store each commit as a full tree; such cleverness is purely in the hands of the diff algorithm... - -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5gsC0ACgkQRgz/WHNxCGqF2wCfaB8KJO4x6qH5i2RD5IgVt0Iw zXUAnRdpYBLMjRZpyJ0L7YKHFIsrOczM =gLts -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Commit comments trying to produce ol
Hello, I tried to write this in a commit comment: # First Item # Second item And fossil thought those were comments to be ignored. Couldn't fossil simply ignore the lines with '#' as first character? or that has some disadvantadges? Thank you! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Commit comments trying to produce ol
On Fri, 2 Sep 2011 18:15:47 +0200 Lluís Batlle i Rossell virik...@gmail.com wrote: I tried to write this in a commit comment: # First Item # Second item And fossil thought those were comments to be ignored. Couldn't fossil simply ignore the lines with '#' as first character? or that has some disadvantadges? While we're at it, I would really prefer if fossil would behave as Subversion does by ignoring everything below a special anchor line in the comment block. To explain: since fossil does not have anything like `git add --patch`, I'm forced to do lump commits from time to time, and this requires writing elaborate commit messages (in the done this, also done that and also done that style). To help with this, I usually execute :r! fossil diff in my Vim which gets spawned to compose the commit message. This command brings the diff which is about to be committed into the editor's buffer. This allows to skim through the prospective changes easily annotating them in the commit message as I go. With Subversion, after finishing the commit message I can just quit-with-save and be done with it but with fossil, I'll get that whole messy diff in my commit message so I had not to forget to remove it before quitting. I fully understand that this use case it peculiar to say the least but I got burned by this several times. P.S. I know about splitting windows and tabs, but it's less convenient to navigate. ___ fossil-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 it possible to edit a ticket's submission time?
Would it be possible to add this feature, at least for making tickets older than the date they were entered? Is there a strong reason to disallow the editing of time stamps on tickets? For my $0.02, I think adding such a feature would require a fair development effort. You'd need to have UI for manipulating a timestamp, or significant validation code on the backend, or both. FWIW, Fossil does allow you to add fields to the ticket table, markup to the ticket create/edit/view pages, and customize the ticket reports. So it seems like you could add your own field for storing your custom timestamp, and update your ticket reports to reference/include the custom field. You'd probably need to do whatever validations you need in client-side javascript. I think there's info in the Fossil Wiki about adding custom fields. -Clark From: Ross Berteig r...@cheshireeng.com To: fossil-users@lists.fossil-scm.org Sent: Thursday, September 1, 2011 5:54 PM Subject: Re: [fossil-users] Is it possible to edit a ticket's submission time? At 05:11 PM 9/1/2011, you wrote: So, no, there does not appear to be any way to set the date on a ticket to something other than the time/date at which you entered the ticket. Would it be possible to add this feature, at least for making tickets older than the date they were entered? Is there a strong reason to disallow the editing of time stamps on tickets? From a quick skim of the documentation on how tickets work at all, it would appear that all one would need to make a ticket appear at an earlier time in the timeline is a ticket artifact containing the right ID, and with the right date, and possibly containing a change for at least one other field. If the date on the artifact is earlier than all others, then it would appear first in the timeline, and give me the effect I want. I'm not certain it is possible to move a ticket completely into the future. My understanding is that the individual artefacts that make up the ticket are immutable, so it wouldn't be possible to replace the oldest artefact with one with a newer date, and additional artefacts changing a ticket with newer dates are what happens when you edit a ticket now. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ 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] The autosetup, and readline
On Fri, Sep 02, 2011 at 07:43:21PM +1000, Steve Bennett wrote: On 02/09/2011, at 6:24 PM, Lluís Batlle i Rossell wrote: It looks like it is not testing the symbol anymore. OK. Try this fix instead. It works, thank you! I use tclsh, because that's the only way to be able to run make test after building a new fossil. :) Regards, Lluís. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] cannot push or commit
At a complete loss. This is what i get every time, no matter what i do. Perhaps there is some fundamental thing i am not understanding. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push Server:http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 713 bytes sent, 0 bytes received 2011/9/1 Lluís Batlle i Rossell virik...@gmail.com: On Thu, Sep 01, 2011 at 12:23:27PM -0500, Nolan Darilek wrote: Also, to expand even further, Fossil doesn't synchronize users along with the repository, so no need to make your local username/password the same. Just putting that out there, as when I was new I thought there was a shared list of users. You can take the list of users too, running 'fossil configuration pull user'. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Ron Georgia John 13:23 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] cannot push or commit
On Fri, Sep 02, 2011 at 01:44:51PM -0400, ron georgia wrote: At a complete loss. This is what i get every time, no matter what i do. Perhaps there is some fundamental thing i am not understanding. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push Server:http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 713 bytes sent, 0 bytes received Ron Georgia John 13:23 You seem to be pushing as an anonymous user who probably doesn't have write permission. You may want to try pushing as a user you've already setup. fossil push http://someusern...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ It should then prompt you for your password, afterwards you can just do fossil push and it will send the correct credentials. -- James Turner ja...@calminferno.net signature.asc Description: Digital signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] cannot push or commit
Thanks James (or Jim) - but here is what i get: rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push http://rgeor...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker password for rgeorgia: via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 fossil: server says: 400 Bad Request Total network traffic: 788 bytes sent, 0 bytes received Note I am using a cgi script to point to the ntracker repository, will that have an affect on things? On Fri, Sep 2, 2011 at 1:51 PM, James Turner ja...@calminferno.net wrote: On Fri, Sep 02, 2011 at 01:44:51PM -0400, ron georgia wrote: At a complete loss. This is what i get every time, no matter what i do. Perhaps there is some fundamental thing i am not understanding. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push Server: http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 713 bytes sent, 0 bytes received Ron Georgia John 13:23 You seem to be pushing as an anonymous user who probably doesn't have write permission. You may want to try pushing as a user you've already setup. fossil push http://someusern...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ It should then prompt you for your password, afterwards you can just do fossil push and it will send the correct credentials. -- James Turner ja...@calminferno.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk5hF60ACgkQrVACqCIZdxhz9gCgrMm/08BOxYEJzg4jIpajxqoD u0sAn0i0eDgCntXTCUUQjB/No7OxeUuI =rVYa -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Ron Georgia John 13:23 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] cannot push or commit
O! Got it! I removed the proxy. fossil set proxy off. Now i use my local proxy setting. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push http://rgeor...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ password for rgeorgia: Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Received: 455 9 0 0 Sent:4621 17 0 9 waiting for server...Total network traffic: 3309 bytes sent, 0 bytes received EXCELLENT! Next, pushing just one file... we shall see. On Fri, Sep 2, 2011 at 2:04 PM, ron georgia rong1...@gmail.com wrote: Thanks James (or Jim) - but here is what i get: rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push http://rgeor...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker password for rgeorgia: via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 fossil: server says: 400 Bad Request Total network traffic: 788 bytes sent, 0 bytes received Note I am using a cgi script to point to the ntracker repository, will that have an affect on things? On Fri, Sep 2, 2011 at 1:51 PM, James Turner ja...@calminferno.net wrote: On Fri, Sep 02, 2011 at 01:44:51PM -0400, ron georgia wrote: At a complete loss. This is what i get every time, no matter what i do. Perhaps there is some fundamental thing i am not understanding. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push Server: http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 713 bytes sent, 0 bytes received Ron Georgia John 13:23 You seem to be pushing as an anonymous user who probably doesn't have write permission. You may want to try pushing as a user you've already setup. fossil push http://someusern...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ It should then prompt you for your password, afterwards you can just do fossil push and it will send the correct credentials. -- James Turner ja...@calminferno.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk5hF60ACgkQrVACqCIZdxhz9gCgrMm/08BOxYEJzg4jIpajxqoD u0sAn0i0eDgCntXTCUUQjB/No7OxeUuI =rVYa -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Ron Georgia John 13:23 -- Ron Georgia John 13:23 ___ fossil-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 it possible to edit a ticket's submission time?
On Fri, Sep 2, 2011 at 1:02 PM, Clark Christensen cdcmi...@yahoo.com wrote: FWIW, Fossil does allow you to add fields to the ticket table, markup to the ticket create/edit/view pages, and customize the ticket reports. So it seems like you could add your own field for storing your custom timestamp, and update your ticket reports to reference/include the custom field. You'd probably need to do whatever validations you need in client-side javascript. I think there's info in the Fossil Wiki about adding custom fields. Yes, I've added custom fields to tickets and made reports that sort on those fields. However, the the request is to be able to have the ticket's first appearance on the Time Line view correspond to the date/time the requester sent his/her message, rather than the time the project maintainer entered the ticket into Fossil. Maybe the ticket entry processing could be enhanced to automatically create an event in the case that a ticket's submission date/time is earlier than it's creation date/time? I think that the Ticket Entry page could be enhanced with Javascript to submit a new event to Fossil. At least when I created an event and used the submit button (rather than the preview button), the response from Fossile was a simple acknowledgement, so the Javascript would not have to do more than parse the response for any errors messages and display those errors, if any. The event summary would be the ticket summary and the even body could be a link to the actual ticket. Possibly the Fossil Header could use some combination of TH1 and Javascript to actually include the contents of the ticket. ___ fossil-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 it possible to edit a ticket's submission time?
At 11:10 AM 9/2/2011, Ron Wilson wrote: On Fri, Sep 2, 2011 at 1:02 PM, Clark Christensen wrote: FWIW, Fossil does allow you to add fields to the ticket table, markup to the ticket create/edit/view pages, and customize the ticket reports. Yes, I've added custom fields to tickets and made reports that sort on those fields. However, the the request is to be able to have the ticket's first appearance on the Time Line view correspond to the date/time the requester sent his/her message, rather than the time the project maintainer entered the ticket into Fossil. Exactly. Maybe the ticket entry processing could be enhanced to automatically create an event in the case that a ticket's submission date/time is earlier than it's creation date/time? Even simpler would be to include the ticket's creation date as a field on the new ticket entry form, pre-filled to now, instead of it being a system-generated field that is not shown to the user. From a user standpoint, this would look just like the date entry on the New Event page, and could work similarly. I'm not sure it really needs any validation, but it would make sense to prevent the creation of a ticket in the future if that were trivial. This would satisfy my needs for new batches of bug reports, and I can live with the current state for all those already entered. The downside of this is that there is no way to edit the ticket time once the ticket is submitted, which could be needed if a gross typo were made. I'm just trying to avoid the strong temptation to deconstruct the repo, edit the offending ticket's artefact's D record by hand, and reconstruct Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ +1 626 303 1602 +1 626 351 1590 FAX ___ fossil-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 it possible to edit a ticket's submission time?
How many tickets are we talking about? If it is only a few then perhaps try the following: # Set your system date to the date for the ticket sudo date -s 08/11/2011 # create the ticket fossil ui # repeat for remaining tickets Maybe do it in a virtualbox instance just be sure to put the date back to where it should be before syncing. On Fri, Sep 2, 2011 at 11:10 AM, Ron Wilson ronw.m...@gmail.com wrote: On Fri, Sep 2, 2011 at 1:02 PM, Clark Christensen cdcmi...@yahoo.com wrote: FWIW, Fossil does allow you to add fields to the ticket table, markup to the ticket create/edit/view pages, and customize the ticket reports. So it seems like you could add your own field for storing your custom timestamp, and update your ticket reports to reference/include the custom field. You'd probably need to do whatever validations you need in client-side javascript. I think there's info in the Fossil Wiki about adding custom fields. Yes, I've added custom fields to tickets and made reports that sort on those fields. However, the the request is to be able to have the ticket's first appearance on the Time Line view correspond to the date/time the requester sent his/her message, rather than the time the project maintainer entered the ticket into Fossil. Maybe the ticket entry processing could be enhanced to automatically create an event in the case that a ticket's submission date/time is earlier than it's creation date/time? I think that the Ticket Entry page could be enhanced with Javascript to submit a new event to Fossil. At least when I created an event and used the submit button (rather than the preview button), the response from Fossile was a simple acknowledgement, so the Javascript would not have to do more than parse the response for any errors messages and display those errors, if any. The event summary would be the ticket summary and the even body could be a link to the actual ticket. Possibly the Fossil Header could use some combination of TH1 and Javascript to actually include the contents of the ticket. ___ 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] Is it possible to edit a ticket's submission time?
On Fri, Sep 2, 2011 at 9:48 PM, Matt Welland estifo...@gmail.com wrote: # Set your system date to the date for the ticket sudo date -s 08/11/2011 Beware with that - it can confuse your build system. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ 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 performance testing and is it possible to increase the sqlite3 timeout?
We are revisiting fossil for use in our team and I've been doing a little performance testing. One thing that we've seen is when two people access the central repo simultaneously sometimes sync can fail and you get the continue without sync: y/N question. This is benign enough and recovery is easy, just do a manual sync but it is one more thing you have to train users on. This is using the fossil serve and not the cgi server. Does anyone else run into this and are there any settings that could improve it? Will it go away with the cgi based serving? I haven't been able to get cgi to work in our environment yet but that is nothing to do with fossil. The test script simply creates and modifies some random files aproximately 2M in size and checks them in. I checked out the repository into two different directories with different .fossil files and run the scripts simultaneously. They sync, update, modify, commit and when necessary merge constantly. I'm getting about 60 syncs to the central database per minute after a day or two of running with 70k revisions in a 250Meg .fossil file. You can get my script(s) from here if interested: http://chiselapp.com/user/kiatoa/repository/testfossil I'd be very interested in hearing what kind of db access rate people see using cgi. ___ fossil-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 performance testing and is it possible to increase the sqlite3 timeout?
On Fri, Sep 2, 2011 at 5:17 PM, Matt Welland estifo...@gmail.com wrote: We are revisiting fossil for use in our team and I've been doing a little performance testing. One thing that we've seen is when two people access the central repo simultaneously sometimes sync can fail and you get the continue without sync: y/N question. This is benign enough and recovery is easy, just do a manual sync but it is one more thing you have to train users on. This is using the fossil serve and not the cgi server. Does anyone else run into this and are there any settings that could improve it? Will it go away with the cgi based serving? I haven't been able to get cgi to work in our environment yet but that is nothing to do with fossil. You probably have your repository databases set to journal_mode=delete instead of journal_mode=wal. For example, see: http://chiselapp.com/user/kiatoa/repository/testfossil/stat Look on the last line toward the right and you see delete. That's the currently configured journal mode. If you look here: http://www.sqlite.org/src/stat You'll see the journal_mode set to WAL. WAL gives much better concurrency and greatly reduces the chance of sync collisions such as you describe above. To change to WAL mode either do: fossil rebuild --wal Or you can do: fossil sql Then enter PRAGMA journal_mode=WAL. The latter is very fast for even the largest repos. Note that fossil serve merely sets of a simple web-server that runs CGI for each inbound request. So it is no more or less efficient that running CGI off of Apache. The test script simply creates and modifies some random files aproximately 2M in size and checks them in. I checked out the repository into two different directories with different .fossil files and run the scripts simultaneously. They sync, update, modify, commit and when necessary merge constantly. I'm getting about 60 syncs to the central database per minute after a day or two of running with 70k revisions in a 250Meg .fossil file. You can get my script(s) from here if interested: http://chiselapp.com/user/kiatoa/repository/testfossil I'd be very interested in hearing what kind of db access rate people see using cgi. ___ 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] MD5 and SHA1 from OpenSSL
On Thu, Sep 01, 2011 at 07:43:56PM +0200, Dmitry Chestnykh wrote: My simple performance test of SHA-1 from checkin [f2ede7da6d] vs OpenSSL shows that the latter is a bit faster: When I ported the NetBSD implementation, I was considering using OpenSSL. The discussion with Richard was essentially that the performance benefit on known architectures is small enough to be irrelevant. This is further aggrevated by the inconsistent performance of OpenSSL. If you can demonstrate a platform where the delta is huge, it wouldn't be difficult to change (as this patch shows). I'm not even aware of a non-crippled SHA1 hardware implementation. The VIA PadLock support is kind of screwed, so I am not even sure if it would apply for this case. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] cannot push or commit
On Thu, Sep 01, 2011 at 12:53:45PM -0400, Martin S. Weber wrote: Sadly if you clone with http://USER@host/...my.fsl and enter the password in the prompt, it will *not* remember the password (at least last time I tried). You can use USER:PASSWOR@host. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
