I tried to emerge VMWorkstation 6 (not the latest by the way (version bump?)) using vmware overlay. And I got something weird. I keyword amd64 in order to merge (it is with KEYWORDS="-*"). When doing 'emerge vmware-workstation', it selects too =vmware-modules-1.0.0.16 but here I have a little problem: vmware-workstation 6 has a amd64 and x86 download, the vmware-workstation ebuild is good, but the vmware-modules ebuild is a bit wrong, if I am using the amd64 version, it tries to download and compile modules from the x86 version instead of using x86_64 file (inside of vmware-modules-1.0.0.16.ebuild: SRC_URI="http://www.example.com/VMware-workstation-6.0.0-44426.i386.tar.gz"), is this correct? And this URI is not valid. I changed this line in ebuild to reflect VMware-workstation-6.0.0-44426.x86_64.tar.gz file in order to use this x86_64 one (same that will be used later for installing workstation) to build kernel modules, but it fails. Reproducible: Always Steps to Reproduce: 1. have vmware layman activated 2. keyword =vmware-workstation-6.0.0-44426 and =vmware-modules-1.0.0.16 with amd64 3. emerge vmware-workstation Actual Results: a) http://www.example.com/VMware-workstation-6.0.0-44426.i386.tar.gz requested by vmware-modules ebuild could not be found in the internet. b) vmware-modules-1.0.0.16 tries to use x86 file instead of x86_64 one c) if it tries to use x86_64 file, it fails Expected Results: 1. vmware-modules build from same file than workstation (the x86_64 one) 2. correct download of file in vmware-modules-1.0.0.16 ebuild
As a note: I saw a Changelog of this vmware overlay, I saw this: 28 Apr 2007; Mike Auty <ikelos@gentoo.org>: (...) Fixed up vmware-workstation-6 ebuild to support native amd64. Ok, vmware-workstation-6 is fixed, but vmware-modules needs a fix too! (and also, vmware-workstation-6.0.0-45731 has been released!). I'll post more info tomorrow as I am not in my box now (but the errores I was talking about earlier when using x86_64 file to build vmware-modules are decompressing errors [something about reaching end of file unexpectedly]
Hi David, thanks for the bug report, but I have the feeling several of the problems you're encountering are related to the fact that vmware-workstation-6 has been released, whereas the ebuilds in the overlay are for the free betas. Since I don't have a license for the full workstation I can't really test it to ensure that it's all working ok. It'd be my guess that the particular version of the files the modules you are trying to download no longer exists. As to the fact that the modules are being retrieved from the i386 package rather than the x86_64 package, it's not yet clear whether that makes a difference (and the person who sent me the amd64 changes for the ebuild did not mention any changes were required for the modules, and since they're compiled on a per-system basis, I'm not sure I'd expect that to matter). In short, please wait for the vmware-workstation 6 version bump to become official, and don't be surprised if the modules that are downloaded say they're from the i386 package. Eventually they will move over the to vmware-any-any compatability modules and they won't need the extra file...
Hi Mike! You don't need a license to use and test Workstation6!! You can just register for free in vmware site and get a free license for latest Workstation for 30 days, so you can test anything you want within this period of time. Just check http://www.vmware.com/vmwarestore/newstore/wkst6_eval_login.jsp register for free, and you will get access to download and they will email to you a license for 30 days [serial number]. This is free, so you can check it out in order to improve ebuilds and even a version bump to new revision 45731 if applicable. I think the change of modules cause a problem when executing /opt/vmware/bin/vmware-config.pl Could it be possible to include amd64? (URI) x86? (URI) for selecting package?
By the way, you can add this URI to ebuild, wich is the vmware's official and has no fail: 32 bits: http://download3.vmware.com/software/wkst/${MY_PN}.i386.tar.gz 64 bits: http://download3.vmware.com/software/wkst/${MY_PN}.x86_64.tar.gz (at least works for version 44426 ebuild)
StormByte, it would be a little foolish of me to bump an ebuild that I can only test for 30 days. What would happen with bugs that got filed on it after 30 days? I wouldn't be able to test them or help fix them. I appreciate your concern in getting this bug fixed quickly, but I'm afraid patience is required at the moment. The ebuild available in the overlay during the testing phase was meant as a prototype to help when the final workstation came out, which is why it was kept in the testing overlay, rather than being put into the main tree. So please, wait a little longer and we will get workstation 6 into the main tree eventually...
Ok, got it :)
Vmware 6 45731 is out and it is the production release of vmware, with no beta expiry.
(In reply to comment #5) > StormByte, it would be a little foolish of me to bump an ebuild that I can only > test for 30 days. just use same account for a new test key for retest.
Ok guys, I'm going to close this because: * workstation-6 is now masked in the main portage tree * it selects x86_64 or i386 appropriately * the sources for the modules are identical on both, so were ever you get the source, they'll compile fine. * the modules, shared amongst x86, amd64, workstation and player are now downloaded from the vmware-player archive, which is freely available and much smaller than vmware-workstation. Please don't complain about this, as soon as vmware-any-any-update supports vmware-6, we'll be moving to that. The only other comments in this bug are about getting workstation 6 bumped (see bug 177876), or finding ways to support vmware without a license, which really don't belong here (or anywhere for that matter). If you have any new issues with vmware-workstation on amd64, please open new bug. Thanks... 5:)
