Why do I get asked to trust a key when adding the Package Hub repository?
The package repository behind Package Hub is signed with a key that is not "known" by SUSE Linux Enterprise Server by default. Therefore the installer needs to ask the user if they signature should be trusted.
Of course SUSE is aware of the expected public key associated with the Package Hub repository, but because of limitations in the current repository handling, we are not able to validate the signature automatically. We plan to address this in the future.
See Package Signatures for more information.
Can I call on SUSE customer support for help with the Package Hub packages?
The packages provided by the Package Hub do not come with commercial support from SUSE. While we can support you enabling the Package Hub repository itself, as well as help with installation or deployment of the rpm packages, we do not provide any support, assistance or guarantees with regard to the software provided by the packages.
Briefly, what is supported by SUSE:
For more details see SUSE Package Hub Support page.
While there is no commercial support from SUSE, can I file a bugreport ?
Yes! Since the packages in SUSE Package Hub are community maintained your feedback is always welcome. Feel free to open a bugreport at SUSE Bugzilla for Package Hub related issues.The bugreport might contain:
I often hear the term "openSUSE Backports" in the context of SUSE Package Hub. What is openSUSE Backports?
openSUSE Backports (or openSUSE:Backports) is the community project maintaining the packages that feed into SUSE Package Hub. These packages are built using the openSUSE Build Service a publically hosted instance of the Open Build Service. The packages are essentially copies of packages from openSUSE distributions built for use with SUSE Linux Enterprise products. Since the Enterprise code base is older than the openSUSE Tumbleweed base that these packages originate from, the builds are often called backports - hence the name openSUSE Backports.
What is the SLE-Module-PackageHub-Subpackages-Module repository?
The SLE-Module-PackageHub-Subpackages-Module repository is a sub-repository of the Package Hub module that provides extra packages required to fulfill dependencies of the core Package Hub packages.
#Background The way software is maintained for SUSE Linux Enterprise products, a single source tree results in multiple binary rpm packages. Typical split is between runtime binaries, dynamic libraries, documentation, and files only needed for development. For large / complex software, the packages may also be split into further functional groups. With SUSE Linux Enterprise products, it's not uncommon that only a subset of those multiple binary rpms is delivered as part of the product. Only those parts required for the supported functionality are product delivered. Note: All sub-packages are built; only a subset is published.
#Enter SUSE Package Hub Some of the community maintained packages that make up SUSE Package Hub have runtime dependencies on sub-packages that are not published as part of the generally supported SUSE Linux Enterprise product. To satisfy those dependencies, we published those extra packages as "unsupported" packages in the Package Hub channel within the PackageHub-Subpackages repository.
NOTE | The PackageHub-Subpackages repository is only found in Package Hub 15, 15 SP1, 15 SP2 and 15 SP3. It is not part of Package Hub 12 and may be removed in future releases. The PackageHub channels are complex and subject to change. Therefore it's recommended to always enable the Package Hub module using SUSEConnect or YaST to ensure the proper repository setup is achieved.