From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libseccomp: update to 2.4.2
Date: Sat, 04 Jan 2020 16:31:11 +0000 [thread overview]
Message-ID: <4C6B13B0-4F5B-483E-913F-508EE335400A@ipfire.org> (raw)
In-Reply-To: <46404e15-3ac2-3045-606c-eef8079eec6e@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 4 Jan 2020, at 15:31, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Please refer to https://github.com/seccomp/libseccomp/releases/tag/v2.4.2
> for release notes.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/packages/libseccomp | 3 ++-
> lfs/libseccomp | 8 ++++----
> 2 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/config/rootfiles/packages/libseccomp b/config/rootfiles/packages/libseccomp
> index 402a7e942..615c852fb 100644
> --- a/config/rootfiles/packages/libseccomp
> +++ b/config/rootfiles/packages/libseccomp
> @@ -1,9 +1,10 @@
> usr/bin/scmp_sys_resolver
> #usr/include/seccomp.h
> +#usr/include/seccomp-syscalls.h
> #usr/lib/libseccomp.la
> #usr/lib/libseccomp.so
> usr/lib/libseccomp.so.2
> -usr/lib/libseccomp.so.2.4.0
> +usr/lib/libseccomp.so.2.4.2
> #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 d577793d1..4d1e4a3d8 100644
> --- a/lfs/libseccomp
> +++ b/lfs/libseccomp
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 2.4.0
> +VER = 2.4.2
>
> 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 = 1
> +PAK_VER = 2
>
> DEPS = ""
>
> @@ -44,7 +44,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = 91625d78af26c646b03be3de58e71988
> +$(DL_FILE)_MD5 = ee87fb68ae293883bde9e042c6bc324f
>
> install : $(TARGET)
>
> --
> 2.16.4
prev parent reply other threads:[~2020-01-04 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 15:31 Peter Müller
2020-01-04 16:31 ` 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=4C6B13B0-4F5B-483E-913F-508EE335400A@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