Re: [fossil-users] Newbie question about basics of using fossil
On Fri, Jun 8, 2012 at 1:10 AM, Joan Picanyol i Puig wrote: > > The repo file itself needs to live somewhere outside of the "source > tree." > > I'm not convinced this is true, in fact I believe I've had the repo at > the root of the checkout some times. > Sorry, i was thinking of another case: trying to open a repo from within another repo. IIRC fossil fails by default if you do this but allows a flag override that (i may be wrong about the flag). > > Why not just do everything from the root dir? Chicken-egg - the repo > > file will then live under the directory which it controls (this is > > considered [by myself to be] bad practice). > > fossil will ignore the repo file if you don't add it. In the general case it's bad practice to keep the repo in the directory being controlled. Too many things can go wrong. e.g. i once did a global find/grep/replace in a source tree and, due to a broken glob, ended up corrupting my repo file. (i've done similar things to svn checkouts more than once, hosing the .svn directory state.) > I believe the (basic) Unix permission model can be easily supported in > post-NT-Windows. > i'm willing to bet that if sufficient[ly portable] patches were contributed, Richard would bless them. That could be a good idea, but the file format does not seem to be > easily extended to support tagging "F"ile cards, since "T"ags are a card > in the manifest as well. I believe it is much easier to extend de "F"ile > card specification in a backward compatible way by specifying a 3 digit > special code to mean "this permissions as defined by chmod()". Extend it > still further to preserve uid<->login. > i have no idea - i'm not familiar with the raw manifest format. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Newbie question about basics of using fossil
[attempting to regroup subthreads]
[if short on time, please skim to the end to comment on the design]
* Martin Gagnon [20120607 12:06]:
> Le 2012-06-07 à 05:30, Joan Picanyol i Puig a écrit :
> > * Andrew Stuart [20120531 16:15]:
> >> There are source code files and also operating system configuration
> >> files.
> >
> > I would keep two different repositories. For the second one, see below.
> >
> >> I use sudo to edit these files as most of the files are editable only
> >> by root.
[...]
> > Needless to say, I'd encourage you to share your findings for the
> > "fossil as a SCM for OS configuration" use case.
>
> For file from '/': look this thread:
>
> http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05576.html
>
> Fossil isn't usable from '/' dir. as a checkout. Some commands
> sometimes work, most of them doesn't. So for system config. I end up
> working on a checkout somewhere in a subdir in my home and I have a
> script which copy file that have changed from '/' to my checkout.
> ('fossil ls' is useful here)
I did save your message from that thread, but ruby & meld are
incompatible with my "minimal depencies" policy. Also, sudo does have
its own issues and is not available in several scenarios.
* Stephan Beal [20120607 12:04]:
> On Thu, Jun 7, 2012 at 11:30 AM, Joan Picanyol i Puig <
> lists-fos...@biaix.org> wrote:
>
> > * Andrew Stuart [20120531 16:15]:
> > > There are source code files and also operating system configuration
> > > files.
> >
> > I would keep two different repositories. For the second one, see below.
>
> And i would go one step further and NOT use fossil for the system files.
I would consider being able to use fossil for this a step further :)
> Fossil does not support file permissions other than the +x bit
But this can be just a missing feature, from
http://www.fossil-scm.org/fossil/doc/trunk/www/fileformat.wiki :
The optional 3rd argument defines any special access permissions
associated with the file. The only special code currently defined is
"x" which means that the file is executable. All files are always
readable and writable.
> and does not understand user/group ownership. Without that, using it
> for managing system-level files is a disaster waiting to happen. If
> certain files do not have exactly the right permissions... kaboom.
pre-commit/post-update hooks could be used to work around this issue.
See below regarding your "use tags for tracking permissions proposal".
> The repo file itself needs to live somewhere outside of the "source tree."
I'm not convinced this is true, in fact I believe I've had the repo at
the root of the checkout some times.
> Why not just do everything from the root dir? Chicken-egg - the repo
> file will then live under the directory which it controls (this is
> considered [by myself to be] bad practice).
fossil will ignore the repo file if you don't add it.
> Fossil is not the right tool for that job.
I'd certainly like it to be.
* Martin Gagnon [20120607 12:32]:
> may be storing the output of: ls -ln $(fossil ls) in the
> repo could be used from a script to check/restore permissions...
uids (or SIDs in Windows) might not be constant among diferents systems.
I believe the uid<->uname mapping should be preserved on commit and
require a command line override if it differs on checkout
* Stephan Beal [20120607 13:29]:
> Permissions are a touchy subject because they're inherently
> platform-specific and fossil tries to be platform-agnostic insofar as is
> feasible. Once fossil has Unix permissions support, people will want
> extended attributes support, ACLs, and other weird stuff (not that Unix
> permissions aren't weird, but they are the most common case).
I believe the (basic) Unix permission model can be easily supported in
post-NT-Windows.
* Stephan Beal [20120607 13:38]:
> i think tags (which are key/value pairs in fossil) could be used for
> this if we would extend them to be able to tag arbitrary artifact
> types (i seem to recall, possibly incorrectly, that we can only tag
> commits right now?). e.g. tag unix-perms=0754.
That could be a good idea, but the file format does not seem to be
easily extended to support tagging "F"ile cards, since "T"ags are a card
in the manifest as well. I believe it is much easier to extend de "F"ile
card specification in a backward compatible way by specifying a 3 digit
special code to mean "this permissions as defined by chmod()". Extend it
still further to preserve uid<->login.
qvb
--
pica
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Update of checkout after push operations.
I have one central repository, that I use as an archive for a web site. The web site root directory is actually checkout of the trunk branch of the repository. I am using lighttpd server on Linux and fossil as a CGI script in very standard manner. So, I need when I make a push (or commit with autosync) from a remote computer to the central repository, some script to make "fossil update" to the checkout directory and this way to update the content of the web site. Is it possible at all? Any Ideas? ___ 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] Newbie question about basics of using fossil
At Thu, 7 Jun 2012 12:11:00 +0200, Stephan Beal wrote: > And i would go one step further and NOT use fossil for the system files. > Fossil does not support file permissions > other than the +x bit and does not understand user/group ownership. Without > that, using it for managing system-level > files is a disaster waiting to happen. If certain files do not have exactly > the right permissions... kaboom. > > > I use sudo to edit these files as most of the files are editable only > > by root. > > > > How do I use Fossil in this context? > > i strongly recommend against it. Others on this list will just as strongly > argue the opposite, however. (And we're > all right ;) > I personally use fossil for (among other things), managing my /etc directory on two different machines. Thus far, I've had no problems, although I took care to ensure that certain offending files were not included. I manage the repository as root, make sure that all permissions remain root only, with no group access, and made the web interface permissions never allow nobody/anonymous (there were other details that I paid attention to, security-wise, as well). That said, I primarily just use it to revert or backup certain files when they change unexpectedly. I don't think that managing the '/' directory under fossil seems like a great idea, but I've been wrong before. :) Tim ___ 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] Markdown engine integrated into fossil
On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin < baptiste.darous...@gmail.com> wrote: > Is there any status on this? rejected ? still under review ? > DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on July 3! > > regards, > Bapt > ___ > 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] Markdown engine integrated into fossil
Is there any status on this? rejected ? still under review ? regards, Bapt ___ 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] Newbie question about basics of using fossil
On Thu, Jun 7, 2012 at 1:36 PM, Stephan Beal wrote: > and fossil tries to be platform-agnostic insofar as is feasible. Once > fossil has Unix permissions support, people will want extended attributes > support, ACLs, and other weird stuff (not that Unix permissions aren't > weird, but they are the most common case). > What "might be possible" within the current code base would be something similar to svn properties. i think tags (which are key/value pairs in fossil) could be used for this if we would extend them to be able to tag arbitrary artifact types (i seem to recall, possibly incorrectly, that we can only tag commits right now?). e.g. tag unix-perms=0754. That might even have other interesting uses (specifying the mime type comes to mind (fossil's current support for mime types is quite minimal)) and abuses (nothing comes to mind, but i have no gift for spotting malicious abuses and attack vectors). When/if tcl scripting ever becomes a core fossil feature, a post-checkout/post-revert script could then check/set permissions based on the tags. Anyway... -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Newbie question about basics of using fossil
On Thu, Jun 7, 2012 at 12:38 PM, Martin Gagnon wrote: > sure it would be nice to keep permission and ownership may be storing > the output of: ls -ln $(fossil ls) in the repo could be used from a > script to check/restore permissions... > Permissions are a touchy subject because they're inherently platform-specific and fossil tries to be platform-agnostic insofar as is feasible. Once fossil has Unix permissions support, people will want extended attributes support, ACLs, and other weird stuff (not that Unix permissions aren't weird, but they are the most common case). Fossil initially had _no_ support for permission, on portability/philosophical grounds, but Richard eventually caved to public pressure and added support for the executable bit primarily because not having it breaks the "configure" script which lives in the vast majority of open source repos. Fossil is designed/meant for managing _source repos_, and it is very rare that source repos use non-default permissions for files (other than +x, which is an unfortunate but exceedingly common special case). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] /info/... failure
On Thu, Jun 07, 2012 at 06:51:55AM -0400, Richard Hipp wrote: > On Thu, Jun 7, 2012 at 6:46 AM, Lluís Batlle i Rossell > wrote: > > > On Thu, Jun 07, 2012 at 06:36:23AM -0400, Richard Hipp wrote: > > > On Thu, Jun 7, 2012 at 3:51 AM, Christopher Vance > >wrote: > > > > > > > Firefox gave the message I quoted. > > > > Chrome said that the server returned no data. > > > > Safari just shows an empty page. > > > > Telnet to the relevant port returns no data. > > > > > > > > > > Ok. Good clue. > > > > > > It appears that the Fossil binary is segfaulting while it is trying to > > > generate the page. What version of Fossil are you running? Have you > > tried > > > updating to the tip of trunk? > > > > As of debugging this, you (Christopher) can look at the PID of the fossil > > server, attach to it with gdb (gdb fossil PID), then run "set > > follow-fork-mode > > child", and tell gdb "contiue". Then try to visit the page, and gdb should > > stop > > at the segfaulting point. > > > > Not that easy, unfortunately. Fossil starts a new instance of itself to > handle each incoming page request, leaving the debugger looking at the > original instance, which is not the one that is crashing. > > The way to debug this is: > > (1) Start your debugger > (2) Invoke fossil with a single argument "test-http" > (3) Manually type in an HTTP header. This can be minimal: "GET > /timeline". You'll need to press enter twice to signal the end-of-header. > > With any luck, you'll hit the segfault that way. But sometimes, the > problem is due to a specific login or user permission, in which case a more > elaborate HTTP request has to be entered. Well, the key was "set follow-fork-mode child". But that requires the user to have the browser ready to access the faulting link as the *first* fossil request after continuing gdb. :) I find the core dump way easier, sure. I didn't know the test-http approach. Thank you, 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] /info/... failure
On Thu, Jun 7, 2012 at 6:46 AM, Lluís Batlle i Rossell wrote: > On Thu, Jun 07, 2012 at 06:36:23AM -0400, Richard Hipp wrote: > > On Thu, Jun 7, 2012 at 3:51 AM, Christopher Vance >wrote: > > > > > Firefox gave the message I quoted. > > > Chrome said that the server returned no data. > > > Safari just shows an empty page. > > > Telnet to the relevant port returns no data. > > > > > > > Ok. Good clue. > > > > It appears that the Fossil binary is segfaulting while it is trying to > > generate the page. What version of Fossil are you running? Have you > tried > > updating to the tip of trunk? > > As of debugging this, you (Christopher) can look at the PID of the fossil > server, attach to it with gdb (gdb fossil PID), then run "set > follow-fork-mode > child", and tell gdb "contiue". Then try to visit the page, and gdb should > stop > at the segfaulting point. > Not that easy, unfortunately. Fossil starts a new instance of itself to handle each incoming page request, leaving the debugger looking at the original instance, which is not the one that is crashing. The way to debug this is: (1) Start your debugger (2) Invoke fossil with a single argument "test-http" (3) Manually type in an HTTP header. This can be minimal: "GET /timeline". You'll need to press enter twice to signal the end-of-header. With any luck, you'll hit the segfault that way. But sometimes, the problem is due to a specific login or user permission, in which case a more elaborate HTTP request has to be entered. > > It would be better if you can do that with the trunk fossil, built with > debug > info, without optimisations, and having the source code available. > > 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 > -- 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] /info/... failure
On Thu, Jun 07, 2012 at 12:46:07PM +0200, Lluís Batlle i Rossell wrote: > On Thu, Jun 07, 2012 at 06:36:23AM -0400, Richard Hipp wrote: > > On Thu, Jun 7, 2012 at 3:51 AM, Christopher Vance wrote: > > > > > Firefox gave the message I quoted. > > > Chrome said that the server returned no data. > > > Safari just shows an empty page. > > > Telnet to the relevant port returns no data. > > > > > > > Ok. Good clue. > > > > It appears that the Fossil binary is segfaulting while it is trying to > > generate the page. What version of Fossil are you running? Have you tried > > updating to the tip of trunk? > > As of debugging this, you (Christopher) can look at the PID of the fossil > server, attach to it with gdb (gdb fossil PID), then run "set follow-fork-mode > child", and tell gdb "contiue". Then try to visit the page, and gdb should > stop > at the segfaulting point. > > It would be better if you can do that with the trunk fossil, built with debug > info, without optimisations, and having the source code available. Another easier way is to activate core dumps. "ulimit -S -c unlimited" before starting the server. Then visit the page, and wait for a core dump file to appear. Then you can load it in gdb: gdb fossil core ___ 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] /info/... failure
On Thu, Jun 07, 2012 at 06:36:23AM -0400, Richard Hipp wrote: > On Thu, Jun 7, 2012 at 3:51 AM, Christopher Vance wrote: > > > Firefox gave the message I quoted. > > Chrome said that the server returned no data. > > Safari just shows an empty page. > > Telnet to the relevant port returns no data. > > > > Ok. Good clue. > > It appears that the Fossil binary is segfaulting while it is trying to > generate the page. What version of Fossil are you running? Have you tried > updating to the tip of trunk? As of debugging this, you (Christopher) can look at the PID of the fossil server, attach to it with gdb (gdb fossil PID), then run "set follow-fork-mode child", and tell gdb "contiue". Then try to visit the page, and gdb should stop at the segfaulting point. It would be better if you can do that with the trunk fossil, built with debug info, without optimisations, and having the source code available. 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] Problem with "fossil winsrv" (cont'd)
On Thu, Jun 7, 2012 at 12:24 AM, Richie Adler wrote: > Thomas Schnurrenberger decía, en el mensaje "Re: [fossil-users] Problem > with > "fossil winsrv" (cont'd)" del Miércoles, 06 de Junio de 2012 17:35:59: > > On 06.06.2012 20:59, Marcelo wrote: > >> > >> What do you think of my proposed change? > >> > > I have committed a fix to the Fossil repository. > > It can be found in the branch "winsrv". > > > > Please try it out. > > No development enviroment here, but I'll see what I can do. > You can download a complete development environment from http://www.mingw.org/ - I did this just the other day on the Windows 8 RC and it works great. After mingw is installed, check out the latest Fossil trunk version and then do: sh configure make You will be left with "fossil.exe" in the top-level directory. Then move "fossil.exe" to someplace on your path. > > -- > > o-=< Marcelo >=-o > > ___ > 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] Newbie question about basics of using fossil
On Thu, Jun 7, 2012 at 6:11 AM, Stephan Beal wrote: > On Thu, Jun 7, 2012 at 11:30 AM, Joan Picanyol i Puig < > lists-fos...@biaix.org> wrote: > >> * Andrew Stuart [20120531 16:15]: >> > There are source code files and also operating system configuration >> > files. >> >> I would keep two different repositories. For the second one, see below. >> > > And i would go one step further and NOT use fossil for the system files. > Fossil does not support file permissions other than the +x bit and does not > understand user/group ownership. Without that, using it for managing > system-level files is a disaster waiting to happen. If certain files do not > have exactly the right permissions... kaboom. > > > I use sudo to edit these files as most of the files are editable only >> > by root. >> > >> > How do I use Fossil in this context? >> > > i strongly recommend against it. Others on this list will just as strongly > argue the opposite, however. (And we're all right ;) > > >> > Where should I set up the fossil repository? In my unprivileged user >> > home directory? >> > > The repo file itself needs to live somewhere outside of the "source tree." > i tend to keep all of mine in a single dir. > > >> > How should I be handling the need to use sudo to access the various >> > files that I work on? I suspect I'll be running into various >> > permissions issues constantly? >> > > Yes. See above. If you manage to hose the rights on /etc/shadow then you > could prevent users (i.e. yourself) from logging in. > > > Would my workflow look something like this for example? >> > 1: Create fossil repo in my home directory >> > 2: Go to the location of a file I want to put in fossil >> > 3: "fossil open" in this directory >> > 4: "fossil add" the files I wish to put under scm >> > > That's more or less correct, but understand that all files stored in a > repo must live under the same directory structure on your system. Thus you > need one for /etc, one for /var/, or whatever it is you want to save. Why > not just do everything from the root dir? Chicken-egg - the repo file will > then live under the directory which it controls (this is considered [by > myself to be] bad practice). > > > > >> > Although I have read the quickstart guide it doesn't really nudge me >> > in the right direction of how to actually drive it in a practical >> > manner, especially where I have to use sudo. >> > > Fossil is not the right tool for that job. > > > (Let the flame wars begin! ;) > > In my use case, I only use it in one direction. It's only to have a nice history of what change in system files. I would not do a checkout with a specific revision or anything else that would alter files in system config using a fossil command.. for sure it would be nice to keep permission and ownership may be storing the output of: ls -ln $(fossil ls) in the repo could be used from a script to check/restore permissions... -- Martin G. ___ 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] /info/... failure
On Thu, Jun 7, 2012 at 3:51 AM, Christopher Vance wrote: > Firefox gave the message I quoted. > Chrome said that the server returned no data. > Safari just shows an empty page. > Telnet to the relevant port returns no data. > Ok. Good clue. It appears that the Fossil binary is segfaulting while it is trying to generate the page. What version of Fossil are you running? Have you tried updating to the tip of trunk? > > I have local copies of the sqlite and fossil repositories with some > extra tickets for myself, and a branch paralleling release which > differs only by including an additional makefile. The latest revisions > I have on both repos (208825cd83 and cff9cc34f0) have this problem. > > On 6 June 2012 22:37, Richard Hipp wrote: > > > > > > On Wed, Jun 6, 2012 at 7:55 AM, Christopher Vance > > wrote: > >> > >> I'm running fossil 1.22 on MacOS Lion. With a number of repositories, > >> but not all of them, I find the web ui does not allow access to > >> details of some checkins. (The use case is that I want to add the > >> ticket reference to the subject line because I forgot on commit.) The > >> error I get in this case is always 'The connection was reset'. > > > > > > It sounds like that message is coming from your web browser. Which web > > browser are you using? > > > >> > >> > >> -- > >> Christopher Vance > >> ___ > >> 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 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] Newbie question about basics of using fossil
Le 2012-06-07 à 05:30, Joan Picanyol i Puig a écrit :
> * Andrew Stuart [20120531 16:15]:
>> There are source code files and also operating system configuration
>> files.
>
> I would keep two different repositories. For the second one, see below.
>
>> I use sudo to edit these files as most of the files are editable only
>> by root.
>>
>> How do I use Fossil in this context?
>> Where should I set up the fossil repository? In my unprivileged user
>> home directory?
>> How should I be handling the need to use sudo to access the various
>> files that I work on? I suspect I'll be running into various
>> permissions issues constantly?
>>
>> Would my workflow look something like this for example?
>> 1: Create fossil repo in my home directory
>> 2: Go to the location of a file I want to put in fossil
>> 3: "fossil open" in this directory
>> 4: "fossil add" the files I wish to put under scm
>>
>> Although I have read the quickstart guide it doesn't really nudge me
>> in the right direction of how to actually drive it in a practical
>> manner, especially where I have to use sudo.
>
> This has come up before. See
> http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg04760.html
>
> What I'm currently doing is have soft-link to / in the directory of
> a non-root admin user. I don't know if/how it interacts with symlinks
> support. The versions of fossil in which I have this setup are:
>
>This is fossil version 1.21 [002580c50d] 2011-12-13 13:53:56 UTC
>This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC
>
> I'm still hoping for improved handling of permissions, and have not yet
> explored the possibilities of "Add the ability to run TH1 scripts after
> sync requests"
>
> Needless to say, I'd encourage you to share your findings for the
> "fossil as a SCM for OS configuration" use case.
>
For file from '/': look this thread:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05576.html
Fossil isn't usable from '/' dir. as a checkout. Some commands sometimes work,
most of them doesn't. So for system config. I end up working on a checkout
somewhere in a subdir in my home and I have a script which copy file that have
changed from '/' to my checkout. ('fossil ls' is useful here)
So I always edit files from '/', and after I sync to my checkout dir with the
script. I would like very much to work directly where file are used, I might
try to start a branch to fix that eventually.
--
Martin G.
___
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] Newbie question about basics of using fossil
On Thu, Jun 7, 2012 at 11:30 AM, Joan Picanyol i Puig < lists-fos...@biaix.org> wrote: > * Andrew Stuart [20120531 16:15]: > > There are source code files and also operating system configuration > > files. > > I would keep two different repositories. For the second one, see below. > And i would go one step further and NOT use fossil for the system files. Fossil does not support file permissions other than the +x bit and does not understand user/group ownership. Without that, using it for managing system-level files is a disaster waiting to happen. If certain files do not have exactly the right permissions... kaboom. > I use sudo to edit these files as most of the files are editable only > > by root. > > > > How do I use Fossil in this context? > i strongly recommend against it. Others on this list will just as strongly argue the opposite, however. (And we're all right ;) > > Where should I set up the fossil repository? In my unprivileged user > > home directory? > The repo file itself needs to live somewhere outside of the "source tree." i tend to keep all of mine in a single dir. > > How should I be handling the need to use sudo to access the various > > files that I work on? I suspect I'll be running into various > > permissions issues constantly? > Yes. See above. If you manage to hose the rights on /etc/shadow then you could prevent users (i.e. yourself) from logging in. > Would my workflow look something like this for example? > > 1: Create fossil repo in my home directory > > 2: Go to the location of a file I want to put in fossil > > 3: "fossil open" in this directory > > 4: "fossil add" the files I wish to put under scm > That's more or less correct, but understand that all files stored in a repo must live under the same directory structure on your system. Thus you need one for /etc, one for /var/, or whatever it is you want to save. Why not just do everything from the root dir? Chicken-egg - the repo file will then live under the directory which it controls (this is considered [by myself to be] bad practice). > > Although I have read the quickstart guide it doesn't really nudge me > > in the right direction of how to actually drive it in a practical > > manner, especially where I have to use sudo. > Fossil is not the right tool for that job. (Let the flame wars begin! ;) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Newbie question about basics of using fossil
* Andrew Stuart [20120531 16:15]: > There are source code files and also operating system configuration > files. I would keep two different repositories. For the second one, see below. > I use sudo to edit these files as most of the files are editable only > by root. > > How do I use Fossil in this context? > Where should I set up the fossil repository? In my unprivileged user > home directory? > How should I be handling the need to use sudo to access the various > files that I work on? I suspect I'll be running into various > permissions issues constantly? > > Would my workflow look something like this for example? > 1: Create fossil repo in my home directory > 2: Go to the location of a file I want to put in fossil > 3: "fossil open" in this directory > 4: "fossil add" the files I wish to put under scm > > Although I have read the quickstart guide it doesn't really nudge me > in the right direction of how to actually drive it in a practical > manner, especially where I have to use sudo. This has come up before. See http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg04760.html What I'm currently doing is have soft-link to / in the directory of a non-root admin user. I don't know if/how it interacts with symlinks support. The versions of fossil in which I have this setup are: This is fossil version 1.21 [002580c50d] 2011-12-13 13:53:56 UTC This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC I'm still hoping for improved handling of permissions, and have not yet explored the possibilities of "Add the ability to run TH1 scripts after sync requests" Needless to say, I'd encourage you to share your findings for the "fossil as a SCM for OS configuration" use case. qvb -- pica ___ 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] /info/... failure
Disabling 'Show version differences by default' in the Timeline configuration enables access to at least some of these changes. Doing this with fossil checkin cff9cc34f0 enables me to see the checkin data. I am able to view the differences as a patch or as a unified diff, but the side-by-side diff gives me the same no data problem mentioned before. The repo on fossil-scm.org, of course, behaves much more nicely. :-) Do you have some things I could do to help diagnose and get rid of this problem? -- Christopher Vance On 7 June 2012 17:51, Christopher Vance wrote: > Firefox gave the message I quoted. > Chrome said that the server returned no data. > Safari just shows an empty page. > Telnet to the relevant port returns no data. > > I have local copies of the sqlite and fossil repositories with some > extra tickets for myself, and a branch paralleling release which > differs only by including an additional makefile. The latest revisions > I have on both repos (208825cd83 and cff9cc34f0) have this problem. > > On 6 June 2012 22:37, Richard Hipp wrote: >> >> >> On Wed, Jun 6, 2012 at 7:55 AM, Christopher Vance >> wrote: >>> >>> I'm running fossil 1.22 on MacOS Lion. With a number of repositories, >>> but not all of them, I find the web ui does not allow access to >>> details of some checkins. (The use case is that I want to add the >>> ticket reference to the subject line because I forgot on commit.) The >>> error I get in this case is always 'The connection was reset'. >> >> >> It sounds like that message is coming from your web browser. Which web >> browser are you using? >> >>> >>> >>> -- >>> Christopher Vance >>> ___ >>> 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 mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] /info/... failure
Firefox gave the message I quoted. Chrome said that the server returned no data. Safari just shows an empty page. Telnet to the relevant port returns no data. I have local copies of the sqlite and fossil repositories with some extra tickets for myself, and a branch paralleling release which differs only by including an additional makefile. The latest revisions I have on both repos (208825cd83 and cff9cc34f0) have this problem. On 6 June 2012 22:37, Richard Hipp wrote: > > > On Wed, Jun 6, 2012 at 7:55 AM, Christopher Vance > wrote: >> >> I'm running fossil 1.22 on MacOS Lion. With a number of repositories, >> but not all of them, I find the web ui does not allow access to >> details of some checkins. (The use case is that I want to add the >> ticket reference to the subject line because I forgot on commit.) The >> error I get in this case is always 'The connection was reset'. > > > It sounds like that message is coming from your web browser. Which web > browser are you using? > >> >> >> -- >> Christopher Vance >> ___ >> 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 mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
