mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: Re: [ptxdist] [APPLIED] boost: Rework version and add matching CPE identfiers
Date: Tue,  6 Oct 2026 09:01:17 +0200	[thread overview]
Message-ID: <20261006070117.2791928-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260921104755.534119-2-ada@thorsis.com>

Thanks, applied as d8093710d25d949b9dfe72398097e4fa82ea562e.

Michael

[sent from post-receive hook]

On Tue, 06 Oct 2026 09:01:17 +0200, Alexander Dahl <ada@thorsis.com> wrote:
> The version format with dots is the one matched by CPE.  This way it is
> not necessary to override with <PKG>_CVE_VERSION.  The dotted variant is
> also better suited in SBOM for later use in CVE scanning tools.  Bonus:
> the changed download URL has less HTTP redirects.
> 
> Link: https://nvd.nist.gov/products/cpe/search/results?keyword=cpe:2.3:a:boost:boost
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> Message-Id: <20260921104755.534119-2-ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/boost.make b/rules/boost.make
> index a3b453efb051..013351972aca 100644
> --- a/rules/boost.make
> +++ b/rules/boost.make
> @@ -15,15 +15,16 @@ PACKAGES-$(PTXCONF_BOOST) += boost
>  #
>  # Paths and names
>  #
> -BOOST_VERSION	:= 1_89_0
> +BOOST_VERSION	:= 1.89.0
>  BOOST_SHA256	:= 85a33fa22621b4f314f8e85e1a5e2a9363d22e4f4992925d4bb3bc631b5a0c7a
> -BOOST		:= boost_$(BOOST_VERSION)
> +BOOST		:= boost_$(subst .,_,$(BOOST_VERSION))
>  BOOST_SUFFIX	:= tar.bz2
> -BOOST_URL	:= $(call ptx/mirror, SF, boost/$(BOOST).$(BOOST_SUFFIX))
> +BOOST_URL	:= $(call ptx/mirror, SF, boost/$(BOOST_VERSION)/$(BOOST).$(BOOST_SUFFIX))
>  BOOST_SOURCE	:= $(SRCDIR)/$(BOOST).$(BOOST_SUFFIX)
>  BOOST_DIR	:= $(BUILDDIR)/$(BOOST)
>  BOOST_LICENSE	:= BSL-1.0
>  BOOST_LICENSE_FILES := file://LICENSE_1_0.txt;md5=e4224ccaecb14d942c71d31bef20d78c
> +BOOST_CVE_PRODUCT := boost:boost
>  
>  # ----------------------------------------------------------------------------
>  # Prepare



      reply	other threads:[~2026-10-06  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 10:47 [ptxdist] [PATCH v2 0/1] Add matching CPE identifiers Alexander Dahl via ptxdist
2026-09-21 10:47 ` [ptxdist] [PATCH v2 1/1] boost: Rework version and add matching CPE identfiers Alexander Dahl via ptxdist
2026-10-06  7:01   ` Michael Olbrich [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=20261006070117.2791928-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    /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