I can't say why exactly but realize /etc/portage/patches/sys-auth/pam_ssh/my.patch isn't applied - while all the others at /etc/portage/patches/* are. Probably this is due to '_' char in PN? Or why else? Reproducible: Always Steps to Reproduce: 1. copy my.patch to /etc/portage/patches/sys-auth/pam_ssh/ 2.$ ebuild /usr/portage/sys-auth/pam_ssh/pam_ssh-1.98.ebuild prepare Actual Results: >>> Unpacking source... >>> Unpacking pam_ssh-1.98.tar.bz2 to /var/tmp/portage/sys-auth/pam_ssh-1.98/work >>> Source unpacked in /var/tmp/portage/sys-auth/pam_ssh-1.98/work >>> Preparing source in /var/tmp/portage/sys-auth/pam_ssh-1.98/work/pam_ssh-1.98 ... >>> Source prepared. Expected Results: ... >>> Preparing source in /var/tmp/portage/sys-auth/pam_ssh-1.98/work/pam_ssh-1.98 ... * Applying user patches from /etc/portage/patches//sys-auth/pam_ssh ... * my.patch ... * Done with patching >>> Source prepared.
Created attachment 517342 [details, diff] /etc/portage/patches/sys-auth/pam_ssh/my.patch
The ebuild would have to use EAPI=6 or call the epatch_user function.
Created attachment 517344 [details] sys-auth/pam_ssh-1.98.ebuild adopted to EAPI=6 indeed this works.
>=2.2 are EAPI-7 based.
