1
edit
Changes
→Project Outcome
<!-- 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 ==
'''[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/raspi-reposF17/packages/arm/os/ RPM Packages]''' should After I sign your rpms they will be placed here on the scotland server:/var/www/html/sbr600/raspi-reposF17/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.
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
== Communication ==