On 04/01/10 13:52, Bart Smaalders wrote:
> On 04/01/10 10:15, Gordon Ross wrote:
>> Have a look at these dependencies for VirtualBox in "extra":
>>
>> Name Dependency Installed Version
>> SUNWcs 0.5.11 (Build 5.11-0.101) 0.5.11 (Build 5.11-0.134)
>> SUNWckr 0.5.11 (Build 5.11-0.101) (not installed)
>> SUNWcsl 0.5.11 (Build 5.11-0.101) 0.5.11 (Build 5.11-0.133)
>> SUNWlibms 0.5.11 (Build 5.11-0.101.6) 0.5.11 (Build 5.11-0.133)
>> SUNWPython25 2.5 (Build 5.11-0.101) (not installed)
>> SUNWpng 0.5.11 (Build 5.11-0.101) (not installed)
>> SUNWfontconfig 2.5.0 (Build 5.11-0.101) 2.7.3 (Build
>> 5.11-0.133)
>> SUNWfreetype2 2.3.7 (Build 5.11-0.101) 2.3.9 (Build
>> 5.11-0.133)
>> SUNWgccruntime 3.4.3 (Build 5.11-0.101) (not installed)
>> SUNWzlib 1.2.3 (Build 5.11-0.101) 1.2.3 (Build 5.11-0.133)
>> SUNWPython 2.4.4 (Build 5.11-0.101) 2.4.6 (Build 5.11-0.133)
>> SUNWusb 0.5.11 (Build 5.11-0.101) (not installed)
>> SUNWxwrtl 0.5.11 (Build 5.11-0.101) 0.5.11 (Build 5.11-0.133)
>> virtualbox/kernel 3.1.0 (Build 5.11-0.101) (not installed)
>>
>> When I tried installing it, the package manager started downloading
>> SUNWPython25 etc. along with 95 MB worth of dependencies.
>>
>
> The likelyhood is that python2.5 isn't on your system by default,
> so if VirtualBox needs it you'll get it....
As Bart suggests, the behavior you describe seems correct for the
information you provided. You describe explicit dependencies on several
packages that you don't have installed: SUNWckr, SUNWPython25, SUNWpng,
SUNWgccruntime, SUNWusb, and virtualbox/kernel.
> I'm running snv_134. Don't the renamed packages in 133+ satisfy the
> above dependencies? Seems like something may be broken. Not sure what.
Most of the missing packages listed fall into the category you describe:
Old name New name
-------------- ----------------------------
SUNWckr system/kernel
SUNWPython25 runtime/python-25
SUNWpng image/library/libpng
SUNWgccruntime system/library/gcc-3-runtime
SUNWusb driver/usb
Except for virtualbox/kernel, which is obsolete as of 3.1.0, and that
dependency is optional anyway.
It doesn't really mean much that the old package names are not
installed; pkg(1) will always uninstall the old (renamed) packages when
it can. Since you don't say which of the new names above you might be
missing, it's hard to say what's being downloaded on your behalf. Bart
suggested Python 2.5, and that seems quite likely.
> I just went back to installing the SVR4-style package from
> virtualbox.org for now, but it would be greate if the new
> package manager could handle the updates for me. Ideas?
The new package manager was handling the updates for you, but you didn't
trust it.
By going back to the old SVr4 packages, you're relying on the depend
files delivered with the SVr4 SUNWvbox package, and on the legacy
actions delivered as part of the IPS packages.
That should all work correctly, assuming it's consistent with the IPS
dependencies. And if that's the case, and you're really missing
something you need, then downloading and attempting to install the SVr4
packages should fail due to missing dependencies. Since you implied
that that's not the case, and the SVr4 download "just worked," it would
be interesting to know what IPS thinks you need, that SVr4 doesn't.
What does "pkginfo -l SUNWPython25 SUNWPython25-devel" report? And "pkg
info -l SUNWPython25 python-25"?
Or, as Alan asked:
> What do you see if you run the CLI test-only command "pfexec pkg install
> -nv virtualbox" ?
--Mark
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
