Summary: | app-emulation/vmware-modules-1.0.0.16-r1 failed to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Ruskin <aoyu93> |
Component: | Current packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Ruskin
2007-09-17 10:52:29 UTC
Hi, I'm afraid I'm having difficulty replicating this problem, can you please try building the modules directly from the tree (i.e. removing the vmware overlay from your overlay list)? Please also verify that you don't have any vmware or vmware-mod eclasses in your /usr/local/portage overlay. Finally, if you could check that you're downloading vmware-any-any-update113.tar.gz (you should be able to find it in /usr/portage/distfiles after you've attempted to emerge vmware-modules)? Hopefully that'll help us determine what's going on a little better. Thanks... 5:) Good tips. I removed vmware from my overlay and then tried to emerge -uDNvat world: ... done! [nomerge ] app-emulation/vmware-player-2.0.0.45731 [?] [ebuild U ] app-emulation/vmware-modules-1.0.0.16-r1 [1.0.0.16] 459 kB Total: 1 package (1 upgrade), Size of downloads: 459 kB Portage tree and overlays: [0] /usr/portage [?] indicates that the source repository could not be determined I thought the "?" was strange, so I did emerge vmware-player vmware-modules -1 and was successful. Ok, glad you managed to get it sorted. 5:) I'm going to mark this as WORKSFORME, simply to mean that it wasn't a direct issue with the ebuild (and hence wasn't really FIXED). Please do report any more bugs you may find whilst using the modules. Thanks... |