If you emerge with USE="crypt -old-crypt", you get binaries that support loop-AES but not cryptoloop. If you emerge with USE="-crypt old-crypt", you get binaries that support cryptoloop but not loop-AES. If you emerge with USE="crypt old-crypt", you get two sets of binaries (one of them suffixed -old-crypt), but neither supports loop-AES. I have a one-line patch to the 2.12q-r1 ebuild (to follow) which appears to fix this, causing the main binaries to support loop-AES and the additional -old-crypt ones to support cryptoloop -- which I presume was the intention. This bug appears to have been present at least since 2.12p-r1 (the earliest loop-AES-supporting version currently in portage -- 2.12i-r1 has the loop-AES stuff commented out). Reproducible: Always Steps to Reproduce: 1. USE="crypt old-crypt" emerge util-linux 2. losetup -a 3. losetup-old-crypt -a Actual Results: Neither version of losetup supported the loop-AES -a option Expected Results: losetup should have had the loop-AES support, which losetup-old-crypt should have been the cryptoloop version.
Created attachment 66069 [details, diff] Patch
left over from when USE=old-crypt didnt produce a second set of binaries fixed in cvs, thanks
