koji build --scratch TARGET /path/to/local.built.src.rpm
Please read the full documentation before you try it!
Create a Fedora Accounts System (FAS) account.
Create a Red Hat Bugzilla account.
Both should use the same e-mail address!
Join the following mailing lists:
In FAS, accept the Contributors License Agreement. Wait for approval.
You should upload your SSH key, usually, ~/.ssh/id_rsa.pub. If you don’t have it in your system, please create one using ssh-keygen.
You will need to download a client-side certificate from your FAS account. It will be called dogencert. Copy it to ~/.fedora.cert.
You will need to download the fedora-upload-ca.cert from https://admin.fedoraproject.org/accounts/fedora-upload-ca.cert to ~/.fedora-upload-ca.cert.
You will need to download the fedora-server-ca.cert from https://admin.fedoraproject.org/accounts/fedora-server-ca.cert to ~/.fedora-server-ca.cert.
Then, join the following groups:
Fedora Bugs Group
Fedora Packager Group
When your package is sponsored you will be moved to the Fedora Packager CVS Commit Group.
You can use the following references:
Packaging Red hot, Paneer (butter) Masala: Packaging RPM
You can use Koji to build packages for Fedora Collection and EPEL, by using:
koji build --scratch TARGET /path/to/local.built.src.rpm
where:
TARGET is dist-f12 (for Fedora 12). Use koji list-targets to see available targets.
You can put the .spec and .src.rpm in your FAS account (150 MB available). For example:
Create a review request from using the following URL: https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=extras-review
In Review Summary put the name of the package.
In Provide URLs for .spec file and .src.rpm.
In description add the .spec file description.
In the Review Description mention it is your first package.
Add FE-NEEDSPONSOR in the Bug blocks field. This is only required for your first package, not after that.
If there are any changes requested, please review them at your submitted Review Request at bugzilla.redhat.com.
Once the .spec and .src.rpm is sponsored/approved, you need to make a new package CVS request:
Add the following note in your bugzilla.redhat.com Review Request page (mcu8051ide is an example here):
New Package CVS Request ======================= Package Name: mcu8051ide Short Description: IDE for MCS-51 based microcontrollers Owners: shakthimaan chitlesh Branches: F-11 F-12 EL-5
Changing the fedora-cvs flag to "?" in the Bugzilla page. It means CVS admin attention is needed.
Once CVS has been approved, checkout the package:
$ cd ~ $ mkdir cvs $ cd cvs $ fedora-cvs mcu8051ide
You can now import the .src.rpm to devel:
$ cd mcu8051ide $ ./common/cvs-import.sh /home/foo/rpmbuild/SRPMS/mcu8051ide-1.1-4.fc12.src.rpm
It will open up vi for you to give the commit message.
You should also import it to the respective branches you have mentioned earlier — F-11, F-12 and EL-5 as follows:
$ ./common/cvs-import.sh -b F-11 /home/foo/rpmbuild/SRPMS/mcu8051ide-1.1-4.fc12.src.rpm $ ./common/cvs-import.sh -b F-12 /home/foo/rpmbuild/SRPMS/mcu8051ide-1.1-4.fc12.src.rpm $ ./common/cvs-import.sh -b EL-5 /home/foo/rpmbuild/SRPMS/mcu8051ide-1.1-4.fc12.src.rpm
If you have already pushed a package to cvs, and you have made an updated package locally, just repeat the above for the newly created RPM package.
These commits will also generate automated e-mails to: https://www.redhat.com/mailman/listinfo/fedora-extras-commits
Enter into each branch directory (devel, F-11, F-12, et. al.) and do the following:
$ cvs up $ make build &
From Fedora 11, one needs to use rpmbuild-md5 to build EPEL packages, because, Fedora RPM packages use SHA256, while EL5 uses MD5.
Login to Fedora Update System: https://admin.fedoraproject.org/updates/new/
Package: Type the first name of the package, and your package builds will be displayed. Add for all the package builds.
Type: For a new package, it is newpackage.
Request: Can be Stable.
Bugs: Write the relevant bugzilla bug request number here.
Notes: Any notes that you want to be mentioned.
Click on Save Update to send the package update.
References