Fossil SCM
Update after clone requires reset of login information
Fixed
ffa87168ce1b552…
· opened 14 years, 9 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Important
- Resolution
- Fixed
- Subsystem
- —
- Created
- June 15, 2011 3:45 a.m.
When doing "upd" after having done a "clone", the first time, one needs to enter password information again (actually, the stored password info is incorrect).
I have attached a bash script to show the problem.
Here is the output from the script:
lap: ~/tmp$ ./testfossil.sh
project-id: 8a46654dc533fbd7a53f43a56919e4fe19ea590c
server-id: fce4372a0950404edb9eea18118d1a737694ce9e
admin-user: tester (initial password is "8ad07e")
password for tester:
Bytes Cards Artifacts Deltas
Sent: 53 1 0 0
Received: 342 5 1 0
Sent: 58 2 0 0
Received: 634 2 0 0
Total network traffic: 540 bytes sent, 1129 bytes received
Rebuilding repository meta-data...
100.0% complete...
project-id: 8a46654dc533fbd7a53f43a56919e4fe19ea590c
server-id: 96dcfa3eeda2dd9b6a15cd4fcc5f2fc4270ea2b1
admin-user: ron (password is "0b7842")
Autosync: http://tester@localhost:8080/
Bytes Cards Artifacts Deltas
Sent: 130 1 0 0
Error: login failed
Received: 52 1 0 0
Sent: 130 1 0 0
Error: login failed
Received: 52 1 0 0
Sent: 130 1 0 0
Error: login failed
Received: 52 1 0 0
Total network traffic: 1036 bytes sent, 804 bytes received
fossil: Autosync failed