This bug was fixed in the package libseccomp - 2.4.2-2ubuntu1
---------------
libseccomp (2.4.2-2ubuntu1) focal; urgency=medium
* Merge with Debian unstable (LP: 1849785). Remaining changes:
* Add autopkgtests
* Dropped changes (in upstream now):
- db-properly-reset-attribute-state.patch
- Updated to new upstream 2.4.1 version to fix security issue.
- add-log-action.patch: Minimal backport to support the
SECCOMP_RET_LOG action that was released in Linux kernel version
4.14.
* Dropped changes (in Debian now):
- debian/tests/testsuite-live:
- build utils with -pthread
- build tools/scmp_api_level
- debian/control: add valgrind to Build-Depends to get more unit tests.
- debian/*.install: change python paths.
- debian/libseccomp2.symbols: added new symbols.
- debian/rules: add dh_auto_configure before dh_auto_install to pick up
all the python versions.
- debian/patches/*: removed, all included in new version.
libseccomp (2.4.2-2) unstable; urgency=medium
[ Christian Ehrhardt ]
* d/rules: fix potential FTFBS after full python3 switch
* d/t/control: drop python2 test following the removal of the package
[ Felix Geyer ]
* Remove build-dependency on valgrind for mips64el as it's broken there.
* Backport patch to define __SNR_ppoll again.
- Add api_define__SNR_ppoll_again.patch
* Replace custom patch for cython3 with the upstream fix.
libseccomp (2.4.2-1) unstable; urgency=medium
[ Christian Ehrhardt ]
* New upstream release 2.4.2 for compatibility with newer kernels and
fixing FTBFS (LP: #1849785).
- drop d/p/python_install_dir.patch (now upstream)
- d/rules: adapt to python 3.8 lacking the m modifier on includes
see https://wiki.debian.org/Python/Python3.8
- d/p/tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch: fix
build time test on arm64
[ Felix Geyer ]
* Drop Python 2 bindings. (Closes: #936917)
- Add cython3.patch to use the Python 3 cython variant.
libseccomp (2.4.1-2) unstable; urgency=medium
* Remove build-dependency on valgrind for mipsel and x32 as it's broken
on those archs.
* Set Rules-Requires-Root: no.
libseccomp (2.4.1-1) unstable; urgency=medium
* New upstream release.
- Addresses CVE-2019-9893 (Closes: #924646)
* Drop all patches for parisc arch support, merged upstream.
* Build-depend on valgrind to run more unit tests.
* Run dh_auto_configure for every python 3 version to install the extension
in the correct path.
* Update the symbols file.
* Adapt autopkgtest to new upstream version:
- Build against pthread
- Build scmp_api_level tool
* Upgrade to debhelper compat level 12.
- Add d/not-installed file
* Fix install path of the python module.
- Add python_install_dir.patch
* Add autopkgtest for python packages.
-- Christian Ehrhardt <christian.ehrha...@canonical.com> Wed, 13 Nov
2019 08:41:54 +0100
** Changed in: libseccomp (Ubuntu)
Status: Triaged => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9893
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1849785
Title:
FTBFS on i386/ppc64/s390x (Eoan+Focal)
Status in libseccomp:
Fix Released
Status in libseccomp package in Ubuntu:
Fix Released
Status in libseccomp source package in Eoan:
Triaged
Bug description:
Due to the python 3.8 transition in focal this was rebuilt but fails atm.
=>
https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz
The simulations fail in this case:
batch name: 36-sim-ipc_syscalls
test mode: c
test type: bpf-sim
Test 36-sim-ipc_syscalls%%001-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%002-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%003-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%004-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%005-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%006-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%007-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%008-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%009-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%010-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%011-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%012-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%013-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%014-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%015-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%016-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%017-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%018-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%019-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%020-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%021-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%022-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%023-00001 result: ERROR 36-sim-ipc_syscalls rc=14
Test 36-sim-ipc_syscalls%%024-00001 result: ERROR 36-sim-ipc_syscalls rc=14
test mode: c
test type: bpf-valgrind
Test 36-sim-ipc_syscalls%%025-00001 result: FAILURE 36-sim-ipc_syscalls
rc=14
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
Test 37-sim-ipc_syscalls_be%%001-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%002-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%003-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%004-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%005-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%006-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%007-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%008-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%009-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%010-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%011-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test arch: s390
Test 37-sim-ipc_syscalls_be%%012-00001 result: ERROR 37-sim-ipc_syscalls_be
rc=14
test mode: c
test type: bpf-valgrind
Test 37-sim-ipc_syscalls_be%%013-00001 result: FAILURE
37-sim-ipc_syscalls_be rc=14
It is always the s390x test - even when running on i386/ppc64
On x86_64 this test succeeds:
Test 36-sim-ipc_syscalls%%025-00001 result: SUCCESS
batch name: 37-sim-ipc_syscalls_be
test mode: c
test type: bpf-sim
test arch: s390
To manage notifications about this bug go to:
https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
