[Git][security-tracker-team/security-tracker][master] 3 commits: security_db: don't fail if there's no (old)stable releases

[Salvatore Bonaccorso (@carnil)]

Salvatore Bonaccorso pushed to branch master at Debian Security Tracker / security-tracker


Commits:
84e781d2 by Emilio Pozuelo Monfort at 2025-02-19T09:39:43+01:00
security_db: don't fail if there's no (old)stable releases

In an extended / forked setup, there could be no (old)stable
releases. If that's the case, don't add their point release
information, instead of crashing.

- - - - -
e5895d21 by Emilio Pozuelo Monfort at 2025-02-19T09:41:46+01:00
Makefile: allow overriding definitions

In case one wants to fully override what's loaded.

- - - - -
24143bcf by Salvatore Bonaccorso at 2025-02-19T09:13:19+00:00
Merge branch 'no-pu' into 'master'

Better support for fully forked trackers

See merge request security-tracker-team/security-tracker!205
- - - - -


2 changed files:

- Makefile
- lib/python/security_db.py


Changes:

=====================================
Makefile
=====================================
@@ -3,8 +3,10 @@ PYTHON_MODULES = $(wildcard lib/python/*.py)
 MIRROR = http://deb.debian.org/debian
 SECURITY_MIRROR = http://security.debian.org/debian-security
 
-# Include the definitions of the releases to be fetched
-include lib/*-releases.mk
+# Include the definitions of the releases to be fetched.
+# We use a variable so that it's easy to override.
+DEFINITIONS = $(wildcard lib/*-releases.mk)
+include $(DEFINITIONS)
 
 # There's a "RELEASES" variable defining the name of all releases to
 # process. Then for each release, there are 5 associated variables:


=====================================
lib/python/security_db.py
=====================================
@@ -1103,11 +1103,19 @@ class DB:
             if self.verbose:
                 print("    insert next-point-update.txt/next-oldstable-point-update.txt")
 
-            insert_next_point_update(PointUpdateParser.parseNextPointUpdateStable(),
-                                     config.get_release_codename('stable'))
+            try:
+                release = 'stable'
+                insert_next_point_update(PointUpdateParser.parseNextPointUpdateStable(),
+                                         config.get_release_codename(release))
+            except ValueError:
+                print(f"No entry in config.json for release {release}, not adding point release data")
 
-            insert_next_point_update(PointUpdateParser.parseNextOldstablePointUpdate(),
-                                     config.get_release_codename('oldstable'))
+            try:
+                release = 'oldstable'
+                insert_next_point_update(PointUpdateParser.parseNextOldstablePointUpdate(),
+                                     config.get_release_codename(release))
+            except ValueError:
+                print(f"No entry in config.json for release {release}, not adding point release data")
 
         read_next_point_update()
 



View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/compare/4b4507b2edbbd53439724b1b69ccd96449c92788...24143bcfcf2cd147fe665feb05d38012b563e9e8

-- 
View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/compare/4b4507b2edbbd53439724b1b69ccd96449c92788...24143bcfcf2cd147fe665feb05d38012b563e9e8
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-security-tracker-commits/attachments/20250219/d6d263ec/attachment-0001.htm>