On Thu, 07 Nov 2013 05:52:15 +0100, Andy Bradford
<amb-sendok-1386391935.hjbliiljijknmndin...@bradfords.org> wrote:
Thus said "j. van den hoff" on Wed, 06 Nov 2013 10:18:08 +0100:
fossil clone http://userid@server/repo myclone.fossil
fossil user new localname
fossil user default localname
all commits appear in the timeline with user "localname" (as they
should).
however, the GUI says "logged in as `userid' and tickets and wiki
changes appear in the timeline as coming from user `userid' (i.e. the
user having done the clone).
first of all thanks a lot for bothering with this.
This seems to be the behavior that I would expect. Either that or there
are some details missing in what you're reporting. How did you ``enter''
the GUI that you were viewing?
the simplest way: fossil ui
Here is what I did:
fossil new new.fossil
fossil server -P 8081 new.fossil &
fossil user -R new.fossil new tester
fossil user -R new.fossil cap tester v
fossil clone http://tester@localhost:8081/ clone.fossil
mkdir clone; cd clone; fossil open ../clone.fossil
echo $RANDOM > file
fossil add file
fossil ci -m file
In my browser, I connect to http://localhost:8081/ and login as tester
(newly created developer account). I see that file has been committed by
a user tester.
Now, I continue on still in the clone directory:
fossil user new localname
fossil user default localname
echo $RANDOM > file
fossil ci -m again
Now, in my timeline I see a new checkin by user localname. This seems
correct to me.
So I continue on (still in clone directory):
fossil user cap localname v
echo $RANDOM > file
fossil ci -m newcap
Now, in my timeline I see a new checkin by localname with a comment of
newcap. Again, this seems correct.
yes, with file checkins everything works as expected for me, too (i.e.
setting up the new "local" default user after the cloning this user is the
one doing the
checkins.
I continue and now create a new wiki page:
echo 'Wiki' | fossil wiki create Wiki
fossil sync
Now, in my timeline I see a new wiki page was added by a user named
localname.
I did not try out _this_ possibility of doing wiki edits from the command
line. I can confirm that such
edits end up in the repo as coming from 'localname'.
If I logout of the web interface and login with an admin user, I will
see that the commits were made by localname (the remote username) but
that they were received into my repository using a login of tester.
probably not relevant to the problem at hand, but where and when do I see
this info that the commit was received using a login as `tester'?
Again, this is expected (I think). The wiki pages show as having come
from localname as well (but don't list the received user account).
What have I missed?
I did the wiki edits via the GUI. that is the difference. and the GUI
still states (correctly without doubt) "logged in as tester" when the wiki
edit occurs. so what that means is: after having set up `localname' as the
default user in the clone, commits and wiki edits coming from the command
line end up in the timeline accordingly, but when starting `fossil ui' at
that point I'm logged in automatically as `tester' and wiki changes than
come from `tester'.
I understand that there is a rationale for this but I can tell you it sure
is confusing for the average user. the question "what's my effective user
ID right now?" after adding the new default user sure would be answered
"it is `localname'". so the different user ID under which GUI based
actions are logged comes as a surprise. also I'm just now in the process
of "advertising" fossil as a good tool for managing a multi-group set of
text documents and tickets. within no time the users are running in the
above type of problem and are already starting to find fossil a pain in
the back which is a pity since it's leaves the unjustified impression that
fossil is "complicated".
the problem (if it is justified to call it that) is that after cloning as
`tester' and setting up the new default user `localname' (even if
explicitly making `localname' the `s' user, too), only edits coming from
the command line (including wiki changes) are assigned to `localname' but
changes via the ui still come from `tester'. only if removing the `s'
capability of `tester' (and if `localname' has been made `s' user
previously) does the login switch to `localname' (even in the running GUI
w/o logout+login) so that changes via the GUI then come from `localname',
too.
from a simple user perspective I would think doing
fossil user default localname
and possibly (although I would prefer this to occur automatically)
fossil user capabilities localname s
should suffice to make `fossil ui' than login under that name. right now
it seems if one has tow `s' users, namely 1: `tester' and 2.: `localname'
the first one (in terms of when chronologically created) wins so the `s'
has to be removed from `tester', too.
is this clearer know? what do you think? is it
worth/correct/desirable/possible to change the current behavior?
greetings,
j.
Thanks,
Andy
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
