- Updated syscall table for Linux 5.17.
- Minor fixes with binary trees.
- Minor documentation improvements.

Patch applied successfully.

Signed-off-by: Linnea Gunnarsson <[email protected]>
---
 ...1-run-time-use-a-broadly-supported-shell-interpreter.patch | 0
 patches/{libseccomp-2.5.3 => libseccomp-2.5.4}/series         | 0
 rules/libseccomp.make                                         | 4 ++--
 3 files changed, 2 insertions(+), 2 deletions(-)
 rename patches/{libseccomp-2.5.3 => 
libseccomp-2.5.4}/0001-run-time-use-a-broadly-supported-shell-interpreter.patch 
(100%)
 rename patches/{libseccomp-2.5.3 => libseccomp-2.5.4}/series (100%)

diff --git 
a/patches/libseccomp-2.5.3/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
 
b/patches/libseccomp-2.5.4/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
similarity index 100%
rename from 
patches/libseccomp-2.5.3/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
rename to 
patches/libseccomp-2.5.4/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
diff --git a/patches/libseccomp-2.5.3/series b/patches/libseccomp-2.5.4/series
similarity index 100%
rename from patches/libseccomp-2.5.3/series
rename to patches/libseccomp-2.5.4/series
diff --git a/rules/libseccomp.make b/rules/libseccomp.make
index 5a6f45f1c..b3b99c189 100644
--- a/rules/libseccomp.make
+++ b/rules/libseccomp.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBSECCOMP) += libseccomp
 #
 # Paths and names
 #
-LIBSECCOMP_VERSION     := 2.5.3
-LIBSECCOMP_MD5         := 5096d3912a605a72b27805fa0ef9886d
+LIBSECCOMP_VERSION     := 2.5.4
+LIBSECCOMP_MD5         := 74008bb33234e0c2a0d998e7bee5c625
 LIBSECCOMP             := libseccomp-$(LIBSECCOMP_VERSION)
 LIBSECCOMP_SUFFIX      := tar.gz
 LIBSECCOMP_URL         := 
https://github.com/seccomp/libseccomp/releases/download/v$(LIBSECCOMP_VERSION)/$(LIBSECCOMP).$(LIBSECCOMP_SUFFIX)
-- 
2.32.0


_______________________________________________
ptxdist mailing list
[email protected]
To unsubscribe, send a mail with subject "unsubscribe" to 
[email protected]

Reply via email to