From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/sane-backends: update CPE
Date: Fri, 12 Jun 2026 13:38:09 +0200 [thread overview]
Message-ID: <20260612113809.253107-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260602124047.287780-1-thomas.perale@mind.be>
In reply of:
> The CPE 'sane-backends_project:sane-backends' only has a single CVE
> assigned in 2017 while 'sane-project:sane_backends' has 9 since 2017
> [1].
>
> See the package CVE history at [2].
>
> [1] https://nvd.nist.gov/vuln/detail/CVE-2023-46047
> [2] https://security-tracker.debian.org/tracker/source-package/sane-backends
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Applied to 2025.02.x & 2026.02.x. Thanks
> ---
> package/sane-backends/sane-backends.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/package/sane-backends/sane-backends.mk b/package/sane-backends/sane-backends.mk
> index fe89e7747d..de1375550c 100644
> --- a/package/sane-backends/sane-backends.mk
> +++ b/package/sane-backends/sane-backends.mk
> @@ -10,7 +10,8 @@ SANE_BACKENDS_SITE = \
> SANE_BACKENDS_CONFIG_SCRIPTS = sane-config
> SANE_BACKENDS_LICENSE = GPL-2.0+
> SANE_BACKENDS_LICENSE_FILES = COPYING
> -SANE_BACKENDS_CPE_ID_VALID = YES
> +SANE_BACKENDS_CPE_ID_VENDOR = sane-project
> +SANE_BACKENDS_CPE_ID_PRODUCT = sane_backends
> SANE_BACKENDS_INSTALL_STAGING = YES
>
> SANE_BACKENDS_CONF_OPTS = \
> --
> 2.54.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-06-12 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 12:40 [Buildroot] [PATCH] package/sane-backends: update CPE Thomas Perale via buildroot
2026-06-03 18:48 ` Peter Korsgaard
2026-06-12 11:38 ` Thomas Perale via buildroot [this message]
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=20260612113809.253107-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
/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