When I issue `emerge -C mail-client/pine-maildir`, I see the following: mail-client/pine-maildir selected: 4.56 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging mail-client/pine-maildir-4.56... No package files given... Grabbing a set. /var/db/pkg/mail-client/pine-maildir-4.56/pine-maildir-4.56.ebuild: line 91: syntax error near unexpected token `(' /var/db/pkg/mail-client/pine-maildir-4.56/pine-maildir-4.56.ebuild: line 91: ` -e "s:\$(SSLDIR)/certs:/etc/ssl/certs:" \' !!! ERROR: mail-client/pine-maildir-4.56 failed. Call stack: ebuild.sh, line 1454: Called die !!! error sourcing ebuild !!! If you need support, post the topmost build error, and the call stack if relevant. !!! FAILED prerm: 1 Reproducible: Always Steps to Reproduce: 1. emerge -C mail-client/pine-maildir Expected Results: A clean unmerge.
Nothing we could do w/ your locally corrupted ebuild. Edit /var/db/pkg/mail-client/pine-maildir-4.56/pine-maildir-4.56.ebuild and fix the syntax error there.
Not sure how you determined this file has been corrupted, as it has not been touched on this machine. When I tried to fix the obvious errors it ran into other issues. I have tried deleting the ebuild file, but an `emerge --sync` doesn't seem to bring it back.
Uh, emerge --sync won't bring ebuilds back into your VDB. You can grab one here... http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-mail/pine-maildir/?hideattic=0
Yes, and the version in CVS is byte-for-byte the same file I had before. And it fails, just like before.
We won't fix ebuilds removed from the tree, period. Replace the thing with a dummy ebuild if you still can't uninstall it.