Re: Error on make with local testing instance

[Salvatore Bonaccorso <carnil@debian.org>]

Hi Neil,

On Fri, May 21, 2021 at 02:32:33PM +0100, Neil Williams wrote:
> https://security-team.debian.org/security_tracker.html#setting-up-a-local-testing-instance
> 
> After running make update-packages successfully in a fresh clone, I get:
> 
> neil@felix:security-tracker (master)$ make
> bin/update-db data/security.db
> Traceback (most recent call last):
>   File "bin/update-db", line 27, in <module>
>     warnings = db.readBugs(cursor, 'data')
>   File "/home/neil/Documents/freexian/security-team/security-tracker/lib/python/security_db.py", line 970, in readBugs
>     clear_db()
>   File "/home/neil/Documents/freexian/security-team/security-tracker/lib/python/security_db.py", line 917, in clear_db
>     cursor.execute("DELETE FROM next_point_update")
>   File "src/cursor.c", line 1019, in APSWCursor_execute.sqlite3_prepare
>   File "src/statementcache.c", line 386, in sqlite3_prepare
> apsw.SQLError: SQLError: no such table: next_point_update
> make: *** [Makefile:19: all] Error 1
> 
> Is there a missing command in the guide?

No I think this was a (logical?) bug introduced with 8846bec76339
("Fix CVE10k problem for CVE with more than 4 numbers").  The schema
version is 23, and then the next_point_update is not created if you
start with a fresh instance.

Looking into it.

As temporary workaround you can create the table, with

CREATE TABLE next_point_update (cve_name TEXT NOT NULL, release TEXT NOT NULL, PRIMARY KEY (cve_name, release))

in the data/security.db and then continue.

Regards,
Salvatore