I either forgot or have never used this but it sure must be possible:

the situation:

1. password of remote repo specified when cloning is stored locally (i.e. the query whether to do that was confirmed).

2. password now has been changed on remote repo (via login through web ui)

3. push/pull etc between local client and remote server now (of course) fail since stored password is no longer valid

question: how to get a new password query for communication with the remote repo?

i'm not 100% sure this will work, but try:

fossil remote-url https://name@host/path

Alternately, close the checkout, re-clone the repo, then re-open it with the --keep flag to keep any local changes you may have. (i would demonstrate, but am typing one-handed on a tablet :/.)

that was it. I indeed remember now... thanks for solving this.

ps: yes I did re-clone prior to posting the question. that is of course possible but potentially tedious

pps: I also scanned the concatenation of all fossil help pages for "password" without a hit that would have solved the question. "fossil remote-url" is not really obvious if the user ever only does an initial clone from some repo with an invariant URL. so it might help to add this issue ("reset/change stored login password") in some way to suitable manpages (clone, maybe?) or initiate password query on failed login requests? does that make sense?

i'm a little surprised that pull doesn't have a flag to force this. i'll take a look at that tomorrow (it's currently the middle of the night in my time zone).

i'm a little surprised that pull doesn't have a flag to force this. i'll take a look at that tomorrow (it's currently the middle of the night in my time zone).

wich is the same as mine I believe. so tomorrow sounds like a good idea :)