api_define__SNR_ppoll_again
From
2e54815cd843687d750cc9822f992389bb7b76cd Mon Sep 17 00:00:00 2001
From: Miroslav Lichvar <mlichvar@redhat.com>
Date: Wed, 13 Nov 2019 13:36:10 +0100
Subject: [PATCH] api: define __SNR_ppoll again
Commit
bf747eb21e428c2b3ead6ebcca27951b681963a0 accidentally removed the
__SNR_ppoll definition. Add it back, using a PNR value if disabled in
the kernel headers.
Signed-off-by: Miroslav Lichvar <mlichvar@redhat.com>
Gbp-Pq: Name api_define__SNR_ppoll_again.patch
cython3
From
8d09eb9314ad00aa0584345ae66d4419b38da8e0 Mon Sep 17 00:00:00 2001
From: Paul Moore <paul@paul-moore.com>
Date: Wed, 13 Nov 2019 20:54:25 -0500
Subject: [PATCH] build: try to use explicitly marked Python 3.x tools first
Python 2.x is going EOL very soon, so let's require Python 3.x now
and attempt to use the explicitly marked Python 3.x tools first.
Signed-off-by: Paul Moore <paul@paul-moore.com>
Gbp-Pq: Name cython3.patch
tests: rely on __SNR_xxx instead of __NR_xxx for syscalls
We recently changed how libseccomp handles syscall numbers that are
not defined natively, but we missed test #15.
Signed-off-by: Paul Moore <paul@paul-moore.com>
Note: Tagged for v2.5, but needed to build 2.4.2 with newer kernels on arm
This is part of PR: https://github.com/seccomp/libseccomp/pull/182
Upstream Bug: https://github.com/seccomp/libseccomp/issues/184
Origin: upstream, https://github.com/pcmoore/misc-libseccomp/commit/
35803ceb43c453762a3ab5177c5f8d5dbb813478
Bug-Ubuntu: https://bugs.launchpad.net/bugs/
1849785
Last-Update: 2019-11-12
Gbp-Pq: Name tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch