Fossil SCM
fossil database gets deleted on <fossil close> when its located in working copy
Fixed
3ba4f30f554cbb8…
· opened 13 years, 3 months ago
- Type
- Incident
- Priority
- —
- Severity
- Severe
- Resolution
- Overcome_By_Events
- Subsystem
- —
- Created
- Dec. 12, 2012 1:35 p.m.
I usually name my databases like ".db.fossil"... and 3 days ago i closed the working copy with
fossil close
It deleted the working files but my databases was erased too.
Comments (2)
nobody
13 years, 3 months ago
I usually name my databases like ".db.fossil"... and 3 days ago i closed the working copy with
fossil close
It deleted the working files but my databases was erased too.
drh
13 years, 3 months ago
Already fixed by check-in [fcdeaa2909]. But this problem should not have existed in a released version of Fossil. The OP must be running a self-compiled version of Fossil made from sources obtained between 2012-11-10 and 2012-11-28, which is the window during which this bug existed.