I am attempting to use portage on Mac OS X 10.2.8 (Darwin 6.8). The command 'emerge info' captures the output of 'uname -mrp'. On my system, running uname from the shell returns: % uname -mrp 6.8 Power Macintosh powerpc However, when running 'emerge info', I see: % emerge info Portage 2.0.49-r3 (unavailable, gcc-3.1, glibc-unavailable, 6.8) ============================================================ ===== System uname: sh: /bin/uname: No such file or directory [more output follows] Going back to the shell: % which uname /usr/bin/uname Therefore I suggest that 'emerge info' invoke an unscoped 'uname -mrp' rather than '/bin/uname -mrp'. My justification is that in the getportageversion() function also in the emerge script, an unscoped "uname -r" is invoked. Reproducible: Always Steps to Reproduce: 1. Install portage on Mac OS X 10.2.8. Easier said than done... 2. Run 'emerge info'. 3. Examine the 3rd line of the output. Actual Results: System uname: sh: /bin/uname: No such file or directory Expected Results: 6.8 Power Macintosh powerpc Portage 2.0.49-r3 (unavailable, gcc-3.1, glibc-unavailable, 6.8) ============================================================ ===== System uname: sh: /bin/uname: No such file or directory ACCEPT_KEYWORDS="" AUTOCLEAN="yes" CFLAGS="-O2 -pipe" CHOST="ppc-darwin" COMPILER="" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/ 3/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="-sandbox ccache" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/ distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE=""
Created attachment 19495 [details, diff] emerge patch
Created attachment 19496 [details, diff] portage.py patch
This should fix it, we may want to figure out how to *just* use os.uname
os.uname patch added to cvs.
this is fixed in current stable portage version