See my previous bug #12419. The conflict has not changed in later versions. I'm running evms-1.2.1-r1 on a new 1.4_rc4 install, and the same conflict exists with e2fsprogs-1.33. Perhaps the e2fsprogs-1.33 ebuild needs to be modified to prevent this condition. Demo
I can vouch for this too. The plug-in Ext2/3 in module /lib/evms/libe2fsim.1.2.1.so requires Engine services API version (8.1.0) which is less than this Engine's services API version (10.0.0). solution: rm /lib/evms/libe2fsim.1.2.1.so
I'm new to evms, and have this bug too.. what does it mean? and I'm gonna try the "solution" because this isn't a critical machine.. but what is the propper fix? I assume that a new library is avaiable somewhere?
EVMS comes with it's own ext2-fs plugin. There is absolutly no need for e2fsprogs to install the evms plugin. The plugin from e2fsprogs is so old that it will not work with any evms version currently in portage anyway. (I think it's from evms 1.0.x times). I would recomment to change the e2fsprogs ebuild to not install /lib/evms/libe2fsim.1.2.1.so anymore.
2.3.4 fixes this (and I think 2.3.2 might also)