public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libseccomp: Update to version 2.4.3
Date: Fri, 08 May 2020 09:50:51 +0100	[thread overview]
Message-ID: <4CDE1B32-E245-46C5-8372-A6EC0CBFFAB3@ipfire.org> (raw)
In-Reply-To: <20200508062319.12826-1-ummeegge@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2608 bytes --]

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 8 May 2020, at 07:23, Erik Kapfer <ummeegge(a)ipfire.org> wrote:
> 
> - Add list of authorized release signatures to README.md
> - Fix multiplexing issue with s390/s390x shm* syscalls
> - Remove the static flag from libseccomp tools compilation
> - Add define for __SNR_ppoll
> - Update our Travis CI configuration to use Ubuntu 18.04
> - Disable live python tests in Travis CI
> - Use default python, rather than nightly python, in TravisCI
> - Fix potential memory leak identified by clang in the scmp_bpf_sim too
> 
> The changelog can be found in here https://github.com/seccomp/libseccomp/blob/master/CHANGELOG .
> 
> Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
> ---
> config/rootfiles/packages/libseccomp | 4 ++--
> lfs/libseccomp                       | 7 ++++---
> 2 files changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/config/rootfiles/packages/libseccomp b/config/rootfiles/packages/libseccomp
> index 615c852fb..081103b21 100644
> --- a/config/rootfiles/packages/libseccomp
> +++ b/config/rootfiles/packages/libseccomp
> @@ -1,10 +1,10 @@
> usr/bin/scmp_sys_resolver
> -#usr/include/seccomp.h
> #usr/include/seccomp-syscalls.h
> +#usr/include/seccomp.h
> #usr/lib/libseccomp.la
> #usr/lib/libseccomp.so
> usr/lib/libseccomp.so.2
> -usr/lib/libseccomp.so.2.4.2
> +usr/lib/libseccomp.so.2.4.3
> #usr/lib/pkgconfig/libseccomp.pc
> #usr/share/man/man1/scmp_sys_resolver.1
> #usr/share/man/man3/seccomp_api_get.3
> diff --git a/lfs/libseccomp b/lfs/libseccomp
> index 064fb5896..676b516e9 100644
> --- a/lfs/libseccomp
> +++ b/lfs/libseccomp
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 2.4.2
> +VER        = 2.4.3
> 
> THISAPP    = libseccomp-$(VER)
> DL_FILE    = $(THISAPP).tar.gz
> @@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
> DIR_APP    = $(DIR_SRC)/$(THISAPP)
> TARGET     = $(DIR_INFO)/$(THISAPP)
> PROG       = libseccomp
> -PAK_VER    = 2
> +PAK_VER    = 3
> 
> DEPS       =
> 
> @@ -44,7 +44,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = ee87fb68ae293883bde9e042c6bc324f
> +$(DL_FILE)_MD5 = 3a2c3b7539c1b6a933c20cd1fdcb2252
> 
> install : $(TARGET)
> 
> @@ -77,6 +77,7 @@ $(subst %,%_MD5,$(objects)) :
> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> 	@$(PREBUILD)
> 	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar vxf $(DIR_DL)/$(DL_FILE)
> +	cd $(DIR_APP) && ./autogen.sh
> 	cd $(DIR_APP) && ./configure \
> 		--prefix=/usr \
> 		--disable-static
> -- 
> 2.20.1
> 


      reply	other threads:[~2020-05-08  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  6:23 Erik Kapfer
2020-05-08  8:50 ` Michael Tremer [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=4CDE1B32-E245-46C5-8372-A6EC0CBFFAB3@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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