From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: "Clément Ramirez" <ramirez.clement3@gmail.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/qemu: security bump version to 8.1.1
Date: Tue, 10 Oct 2023 11:54:57 +0300 [thread overview]
Message-ID: <87v8bec0pm.fsf@tarshish> (raw)
In-Reply-To: <CADRKr2ov7vayiQPreXt1Z5mhy848UJxztJ+seMmGk1t36ikRiw@mail.gmail.com>
Hi Clément,
On Tue, Oct 10 2023, Clément Ramirez wrote:
>> Provided that these CVEs are fixed with this version bump, why do we
>> need to ignore them?
>
> When I don't ignore the CVEs fixed with the version bump, the
> pkg-stats tool keeps displaying them.
> I think it's because the CPE database has no entries for the qemu 8.1.1 version
> and therefore does not know which CVEs are fixed in this specific version.
This is something that should be fixed in the CPE database.
In the mean time there should be a comment that explains why we ignore
these CVEs even though they do not actually affect the current package
version.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-10 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 7:05 [Buildroot] [PATCH] package/qemu: security bump version to 8.1.1 Clement Ramirez
2023-10-10 7:47 ` Baruch Siach via buildroot
2023-10-10 8:41 ` Clément Ramirez
2023-10-10 8:54 ` Baruch Siach via buildroot [this message]
2023-10-10 9:15 ` Clément Ramirez
2023-11-01 16:29 ` Thomas Petazzoni via buildroot
2023-11-02 9:37 ` Clément Ramirez
2023-11-02 9:47 ` Thomas Petazzoni via buildroot
2023-11-02 9:51 ` Clément Ramirez
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=87v8bec0pm.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=ramirez.clement3@gmail.com \
--cc=romain.naour@gmail.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