How did you determine these are missing?
I created a SLES 11 SP4 Pool catalog and the rpms match the channel
For Example, these are the java rpm's in the channel: https://nu.novell.com/repo/$RCE/SLES11-SP4-Pool/sle-11-x86_64/rpm/x86_64/
And this is what is in my catalog:
Description of Required Channels
A subset of the unpacked installation media, it only contains those packages that are considered to be the core of SPx (approximately 30% of the package total). The SP repositories only contain packages specific to a SP and its themes (for example, hardware enablement). Exists only in SP2.
Maintenance updates to packages in the corresponding Core or Pool repository.
Containing all binary RPMs from the installation media, plus pattern information and support status metadata.
the 'Pool' repo would not seem to include updates... ?
The pool option should include updates as per documentation.
Is that what suse says? That snippet is from suse’s website. Where do you see that ‘pool’ includes the os updates ?
Pool: All the updates until the specified OS level. For an OS-Architecture combination, if you require the updates from an OS level to the next or the latest OS level, you must use the Pool option. For example, you must use the Pool option if you want to bring your target from SUSE Linux Enterprise 10 SP1 to SUSE Linux Enterprise 10 SP4.
so first of all - we are not suse - so suse is where you should be looking for clarity on what their repos are for.
so what about the description makes you think that pool will get updates on top of whatever SP version it is ?
New from SLE?10-SP2. This is an rpm-md (xml-based rpm metadata) repository containing all packages from the respective SP installation medium. The intention of this catalog is to minimize the need for multiple installation source and update repositories for clients that have been upgraded to a newer service pack one or more times.
Since -Pool exists to serve as installation source (only), it does not contain any source packages. The source packages for the shipping product corresponding to the -Pool, only exist on the product medium (e.g. SLES10-SP2 DVD2).
There is generally no need to both have the -Pool repository and the corresponding installation source (medium) enabled/defined. While the installation source will be picked first in case -Pool is also available, the former can be disabled/deleted.
As an example, if a server has been originally installed from the SLES 10 medium, then online updated to SP1 and later to SP2, then it could potentially have the following repositories available :
- SLES 10 installation source
- SLES10SP1-Online catalog
- SLES10SP2-Online catalog
- SLES10SP2-Updates catalog
In case e.g. the SLE?10 SP2 installation source is not available or desired, the SLE?10-SP2-Pool can be used as an alternative and eliminate the need for first three repositories above (SLES 10 installation source, SLES10SP1-Online and SLES10SP2-Online). This way it is possible to use SMT to provide both software update and installation source repositories.
NOTE : The pool repositories can not be used as installation sources during the installation process of machines. As a side note, an SMT server can also be configured to host installation repositories from the YaST Installation Server module.
thanks for sharing that info. Do you know the web URL to which Bladelogic server connects to download the patches for SUSE