Mark Bennett wrote:
> If it was just the missing entire package, then why did I manage to 
> successfully install about eight packages before it failed ?

Luck, package constraints, take your pick.

But I'm fairly certain that is the issue at this point.

More specifically, the crash you saw (I believe) is because newer 
versions of packages are 'multi-variant', that is they support SPARC and 
x86.  As a result of that change, older package clients can't parse 
newer package code.

So, my guess is that pkg(1) was trying to install a version of 
SUNWspnego for something newer than the build you are running, and 
because you don't have the "entire" package to constrain the system, it 
picked it up.

Either way, you need to have an incorporation package such as 'entire' 
installed to properly constrain the package versions on your system. 
Installing 'entire' will not install a bunch of other packages on your 
system, so don't worry about that.

But without a package such as 'entire' installed, you won't be able to 
properly upgrade your system using image-update, and 'install' may not 
work properly either.

> Is there any way to recover from a situation like this, other than start from 
> scratch again?

Install the 'entire' package now, and then you can install SUNWspnego.

In either case, you'll want to install the newest version of SUNWipkg 
which should also resolve the traceback you saw, if it is available for 
the build you are using.

Cheers,
-- 
Shawn Walker

Reply via email to