The marble ebuild tries to patch files that it does not find. This is probably due to a wrong path in the find command in line 46 of the marble ebuild (line 47 in marble-4.7.4.ebuild) > find "${S}/marble/src/bindings/python/sip" -name "*.sip" | xargs -- sed -i 's/#include <marble\//#include </' ${S}/marble expands to ${WORKDIR}/marble-4.8.3/marble, but it should be only ${WORKDIR}/marble-4.8.3 The output containing the error message: >>> Emerging (1 of 1) kde-base/marble-4.8.3 * marble-4.8.3.tar.xz RMD160 SHA1 SHA256 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking marble-4.8.3.tar.xz to /var/tmp/portage/kde-base/marble-4.8.3/work >>> Source unpacked in /var/tmp/portage/kde-base/marble-4.8.3/work >>> Preparing source in /var/tmp/portage/kde-base/marble-4.8.3/work/marble-4.8.3 ... * Converting shebang in 'data/flags/downloadflags.py' * Converting shebang in 'data/ciasource/cia2kml.py' * Converting shebang in 'tools/add_kml/add_kml_tag.py' find: `/var/tmp/portage/kde-base/marble-4.8.3/work/marble-4.8.3/marble/src/bindings/python/sip': No such file or directory sed: no input files >>> Source prepared.
Thanks for spotting this QA issue, it is fixed in tree now. Sync in some hours to get the changes. + 04 May 2012; Johannes Huber <johu@gentoo.org> marble-4.7.4.ebuild, + marble-4.8.1.ebuild, marble-4.8.2.ebuild, marble-4.8.3.ebuild: + Remove useless sed which fails and produces an 'no input files' message. The + cause of the sed is fixed upstream since 2008/11/16. Fixes bug #414635.
