Ok, I managed to get it to rebuild. I had to use sqlite3 to do it though.
`fossil sql -R repo` gave me the same error as before so:
$> sqlite3 repo
SQLite> ALTER TABLE config ADD COLUMN mtime INTEGER;
SQLite> UPDATE config SET mtime=date('now');
SQLite> .q
$> fossil rebuild repo
And all is well. Thanks for the clues 😊
From: Richard Hipp
Sent: December 12, 2017 2:06 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Older fossil archives are not rebuild-able
On 12/12/17, J Knight <[email protected]> wrote:
> Hello. I have some older fossil archives that report:
>
> SQLITE_ERROR: table config has no column named mtime
> fossil: table config has no column named mtime: {REPLACE INTO
> config(name,value,mtime) VALUES('hash-policy',1,now())}
>
> issuing a ‘rebuild’ and a ‘rebuild –force’ gives the same error. Is there
> some way to bring these up to date or somehow migrate?
The update should be automatic by these lines:
https://www.fossil-scm.org/fossil/artifact/e094c603?ln=81-85
I don't know why it is not working for you.
Possible work-around:
Run: fossil sql $yourrepo
Enter: ALTER TABLE config ADD COLUMN mtime INTEGER;
Then: UPDATE config SET mtime=now();
Let me know if that helps.
>
> thanks
>
>
>
--
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
