by Glynn Foster
Published June 2014
Oracle Solaris 11 uses a new network-based packaging system called the Image Packaging System to manage the complete software lifecycle—including the installation, upgrade, and removal of software packages. This article summarizes how to interpret package versioning using Oracle Solaris 11 so you can better understand the state of software installed on your systems.
Oracle Solaris 11 uses package constraints, called incorporations, to control different versions of software installed on the system. This ensures that the state of the system is consistent and, more importantly, that a set of package versions has been tested by Oracle and that the package versions work well together.
A package called
entire is the primary incorporation package that determines the overall state of a system. We can take a look at the version of the
entire incorporation package using the
pkg info command, as shown in Listing 1:
root@solaris:~# pkg info entire Name: entire Summary: entire incorporation including Support Repository Update (Oracle Solaris 220.127.116.11.0). Description: This package constrains system package versions to the same build. WARNING: Proper system update and correct package selection depend on the presence of this incorporation. Removing this package will result in an unsupported system. For more information see https://support.oracle.com/CSP/main/article ?cmd=show&type=NOT&doctype=REFERENCE&id=1501435.1. Category: Meta Packages/Incorporations State: Installed Publisher: solaris Version: 0.5.11 (Oracle Solaris 18.104.22.168.0) Build Release: 5.11 Branch: 0.175.1.20.0.5.0 Packaging Date: June 13, 2014 04:23:23 PM Size: 5.46 kB FMRI: pkg://firstname.lastname@example.org,5.11-0.175.1.20.0.5.0:20140613T162323Z
From the output in Listing 1, we can see that the version installed on this system is Oracle Solaris 22.214.171.124.0. What this translates to is that it is a system based on Oracle Solaris 11.1 that has been updated with a Support Repository Update (SRU). SRUs are monthly updates Oracle provides to supported customers, which fix bugs, provide security alerts, or provide support for new hardware.
The package Fault Management Resource Identifier (FMRI) is a unique string that describes a package version. The package FMRI for the
entire package is
The FMRI can be generalized into the elements shown in Listing 2:
If we use the generalized form shown in Listing 2 and break down the
entire package FMRI, we get the elements shown in Table 1.
| || ||Publisher|
| || ||Package name|
| || ||Component version|
| || ||Release version, for example, Oracle Solaris 11|
| || ||Branch version|
| || ||Package time stamp (ISO 8601 UTC format)|
We can also further break down the
0.175.1.20.0.5.0 for the
entire package) as shown in Listing 3:
Using the form in Listing 3 with
entire, we get the elements shown in Table 2:
| || ||Build number of development gate|
| || ||Update version, for example, Oracle Solaris 11.1|
| || ||SRU version|
| || ||Reserved (not currently used)|
| || ||Build number of SRU|
| || ||Nightly build number|
So in summary, this system is installed with Oracle Solaris 11.1 SRU 20.5.
Interim Diagnostic Reliefs (IDRs) are essentially package updates that help diagnose customer issues or provide temporary relief for a problem until a formal package update has been issued. Usually they are applied by a single customer and made available only through a standalone package archive (as indicated by a
.p5p file name extension). In the event that an IDR fix is applied, a package version might have two additional elements included in the
branch_version, as follows:
You can see whether any IDRs have been applied to a system by using the
pkg list command, as follows:
root@solaris:~# pkg list idr* NAME (PUBLISHER) VERSION IFO idr104 1 i--
Assuming an IDR has been formally fixed and released as part of a subsequent SRU release, when you do a
pkg update to get to this new SRU, the IDR will automatically be backed out.
More information about managing Oracle Solaris 11 software can be found in the following resources on My Oracle Support:
And here are some additional Oracle Solaris resources:
Glynn Foster is a principal product manager for Oracle Solaris. He is responsible for a number of technology areas including OpenStack, the Oracle Solaris Image Packaging System, installation, and configuration management.
|Revision 1.0, 06/25/2014|