Currently virtual/udev[static_libs] can't be satisfied by sys-apps/systemd and pulls in sys-fs/udev, which is not compatible with the new revision of sys-apps/systemd (and vice versa). It's currently impossible to have both virtual/udev[static_libs] and systemd on the same system. virtual/udev[static_libs] is needed by e.g. cryptsetup[static]. Reproducible: Always
*** Bug 463374 has been marked as a duplicate of this bug. ***
I have no objection to adding that.
Added now. I didn't revbump since -199 will land soon enough.
We're on -206-r5 now and the issue is still there, so why is this "RESOLVED FIXED" ?
systemd upstream declared static libraries as being unsupported, so we dropped it as well.
Thanks, guess I have to use a hackish ebuild that gives the USE flag without building static for now. :( Anyway, as this (the problem with virtual/udev and static_libs) is not fixed I think somebody should re-open this issue.
I 'am interested too. Because i don't how to build an initrd with lvm for my lvm root device without static-libs.
as for now: zymtest1 systemd # grep static-libs *.ebuild systemd-204-r1.ebuild systemd-208-r2.ebuild systemd-208-r3.ebuild systemd-210.ebuild systemd-9999.ebuild zymtest1 systemd # grep static-libs *.ebuild systemd-204-r1.ebuild: keymap +kmod lzma openrc pam policykit python qrcode selinux static-libs zymtest1 systemd # LANG=C date -u Wed Feb 26 07:06:48 UTC 2014 it is still not a fix in the portage stable. :(
a temp solution maybe remove the static-libs flags from the virtual/udev when rdepends on >=systemd-208 :(