Skip to contentSkip to conversation

binutils: set CVE_VERSION

PATCH In review Ross Burton 2 participants 2 messages Mar 28, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 binutils: set CVE_VERSION

PV is 2.32.0 even though the actual release upstream is 2.32. To a human this is insignificant, but to automated tooling it matters. Specifically, cve-check-tool can't identify CVEs that are in 2.32.

Set CVE_VERSION for now, which should be removed when PV and the upstream version match again.

---
 meta/recipes-devtools/binutils/binutils-2.32.inc | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-devtools/binutils/binutils-2.32.inc +1 -0
index 15406441241..5d0c16b13ec 100644
@@ -20,6 +20,7 @@ def binutils_branch_version(d):
 # correctly set to match the upstream version tag).
 UPSTREAM_VERSION_UNKNOWN = "1"
 PV = "2.32.0"
+CVE_VERSION = "2.32"
 BINUPV = "${@binutils_branch_version(d)}"
 #BRANCH = "binutils-${BINUPV}-branch"
 BRANCH ?= "binutils-2_32-branch"
Signature · 1 line
2.11.0
Reviewed-by on v1 1/1
#1 lore raw
Quoted 8 lines · Ross Burton

PV is 2.32.0 even though the actual release upstream is 2.32. To a human this is insignificant, but to automated tooling it matters. Specifically, cve-check-tool can't identify CVEs that are in 2.32.

Set CVE_VERSION for now, which should be removed when PV and the upstream version match again.

Signature · 1 line
Tom