This bug was fixed in the package libseccomp - 2.5.1-1ubuntu1
---------------
libseccomp (2.5.1-1ubuntu1) hirsute; urgency=medium
[ Christian Ehrhardt ]
* Merge with Debian; remaining changes:
- Add autopkgtests
* Dropped changes:
- d/p/db-consolidate-some-of-the-code-which-adds-rules.patch [in v2.5.0]
- d/p/db-add-shadow-transactions.patch [in v2.5.0]
- add-5.4-local-syscall-headers.patch [only for backports]
- Add missing syscalls for aarch64 [in v2.5.0]
* Added changes:
- bump to recent stable release v2.5.1
- drop patches that are upstream in 2.5.1
- d/p/all_only_request_the_userspace_notification_fd_once.patch
- d/p/arch_ensure_we_dont_munge_pseudo_syscall_numbers.patch
- d/p/build_undefine_mips_to_prevent_build_problems.patch
- d/p/system_change_our_notification_fd_handling.patch
- d/p/tests_use_openat_and_fstat_instead_of_open_and_stat_syscalls.patch
[ Alex Murray ]
* Add system call headers for powerpc required for backport to xenial
- d/p/add-5.8-powerpc-syscall-headers.patch
[ Balint Reczey ]
* Fix failing autopkgtests on armhf with glibc 2.33 (LP: #1915874)
- Update various autopkgtests to permit the use of statx as this is
now required with glibc 2.33
libseccomp (2.5.1-1) unstable; urgency=medium
* New upstream release.
* Drop all patches as they have been applied upstream.
libseccomp (2.5.0-3) unstable; urgency=medium
* Cherry-pick patch from the 2.5 branch to fix test error on mips:
- arch_ensure_we_dont_munge_pseudo_syscall_numbers.patch
libseccomp (2.5.0-2) unstable; urgency=medium
* Upload to unstable.
* Cherry-pick patches from the 2.5 branch to fix build and test errors:
- build_undefine_mips_to_prevent_build_problems.patch
- tests_use_openat_and_fstat_instead_of_open_and_stat_syscalls.patch
libseccomp (2.5.0-1) experimental; urgency=medium
* New upstream release.
- Build-depend on gperf.
- Update symbols file.
* Remove patches that have been applied upstream:
- cython3.patch
- riscv64_support.patch
* Cherry-pick patches from the 2.5 branch:
- all_only_request_the_userspace_notification_fd_once.patch
- system_change_our_notification_fd_handling.patch
libseccomp (2.4.4-1) unstable; urgency=medium
* Team upload.
[ Debian Janitor ]
* Set upstream metadata fields: Repository, Repository-Browse.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository.
[ Felix Geyer ]
* New upstream release.
* Download and verify orig gpg signature.
-- Alex Murray <alex.mur...@canonical.com> Thu, 18 Feb 2021 10:57:21
+1030
** Changed in: libseccomp (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1915874
Title:
autopkgtest fails in hirsute on armhf with glibc 2.33
Status in libseccomp package in Ubuntu:
Fix Released
Bug description:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/libs/libseccomp/20210214_103448_4822f@/log.gz
...
autopkgtest [10:33:19]: test test-filter: [-----------------------
= ./debian/tests/data/all-3.19.filter =
DEBUG: seccomp_load_filters ./debian/tests/data/all-3.19.filter
Bad system call (core dumped)
FAIL: expected to pass
...
The problem seems to be that with the new glibc upstream version the
test binaries started using statx which is not listed in the .filter
files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1915874/+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
