Create the Raspi Repositories
- 1 Project Name
- 1.1 Project Description
- 1.2 Project Leader(s)
- 1.3 Project Contributor(s)
- 1.4 Project Details
- 1.5 Signing SOP
- 1.6 Project Plan
- 1.7 Project Outcome
- 1.8 Communication
- 1.9 Project News
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
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
Binary Files should be placed here on the scotland server: /var/www/html/sbr600/raspi-incoming/binary/
Source RPM Files should be placed here on the scotland server: /var/www/html/sbr600/raspi-incoming/srpm
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 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.
And if you’re having trouble with your part of the project don't give up nothing worth doing was ever easy.
Tracking mechanism: Bugzilla
Goals for each release and plans for reaching those goals:
- 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.
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:
Completed Raspberry Pi F17 Remix OS Repo:
Completed Raspberry Pi F17 Remix Source Repo:
Raspberry Pi Public GPG-Key:
Raspberry Pi Fedora Remix Release 17:
Upsteam Wiki and Web
Source Code Control