| 1 |
On Thu, 13 Nov 2008 09:38:05 +0200, Dirk Uys wrote: |
| 2 |
|
| 3 |
> I'm running a stable gentoo installation and getting a block on |
| 4 |
> vmware-player: [ebuild U ] app-emulation/vmware-player-2.5.0.118166 |
| 5 |
> [2.0.5.109488] 61,559 kB |
| 6 |
> [ebuild N ] app-emulation/vmware-modules-1.0.0.23 478 kB |
| 7 |
> [blocks B ] >=app-emulation/vmware-modules-1.0.0.23 (is blocking |
| 8 |
> app-emulation/vmware-player-2.0.5.109488) |
| 9 |
> |
| 10 |
> I have the following in /etc/package.keyworkds/vmware-player |
| 11 |
> |
| 12 |
> <file /etc/package.keyworkds/vmware-player> |
| 13 |
> app-emulation/vmware-player ~amd64 |
| 14 |
> app-emulation/vmware-modules ~amd64 |
| 15 |
> dev-cpp/libsexymm ~amd64 |
| 16 |
> x11-libs/libview ~amd64 |
| 17 |
> </file> |
| 18 |
> |
| 19 |
> Is this just a consequence of mixing stable and unstable, or is there |
| 20 |
> a way I can get around this? |
| 21 |
|
| 22 |
Each vmware package depends on a specific modules version. In order to |
| 23 |
update vmware-player, you must first update vmware-modules,but that |
| 24 |
version is blocked by the existing player. There are two alternatives |
| 25 |
|
| 26 |
Unmerge vmware-player then reemerge it. |
| 27 |
Upgrade to the latest portage, which handles these blocks for you. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Neil Bothwick |
| 32 |
|
| 33 |
BBS: (n.) a system for connecting computers and exchanging gossip, |
| 34 |
facts, and uninformed speculation under false names. |
Archives