= Challenges =
RocellaThe process of building and troubleshooting packages isn't easy. Any project would encounter errors through the process of completing and making it work. For us, it was all about the finishing product. A finish package could result into completing other packages that depends on it. Just like a matrix map. These packages need other packages in order to work. The most common problem we encountered is dependency issue. Dependency issue are problems that would need another package in order for one package to build. Those packages sometimes need another package to build. This process could go on forever. However, we managed to deal with some and actually got the dependency packages to build, as well as the initial package. Another common error could be that the package does not build on Fedora ARM, therefore, we need to exclude those packages in the spec file so that ARM-KOJI doesn't find the dependency issue. For example: Dependency issuePackage for (libvirt-0.8.2-1.fc13.src.rpm, armv5tel)Root.log error''DEBUG util.py:256: No Package Found for numactl-devel'' OR Package for (ocaml-3.11.2-2.fc13.src.rpm)BuildError: No matching arches were found The little errors could be in the spec file; such as, version error, URL, source URL, etc. The best way to resolve any problem is to push through the packages in the architecture (ARM, or KOJI) as a task. If that task fails it will show errors whether it's build.log, or root.log error. Root.log errors are usually dependency problem. Build.log could be a spec file issue. In those logs you can resolve and find out the problems that the packages are having with the architecture that it's trying to build on.
= Results =
