Thanks Dan. Alas, I get stuck here:
root@massive02-b:~# pkg -R /mnt update Creating Plan - pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151012 Release Signing Certificate/[email protected] could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority The package involved is:pkg://omnios/locale/[email protected],5.11-0.151012:20140913T033547Z Ian On Wed, Dec 10, 2014 at 10:55 AM, Dan McDonald <[email protected]> wrote: > >> On Dec 10, 2014, at 1:42 PM, Ian Kaufman <[email protected]> wrote: >> >> It looks like this system is in some weird state where there are >> packages from 151006 and 151008. > > Oh my. > > Yes, you've been bitten by the pkg upgrade problems between 006 and 008. > This was before my time here, so I'm not sure how best to extricate yourself > from things. > > If you want, you can jump forward to the current stable release (r151012). > If you want to try that, and you don't have zones, do this: > > > 1.) Create a new BE, call it 012 for this example: beadm create 012 > > 2.) Mount the BE on /mnt: beadm mount 012 /mnt > > 3.) Change the publisher on the new BE to point to r151012's repo: > pkg -R /mnt set-publisher -G http://pkg.omniti.com/omnios/release/ -g > http://pkg.omniti.com/omnios/r151012/ omnios > > 4.) Apply the update to the new BE: pkg -R /mnt update > > 5.) Unmount the BE: beadm umount 012 > > 6.) Either reboot and use the GRUB menu to try out the new 012 BE, or "beadm > activate 012" to make it go there on the next reboot. > > > Dan > -- Ian Kaufman Research Systems Administrator UC San Diego, Jacobs School of Engineering ikaufman AT ucsd DOT edu _______________________________________________ OmniOS-discuss mailing list [email protected] http://lists.omniti.com/mailman/listinfo/omnios-discuss
