Fossil Forum

BUG? Error when "commit --verbose" an added file

BUG? Error when "commit --verbose" an added file

BUG? Error when "commit --verbose" an added file

(1.1) By teodomiro on 2024-07-09 00:18:32 edited from 1.0 [source]

Hi, fossil shows an error when I try to commit --verbose an added file.

file1.txt is a modified file and file2.txt is a new file which I've added to the repo:

$ fossil add file1.txt
SKIP file1.txt
$ fossil add file2.txt
ADDED file2.txt
$ fossil commit --verbose file1.txt file2.txt
Pull from file:///myrepo.fossil
Round-trips: 1   Artifacts sent: 0  received: 0
Pull done, wire bytes sent: 366  received: 4141  remote: 
SQLITE_ERROR(1): no such column: pathname in "SELECT pathname, deleted, rid WHERE id=20"
Database error: no such column: pathname
SELECT pathname, deleted, rid WHERE id=20

Without --verbose, all works as expected.

(2) By Stephan Beal (stephan) on 2024-07-09 00:22:27 in reply to 1.0 [link] [source]

Without --verbose, all works as expected.

Thank you for the report. Please try the current trunk and let us know if that does not resolve the problem for you. This bug was a side-effect of some refactoring late last year and went unnoticed because fossil's own devs (apparently) don't use --verbose when checking in very often.

(3) By teodomiro on 2024-07-09 16:54:24 in reply to 2 [link] [source]

Thanks for the fix. I patched 2.24 with the change and everything is working now.