The 5.1.0 ebuild contains this line: SITEFILE=50${PN}-gentoo-5.1.el The files dir, on the other hand, has a file starting with 60, not 50. So the ebuild won't install. Given the fact that both files were committed at the same time, I assume the committer intended them to match, and had a typo instead. * Installing site initialisation file for GNU Emacs ... cp: cannot stat `/usr/portage/app-emacs/python-mode/files/50python-mode-gentoo-5.1.el': No such file or directory sed: can't read /var/tmp/portage/app-emacs/python-mode-5.1.0/temp/50python-mode-gentoo.el: No such file or directory install: cannot stat `/var/tmp/portage/app-emacs/python-mode-5.1.0/temp/50python-mode-gentoo.el': No such file or directory !!! doins: /var/tmp/portage/app-emacs/python-mode-5.1.0/temp/50python-mode-gentoo.el does not exist * elisp-site-file-install: doins failed [ !! ] * * ERROR: app-emacs/python-mode-5.1.0 failed. * Call stack: * ebuild.sh, line 49: Called src_install * environment, line 2652: Called elisp_src_install * environment, line 1034: Called die * The specific snippet of code: * elisp-site-file-install "${FILESDIR}/${SITEFILE}" || die; * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/app-emacs:python-mode-5.1.0:20090416-134117.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emacs/python-mode-5.1.0/temp/environment'. *
Thanks for the notice, but don't add random people to CC, bug wranglers will eventually handle the report.
Fixed
*** Bug 266389 has been marked as a duplicate of this bug. ***