From: "Bjørn Damstedt Rasmussen" <contact@bearware.dk>
To: buildroot@buildroot.org
Cc: "Tudor Holton" <buildroot@tudorholton.com>,
"Bjørn Damstedt Rasmussen" <contact@bearware.dk>
Subject: [Buildroot] [PATCH 1/2] package/setserial: CPE ID for setserial
Date: Fri, 2 Oct 2026 22:29:34 +0200 [thread overview]
Message-ID: <20261002202935.943329-1-contact@bearware.dk> (raw)
This allows setserial to be checked for CVEs.
Signed-off-by: Bjørn Damstedt Rasmussen <contact@bearware.dk>
---
package/setserial/setserial.mk | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/setserial/setserial.mk b/package/setserial/setserial.mk
index 9beee349c8..bba8dfdb88 100644
--- a/package/setserial/setserial.mk
+++ b/package/setserial/setserial.mk
@@ -10,6 +10,9 @@ SETSERIAL_SITE = https://snapshot.debian.org/archive/debian/20250307T084701Z/poo
SETSERIAL_EXTRA_DOWNLOADS = setserial_$(SETSERIAL_VERSION)-57.debian.tar.xz
SETSERIAL_LICENSE = GPL-2.0
SETSERIAL_LICENSE_FILES = debian/copyright
+SETSERIAL_CPE_ID_VENDOR = setserial_project
+SETSERIAL_CPE_ID_PRODUCT = setserial
+
# make all also builds setserial.cat which needs nroff
SETSERIAL_MAKE_OPTS = setserial
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-10-02 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 20:29 Bjørn Damstedt Rasmussen [this message]
2026-10-02 20:29 ` [Buildroot] [PATCH 2/2] package/openjdk: CPE ID for openjdk Bjørn Damstedt Rasmussen
2026-10-03 13:18 ` Thomas Petazzoni via buildroot
2026-10-03 13:16 ` [Buildroot] [PATCH 1/2] package/setserial: CPE ID for setserial Thomas Petazzoni via buildroot
-- strict thread matches above, loose matches on Subject: below --
2026-10-03 17:36 Bjørn Damstedt Rasmussen
2026-10-03 17:50 ` Thomas Petazzoni via buildroot
2026-10-10 9:24 ` Thomas Perale via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261002202935.943329-1-contact@bearware.dk \
--to=contact@bearware.dk \
--cc=buildroot@buildroot.org \
--cc=buildroot@tudorholton.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox