[OmniOS-discuss] Problem upgrading to r151008

Chris Nehren cnehren+omnios-discuss at omniti.com
Fri Dec 6 15:50:11 UTC 2013


On Fri, Dec 06, 2013 at 15:30:29 +0000, Andy wrote:
> 
> On Fri, 6 Dec 2013, Chris Nehren wrote:
> 
> ; On Fri, Dec 06, 2013 at 09:48:49 -0500, Chris Nehren wrote:
> ; > On Fri, Dec 06, 2013 at 10:35:44 +0000, Andy wrote:
> ; > >
> ; > > Hi,
> ; > >
> ; > > pickle# (11) pkg list runtime/perl-64
> ; > > pkg list: no packages matching 'runtime/perl-64' installed
> ; > >
> ; > > pickle# (14) pkg update --be-name=r151008e
> ; > >             Packages to update:  96
> ; >                                    ^^
> ; >
> ; > There should be far more packages than this. This means that
> ; > something is being held back from being upgraded, which means...
> ; >
> ; > > ld.so.1: zsh: fatal: libc.so.1: version 'ILLUMOS_0.6' not found (required
> ; > > by file /usr/bin/zsh)
> ; > > ld.so.1: zsh: fatal: libc.so.1: open failed: No such file or directory
> ; >
> ; > that you get this. I had this issue on my hetzner box as well.
> ; > Something that you've installed might be holding back other
> ; > packages.
> ;
> ; Following up on this, could we see the list of packages you have
> ; installed right now, your configured publishers, and the output
> ; of `pkg update -nv --be-name=r151008 entire at 11-0.151008
> ; omnios-userland illumos-gate osnet-incorporation`? This'll help
> ; us more usefully troubleshoot what's going on.
> 
> Pkg can't find 'omnios-userland' but the full list of installed
> packages is below. The lack of the userland incorporation might be the
> problem. Would the output of 'pkg update -nv' without the userland
> incorporation be useful?
> 
> The output does include:
> 
>  No suitable version of required package pkg://omnios/incorporation/jeos/omnios-userland@11,5.11-0.151008:20131205T191259Z found:

You'll want to install
incorporation/jeos/omnios-userland at 11,5.11-0.151006:20131030T205312Z
as I suggested to John and try again. There was an issue with
omnios-userland that we're going to be fixing soon.

-- 
Chris Nehren
Site Reliability Engineer, OmniTI


More information about the OmniOS-discuss mailing list