vmware-player broken after upgrade

Asked by Wim van der Meer

I am running Ubuntu Dapper.

Until now I was still using vmware with the 2.6.15-27 kernel because the vmware-player-kernel-modules-2.6.15-28 package was not available yet.

Now vmware-player-kernel-modules requires the vmware-player-kernel-modules-2.6.15-28 package, but this package is not available in the repository, so the install breaks. Is there anybody who knows what is going on? Is there a way to install vmware-player so it will use the vmware-player-kernel-modules-2.6.15-27 package?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu vmware-player-kernel-2.6.15 Edit question
Assignee:
No assignee Edit question
Solved by:
Wim van der Meer
Solved:
Last query:
Last reply:
Revision history for this message
Maurizio Moriconi (bugman) said :
#1

Link to an existing bug (#66419)

Revision history for this message
Wim van der Meer (wim-zaf) said :
#2

I believe that this bug descibes a different problem, because the modules that vmware player depends upon were in the repository at the time of this bug report.

Bug #66419 describes the problem that the vmware-player-kernel-modules for the 2.6.15-27 kernel image was not available. This module is available now, but now vmware-player 1.0.1-4 depends on vmware-player-kernel-modules, which depends on vmware-player-kernel-modules-2.6.15-28, but this package is not in the repository.

So currently it is impossible to install vmware-player, becuase one of the packages it depends upon is not in the repository.

(Actually I found a workaround by installing an older version of vmware-player-kernel-modules (version 2.6.15.10-6) which depends on vmware-player-kernel-modules-2.6.15-23 (this package is in the repository), then installing vmware-player-kernel-modules-2.6.15-27 as well, and then installing vmware-player, which I am then able to run with a 1.6.15-27 kernel.)

Revision history for this message
Maurizio Moriconi (bugman) said :
#3

Ok try to fill another bug.

BugMaN

Revision history for this message
Best Wim van der Meer (wim-zaf) said :
#4

OK, just did that. Thanks. I'll close this ticket.