All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Bjørn Damstedt Rasmussen" <contact@bearware.dk>
Cc: buildroot@buildroot.org, Tudor Holton <buildroot@tudorholton.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/setserial: CPE ID for setserial
Date: Sat, 3 Oct 2026 15:16:27 +0200	[thread overview]
Message-ID: <asD_xB8IAC3nT-i0@windsurf> (raw)
In-Reply-To: <20261002202935.943329-1-contact@bearware.dk>

Hello Bjørn,

On Fri, Oct 02, 2026 at 10:29:34PM +0200, Bjørn Damstedt Rasmussen wrote:
> This allows setserial to be checked for CVEs.
> 
> Signed-off-by: Bjørn Damstedt Rasmussen <contact@bearware.dk>

Thanks a lot for your two patches. Could you provide in each commit
message some evidence that the added CPE vendor/product information is
correct?

> 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

These are already the default values for those variables, so how does
this help?

If it's all a matter of telling Buildroot that the CPE identification
information has been checked, then:

SETSERIAL_CPE_ID_VALID = YES

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-10-03 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 20:29 [Buildroot] [PATCH 1/2] package/setserial: CPE ID for setserial Bjørn Damstedt Rasmussen
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 ` Thomas Petazzoni via buildroot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-03 17:36 [Buildroot] [PATCH 1/2] package/setserial: CPE ID for setserial 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=asD_xB8IAC3nT-i0@windsurf \
    --to=buildroot@buildroot.org \
    --cc=buildroot@tudorholton.com \
    --cc=contact@bearware.dk \
    --cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.