| | 1 | = QWG Templates Frequently Asked Questions = |
| | 2 | [[TracNav]] |
| | 3 | |
| | 4 | [[TOC(inline)]] |
| | 5 | |
| | 6 | |
| | 7 | == RPM Repository Configuration == |
| | 8 | |
| | 9 | === RPM present but configuration complaining it is missing === |
| | 10 | |
| | 11 | During compilation, a check is made all the RPMs included in the configuration are present in a RPM repository. This check is not done by looking directly at the directory contents but using a PAN template associated with the RPM repository and representing its contents. This template is generally sitting in a `repository/` subdirectory in your site configuration. |
| | 12 | |
| | 13 | To update these templates with SCDB to reflect the current contents of the repositories, you need to run the following command: |
| | 14 | {{{ |
| | 15 | external/ant/bin/ant update.rep.templates |
| | 16 | }}} |
| | 17 | |
| | 18 | If the RPM you are looking for doesn't show up in the template, it may suggest a misconfiguration of the repository template. You need to ensure the first lines (which are comments) reflect your local configuration. If this is not the case, fix the configuration, delete every line after the initial comments and re-run the command above. |
| | 19 | |
| | 20 | === RPM present but installation failing to find it === |
| | 21 | |
| | 22 | When configuration is compiled, a check is made all RPMs needed are present in a RPM repository to ensure there will be no failure at deployment time so this error should not happen. Unfortunatly there is one exception when the configuration uses several architecture of the same version of a package. In this particular case, you need to ensure that the RPMs for all architectures are sitting in the same RPM repository else you will get an error at installation time despite the compilation succeeded. |
| | 23 | |
| | 24 | This happens because of a SPMA schema restriction where all the architectures of the same package version share the same repository information in the node profile. As a result, the repository information set in the configuration for the package is the repository where the package for the last architecture processed was found and will not allow to download the others. |
| | 25 | |
| | 26 | This is mainly a problem for packages provided by the OS. Because of a SPMA restriction, if you need to add some `i386` RPMs from `i386` distribution to the `x86_64` distribution, '''it is a requirement''' to put them in the same repository/directory as the other RPMs provided by the distribution. |
| | 27 | |
| | 28 | We plan to address this issue in the future but this is quite a major change to a critical component... |
