Hi list,
I notice that when using ssh:// protocole to clone, even if I have
read/write access to the fossil file from my ssh account, I cannot push to
it.
exemple: (with autosync ON)
===============================================
$ fossil ssh://myhost/somepath/myrep.fossil myrep.fossil
$ mkdir rep
$ cd rep
$ fossil open ../myrep.fossil
<edit some files>
$ fossil commit -m "some messages"
Autosync: ssh://myhost/somepath/myrep.fossil
ssh -e none -T myhost
Bytes Cards Artifacts Deltas
Sent: 130 1 0 0
Received: 400 9 0 0
Total network traffic: 298 bytes sent, 459 bytes received
Closing SSH tunnel: New_Version: 45c982c33dfaeb2f96095604a3286a19237e9d48
Autosync: ssh://myhost/somepath/myrep.fossil
ssh -e none -T myhost
Bytes Cards Artifacts Deltas
Sent: 1194 14 0 2
Error: not authorized to write
Received: 433 1 0 0
Total network traffic: 778 bytes sent, 491 bytes received
fossil: Autosync failed
===============================================
If I'm local and I use file:// instead, it work no problem.. Should ssh://
act like file:// since if we have write access to the ".fossil" file ?
--
Martin G.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
