== Wednesday (September 19) ==
<!-- ---------------------------------------------------------------------------------------------- Week 4 ------------ --> = Week 4 = == Monday (September 24) == === [[Signing RPM packages === An RPM signature, like the digital signature used on many other software-signing systems, is and Creating a private key encryption of a checksum. Repository for RPM uses the GPG libraries for signing. # Create a GPG key: <code>gpg --gen-key</code># Add the e-mail address associated with your gpg key to the <code>%_gpg_name</code> macro in <code>~/.rpmmacros</code> -- the line will look like this: <code>%_gpg_name "<i>e-mail-address</i>"</code># Find (or make) some packages to put in your repository. Make sure that the epoch-version-release is higher than that of any package with the same name in the Fedora repositories.# Sign those packages with: <code>rpm --addsign <i>packagefile</i></code>Packages]]
=== To Do ===
By '''Wednesday, September 26''':
# [[DPI908/SBR600 RPM Signing Lab|RPM Signing Lab]]
# [[DPI908/SBR600 Repo Creation Lab|Repo Creation Lab]]
== Wednesday (September 26) ==<!-- ---------------------------------------------------------------------------------------------- Week 4 ------------ -->
=== Creating a YUM repository ==Week 4 =
A yum repository is just a directory of packages and some metadata. To create a yum repository:# Create a directory that can be served. The protocol used to serve that directory could be http, ftp, nfs, or something else (the files can be served by putting them on a DVD too!). For http, create the directory within <code>/var/www/html</code># Put your signed packages in that directory.# Create the repository metadata for that directory: <code>createrepo <i>/name/of/directory</i></code> (typically: <code>createrepo . </code>) Notice that the repository metadata will be placed in a subdirectory named <code>repodata</code> === Testing === # Create a new repository file in <code>/etc/yum.repos.d</code> by copying and modifying an existing file in that directory. Keep <code>gpgcheck=1</code> but comment out the <code>gpgkey</code> file.# Confirm that you cannot install from that repository using yum, since the gpgkey is unavailable to yum/rpm.# Uncomment the <code>gpgkey</code> line, and point it to a new file within <code>/etc/pki/rpm-gpg/</code># Create that file by running Monday (as your regular userSeptember 24): <code>gpg --export --armour <i>e-mail-address</i></code> and saving the output to the new filename Wednesday (note: you'll need to be your regular user to perform the export, but the root user to install the file).# Confirm that you can now install from your repository. You should be asked whether you wish to import the key for your repo the first time you use a package from that repo. === Creating a Repository-release RPM === To make it easier for users to access your repository, create a RPM containing:# Your repo file# Your GPG key You can link to this repository-release RPM from a web page, and users can install access to your repository by simply clicking on that link. You can also include this package in a [[:fedora:Spin|Spin]] or [[:fedora:Remix|Remix]]. If you ever need to move your repository's location or make other adjustments, you can provide an updated repository-release package which will be installed when your users perform a <code>yum update</code>. Take a look at the [http://rpmfusion.org/ RPMFusion] release RPM for an example. === To Do === By '''Wednesday, September 26''':# [[DPI908/SBR600 RPM Signing Lab|RPM Signing Lab]] <!-- ---------------------------------------------------------------------------------------------- Week 5 ------------ --> = Week 5 = == Monday (October 1) and Wednesday (October 3) ==
=== Project Selection ===
* You must have a strategy in place for reaching your targets.
Be prepared to give a professional, detailed, but very brief (2- to 4-minute) presentation on your project plan next Monday (October 8). Include:
* Your approach to the problem.
* Contacts and resources you've identified.
=== To Do ===
By Monday, October 8:
* Prepare your project page and project plan presentation.
<!-- ---------------------------------------------------------------------------------------------- Week 5 ------------ -->
= Week 5 =
<!-- ---------------------------------------------------------------------------------------------- Week 6 ------------ -->
'''Note:''' Monday is the Thanksgiving Day Holiday.
== Wednesday (October 10) ==
=== Project Plan Presentations (0.0) ===
* 2-4 minute quick presentations
<!-- ---------------------------------------------------------------------------------------------- Week 7 ------------ -->
* http://git-scm.com/
* https://github.com/
=== To Do ===
GIT Lab
* Clone the repository at ssh://sbr600@scotland.proximity.on.ca/~/certs/
* Add your cert using the instructions in the readme.txt file.
* Blog about your experience.
== Wednesday (October 17) ==
=== Python Primer ===
[[SBR600 Python Lab|Python Lab]]
= Study Week and FSOSS =
** 0.3 Milestone: TBA
= Week 9 - O.1 Release Presentation =
* Please book your time slot on [[Fall 2012 DPI908/SBR600 Presentation Schedule| the presentation schedule page]] on a first come first server basis.
* Each presentation should take no more than 10 minutes.
= Week 11 - 0.2 Release Presentation =
* Please book your time slot on [[Fall 2012 DPI908/SBR600 Presentation Schedule| the presentation schedule page]] on a first come first server basis.
* Each presentation should take no more than 10 minutes.
= Week 12 - Practical Quiz / Research Paper Discussion =
== Wednesday ==
=== '''SBR600 Only''': Practical quiz ===
* The quiz consists of one task: you will need to update an RPM to the latest upstream version of the software. For example, if the package is foo-2-1 and there is a new upstream version 3 of foo available, you will need to produce a foo-3-1 package. It would be worthwhile practicing this task in advance.
* The practical quiz will be in T3076 (which not our normal room) so that lab computers will be available.
* Make sure that you have access to your Fedora system, either on your laptop, on a removable disk pack, or through an SSH connection to one of your computers at home. Verify your arrangements! You may want to bring a Fedora Live system on USB or DVD as a backup.
* You may use your notes and online resources during the quiz. However, you may not share information with other people during the quiz.
Solution to the practical quiz:
<center><embed src="http://www.youtube.com/v/9SK3rWAGsMQ?version=3&hl=en_US" type="application/x-shockwave-flash" style="width: 400px; height: 326px;" allowscriptaccess="always" allowfullscreen="true"></embed></center>
=== '''DPI908 Only''': Discussion about the [[DPI908 Research Paper]] ===
* Meet in the usual room
= Week 13 - Wrap-up =
* The 0.3 Presentations are '''CANCELLED'''. Your 0.3 release is still due on '''December 8 at 11:59 pm.'''
== Monday ==
* Guest lecture/interview with Rob Bishop, Raspberry Pi Foundation tech evangelist.
* Evening event: [[Raspberry Pi Hackspace Tour Toronto]]
== Wednesday ==
* Wrap-up - final opportunity to get help and feedback on your 0.3 release
<!--
= Exam Week =
-->
= Guest Lecture Notes =
* [[DPI908/SBR600 Guest Lecture-Paul Whalen-20121119]]
