From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] package/hplip: update CPE
Date: Tue, 2 Jun 2026 14:41:17 +0200 [thread overview]
Message-ID: <20260602124117.288091-1-thomas.perale@mind.be> (raw)
The 'hp:linux_imaging_and_printing_project' hasn't received any new CVE
assignment since 2013, while 'hp:linux_imaging_and_printing' received 4
[1][2][3][4].
See the package vulnerability history at [5].
[1] https://nvd.nist.gov/vuln/detail/CVE-2015-0839
[2] https://nvd.nist.gov/vuln/detail/CVE-2020-6923
[3] https://nvd.nist.gov/vuln/detail/CVE-2026-8631
[4] https://nvd.nist.gov/vuln/detail/CVE-2026-8632
[5] https://security-tracker.debian.org/tracker/source-package/hplip
Signed-off-by: Thomas Perale <thomas.perale@mind.be>
---
package/hplip/hplip.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/hplip/hplip.mk b/package/hplip/hplip.mk
index 59a0f8ace0..54766978de 100644
--- a/package/hplip/hplip.mk
+++ b/package/hplip/hplip.mk
@@ -11,7 +11,7 @@ HPLIP_DEPENDENCIES = cups libusb jpeg host-pkgconf
HPLIP_LICENSE = GPL-2.0, BSD-3-Clause, MIT
HPLIP_LICENSE_FILES = COPYING
HPLIP_CPE_ID_VENDOR = hp
-HPLIP_CPE_ID_PRODUCT = linux_imaging_and_printing_project
+HPLIP_CPE_ID_PRODUCT = linux_imaging_and_printing
HPLIP_CONF_OPTS = \
--disable-qt4 \
--
2.54.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-06-02 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 12:41 Thomas Perale via buildroot [this message]
2026-06-03 18:48 ` [Buildroot] [PATCH] package/hplip: update CPE Peter Korsgaard
2026-06-12 11:38 ` 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=20260602124117.288091-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