Bug#844497: seccomp "Invalid argument" due to old library version

Laurent Bigonville bigon at debian.org
Wed Nov 16 12:58:22 GMT 2016


On Wed, 16 Nov 2016 11:02:26 +0100 =?UTF-8?Q?Stefan_B=c3=bchler?= 
<stbuehler at lighttpd.net> wrote:
 > Hi,
 >
 > pdns.service (from pdns-server in testing) didn't start anymore with
 > this message:
 >
 > pdns.service: Failed at step SECCOMP spawning /usr/sbin/pdns_server: 
Invalid argument
 >
 > (See http://sources.debian.net/src/pdns/4.0.1-5/pdns/pdns.service.in/
 > for the service configuration.)
 >
 > Updating libseccomp2 from 2.1.1-1 (stable) to 2.3.1-2 (testing) fixed
 > it.
 >
 > systemd 232-3 has a build dependency `libseccomp-dev (>= 2.2.3-3~)`, but
 > the resulting package only depends on `libseccomp2 (>= 2.1.0)`.
 >
 > I filed a bug with libseccomp too, and maybe they'll fix their symbols
 > file for future builds.
 >
 > In the meantime I suggest adding an explicit minimum libseccomp2
 > dependency. Given the same build dependency in 230-7~bpo8+2 this is
 > probably broken in jessie-backports too.

FTR the seccomp bug is #844496

When #844496 is fixed systemd pkg will probably need a binNMU




More information about the Pkg-systemd-maintainers mailing list