>>> Safely unmerging already-installed instance... /var/tmp/binpkgs/sci-misc/qcad-2.0.4.0-r3/temp/environment: line 367: syntax error near unexpected token `(' /var/tmp/binpkgs/sci-misc/qcad-2.0.4.0-r3/temp/environment: line 367: ` done <<(get_mounts);' * * ERROR: sci-misc/qcad-2.0.4.0-r3 failed. * Call stack: * ebuild.sh, line 1641: Called die * The specific snippet of code: * preprocess_ebuild_env || \ * die "error processing environment" * The die message: * error processing environment * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/binpkgs/sci-misc/qcad-2.0.4.0-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/binpkgs/sci-misc/qcad-2.0.4.0-r3/temp/environment'. * !!! FAILED prerm: 1 * The 'prerm' phase of the 'sci-misc/qcad-2.0.4.0-r3' package has failed * with exit value 1. The problem occurred while executing the ebuild * located at '/var/db/pkg/sci- * misc/qcad-2.0.4.0-r3/qcad-2.0.4.0-r3.ebuild'. If necessary, manually * remove the ebuild in order to skip the execution of removal phases. >>> Original instance of package unmerged safely. >>> sci-misc/qcad-2.0.4.0-r3 merged. >>> No packages selected for removal by clean >>> Auto-cleaning packages... >>> No outdated packages were found on your system. Reproducible: Always
Hans: Please delete /var/db/pkg/sci-misc/qcad-2.0.4.0-r3/environment.bz2 and retry unmerging QCad. Portage team: I could resolve this as dupe of bug 211176 or some other one, but since we have a few dozen of this sort of bug reports - granted, mostly duplicates for sure - because of broken postrm routines and this won't stop, unless we do something about it, I'm assigning.
Well, I think main problem is that the message in portage-2.1.4.4 isn't informative enough. That's fixed in newer versions that have yet to be marked stable. *** This bug has been marked as a duplicate of bug 211833 ***
