Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francis Laniel <flaniel@linux.microsoft.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/sysdig: bump to version 0.29.2
Date: Wed, 04 May 2022 13:28:16 +0100	[thread overview]
Message-ID: <2628018.mvXUDI8C0e@pwmachine> (raw)
In-Reply-To: <20220503192216.GB2575@scaer>

Hi!

Le mardi 3 mai 2022, 20:22:16 BST Yann E. MORIN a écrit :
> Francis, All,
> 
> On 2022-05-03 15:27 +0100, Francis Laniel spake thusly:
> > Signed-off-by: Francis Laniel <flaniel@linux.microsoft.com>
> > ---
> > 
> >  package/sysdig/sysdig.hash | 2 +-
> >  package/sysdig/sysdig.mk   | 5 +++--
> >  2 files changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff --git a/package/sysdig/sysdig.hash b/package/sysdig/sysdig.hash
> > index 380c9dce1e..c953421f27 100644
> > --- a/package/sysdig/sysdig.hash
> > +++ b/package/sysdig/sysdig.hash
> > @@ -1,3 +1,3 @@
> > 
> >  # sha256 locally computed
> > 
> > -sha256  3721c97f0da43c1a68d2962d30363525d8532ab5f2534dfefc86d175e17e423e 
> > sysdig-0.29.1.tar.gz +sha256 
> > 38ea602085f706af5d07630189216fa240064122650a81456cb092579313ae8e 
> > sysdig-0.29.2.tar.gz> 
> >  sha256  a88fbf820b38b1c7fabc6efe291b8259e02ae21326f56fe31c6c9adf374b2702 
> >  COPYING> 
> > diff --git a/package/sysdig/sysdig.mk b/package/sysdig/sysdig.mk
> > index 318746d44a..2d57c0043f 100644
> > --- a/package/sysdig/sysdig.mk
> > +++ b/package/sysdig/sysdig.mk
> > @@ -4,7 +4,7 @@
> > 
> >  #
> >  #########################################################################
> >  #######> 
> > -SYSDIG_VERSION = 0.29.1
> > +SYSDIG_VERSION = 0.29.2
> > 
> >  SYSDIG_SITE = $(call github,draios,sysdig,$(SYSDIG_VERSION))
> >  SYSDIG_LICENSE = Apache-2.0
> >  SYSDIG_LICENSE_FILE = COPYING
> > 
> > @@ -32,6 +32,7 @@ SYSDIG_CONF_OPTS +=
> > -DFALCOSECURITY_LIBS_SOURCE_DIR=$(FALCOSECURITY_LIBS_SRCDIR)> 
> >  	-DENABLE_DKMS=OFF \
> >  	-DUSE_BUNDLED_DEPS=OFF \
> >  	-DWITH_CHISEL=ON \
> > 
> > -	-DVALIJSON_INCLUDE=$(BUILD_DIR)/valijson-0.6/include/valijson
> > +	-DVALIJSON_INCLUDE=$(BUILD_DIR)/valijson-0.6/include/valijson \
> > +	-DSYSDIG_VERSION=$(SYSDIG_VERSION)
> 
> I've extended the commit log to explain why we need to explicitly set
> the version string.
> 
> Applied to master, thanks.

Thank you a lot for the merges and still sorry for the nit in previous 
commit...
I will take more care next time!

> Regards,
> Yann E. MORIN.
> 
> >  $(eval $(cmake-package))




_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-05-04 12:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 14:26 [Buildroot] [PATCH 0/2] Bump sysdig to 0.29.2 Francis Laniel
2022-05-03 14:27 ` [Buildroot] [PATCH 1/2] package/sysdig: fix DRIVER_NAME definition Francis Laniel
2022-05-03 19:15   ` Yann E. MORIN
2022-05-03 14:27 ` [Buildroot] [PATCH 2/2] package/sysdig: bump to version 0.29.2 Francis Laniel
2022-05-03 19:22   ` Yann E. MORIN
2022-05-04 12:28     ` Francis Laniel [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=2628018.mvXUDI8C0e@pwmachine \
    --to=flaniel@linux.microsoft.com \
    --cc=angelo.compagnucci@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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