|Summary:||Confusing information when nofetch is on with vmware-workstation 6|
|Product:||Portage Development||Reporter:||Anders Aagaard <aagaande>|
|Component:||Core||Assignee:||Gentoo VMWare Bug Squashers [disabled] <vmware+disabled>|
|Package list:||Runtime testing required:||---|
Description Anders Aagaard 2007-06-26 09:01:01 UTC
I was working on installing vmware6, I installed vmware-modules and all dependencies first, and did rm /usr/portage/distfiles/vmware* to wipe out all my old vmware data. When I do emerge vmware-workstation after that I get the error : * Please download the VMware-workstation-6.0.0-45731.tar.gz at http://www.vmware.com/products/desktop/ws_features.html Ok, fair enough, it's listing the wrong file (should be looking for amd64), but nvm that. I grabbed the amd64 package and put it in /usr/portage/distfiles and got the exact same error again. The reason is that vmware-workstation also requires vmware-any-any-update109.tar.gz, that file does not have fetch restriction, but portage does not download it. And instead gives an error about VMware-workstation-6.0.0-45731.tar.gz, even when the correct file exists in distfiles. Reproducible: Always Steps to Reproduce: 1. Install all vmware dependencies 2. Remove all vmware distfiles 3. emerge vmware-workstation
Comment 1 Mike Auty (RETIRED) 2007-06-26 18:41:23 UTC
I can see how that would be confusing (and I also know why the file name issue is occuring, which I'll try to get fixed up), unfortunately, I'm not sure how best to get around the problem. Downloads are no longer available (there's *another* bug about that), so I've had to apply fetch restrictions, and as far as I'm aware, it's not possible to apply fetch restrictions to certain files. The best I think I can do is add an extra line asking people to ensure they've got the correct vmware-any-any-update file. Would this be ok?
Comment 2 Zac Medico 2007-06-27 00:47:36 UTC
(In reply to comment #1) > I've had to apply fetch restrictions, and as far > as I'm aware, it's not possible to apply fetch restrictions to certain files. Portage will still fetch any files having a mirror:// uri even if the package has RESTRICT=fetch. If the file can't be mirrored on gentoo mirrors, you still have the option to use thirdpartymirrors.
Comment 3 Mike Auty (RETIRED) 2007-06-27 00:53:16 UTC
Ok thanks Zac, I'll give that a try in the next couple of days. 5:)
Comment 4 Anders Aagaard 2007-06-27 05:42:47 UTC
(In reply to comment #2) > (In reply to comment #1) > > I've had to apply fetch restrictions, and as far > > as I'm aware, it's not possible to apply fetch restrictions to certain files. > > Portage will still fetch any files having a mirror:// uri even if the package > has RESTRICT=fetch. If the file can't be mirrored on gentoo mirrors, you still > have the option to use thirdpartymirrors. > Ahh, I filed this under portage-dev as I didn't think this was possible.
Comment 5 Jakub Moc (RETIRED) 2007-07-02 21:27:06 UTC
*** Bug 184010 has been marked as a duplicate of this bug. ***
Comment 6 Mike Auty (RETIRED) 2007-09-19 15:58:11 UTC
Ok, hopefully this has now been fixed, could people please test this out for me? Thanks... 5:)