1
edit
Changes
no edit summary
<!-- Change this to DONE when you're done. -->
This page status is: '''DRAFTDONE'''.
= Title =
= Challenges =
The 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 mapfamily tree. These packages need other packages in order for it 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 dependency packages sometimes tend to 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 issue<br>
<br>
Package for (ocaml-3.11.2-2.fc13.src.rpm)<br>
''BuildError: No matching arches were found''<br>
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.
<center>[[File:dependencytree.jpg]]</center>
= Results =
Overall, we have all tried to accomplish the task of our build packages to get pushed to the Fedora 13 updates. We had at least finished one or more packages and feel that we helped out even just a tad bit with the updates. Personally, I had fun doing these even though it got overwhelming. Chris and Paul helped a lot through these times and we do appreciate their help.It was exciting when we did see the check mark near our Packages.We feel happy about helping out and are still continuing to build to get our 0.3 done in a beneficial way to help out the Fedora community. <u>'''Packages Pushed to Fedora 13 Updates:'''</u><br><br>'''Chantell McIntosh:'''<br>• Mrpt-0.9.0-0.2.fc13.src.rpm<br><br>'''Rocella Jimenez:'''<br>• ScientificPython-2.8-12.fc13.src.rpm<br>• pstoedit-3.45-10.fc13.src.rpm<br>• netcdf-4.1.1-3.1.fc13.src.rpm<!br>• totem-pl-parser-2.30.3-1.fc13.src.rpm<br>• gstreamer-0.10.30-1.fc13.src.rpm<br><br>'''MJ Corsame:'''<br>• padevchooser-0.9.4- Results / 0.11.svn20070925.fc13.src.rpm<br><br>'''Andrew Parda:'''<br>• graphviz-2.26.3 status of the project -2.fc13.src.rpm<br>• glom-1.14.1-1.fc13.src.rpm<br>• globus-xio-gsi-driver-0.6-5.fc13.src.rpm<br>Chantell<br>'''Status 0.3:'''<br>Still working on finishing up the packages that we didn't get to finished and get them pushed as soon as possible.
= Links =
* http://zenit.senecac.on.ca/wiki/index.php/Fedora-ARM_Package_Building_and_Troubleshooting/Problems --> '''Problems Page'''* http://zenit.senecac.on.ca/wiki/index.php/Fedora-ARM_Package_Building_and_Troubleshooting --> '''Project Page'''* https://fedorahosted.org/arm/report/1 --> tickets page'''Tracking Tickets Page'''<br>'''BLOGS Links:'''*http://rocellaj.wordpress.com<br>*http://mjcorsame.wordpress.com<br>*http://msbreezy12.wordpress.com<br>*http://aparda.wordpress.com/<br>
= Acknowledgments =
= Pictures / Graphics =
[[File:Fedora_ARM.jpeg]]