public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] libseccomp: Update to version 2.5.2
Date: Tue, 07 Sep 2021 13:03:38 +0200	[thread overview]
Message-ID: <20210907110338.3503953-1-adolf.belka@ipfire.org> (raw)

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

- Update from 2.5.1 to 2.5.2
- Update rootfile
- Changelog
   * Version 2.5.2 - August 31, 2021
     - Update the syscall table for Linux v5.14-rc7
     - Add a function, get_notify_fd(), to the Python bindings to get the
       nofication file descriptor
     - Consolidate multiplexed syscall handling for all architectures into one
       location
     - Add multiplexed syscall support to PPC
     - Add multiplexed syscall support to MIPS
     - The meaning of SECCOMP_IOCTL_NOTIF_ID_VALID changed within the kernel.
       Modify the libseccomp file descriptor notification logic to support the
       kernel's previous and new usage of SECCOMP_IOCTL_NOTIF_ID_VALID

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 config/rootfiles/packages/libseccomp | 2 +-
 lfs/libseccomp                       | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/config/rootfiles/packages/libseccomp b/config/rootfiles/packages/libseccomp
index fb0b35d31..90bee123e 100644
--- a/config/rootfiles/packages/libseccomp
+++ b/config/rootfiles/packages/libseccomp
@@ -4,7 +4,7 @@ usr/bin/scmp_sys_resolver
 #usr/lib/libseccomp.la
 #usr/lib/libseccomp.so
 usr/lib/libseccomp.so.2
-usr/lib/libseccomp.so.2.5.1
+usr/lib/libseccomp.so.2.5.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 38d7a7dde..aaa9f0b1d 100644
--- a/lfs/libseccomp
+++ b/lfs/libseccomp
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2.5.1
+VER        = 2.5.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    = 5
+PAK_VER    = 6
 
 DEPS       =
 
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = 59f5563c532d3fa1df9db0516b36b1cd
+$(DL_FILE)_MD5 = bdee14f3453d118fc29456c6c4cb178e
 
 install : $(TARGET)
 
-- 
2.33.0


             reply	other threads:[~2021-09-07 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 11:03 Adolf Belka [this message]
2021-09-09 20:13 ` Peter Müller

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=20210907110338.3503953-1-adolf.belka@ipfire.org \
    --to=adolf.belka@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