Adam Conrad wrote:
> Adam D wrote:
>> Unpacking vmware-player (from vmware-player_1.0.1-4_amd64.deb) ...
>> license could not be presented; aborting
>> dpkg: error processing vmware-player_1.0.1-4_amd64.deb (--install):
>> subprocess pre-installation script returned error exit status 2
>
>
> Run "sudo dpkg-reconfigure debconf" and pick a frontend other than
> noninteractive. vmware refuses to install if it can't use debconf to
> get you to agree to the EULA, and it can't do that if you aren't
> allowing debconf to talk to you.
>
This make some sense as to why I was not getting any package info when installing. I have had it set properly on all my PPC and intel. This is my first AMD box and had to jump the gun a couple of weeks before the official release of Dapper. fixed :)
> (If you did a ubiquity install from the livecd in the past few months,
> this isn't really your fault, it was a bug in the live install that was
> leaving the frontend at noninteractive... This was fixed before release,
> so fresh installs don't have this problem)
>
> ... Adam
>
>
>
>
Ok.. we are getting a bit closer to the goal but there still seams to be some other issues relating to the vmplayer. Since I compiled my own kernel I will have to make a kernel modules for vmmod however after installing the vmware-player-kernel-source and ran make-kpkg modules_image --append-to-version .amd64-ws1.1 so I can have a deb package of the module to install.. BUT!! LOL That does not work.
<snip>
make[1]: Entering directory `/usr/src/modules/vmware-player-kernel'
/usr/bin/make -w -f debian/rules kdist_clean kdist_config binary-modules
make[2]: Entering directory `/usr/src/modules/vmware-player-kernel'
echo '# NOTE: THIS FILE IS AUTO-GENERATED FROM control.modules.in.in' > \
debian/control.modules.in
sed -e 's/@@KVERSION@@/2.6.15/g' \
-e 's/@@ABIVER@@/2.6.15-23/g' \
debian/control.modules.in.in >> debian/control.modules.in
if [ "" ]; then \
echo '# NOTE: THIS FILE IS AUTO-GENERATED FROM control.in' > \
debian/control; \
sed -e 's/@@KVERSION@@/2.6.15/g' \
-e 's/@@ABIVER@@/2.6.15-23/g' \
debian/control.in >> debian/control ; \
fi
dh_testdir
dh_testdir: cannot read debian/control: No such file or directory
make[2]: *** [clean] Error 1
make[2]: Leaving directory `/usr/src/modules/vmware-player-kernel'
make[1]: *** [kdist_build] Error 2
make[1]: Leaving directory `/usr/src/modules/vmware-player-kernel'
Module /usr/src/modules/vmware-player-kernel failed.
Hit return to Continue
This can't be a kernel version mismatch since I am using a newer kernel that the 2.6.15. (Mine is 2.6.16.14.)
Any clues what debian/control would be referred as?
-Adam