What's the significance of /var/sadm/install/gz-only-packages?
Does pkgadd update the file based on some criteria? or who/what/when does it 
get updated?

The reason I ask is, reinstall of our SVR4 packages using pkgadd is failing on 
multiple machines in our environment (runnins Solaris 10 FCS + global zone 
only) when used with the following admin file:
------------------------------------------------
mail=
instance=overwrite
partial=nocheck
runlevel=nocheck
idepend=nocheck
rdepend=nocheck
space=nocheck
setuid=nocheck
conflict=nocheck
action=nocheck
basedir=default
--------------------------------------------------

It's failing with:

pkgadd: ERROR: The package <SAIpkg1> is currently installed on the system in 
the global zone. To install the new instance of this package in the global zone 
only, you must specify the -G option. To install the new instance of this 
package in all zones you must first remove the existing instance of this 
package from the global zone first (via pkgrm) and then install the new 
instance of this package in all zones.
pkgadd: ERROR: package <SAIpkg1> cannot be installed on this system/zone
 

SAIpkg1 and a bunch of our (SAIpkg2....SAIpkgN) packages exist in 
/var/sadm/install/gz-only-packages. This file contains only a subset of our 
packages. I was wondering who/why they got listed there. None of our packages 
are zone aware i.e. they do not contain SUNW_PKG_*ZONE* variables.

I can reinstall our packages in the following ways:

a) pkgadd -G seems to install the package but it would require us to make 
changes in a lot of scripts.

b) remove SAIpkg1 from /var/sadm/install/gz-only-packages

c) maybe pkgrm SAIpkg1 and reinstall using pkgdd, have not tested this because 
it's not an option for us.


TIA
-- prasad
 
 
This message posted from opensolaris.org

Reply via email to