When emerging dev-db/firebird-1.5.1 before the install phase many sed errors appear. These are caused by a sed attempting to read a directory. This can easily be solved to make a cleaner (e)build output. Reproducible: Always Steps to Reproduce: 1. emerge "=dev-db/firefird-1.5.1" 2. watch the ebuild doing it's work, especially right after the install phase has started 3. Actual Results: many sed errors Expected Results: be a little more cautious with what sed to feed and avoid those errors
Created attachment 63446 [details, diff] small patch made to the ebuild by telling find only to look for files, sed does not have to try to operate on directories, which it doesn't know how to operate on.
Fixed in portage, thanks for help.
