during install ebuild tries to execute following command: sed -i -e '1idap' \ "${D}"/usr/$(get_libdir)/python*/site-packages/dap-*.egg-info/namespace_packages.txt || die and fails because there is no such file as namespace_packages.txt and dap-*.egg-info is a file and not a directory Reproducible: Always Steps to Reproduce: 1.emerge -av dev-python/dap Actual Results: installation fails Expected Results: installs cleanly after commenting out this command package installs fine and works (at least as a dependency for dev-python/basemap)
Removing that sed seems to confuse the generation of ./usr/lib64/python2.6/site-packages/dap-2.2.6.7-py2.6.egg-info There's an empty file and /usr/lib64/python2.6/site-packages/._cfg0000_dap-2.2.6.7-py2.6.egg-info with the content that should be in the file. very strange :)
(In reply to comment #1) > Removing that sed seems to confuse the generation of > ./usr/lib64/python2.6/site-packages/dap-2.2.6.7-py2.6.egg-info > > There's an empty file and > /usr/lib64/python2.6/site-packages/._cfg0000_dap-2.2.6.7-py2.6.egg-info > with the content that should be in the file. very strange :) > (i've got python-2.6.2-r1 and setuptools-0.6.1) I re-run original version of ebuild: and that's relevant error info: Writing /var/tmp/portage/dev-python/dap-2.2.6.7/image/usr/lib64/python2.6/site-packages/dap-2.2.6.7-py2.6.egg-info sed: can't read /var/tmp/portage/dev-python/dap-2.2.6.7/image//usr/lib64/python*/site-packages/dap-*.egg-info/namespace_packages.txt: No such file or directory there is a file named: /var/tmp/portage/dev-python/dap-2.2.6.7/image/usr/lib64/python2.6/site-packages/dap-2.2.6.7-py2.6.egg-info and it looks like this: silownik site-packages # head dap-2.2.6.7-py2.6.egg-info Metadata-Version: 1.0 Name: dap Version: 2.2.6.7 Summary: DAP (Data Access Protocol) client and server for Python. Home-page: http://pydap.org/ Author: Roberto De Almeida Author-email: rob@pydap.org License: MIT Description: Implementation of the `Data Access Protocol <http://opendap.org>`_. hope that helps...
can't reproduce here. could you provide the build log?
Created attachment 203958 [details] build log here you are
I also can't reproduce this bug...
I changed the sed line to a non-generated flag so that you should not encounter the failing sed anymore. Meanwhile you should check your python setup and may be run python-updater. The build log shows some suspicious lines in the beginning.
