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 ==
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 ==
* 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.
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:
== Communication ==