<!-- Change this to DONE when you're done. -->
This page status is: '''DRAFTDONE'''.
= Title =
= Introduction =
We came in storming like it was For this particular project we spent the beach of Normandy all over again. As my fellow Canadian patriot's would say "EHH?!". A group of students undergo a entire school semester of building packages that were fedora 13 package updatesfor ARM. Not know knowing what we were getting into we sure had excitement and determination in our eyes to get this project finished. Little did we know was that, we still haven't fully understood how the process of troubleshooting and building packages was or how big the arm package build farm was. It was indeed a project filled with doubts, hope and fulfillment.
These The group of students mentioned at the top, right below "participants" are students that have little knowledge of how helpful the fedora community is. Being introduce to a vast growing community created room for improvement and friendships. It was indeed a huge improvement on how we tackled those packages we built and without the fedora community, we've pretty much would have been clueless throughout the semester.
At first we were just breaking in and had no clue where to start, but as things started to move and had our Build Master guide us toward the right direction we began building. Of course we needed to learn how to build in order to do this project, so we all took the time to learn efficient methods in doing this. As we imported what we learned into building, we began building our very first package. Being our first build, of course we had errors and errors that we have not encountered before as well, but was pretty self explanatory. Once we've figured out what things we had to fix for that package we ran it through once again and thus having an outcome of "Closed" bold in green - meaning it was completed for that arch.
= 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 family 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 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>Package for (libvirt-0.8.2-1.fc13.src.rpm, armv5tel)<br>Root.log error<br>''DEBUG util.py:256: No Package Found for numactl-devel''<br><br>OR<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>'''ChantellMcIntosh:'''<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-0.11.svn20070925.fc13.src.rpm<br><br>'''Andrew Parda:'''<br>• graphviz-2.26.3-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> <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 List of --> '''Problems]Page'''* http://zenit.senecac.on.ca/wiki/index.php/Fedora-ARM_Package_Building_and_Troubleshooting --> '''Project Page'''* https://fedorahosted.org/arm/report/1 --> '''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 =
All of us<br>'''Chantell McIntosh'''<br> [[File:Camcintosh1.png]]<br> '''Michael John Corsame'''<br> [[File:Corsame2.png]]<br> '''Rocella Jimenez'''<br> [[File:Rocella3.png]]<br>[[File:Rocella4.png]]<br>[[File:Rocella5.png]]<br> '''Andrew Prada'''<br> [[File:Ap6.png]]<br>[[File:Ap7.png]]<br> '''Fedora Arm System:'''<br> [[File:Fedora_ARM.jpeg]]