The current ppp-2.4.4-r22.ebuild ebuild contains these lines: insinto /etc/modprobe.d insopts -m0644 newins "${FILESDIR}/modules.ppp" ppp.conf if use mppe-mppc; then sed -i -e 's/ppp_mppe/ppp_mppe_mppc/' "${D}/etc/modprobe.d/ppp" fi So the file gets installed as "ppp.conf", but with the use flag enabled, sed tries to operate on a different file called "ppp". And as the return value of the sed isn't checked, the problem will most likely go unnoticed. I'm reporting this issue solely based on the contents of the ebuild; I haven't expecienced any consequences of this myself. Is there a tracker for issues with modprobe.d files newly requiring the .conf extension?
Fixed in revision -r23. The old revisions were removed and the new one was submitted with stable keywords.
