1
edit
Changes
→Project Plan
<!-- 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. -->
Normal 0 false false false EN-CA X-NONE X-NONE
== 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.
== Signing SOP ==
First off I 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.
Moving onto the procedure the locations of files are as follows
'''Binary files''' should be placed here on the scotland server:
/var/www/html/sbr600/raspi-incoming/binary/
'''Source files''' should be placed here on the scotland server:
/var/www/html/sbr600/raspi-incoming/srpm
'''RPM packages''' should be placed here on the scotland server:
/var/www/html/sbr600/raspi-repos/
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 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.
And if you’re having trouble with your part of the project don't give up nothing worth doing was ever easy.
* 0.3 Release - Complete package containing public keys and repo files.
