News, tips, partners, and perspectives for the Oracle Solaris operating system
-
Technologies
June 19, 2017
Minimal Content for a Local IPS Package Repository
If you maintain a local IPS package repository, that repository must have at least the following content to support upgrades to new Oracle Solaris releases:
- The repository content for the currently installed GA release
- The repository content for the currently installed SRU, if any
- The repository content for the GA release to which you want to update
- The repository content for the SRU to which you want to update, if any
- If the currently installed GA release is more than one release behind the release to which you want to update, then your local repository must also contain the repository content for each intervening GA release.
- If the currently installed release is Oracle Solaris 11 11/11 with no SRU or an SRU lower than SRU10, then your local repository must also contain the repository content for Oracle Solaris 11 11/11 SRU10.
Examples
To upgrade from Oracle Solaris 11.3 SRU16 to Oracle Solaris 11.3 SRU19, your local IPS package repository must include the following repository content:
- Oracle Solaris 11.3
- Oracle Solaris 11.3 SRU16
- Oracle Solaris 11.3 SRU19
To upgrade from Oracle Solaris 11 11/11 SRU7.5 to Oracle Solaris 11.3 SRU19, your local IPS package repository must include the following repository content:
- Oracle Solaris 11 11/11
- Oracle Solaris 11 11/11 SRU7.5
- Oracle Solaris 11 11/11 SRU10.5
- Oracle Solaris 11.1
- Oracle Solaris 11.2
- Oracle Solaris 11.3
- Oracle Solaris 11.3 SRU19
Download Repositories
You can get this content to add to your local repository by downloading repository files from any of the following locations:
- Oracle Technology Network (OTN)
- My Oracle Support (MOS)
- Oracle Software Delivery Cloud (OSDC)
For example, on MOS see Where to download Oracle Solaris ISO images and Update Releases (Doc ID 1277964.1) for GA repositories. The first link under each release section is a link to download the IPS repository file for that release.
For SRU repositories, see the following on MOS:
- Oracle Solaris 11.3 SRU repositories
- Oracle Solaris 11.2 SRU repositories
- Oracle Solaris 11.1 SRU repositories
- Oracle Solaris 11 11/11 SRU repositories. See SRU10.5 in the list.
These repository files come with instructions and an installation script. Specify your existing local repository as the destination (-d) to add the new content to your local repository.
For more information about creating a local repository, see:
- Creating Package Repositories
- “How to Minimize the Size of Your Oracle Solaris IPS Package Repository”
Upgrade
When you perform your upgrade, specify the result you want and use the preview option (-n) to see whether you will get what you specified. For example:
$ pkg update -nv entire@0.5.11,5.11-0.175.3.19 '*'
In some cases, upgrade requires multiple steps because a subset of software must be updated before other software can be updated. If you are not able to upgrade to your desired end state in one step, upgrade as far as you can, reboot to the new BE, and upgrade again. Release notes provide information about whether a multi-step upgrade will be required.
Join the discussion
-
Could you please explain the reason why the solaris instance requires access to the repositories for the currently installed GA and SRU during update? Thanx.
-
During the build process for the Oracle Solaris packages there is a dependency check to ensure that when a particular package is installed any dependencies it needs are also installed, thus preventing a broken installation and a one step install. Now as time goes on it is possible that new dependencies are needed and these dependencies might be satisfied by either the original GA of the product (because the new dependency has not had any bug fixes) or by the SRU (because the new dependency has had bug fixes). Thus in order to ensure there will be no errors we state the need for having the GA product and currently installed SRU in the repository.