On 26 September 2017 at 06:30, Richard Hipp <[email protected]> wrote: > On 9/26/17, David Mason <[email protected]> wrote: > > if I try: > > fossil clone > > https://dmason%[email protected]/fossil/ > f2017/A-dmason_ryerson.ca.fossil > > foo.fossil > > it prompts for password, but then says it can't find it. > > Fossil prompts for a password whenever it sees a URL of the form > "http[s]://USER@DOMAIN//...". It does this before it ever attempts to > connect the server. So, for example, is should still prompt for the > password if you type: > > fossil clone https://[email protected]/bogus/repo/xyzzy > xyzzy.fossil > > I think your failure is occurring because you added a ".fossil" to the > end of the URL.
Indeed! Thanks... I already noted that in the web access, but the file does end in .fossil and I've always used that before when cloning (using the ssh: access method). Is there a difference in how fossil names are recognized in ssh: vs http(s): ? Or is it because there is already a '.' in the repo name (the full file name is A-dmason_ryerson.ca.fossil <http://[email protected]/fossil/f2017/A-dmason_ryerson.ca.fossil> ) Thanks for your quick response. I spent several hours trying to figure this out, because I couldn't make sense of why this didn't work like my previous experience with ssh: access. ../Dave
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
