Requests that require CVS administrators' approval may be requested by adding the bug tracker number #33 in Bugzilla tickets as described on this page. To accomplish the tasks described here, you need to be a member of the rpmfusionbugs group.
Adding a bug dependency on the Tracker bug in a Bugzilla report means CVS admin attention is needed. They will read your Bugzilla ticket and attempt to take care of your request. In order to make the job faster and easier for the CVS admins, please follow the guidelines on this page in order to format your request in a standard way with all required information.
After your package is approved by the Package Review Process, you may request for a CVS module to be created. Please copy this template into your Bugzilla comment, and add your ticket to the tracker bug numbered #33. After your request is granted, please wait for the next CVS sync, which occurs every 30 minutes. At that point, your package checkout will contain empty directories for each distro branched. Simply add your files to these directories, check-in, tag and build.
Note: Requests for new F-(x-2) packages when F-x goes gold will not be accepted. For example, when Fedora 16 is released, no new package requests for Fedora 14 will be accepted.
Here is a template:
New Package CVS Request ======================= Package Name: Short Description: Owners: Branches: InitialCC: Cvsextras Commits:
And an example:
New Package CVS Request ======================= Package Name: foobar Short Description: kmod of foo Owners: fas_registered_email,fas_registered_email_2 Branches: F-14 F-15 InitialCC: fas_registered_email Cvsextras Commits: yes
note: we remind you that EPEL is a sub project of Fedora that provides a complementary add-on repository built from Fedora packages for Red Hat Enterprise Linux and compatible rebuilds. Read more about EPEL before branching for it.
Valid branch names currently used for Fedora and RPMFusion: F-14 F-15 EL-5 EL-6. The devel branch is implicit and always created, so you need not list it.
Owners must be one or more FAS registered email. If you have multiple owners, add secondary owners with a comma separated list.
InitialCC contain FAS registered email that receive mail pertaining to this package, but are not necessarily owners.
Cvsextras Commits tells whether anyone in cvsextras can commit to the repository. It should be yes unless you have some specific reason why you do not wish for the community to be able to assist with your package. If you do have such a reason, use no and give a short explanation of the necessity of denying community access.
note: RPMFusion currently doesn't support OLPC packages.
Package Change Requests for existing packages
Please try to use the existing review ticket for these special requests, even if that ticket is CLOSED. If you cannot find a review ticket, then creating a new bug is acceptable.
- Additional branches for an existing package
- Ownership, description, or initial CC list changes
Please use the following template to state clearly exactly what you want and why it is justified in your Bugzilla comment. Then make your ticket block ticket #33. Note that there is no need to reopen the ticket if it is closed; the CVS administrators only query on the state of the bug tracker list RF_CVSsync, and it takes extra time for the CVS administrators to look up the original resolution of the ticket so that it can be re-closed properly.
Here is the template:
Package Change Request ====================== Package Name: [New Branches: ] [Updated RPMFusion Owners: ] [Updated RPMFusion CC: ] [Updated EPEL Owners: ] [Updated EPEL CC: ] [Updated Description: ] [Updated Cvsextras Commits: ] [add any required explanatory text here]
The Package Name field is mandatory. Please only include other fields that need to be changed or updated. For Owners and CC changes please list all the owners, both current and new. If the CC list is to be removed use [none] to indicate that. If you are requesting one or more EPEL branches with exactly the same Owners and CC list as for Fedora, then there is no need to write them in the request.
Example, to add EPEL branches:
Package Change Request ====================== Package Name: foobar New Branches: EL-5
Example, to add new co-maintainer "baz":
Package Change Request ====================== Package Name: foobar Updated RPMFusion Owners: foo_username,bar_username,baz_username
If you need other special changes done which cannot be handled by the template fields, like renaming of a package, or complete removal of a package or branch due to rare circumstances, please state your desire and justification below the template in your Bugzilla comment.
Note: for current packages that have been renamed upstream, a new package needs to be created for the new package: please make a New Package CVS Request.