Fossil SCM
attempt to 'fossil init filename' where filename = dirname confuses fossil
Closed
af2658e1fe1d11d…
· opened 15 years, 4 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Minor
- Resolution
- Wont_Fix
- Subsystem
- —
- Created
- Nov. 14, 2010 3:01 p.m.
Hello!
While being busy converting my old darcs repos into Fossil, I did a mistake when naming folder to keep git format (I do darcs --> git --> fossil) and named folder vasb.fossil.
After that I executed:
[gour@atmarama study] fossil init vasb.fossil
fossil: SQLITE_CANTOPEN: cannot open file at line 27473 of [e55ada8924]
fossil: unable to open database file
If you have recently updated your fossil executable, you might
need to run "fossil all rebuild" to bring the repository
schemas up to date.
but, as you can see, Fossil reported a bit strange things, while, in reality, the only problem is to detect there is already folder named the same as the new supposed-to-be-created Fossil repo.
Maybe some improvement could be made in reporting such thing?
Sincerely,
Gour
anonymous claiming to be Joerg Sonnenberger added on 2010-11-14 15:31:55: The only thing I would change is reporting the actual system error, e.g. "EISDIR".
Comments (1)
system
2 years, 2 months ago
Closing as part of periodic cleanup.