the old-crypt useflag in util-linux only works if you also specify -crypt. As "crypt" is a global use flag which is also used for other stuff, the ebuild should be corrected so that the loop-aes patch only gets applied if the cryptoapi wasn't applied before. And just for interest: I know that cryptoapi has its issues, but why do we default on something (loop-aes) which none of our default kernels supply at all? Wouldn't it be more logical to use new-crypt for loop-aes? Reproducible: Always Steps to Reproduce: 1. 2. 3.
cryptoapi is crap ... it's dead upstream and it only still applies to util-linux becuase people (like myself) have been forward porting it i stopped doing that with 2.12p i'll touch up the ebuild to do `! use old-crypt && use crypt && epatch loop-aes`
added ! use old-crypt logic to cvs
