From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Volkov Viacheslav <sv99@inbox.ru>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zbar: add ZBAR_CPE_ID_VENDOR
Date: Thu, 14 Sep 2023 23:33:14 +0200 [thread overview]
Message-ID: <20230914233314.04243ee3@windsurf> (raw)
In-Reply-To: <20230914211133.451932-1-fontaine.fabrice@gmail.com>
On Thu, 14 Sep 2023 23:11:33 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> cpe:2.3:a:zbar_project:zbar is a valid CPE identifier for this package:
>
> https://nvd.nist.gov/products/cpe/detail/438B9E70-F8E2-4318-83B5-46A0DF320CE3
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/zbar/zbar.mk | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks, and thanks for using the new link. This link
shows that upstream is considered to be
https://github.com/mchehab/zbar/tags, which we are not using.
Our Config.in.help text points to
https://git.linuxtv.org/zbar.git/about/ which is an empty page.
We download the tarball from https://www.linuxtv.org/downloads/zbar/
where the latest version is 0.23.90 (which we use). But both Github and
the Git repo at git.linuxtv.org/zbar.git have a 0.23.92 version.
Perhaps there is something to improve here.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-14 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 21:11 [Buildroot] [PATCH 1/1] package/zbar: add ZBAR_CPE_ID_VENDOR Fabrice Fontaine
2023-09-14 21:33 ` Thomas Petazzoni via buildroot [this message]
2023-09-24 18:00 ` Peter Korsgaard
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=20230914233314.04243ee3@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=sv99@inbox.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox