View source for Create the Raspi Repositories

= Project Name =
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
Raspi Repositories

== Project Description ==

<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
Set up the repositories to distribute the F17 Raspberry Pi remix files, including:

Setting up the signing keys
Creating a standard signing procedure (SOP) for signing
Creating a 'release' package containing the public keys and repo files

Expected outcome: repos, release package, SOP
== Project Leader(s) ==

<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first.  Include links to personal pages within wiki and to blog sites. -->
Andrew Greene

== Project Contributor(s) ==

<!-- Name(s) of people casually working on the project, or who have contributed significant help.  Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.

NOTE: only Project Leader(s) should add names here.  You should not add your own name to the Contributor list. -->

== Project Details ==

<!-- Provides more depth than the Project Description.  This is the place for technical discussions, project specs, or other details.  If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->

== Signing SOP ==

First off I would like to apologize for posting this so late but I had to double check some things with the gpg key and make sure everything was working  properly. I ran into a few issues but I believe I have resolved them now.


Here is the basic procedure for getting your package signed the locations of files are as follows


'''[http://scotland.proximity.on.ca/sbr600/raspi-incoming/binary/ Binary Files]''' should be placed here on the scotland server:
/var/www/html/sbr600/raspi-incoming/binary/



'''[http://scotland.proximity.on.ca/sbr600/raspi-incoming/srpm/ Source RPM Files]''' should be placed here on the scotland server:
/var/www/html/sbr600/raspi-incoming/srpm



'''[http://scotland.proximity.on.ca/sbr600/F17/packages/arm/os/ RPM Packages]''' After I sign your rpms they will be placed here on the scotland server:
/var/www/html/sbr600/F17/packages/arm/os/



Once you have placed your packages/files into their prospective directories I will then be notified that there is a new package that needs to be signed.

After receiving this notification I will sign your package then update the [http://scotland.proximity.on.ca/sbr600/F17/packages/arm/os/ Repository] with the newly signed packaged then add your package to the [[Signed RPMS List]]. If you’re not sure if your rpm package has been signed yet you can run the following command from the raspi-repos directory "rpm --checksig <your-rpm-package>" or just check the page link I have provided for convince.


If anyone has any questions, comments or ideas on how to make this process more efficient feel free to send me an email and I will do my best to work with you.

Email: agreene@learn.senecac.on.ca


And if you’re having trouble with your part of the project don't give up nothing worth doing was ever easy.

== Project Plan ==

Tracking mechanism:
Bugzilla

Key contacts:
<!-- Add links to any mentors or key participants in the community. -->

Goals for each release and plans for reaching those goals:
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
* 0.1 Release - proof of concept:  Prepare keys for the F17 Raspberry Pi remix files, test sign packages, test and develope a basic SOP concept/outline.
* 0.2 Release - Refine Standard Signing Procedure, create repos for a pre-release package, test pre-release for bugs.
* 0.3 Release - Complete package containing public keys and repo files.


== Project Outcome ==

Create the Raspi Repositories

Set up the repositories to distribute the F17 Raspberry Pi remix files, including:
Setting up the signing keys
Creating a standard signing procedure (SOP) for signing
Creating a 'release' package containing the public keys and repo files

Completed: repos, release package, SOP


For this release I have completed the Raspberry Pi remix release package, Repos and signing keys for F17. The release package contains the repo files required to download and install various raspberry pi packages from the repo, and the public key I have signed the packages with.

Provided below are links to all of the files that I have worked on to complete this project. 

Completed Spec File:

[http://matrix.senecac.on.ca/%7Eagreene/spec/raspberrypi-fedora-remix-release-17.spec raspberrypi-fedora-remix-release-17.spec]

Completed Raspberry Pi F17 Remix OS Repo:

[http://scotland.proximity.on.ca/sbr600/F17/packages/arm/os/ Raspberry Pi Remix F17 OS Repo]

Completed Raspberry Pi F17 Remix Source Repo:

[http://scotland.proximity.on.ca/sbr600/F17/packages/source/ Raspberry Pi Remix F17 Source Repo]

Raspberry Pi Public GPG-Key:

[http://scotland.proximity.on.ca/sbr600/F17/packages/source/ RPM-GPG-KEY-rasspi-pubkey.asc]

Raspberry Pi Fedora Remix Release 17:

[http://scotland.proximity.on.ca/sbr600/F17/packages/arm/os/raspberrypi-fedora-remix-release-17-0.2-1.fc16.noarch.rpm%20 raspberrypi-fedora-remix-release-17-0.2-1.fc16.noarch.rpm]

== Communication ==

=== Mailing Lists ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->

=== Upsteam Wiki and Web ===
<!-- Links to upstream wiki/web pages -->

=== Links/Bugs/Tracking ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->

=== Source Code Control ===
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->

=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->

http://sbr600blog.blogspot.com/

==== Seneca Particpants ====
Andrew Greene

==== Non-Seneca Participants ====
<!-- Links to the blogs of any non-Seneca participants in this project -->

==== Planets ====
<!-- Links to any planets related to this project -->

== Project News ==

<!-- This is where a permanent record of your releases and updates will go.  In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->