sys-fs/lvm2 shouldn't allow using `static-libs` and `systemd` flags in the same time. Reproducible: Always
We mask those flags in the systemd profiles: # 'static-libs' support on sys-apps/systemd is not provided virtual/libgudev static-libs virtual/libudev static-libs sys-fs/cryptsetup static static-libs sys-fs/lvm2 static static-libs sys-fs/dmraid static
The deps seem correct to me. We should not be replicating the REQUIRED_USE constraint from virtual/libudev in the sys-fs/lvm2 ebuild. I would expect to see a dependency error if you attempt to install lvm2 with both systemd and static-libs enabled. And from what I can tell, that is exactly what happens currently.
can you confirm this is solved for you with sys-fs/lvm-2.02.116-r2 and newer?