From b8e655f8bfa5b0632fee0f4822330ddb50f9ca53 Mon Sep 17 00:00:00 2001 From: Salvatore Bonaccorso Date: Sat, 22 May 2021 11:05:03 +0200 Subject: security_db: Create next_point_table as well on fresh DB initialization 8846bec76339 ("Fix CVE10k problem for CVE with more than 4 numbers") introduced the initialization of schema 22 and introducing the machinery to allow the tracker.d.o support reading next point release information. On updates from already initialized databases with previous schemas this worked fine, but as Neil Williams reported, this fails when starting with a new instance. Link: https://lists.debian.org/debian-security-tracker/2021/05/msg00024.html Fixes: 8846bec76339 ("Fix CVE10k problem for CVE with more than 4 numbers") Signed-off-by: Salvatore Bonaccorso --- lib/python/security_db.py | 2 ++ 1 file changed, 2 insertions(+) (limited to 'lib') diff --git a/lib/python/security_db.py b/lib/python/security_db.py index 674adeb342..caf8ae67bc 100644 --- a/lib/python/security_db.py +++ b/lib/python/security_db.py @@ -444,6 +444,8 @@ class DB: self._initNoDSA(cursor) + self._initNextPointRelease(cursor) + cursor.execute("PRAGMA user_version = %d" % self.schema_version) def _initSchema20(self): -- cgit v1.2.3