release 5.6.4 requires a full wipe of database

[ereshetova]

After upgrading to version 5.6.4 from the previous one, when a tool tries to update the database, this happens:

process_node(): attempt to write to a readonly database process_node(): attempt to write to a readonly database process_node(): attempt to write to a readonly database process_node(): attempt to write to a readonly database process_node(): attempt to write to a readonly database ....

many times

The issue is not visible if the database if fully wiped and downloaded from fresh by the 5.6.4 version.

[ikeydoherty]

Apologies I wasn't aware of that. I'd already purged my old files in trying to fix the issue of NVD URI

[ikeydoherty]

^ Wrong button pushed. So yeah I'll go back to the old cve-check-tool and find a way to detect the break, and implement a workaround if possible.

[ereshetova]

I don't know how much effort this is worth, since I guess we can just wipe out the old db from the builders, but wanted to report it here since other people might see the same issue.

[ikeydoherty]

OK so the new tool is going to correct the faults of the old - and I've begun this with a migration scheme:

https://github.com/ikeydoherty/cve-check-tool/commit/ff8259c3c7fa049643065a8ea37569ee65432fb4 https://github.com/ikeydoherty/cve-check-tool/commit/6effceb85b41d6258d31c80a3bbee9774a777432

Note there are big differences between the old DB and the new DB - hence the format bump. 186MB vs 26MB

Legacy database has the suffix: nvd.db New format now has: nvd-1.db

[ikeydoherty]

Also we should keep this issue open until the new tool is released, just so others are aware, like you said :)