Released: "Workstation Version 6.5.2 | 31 March 2009 | Build 156735" http://www.vmware.com/support/ws65/doc/releasenotes_ws652.html Reproducible: Always
Created attachment 187357 [details] adopted ebuild
(In reply to comment #1) > adopted ebuild I have adopted the name to reflect the new ebuild number. Unfortunately, calling "ebuild ... manifest", it _always_ tried to download the .i386 package. Thus, as a quick hack, I modified # SRC_URI=" # x86? ( # mirror://vmware/software/wkst/${MY_PN}.i386.bundle # http://download.softpedia.ro/linux/${MY_PN}.i386.bundle ) # amd64? ( # mirror://vmware/software/wkst/${MY_PN}.x86_64.bundle # http://download.softpedia.ro/linux/${MY_PN}.x86_64.bundle ) # " to SRC_URI=" mirror://vmware/software/wkst/${MY_PN}.x86_64.bundle http://download.softpedia.ro/linux/${MY_PN}.x86_64.bundle " Furtheron, you have to extend ./files: $ ll files/ ... ... 6.5.2.156735 ... ... vmware-workstation-6.5.2.156735-installer.patch ... With these adaptations, it emerged flawlessly on my amd64 / 2.6.28.
(In reply to comment #0) > Released: "Workstation Version 6.5.2 | 31 March 2009 | Build 156735" ... and WORKS - at least for me ;) First TEST successful: My oldest machine (W2k SP4 UR1) is up and running, Network acces (bridged) working.
Please attach unified diffs (diff -u) when you did changes to an ebuild. That would be much more handy for our devs.
I emerged vmware-workstation-6.5.2.156735 from overlay and worked flawlessly on my ~x86 system Thank you.
Hiya Manfred, Do please check the vmware overlay if you're interested in the latest versions of vmware software. Vmware-workstation-6.5.2.156735 (and vmware-player-6.5.2 and vmware-server-2.0.1) have been in the overlay [1] since two days after they came out. They're going to sit there for a bit for testing before they get added to the main tree, please put them through their paces... 5;) [1] http://overlays.gentoo.org/proj/vmware/browser/trunk/app-emulation/vmware-workstation/vmware-workstation-6.5.2.156735.ebuild
(In reply to comment #6) > Hiya Manfred, > Do please check the vmware overlay ... Mike, sure, I should have done that - I'm sorry for the additional noise! > They're going to sit there for a bit for testing Sure, "naturallemente". > please put them through their paces... 5;) Sure, I'm pleased and will report back ASAP. Kind regards Manfred
(In reply to comment #7) > (In reply to comment #6) Hi, Mike, I fear that now it's really a BUG, as already described in my comment #1 : $ ebuild vmware-workstation-6.5.2.156735.ebuild manifest >>> Downloading 'http://download3.vmware.com/software/wkst/VMware-Workstation-6.5.2-156735.i386.bundle' ... (we can forget the subsequent output being "consequential damage") Please note the >>>.i386.<<< - you know that I'm on amd64 ! BTW, would it perhaps be preferable to ~-set KEYWORDS="-* ~x86 ~amd64" ?
Manfred, building a manifest requires *all* the possible source files that can be downloaded, so that it can correctly determine the hashes. If I were doing the manifest on an x86 machine, it would still require the x86_64 bundle (it just so happens that x86 comes first). Either way, I've already downloaded both myself, and provided the correct hashes in the manifest (which you can find in the vmware overlay). It's only if you modify the ebuild or add/remove any other files from the directory that you'd need to rebuild the manifest, in which case you'll either have to download the file or simply touch it in /usr/portage/distfiles (in which case your manifest will be wrong in case you give it to anyone else). You can get the correct manifest line from here: http://overlays.gentoo.org/proj/vmware/browser/trunk/app-emulation/vmware-workstation/Manifest#L21
(In reply to comment #9) MID-AIR COLLISION : with two meanings ;) > building a manifest requires *all* the possible source files ... For SURE!!! (Too tired from the last 10 days; Sorry.) And yes, I'm bulding my manifests myself ... Anyway, here come the good news: # emerge -a app-emulation/vmware-workstation ... [ebuild I Rf ] app-emulation/vmware-workstation-6.5.2.156735 throws some error messages: Installing VMware Player 2.5.2 Configuring...Traceback (most recent call last): File "/usr/lib64/python2.5/logging/handlers.py", line 73, in emit ] 56% if self.shouldRollover(record): ... but SUCCEEDS: ... Installing VMware Workstation 6.5.2 Configuring... [######################################################################] 100% Installation was successful ... >>> Completed installing vmware-workstation-6.5.2.156735 into /Storage-B/Portage_tmp/portage/app-emulation/vmware-workstation-6.5.2.156735/image/ ... >>> Installing app-emulation/vmware-workstation-6.5.2.156735 ... # /etc/init.d/vmware start SUCCEEDS W2k / WXP / CentOS_5.3 all start flawlessly, including suspend / resume of CentOS. Great.
Hurry, security updates11!! ;)
Ok, this is now in the tree because of the security bugs. The updated vmware-modules will follow, but it works fine with the previous modules...
