[OpenIndiana-discuss] Some advice sought, since: Still not QUITE resolved: Re: Upgraded to OI148: now "entire" is not installed!

[Hans J. Albertsson]

I created a new BE, OIentire
beadm mount OIentire /a

Then I performed a sequence of "pkg -R /a install -v entire" and " pkg 
-R /a uninstall -r -v <packages identified as FAIL reasons for entire 
installation>" actions.
These necessitated some recursive uninstalls of incorporation packages, 
like for l10n and gnome-l10n, and a few other incorporations.

Finally, installing entire from OI b148 onto the new BE, OIentire, went 
thru unhindered.

The uninstalls were too many, it seems, since X among others refuses to 
to start. I had to get on the console of that remote server and reboot 
the current working but formally ailing BE.

So I need to go thru all the packages not in the new BE and replace them 
with their correct versions, I think. Right???

What would be the easiest way? Is there some way to say to pkg or 
something: "make this BE as close to that other BE as possible", or 
"tell me a minimum package list to install"?

I just don't yet understand IPS well enough, and there are so many bits 
to learn for that, so

Please Help Me...
> Message: 1
> Date: Mon, 31 Jan 2011 12:35:17 +0000 (UTC)
> From: Lou Picciano<loupicciano at comcast.net>
> To: Discussion list for OpenIndiana
> 	<openindiana-discuss at openindiana.org>
> Subject: Re: [OpenIndiana-discuss] Upgraded to OI148: now "entire" is
> 	not	installed!
> Message-ID:
> 	<1125062867.2240694.1296477317212.JavaMail.root at sz0093a.westchester.pa.mail.comcast.net>
> 	
> Content-Type: text/plain; charset=utf-8
>
> Hans,
>
>
> I can commiserate a bit; had exactly the same problem you're seeing, and wasn't really aware of the extent of it. Was wondering why certain binaries seemed to be wrong versions, and filesystem wasn't all it should have been...
>
>
>
>
> I did have the idea of beadm-creating a clone, mounted on /a
> then pkg -R /a install -f -v entire...., just to see, but if I know more
> when I try that, I'll get further.
>
>
> Geniuses here led me to essentially your own conclusion; I ultimately installed the entire@ consolidation on a new BE. All now working great!
>
>
> Lou Picciano
>
> ----- Original Message -----
> From: "Hans J. Albertsson"<hans.j.albertsson at branneriet.se>
> To: openindiana-discuss at openindiana.org
> Sent: Monday, January 31, 2011 4:48:10 AM
> Subject: [OpenIndiana-discuss] Upgraded to OI148: now "entire" is not installed!
>
> I upgraded (using pkg image-update) to OI148 (Described in a previous
> email) from OSol b134.
>
> When I now check, the "entire" package is not installed?
>
> Is this OK, or should I
>
> A: Worry?
>
> B: Do something about it? If so, PLEASE tell me what! In some detail,
> please!
>
> Note, in spite of having been at Sun for well over 21 years, I was never
> involved in the recent development of things like Open Solaris in a
> technical way.
> My last years were spent managing unwilling hordes, and then managing a
> lab. I could get a new machine out of the box, into a rack and globally
> accessible in under 2 minutes, but that's the extent of the tech
> challenges of lab management. I'm comfortable with ZFS, too. ZFS hits a
> lab guy every day. But that's it. So please be patient with me and
> advise me.
>
> I did have the idea of beadm-creating a clone, mounted on /a
> then pkg -R /a install -f -v entire...., just to see, but if I know more
> when I try that, I'll get further.
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss