genkernel-next initramfs work only with app-crypt/gnupg-1.4.x, but not with app-crypt/gnupg-2 that require /usr/bin/gpg-agent binary copied into initramfs and more work around in the init script. In the same time, sys-kernel/genkernel-next have ebuild part RDEPEND "gpg? ( app-crypt/gnupg )", that allow "gpg" USE flag with emerged gnupg-2, but during boot you will have "/usr/bin/gpg-agent not found" error (and some more errors, related to gnupg-2 work), plus, boot process will be stoped, since no chance to decrypt luks pgp key for crypted root partition. Unfortunately, gnome-base/gnome-keyring require >=app-crypt/gnupg-2.0.28, so, no chance to mask gnupg-2 and emerge gnupg-1.4.x (at least for me). Is the any chance for SLOT gnupg-1.4.x/2.x.x, or separate gnupg binary build for genkernel-next, or any other solutions? It's a bit ridiculous, when you need work around DE packages in order to create full functional initramfs... Reproducible: Always
What version are you running?
Created attachment 435076 [details] Boot with gnupg-2 and LUKS PGP key. Tested on sys-kernel/genkernel-next-63 and sys-kernel/genkernel-next-64 with identical results. I attached photo with my stopped boot process with initramfs created by sys-kernel/genkernel-next with gnupg-2.
Probably reporting this directly to upstream will help: https://github.com/Sabayon/genkernel-next/issues Thanks
Done. https://github.com/Sabayon/genkernel-next/issues/33 I found in sources https://github.com/Sabayon/genkernel-next/blob/master/gen_initramfs.sh#L585 , and this let me think that the gnupg-2 not supported for sure. Probably, till gnupg-2 not supported, sys-kernel/genkernel-next RDEPEND "gpg? ( app-crypt/gnupg )" should be corrected to avoid app-crypt/gnupg-2 and USE "gpg"?
I have posted a way to get GnuPG 2 to work with genkernel-next here: https://github.com/Sabayon/genkernel-next/issues/33
Package removed.
