[fossil-users] Odd remote-url encoding problem
I got a user who gets this when they try to use remote-url: $ fossil remote-url http://174.143.208.114:5/ http://174.143.208.114%3A5/ $ fossil pull Server:http://174.143.208.114%3A5/ Bytes Cards Artifacts Deltas Send: 193 3 0 0 fossil: can't resolve host name: 174.143.208.114:5 Notice how it's URL converting the : to %3A. Doesn't do that on anyone else's system. He's using: fossil version [3a5b4ad4e2] 2010-08-31 18:21:02 UTC -- Zed A. Shaw http://zedshaw.com/ ___ 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] Odd remote-url encoding problem
On Thu, Sep 02, 2010 at 06:29:26AM -0400, Richard Hipp wrote: This is a bug introduced by the recent ssh:// enhancement. It is fixed now. http://www.fossil-scm.org/fossil/ci/ac8c21b986 Whew! I was gonna have to track that down all day in Mongrel2. :-) -- Zed A. Shaw http://zedshaw.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] fossil on osx with launchd or as a StartupItem
Hi, I was looking at using launchd or startup items to run fossil on my laptop, but I the documentation I have read on fossil-scm.org and developer.apple.com has left me worried that neither are suitable. Is anyone else autostarting fossil on OS X? Cheers, Stephen -- Jobs run from launchd should not duplicate launchd functionality; for instance, they should not use chroot(2). Furthermore, they should not do the things normally required of daemon processes, such as detaching from the terminal they are initially attached to. The only things that are strictly prohibited, however, are fork()/exit() combinations (including indirect methods, such as the daemon(3) library call). A server which attempts to run itself as a daemon in this way will seem to have finished running, potentially leading to launchd respawning it, or disabling the service. As launchd does not get stalled waiting for a child that hasn't yet exited, it's not necessary to try to prevent it. -- http://developer.apple.com/macosx/launchd.html When you do run fossil as root, it automatically puts itself in a chroot jail in the same directory as the repository, then drops root privileges prior to reading any information from the request. Startup Items: http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/Articles/StartupItems.html#//apple_ref/doc/uid/20002132-CJBBHDII ___ 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 on osx with launchd or as a StartupItem
On Thu, Sep 2, 2010 at 3:19 PM, Stephen De Gabrielle spdegabrie...@gmail.com wrote: Hi, I was looking at using launchd or startup items to run fossil on my laptop, but I the documentation I have read on fossil-scm.org and developer.apple.com has left me worried that neither are suitable. Is anyone else autostarting fossil on OS X? I once tried this and came up with the plist attached. I seem to recall actually getting it to work, by typing some obscure command prefaced by sudo in order to get launchd to read in the appropriate plist. But I never could get launchd to run fossil by default after a reboot. inetd was so easy. xinetd is less easy, but doable. launchd is unmanageably complicated. How do they call this progress? I think the key here is to launch Fossil in inetd mode (using the fossil http command) and not in server mode (not with fossil server). That's the way I do it on my Linux desktop and it works great there. (On the Fossil website, Fossil is launched as CGI.) Let us know if you get it working and be sure to tell us what you did. -- ?xml version=1.0 encoding=UTF-8? !DOCTYPE plist PUBLIC -//Apple Computer//DTD PLIST 1.0//EN http://www.apple.com/DTDs/PropertyList-1.0.dtd; plist version=1.0 dict keyDebug/key false/ keyGroupName/key stringdrh/string keyLabel/key stringorg.fossil-scm.fossil/string keyOnDemand/key true/ keyProgram/key string/usr/bin/fossil/string keyProgramArguments/key array string/usr/bin/fossil/string stringhttp/string string/Users/drh/sqlite/string /array keyServiceDescription/key stringSVN Version Control System/string keySockets/key dict keyListeners/key array dict keySockFamily/key stringIPv4/string keySockServiceName/key stringhttp-alt/string keySockType/key stringstream/string /dict dict keySockFamily/key stringIPv6/string keySockServiceName/key stringhttp-alt/string keySockType/key stringstream/string /dict /array /dict keyUmask/key integer2/integer keyUserName/key stringdrh/string keyinetdCompatibility/key dict keyWait/key false/ /dict /dict /plist - Cheers, Stephen -- Jobs run from launchd should not duplicate launchd functionality; for instance, they should not use chroot(2). Furthermore, they should not do the things normally required of daemon processes, such as detaching from the terminal they are initially attached to. The only things that are strictly prohibited, however, are fork()/exit() combinations (including indirect methods, such as the daemon(3) library call). A server which attempts to run itself as a daemon in this way will seem to have finished running, potentially leading to launchd respawning it, or disabling the service. As launchd does not get stalled waiting for a child that hasn't yet exited, it's not necessary to try to prevent it. -- http://developer.apple.com/macosx/launchd.html When you do run fossil as root, it automatically puts itself in a chroot jail in the same directory as the repository, then drops root privileges prior to reading any information from the request. Startup Items: http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/Articles/StartupItems.html#//apple_ref/doc/uid/20002132-CJBBHDII ___ 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] How to remove all deleted files at once?
Hi, Firstly, thank you for this great scm. I really love SQLite and have been using it on my blogging app - Pritlog. I recently started using fossil as a repository for this app. One question I had is - how do I remove all the physically deleted files from the repository? I know that we can do this one file at a time. But, is there a way to do it at once? In Git latest version, I believe when we use --all, it takes care of this. Thanks for your help, Prit (http://pritlog.com) ___ 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 remove all deleted files at once?
On Thu, Sep 2, 2010 at 4:20 PM, Prit p...@hardkap.com wrote:
Hi,
Firstly, thank you for this great scm. I really love SQLite and have been
using it on my blogging app - Pritlog. I recently started using fossil as a
repository for this app. One question I had is - how do I remove all the
physically deleted files from the repository? I know that we can do this one
file at a time. But, is there a way to do it at once? In Git latest version,
I believe when we use --all, it takes care of this.
fossil rm `fossil status | grep MISSING | awk '{print $2}'`
I have never created an automatic way to remove from the repository all
files that have been physically removed from the check-out - mostly becomes
that is not something that I often do, and on the rare occasions when I do
something like that, a unix shell command such as the above is usually
sufficient.
Thanks for your help,
Prit (http://pritlog.com)
___
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] bug in fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC
In the latest snapshot build of fossil, I get problems with URLs in autosync: PS C:\rev\src\capstray fossil ver This is fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC PS C:\rev\src\capstray fossil update trunk Autosync: http://rev:password%40svn.thereverend.org%3A8080/capstray Bytes Cards Artifacts Deltas Send: 146 2 0 0 c:\rev\bin\fossil.exe: can't resolve host name: rev RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunicationsT ___ 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 remove all deleted files at once?
On Thu, Sep 2, 2010 at 4:20 PM, Prit p...@hardkap.com wrote:
Hi,
Firstly, thank you for this great scm. I really love SQLite and have been
using it on my blogging app - Pritlog. I recently started using fossil as
a
repository for this app. One question I had is - how do I remove all the
physically deleted files from the repository? I know that we can do this
one
file at a time. But, is there a way to do it at once? In Git latest
version,
I believe when we use --all, it takes care of this.
fossil rm `fossil status | grep MISSING | awk '{print $2}'`
I have never created an automatic way to remove from the repository all
files that have been physically removed from the check-out - mostly becomes
that is not something that I often do, and on the rare occasions when I do
something like that, a unix shell command such as the above is usually
sufficient.
Thanks for your help,
Prit (http://pritlog.com)
--
D. Richard Hipp
d...@sqlite.org
Thanks Richard for the prompt reply. It would be great if an automated way
can be implemented into fossil. I switch between Windows and Linux quiet
often. Some of the neat linux commands don't have equivalent in Windows.
Also, it might be easier for users to remember and use if there is a
pre-built option. Anyway, whether this is added to fossil or not, I am a fan
of this software and have already switched over to fossil for the pritlog
software.
Thanks for your help,
Prit (http://pritlog.com)
___
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 in fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC
In the latest snapshot build of fossil, I get problems with URLs in autosync: PS C:\rev\src\capstray fossil ver This is fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC PS C:\rev\src\capstray fossil update trunk Autosync: http://rev:password%40svn.thereverend.org%3A8080/capstray Bytes Cards Artifacts Deltas Send: 146 2 0 0 c:\rev\bin\fossil.exe: can't resolve host name: rev RW It looks like fossil remote-url is also adversely affected. All of those +++ symbols below are some bazaar side effect. I didn't type them in or redact any of it. PS C:\rev\src\capstray fossil remote-url http://rev:passw...@svn.thereverend.org:8080/capstray http://rev:0password+revvn.thereverend.org%25 PS C:\rev\src\capstray fossil update trunk Autosync: http://rev:0password+revvn.thereverend.org%25 Bytes Cards Artifacts Deltas Send: 146 2 0 0 c:\rev\bin\fossil.exe: can't resolve host name: rev ___ 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 in fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC
On Thu, Sep 2, 2010 at 7:35 PM, Wilson, Ronald rwils...@harris.com wrote: In the latest snapshot build of fossil, I get problems with URLs in autosync: PS C:\rev\src\capstray fossil ver This is fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC PS C:\rev\src\capstray fossil update trunk Autosync: http://rev:password%40svn.thereverend.org%3A8080/capstray Bytes Cards Artifacts Deltas Send: 146 2 0 0 c:\rev\bin\fossil.exe: can't resolve host name: rev RW It looks like fossil remote-url is also adversely affected. All of those +++ symbols below are some bazaar side effect. I didn't type them in or redact any of it. I suspect your problem was fixed early this morning by http://www.fossil-scm.org/fossil/ci/ac8c21b986 - please try that patch and see if it doesn't get things working for you again. PS C:\rev\src\capstray fossil remote-url http://rev:passw...@svn.thereverend.org:8080/capstray http://rev:0password+revvn.thereverend.org%25 PS C:\rev\src\capstray fossil update trunk Autosync: http://rev:0password+revvn.thereverend.org%25 Bytes Cards Artifacts Deltas Send: 146 2 0 0 c:\rev\bin\fossil.exe: can't resolve host name: rev ___ 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 in fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC
I'm using that patch. PS C:\rev\src\capstray fossil ver This is fossil version [ac8c21b986] 2010-09-02 10:28:21 UT RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications(tm) From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp Sent: Thursday, September 02, 2010 7:45 PM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] bug in fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC On Thu, Sep 2, 2010 at 7:35 PM, Wilson, Ronald rwils...@harris.commailto:rwils...@harris.com wrote: In the latest snapshot build of fossil, I get problems with URLs in autosync: PS C:\rev\src\capstray fossil ver This is fossil version [ac8c21b986] 2010-09-02 10:28:21 UTC PS C:\rev\src\capstray fossil update trunk Autosync: http://rev:password%40svn.thereverend.org%3A8080/capstray Bytes Cards Artifacts Deltas Send: 146 2 0 0 c:\rev\bin\fossil.exe: can't resolve host name: rev RW It looks like fossil remote-url is also adversely affected. All of those +++ symbols below are some bazaar side effect. I didn't type them in or redact any of it. I suspect your problem was fixed early this morning by http://www.fossil-scm.org/fossil/ci/ac8c21b986 - please try that patch and see if it doesn't get things working for you again. PS C:\rev\src\capstray fossil remote-url http://rev:passw...@svn.thereverend.org:8080/capstray http://rev:0password+revvn.thereverend.org%25 PS C:\rev\src\capstray fossil update trunk Autosync: http://rev:0password+revvn.thereverend.org%25 Bytes Cards Artifacts Deltas Send: 146 2 0 0 c:\rev\bin\fossil.exe: can't resolve host name: rev ___ fossil-users mailing list fossil-users@lists.fossil-scm.orgmailto:fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.orgmailto:d...@sqlite.org inline: image001.png___ 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] Evaluating Fossil and have a question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/02/2010 09:12 PM, Richard Hipp wrote: I'm not exactly clear on what you read, but I think what was being communicated is that if you have a single project repository, you can checkout multiple trees that one repository into different directories of your local disk. So if your repository is named ~/myrepo.fossil, you might have three different checkouts at ~/myproj/dev, ~/myproj/testing, and ~/myproj/release. All three checkouts can be of different versions of the project. Each can update and commit independently of the others. But all three use the same repository files myproj.fossil. Here's what I read: Each source tree that is controlled by fossil is associated with a single repository on the local disk drive. You can tie two or more source trees to a single repository if you want (though one tree per repository is the most common configuration.) So a single repository can be associated with many source trees, but each source tree is associated with only one repository. So I thought that might have meant multiple, distinct trees, similar to how one can have branches in Git with independent directory structures but all separate from each other, even if they are stored in the same repository. I'm wondering how difficult/desirable it might be to support a case like the one I mentioned? Maybe you could have a single repository with multiple roots, and do something like: mkdir project_a; cd project_a; fossil open ../myproj.fossil project_a cd ..; mkdir project_b;... Or maybe some means of opening a project's subdirectory such that open with normal parameters would copy out all subdirectories/projects while open myproj.fossil src might only extract the src directory, but that may be entirely impractical. Thanks for the quick and detailed response. :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyAYQEACgkQIaMjFWMehWKqSACeKKuQ6AfqFT1yYwCURaq5wHIg 3SwAnRZ37vOsS87KMmKmRj2y1NWnrlkg =CBuX -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
