Re: [fossil-users] Login Group Confusion
On Thu, Feb 23, 2012 at 7:16 AM, Chris Peachment wrote: > Hello All: > > I'm using a copy of fossil compiled from the latest leaf: > >Fossil version 1.22 [3a44f95f40] 2012-02-21 02:01:20 > > I have 6 repositories all stored in the same directory on a Linux64 box > as a remote server (Bluehost.com). > > All repositories require login for access and all have the same login > id and pw for a super user. They are all accessible individually over > the internet via a browser, using separate logins to each. > > I am attempting to establish single sign on for all 6 repositories > using the login-groups feature. > > I can not attach all 6 repositories to the login-group successfully. > Viewing the Login Group Configuration list for each repository shows > a problem. There always seems to be one that has a list that is just > 4 entries long instead of the expected 5 entries (excluding self). > The missing entry has varied without a clear pattern. > > After several attempts, including log out between actions, clearing > browser cache, and fossil rebuild, I'm calling for help. I think > there is a bug in this function. > > The simplest evidence of a fault that I have, comes from > > 1. first ensuring all repos are not part of any group, > 2. then connecting (A) User Acceptance repo with (B) Production repo, > 3. connection shown list (A) uat-at-2012-02-23-07:42:40XX.png > 4. bug revealed by list in (B) prod-at-2012-02-23-07:28:15XX.png > > The last mentioned image shows no entry under the titles in the list > of group members when I expect to see User Acceptance Testing as the > single entry in the list. > > Fossil knows there is a login group connection because it does not > display the entry fields needed to make the group connection. > > Any advice or suggestions for fixes are welcomed. > That's wierd. I don't know what's wrong. Can you describe to me how I can reproduce the problem? > > Thanks in advance, > > Chris > > > > ___ > 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] Login Group Confusion
On Thu, Feb 23, 2012 at 8:27 AM, Chris Peachment wrote: > Hello DRH: > > Thank you for your prompt reply. > > It is possible that one or more of the repositories has some as yet > unknown configuration issue, so I started with new, empty repositories > for the following test. It reveals something unexpected that might be > related. Repositories are stored in a directory outside the web visible > tree and are accessed over html using a three line script: > > #!/xxx/local/bin/fossil > directory: /xxx/repos/ > notfound: http://xxx/site/repo-not-found.html > > > 1. In a terminal logged in to the server: fossil init a.fossil > 2. In a terminal logged in to the server: fossil init b.fossil > 3. In a terminal logged in to the server: fossil init c.fossil > 4. In a terminal logged in to the server: fossil init d.fossil > I can't tell from the text that follows if you are setting up the login-groups right or not. The correct way to do it is as follows: A. Login via browser to b.fossil. Go to the /Admin/Login-Groups screen and join a.fossil. B. Login via browser to c.fossil. Go to the /Admin/Login-Groups screen and join a.fossil. C. Login via browser to d.fossil. Go to the /Admin/Login-Groups screen and join a.fossil. Is that what you are doing? > > 5. In a local browser enter the url to access a.fossil as usual. > 6. In the browser login using the fossil initial password. > 7. Select the Admin - Login Group function. > 8. Enter the path to b.fossil and its admin userid / pw. > 9. Leave the "Name of login-group" field with its default value >of "New Login Group". > > 10. Switch to a new tab in the browser, login to b.fossil and >confirm the login group connection is made. > > 11. Switch to a third tab in the browser and repeat steps 5 - 8 >using c.fossil as the next repo to be connected. > 12. Repeat step 9. Do not blank the field as likely should be done. > > 13. Switch to a new tab in the browser, login to c.fossil and >confirm the login group connection is made. There is a problem >as shown by the attachment: repo-c-at-2012-02-23-09:08:44XX.png > >The "Project Name" field for the target repo (b) is blank. > > 14. Switch to a fourth tab in the browser and repeat steps 5 - 8 >using d.fossil as the next repo to be connected. > 15. Repeat step 9. Blank out the "Name of login-group" field. > > 16. Switch to a new tab in the browser, login to d.fossil and >confirm the login group connection is made. There is a problem >as shown by the attachment: repo-d-at-2012-02-23-09:15:36XX.png > >The "Project Name" field for the target repo (b) is blank in >this listing also. > > I might have left the "Name of login-group" field with its default > value in my previous attempts and then did not notice its full effect > until a later stage when adding the fourth or fifth repo to the group. > > There was a point of confusion in my mind, so I allowed both cases in > various actions. When I tried to leave the login group for ALL repos > and start again, I was getting reports of continuing connections and > unexpected logout or unexpected still logged in that made me think > the clean up was not complete. > > Hope this helps. > > Chris > > > On Thu, 2012-02-23 at 07:41 -0500, Richard Hipp wrote: > > > > > > On Thu, Feb 23, 2012 at 7:16 AM, Chris Peachment > > wrote: > > Hello All: > > > > I'm using a copy of fossil compiled from the latest leaf: > > > >Fossil version 1.22 [3a44f95f40] 2012-02-21 02:01:20 > > > > I have 6 repositories all stored in the same directory on a > > Linux64 box > > as a remote server (Bluehost.com). > > > > All repositories require login for access and all have the > > same login > > id and pw for a super user. They are all accessible > > individually over > > the internet via a browser, using separate logins to each. > > > > I am attempting to establish single sign on for all 6 > > repositories > > using the login-groups feature. > > > > I can not attach all 6 repositories to the login-group > > successfully. > > Viewing the Login Group Configuration list for each repository > > shows > > a problem. There always seems to be one that has a list that > > is just > > 4 entries long instead of the expected 5 entries (excluding > > self). > > The missing entry has varied without a clear pattern. > > > > After several attempts, including log out between actions, > > clearing > > browser cache, and fossil rebuild, I'm calling for help. I > > think > > there is a bug in this function. > > > > The simplest evidence of a fault that I have, comes from > > > > 1. first ensuring all repos are not part of any group, > > 2. then connecting (A) User Acceptance repo with (B) > > Production repo, > >
Re: [fossil-users] Login Group Confusion
On Thu, 2012-02-23 at 08:54 -0500, Richard Hipp wrote: > > I can't tell from the text that follows if you are setting up the > login-groups right or not. The correct way to do it is as follows: > > A. Login via browser to b.fossil. Go to the /Admin/Login-Groups > screen and join a.fossil. > B. Login via browser to c.fossil. Go to the /Admin/Login-Groups > screen and join a.fossil. > C. Login via browser to d.fossil. Go to the /Admin/Login-Groups > screen and join a.fossil. > > Is that what you are doing? > > I believe so. There is not much discretion available on this form. A small point of confusion is that I used b.fossil as the reference and joined a, c, and d to it. For each join action, the entries consisted of: Repository filename in group to join: [path to repo]/b.fossil Login on the above repo: my logged in user id Password: same as returned by the fossil init b.fossil Name of login-group: "New Login Group" for a,c but blank for d. ___ 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 maintain a set of patches?
On Fri, 10 Feb 2012 15:46:15 -0500 Leo Razoumov wrote: > I am sorry if my language was not clear. Here are the diagrams: I am sorry to jump in this thread...we might soon start working on our application which is meant for niche market and therefore potential contributors although experts in the field are probably not savvy with DVCS tools, so Fossil is definitely unprecedented wiht its features and simplicity to setup & use. Otoh, we're familiar with DVCS tools (starting from darcs, bzr, mtn) and now being hg user would like to not to lose any functionality from e.g. hg. My question is connected with Mercurial's MQ feature... > Then after some time trunk moves forward > > ABCDE-- <= trunk > \-P1--P2--P3 <= my-patches Let's assume I've the same situation like above, but consider that my patches are too granular to commit each one to the trunk and would like to eg. combine P1 & P3 together and then apply them as: P2' --> P1_P3' to my trunk. Is it possible to do it in Fossil? Mercurial's MQ offers qfold command, and here is the help file for it: [gour@atmarama gour] hg help qfold hg qfold [-e] [-k] [-m TEXT] [-l FILE] PATCH... fold the named patches into the current patch Patches must not yet be applied. Each patch will be successively applied to the current patch in the order given. If all the patches apply successfully, the current patch will be refreshed with the new cumulative patch, and the folded patches will be deleted. With -k/--keep, the folded patch files will not be removed afterwards. The header for each folded patch will be concatenated with the current patch header, separated by a line of "* * *". Returns 0 on success. options: -e --edit edit patch header -k --keep keep folded patch files -m --message TEXT use text as commit message -l --logfile FILE read commit message from file use "hg -v help qfold" to show more info Sincerely, Gour -- There are principles to regulate attachment and aversion pertaining to the senses and their objects. One should not come under the control of such attachment and aversion, because they are stumbling blocks on the path of self-realization. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
