For this lab we were given the task of using Mock and Koji to test and resolve the dependencies from our RPM that we created in the previous lab.
Mock is a vital tool that’s used for resolving dependency requirements for packages. Mock creates a sandbox environment where it isolates the RPM. That way the RPM can be tested with no interference from any outside packages. This tool is essential in the RPM build process.
Koji is similar to mock with a few more features. Koji has full web interface where users can see their package’s current status and whether it passed or failed within the build system.
When installing Koji a certificate is generated making Koji extremely secure. Only Fedora packagers are granted the certificate. If you were to try to manually generate a certificate then you’d have some difficulty in doing so. Below is a screen shot of what the Koji interface looks like.
koji build dist-f15 --scratch yourSRPM
After this command has been entered you will be notified if the build is either successful or unsuccessful. Once this build is successful then you can loin to Koji to view the state of your build. Below is a screenshot of my build in Koji.
At first using these tools was very difficult to understand the process of how everything worked. It took a lot of troubleshooting and error checking to understand the concept of Mock. I learned that the Spec file has to have all of the required dependencies order for the build to work.
Koji also took some time to understand as well. At first I had problems importing my certificate but after generating a new one it imported successfully. What I like about Koji is that its a practical tool that you can check in real time what the status of your package is. I find Koji very interesting and I would like to learn more about it in the near future.