If you upgrade a package and the old version's ebuilds do not exist in portage, it gives errors. It still succeeds with the unmerge, but it should at least not spit out error information. Reproducible: Always Steps to Reproduce: 1. upgrade gentoolkit from 0.1.25 to 0.1.27 2. 0.1.25 is no longer in portage Actual Results: app-admin/gentoolkit selected: 0.1.25 protected: 0.1.27 omitted: none ... >>>Unmerging app-admin/gentoolkit-0.1.25 No package files given.... Grabbing a set /usr/sbin/ebuild.sh: line 1057: /usr/portage/app-admin/gentoolkit/gentoolkit-0.1.25.ebuild: No such file or directory !!! Error: app-admin/gentoolkit-0.1.25 failed !!! Function, Line 1057, Exit code 1 !!! error sourcing ebuild uninstalls files... Repeats the same error... Then finishes happily. Expected Results: It should not present the errors, or present them in a better way
Works here, so I assume it is fixed.