qemu-7.1.0-r2 cannot be built with USE="-seccomp"

[proteusx]

I always compile qemu with USE="-seccomp" but with qemu-7.1.0-r2 I get this:

Code: Select all

 # USE="-seccomp" emerge -vp qemu

!!! Problem resolving dependencies for app-emulation/qemu

!!! The ebuild selected to satisfy "qemu" has unmet requirements.
- app-emulation/qemu-7.1.0-r2::gentoo USE="aio alsa bzip2 caps capstone curl doc
  fdt filecaps gnutls gtk iscsi jpeg ncurses nls opengl oss pam
  pin-upstream-blobs png pulseaudio python sdl slirp smartcard spice ssh udev
  usb usbredir vde vhost-net virtfs vnc vte xattr -accessibility -bpf -debug
  -fuse -glusterfs -infiniband -io-uring -jack -jemalloc -lzo -multipath -nfs
  -numa -plugins -rbd -sasl -sdl-image -seccomp (-selinux) -snappy -static
  -static-user -systemtap -test -virgl -xen -zstd" ABI_X86="(64)"
  PYTHON_TARGETS="python3_8 -python3_10 -python3_11 -python3_9"
  QEMU_SOFTMMU_TARGETS="i386 x86_64 -aarch64 -alpha -arm -avr -cris -hppa
  -loongarch64 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel
  -nios2 -or1k -ppc -ppc64 -riscv32 -riscv64 -rx -s390x -sh4 -sh4eb -sparc
  -sparc64 -tricore -xtensa -xtensaeb" QEMU_USER_TARGETS="i386 x86_64 -aarch64
  -aarch64_be -alpha -arm -armeb -cris -hexagon -hppa -loongarch64 -m68k
  -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -mipsn32 -mipsn32el
  -nios2 -or1k -ppc -ppc64 -ppc64le -riscv32 -riscv64 -s390x -sh4 -sh4eb -sparc
  -sparc32plus -sparc64 -xtensa -xtensaeb"

----------------------------------------------------------------------------
    The following REQUIRED_USE flag constraints are unsatisfied:
        seccomp
----------------------------------------------------------------------------

          The above constraints are a subset of the following complete
          expression:
              caps seccomp any-of ( python_targets_python3_8
              python_targets_python3_9 python_targets_python3_10
              python_targets_python3_11 ) qemu_softmmu_targets_arm? ( fdt
              ) qemu_softmmu_targets_microblaze? ( fdt
              ) qemu_softmmu_targets_mips64el? ( fdt
              ) qemu_softmmu_targets_ppc64? ( fdt ) qemu_softmmu_targets_ppc?
              ( fdt ) qemu_softmmu_targets_riscv32? ( fdt
              ) qemu_softmmu_targets_riscv64? ( fdt
              ) qemu_softmmu_targets_x86_64? ( fdt ) sdl-image? ( sdl ) static?
              ( static-user !alsa !gtk !jack !opengl !pam !pulseaudio !plugins
              !rbd !snappy !udev ) static-user? ( !plugins ) virgl? ( opengl
              ) virtfs? ( caps xattr ) vnc? ( gnutls ) vte? ( gtk ) multipath?
              ( udev ) plugins? ( !static !static-user )

qemu-7.1.0-r2.ebuild shows this:

Code: Select all

REQUIRED_USE="caps seccomp
...................... etc.

Hence it appears that building qemu without USE="caps seccomp" is now impossible.

Is this intentional or is it a mistake in the latest ebuild?

[fedeliallalinea]

Is this intentional or is it a mistake in the latest ebuild?

It's intentional, look this commit and bug #873190.

[proteusx]

It's intentional, look this commit and bug #873190.

Thank you for the reply.
I had already seen that bug report but It does not say why USE="seccomp" must be applied in all cases.
Also, if the ebuild specifies unconditionally REQUIRED_USE="caps seccomp", doesn't this make the option seccomp (and caps) functionally unavailing?

[grknight]

It's intentional, look this commit and bug #873190.

Thank you for the reply.
I had already seen that bug report but It does not say why USE="seccomp" must be applied in all cases.
Also, if the ebuild specifies unconditionally REQUIRED_USE="caps seccomp", doesn't this make the option seccomp (and caps) functionally unavailing?

The USE vhost-user-fs was removed which previously required caps and seccomp.

I have responded to the bug on your final point and agree it has not gone far enough. If something is required, make it required.