When I want to emerge app-emulation/vmware-workstation-tools-5.5.3 (also 5.5.1-r2) it stops on unpacking vmware-any-any-update105.tar.gz. The file "vmware-any-any-update105.tar.gz" is NOT downloaded to /usr/portage/disfiles or anywhere else on my system. In latest stable ebuild app-emulation/vmware-workstation-tools-5.5.1 (not in portage tree anymore) it works! emerge output: -------------------------------------------------------------------------- >>> Emerging (1 of 1) app-emulation/vmware-workstation-tools-5.5.3 to / * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Adding group 'vmware' to your system ... * - Groupid: next available >>> Unpacking source... * You will need VMwareTools-5.5.3-34685.tar.gz from the VMware installation. * Select VM->Install VMware Tools from VMware's menu. * This ebuild will need the cdrom for vmware-workstation-tools * If you do not have the CD, but have the data files * mounted somewhere on your filesystem, just export * the variable CD_ROOT so that it points to the * directory containing the files. * For example: * export CD_ROOT=/mnt/cdrom * Found CD #1 root at /mnt/cdrom >>> Unpacking vmware-any-any-update105.tar.gz to /var/tmp/portage/vmware-workstation-tools-5.5.3/work !!! ERROR: app-emulation/vmware-workstation-tools-5.5.3 failed. Call stack: ebuild.sh, line 1546: Called dyn_unpack ebuild.sh, line 708: Called src_unpack ebuild.sh, line 1255: Called vmware_src_unpack vmware.eclass, line 119: Called unpack 'vmware-any-any-update105.tar.gz' ebuild.sh, line 369: Called die !!! vmware-any-any-update105.tar.gz does not exist !!! If you need support, post the topmost build error, and the call stack if relevant. -------------------------------------------------------------------------- Reproducible: Always Steps to Reproduce:
I also see this problem. I even did a hack to get around this - I suspend the emerge once it has started and drop in the any-any update tarball into the /var/tmp/portage/vmwa<yadda>/work directory and then resume. It builds and emerges just fine. However, it appears something is badly broken because you cannot run the configure tools script whatsoever.
This should be fixed in CVS... wait a couple hours, emerge --sync, then try again.