On Thu, Jun 04, 2009 at 01:32:30PM -0700, Mike "Ford" Ditto wrote:
> Well, now that I know how to recover, I feel brave; let me try it
> again, maybe this will give you some clues...
>
> $ BUILD=`uname -v | sed -e "s/snv_//" -e "s/[a-z]//"`
> $ pfexec pkg refresh
> $ pfexec pkg install entire at 0.5.11-0.${BUILD}
> Creating Plan - pkg: pkg:/entire at 0.5.11,5.11-0.86:20080504T125439Z already
> installed
> No updates available for this image.
> $ pfexec pkg install SUNWipkg at 0.5.11-0.${BUILD}
> Creating Plan \ pkg: pkg:/SUNWipkg at 0.5.11,5.11-0.86:20090512T150104Z
> already installed
> Creating Plan | pkg: pkg:/SUNWpython-cherrypy at
> 3.1.0,5.11-0.86:20080905T234838Z already installed
> pkg: pkg:/SUNWpython-mako at 0.2.2,5.11-0.86:20090512T150118Z already
> installed
> pkg: pkg:/SUNWpython-ply at 3.1,5.11-0.86:20090512T150119Z already installed
> pkg: pkg:/SUNWpython-pyopenssl at 0.7,5.11-0.86:20080905T234839Z already
> installed
> pkg: pkg:/SUNWpython24-simplejson at 0.5.11,5.11-0.86:20090512T150128Z
> already installed
> No updates available for this image.
Up until this point, it all makes sense.
> $ pfexec pkg install SUNWinstall-libs
> DOWNLOAD PKGS FILES XFER (MB)
> Completed 20/20 3556/3556 58.44/58.44
>
> PHASE ACTIONS
> Install Phase 1333/6412 Action install failed
> for 'lib/libc.so.1' (pkg:/SUNWcsl):
Here's where it goes crazy. If you're still feeling brave, can you redo
the previous commands, and then run "pkg install -nv SUNWinstall-libs"
instead of the real install? This will tell us exactly what package
versions it intends to install, without actually doing so. The constraints
on your system introduced by entire, coupled with the version of the pkg
command, should have warned you that a new version of libc wasn't possible
to install. Which indicatest that the version it was trying to install was
actually within the constraints. Which is confusing. The output of "pkg
list -avf SUNWcsl" would also be useful (once you've gotten past the
install of the new SUNWipkg, that is).
Thanks,
Danek
