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> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | normal | CC: | bluebird, dev-portage |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Anders Aagaard
2007-06-26 09:01:01 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? (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. Ok thanks Zac, I'll give that a try in the next couple of days. 5:) (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. *** Bug 184010 has been marked as a duplicate of this bug. *** Ok, hopefully this has now been fixed, could people please test this out for me? Thanks... 5:) (In reply to comment #6) > Ok, hopefully this has now been fixed, could people please test this out for > me? Thanks... 5:) > Works, thanks a lot :) |