Merge lp:~paelzer/britney/hints-ubuntu-focal-libseccomp-i386 into lp:~ubuntu-release/britney/hints-ubuntu

[Christian Ehrhardt ]

[Christian Ehrhardt  (paelzer)]

FYI: Moving it up to the right section and dropping the (outdated) version restriction.

[Christian Ehrhardt  (paelzer)]

Case#2 of https://lists.ubuntu.com/archives/ubuntu-devel/2019-December/040859.html

[Steve Langasek (vorlon)]

Because libseccomp has 3 autopkgtests and it appears only one of them depends on python, it might be possible to mark this one test Restrictions: skip-not-installable and get the others passing. Do you want to investigate this before we mark libseccomp as completely untestable?

[Steve Langasek (vorlon)]

Sorry, that's not entirely accurate; test-filter test-scmp_sys_resolver depend on @, so also require the python3 module to be pulled in. However, neither test /uses/ python, so judicious adjustment of the test dependencies might make those testable.

[Steve Langasek (vorlon)]

And test-filter relies on installing seccomp filters on /bin/date, which is going to be a 64-bit binary instead of 32-bit, so that test will also fail.

I can get the test-scmp_sys_resolver test to pass and probably testsuite-live, but I'm convinced there's enough here we should just badtest.

=== modified file 'ubuntu-release'
--- ubuntu-release	2020-01-06 17:07:09 +0000
+++ ubuntu-release	2020-01-07 10:06:48 +0000
@@ -8709,6 +8709,7 @@
 force-badtest python-cffi/all/i386 
 force-badtest umockdev/all/i386
 force-badtest upower/all/i386
+force-badtest libseccomp/all/i386
 
 # requires dh-python to not generate dependencies on python3.7, python3:any
 force-badtest glib2.0/all/i386
@@ -8869,7 +8870,6 @@
 force-badtest libraw/0.19.5-1/i386
 force-badtest libsass/3.5.5-4/i386
 force-badtest libsdl-sge/030809dfsg-9/i386
-force-badtest libseccomp/2.4.1-0ubuntu0.19.10.3/i386 libseccomp/2.4.2-2ubuntu1/i386
 force-badtest libsoxr/0.1.3-2build1/i386
 force-badtest libthai/0.1.28-3/i386
 force-badtest libtommath/1.2.0-3/i386