Package SCM admin requests
Requests that require package administrators approval may be requested through the fedora-cvs flag in Bugzilla tickets as described on this page. To accomplish the tasks described here, you need to be a member of the fedorabugs group. The fedora-cvs flag is changed by clicking on the more flags link next to Flags: in the bug summary. Then you can change its value:
Changing the fedora-cvs flag to "?" in a Bugzilla report means 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 package admins, please follow the guidelines on this page in order to format your request in a standard way with all required information.
Be sure to use the same bugzilla ticket that you used to get the package approved in the first place, to make your request.
After your package is approved by the Package Review Process, you need to request for a repository to be created for your package. Please copy this template into the Bugzilla comment of your bug that's been passed for review, and set fedora-cvs flag to ?. (The flag references CVS for purely historical reasons.) If you are newly sponsored member of the Fedora Packager group you might have to wait an hour before you will get the permission to set the flag in Bugzilla as the sync is done hourly. After your SCM request is granted, please wait for permissions to be synchronized (which occurs automatically every ten minutes). At that point, your package checkout will contain empty branches for each distro branch. Simply add your files to these branches, commit, push, and build. You can reference Using Fedora GIT for more information on these operations.
New Package SCM Request ======================= Package Name: Short Description: Upstream URL: Owners: Branches: InitialCC:
New Package SCM Request ======================= Package Name: pkgname Short Description: summary of package Upstream URL: http://pkgname-project.org/pkgname Owners: foo bar Branches: f19 f20 el6 epel7 InitialCC: baz
- Package name:
- It is expected that the requested Package Name matches the package name in the bug summary.
- If they don't match, your request will not be processed without verification.
- Package name is case sensitive. (pkgname and Pkgname are not same)
- Upstream URL:
- Upstream URL must start with either http:// or https://.
- Owners must be one or more FAS usernames.
- If you have multiple owners, add secondary owners with a space separated list.
- This field does not accept email addresses.
- This field is also case sensitive.
- Valid branch names currently used for Fedora: f20 f21 el5 el6 and epel7.
- The devel branch is implicit and always created, so you need not list it. (This implies that Branches: can be left blank if you only wish for a devel branch.)
- InitialCC contain FAS usernames that receive mail pertaining to this package, but are not necessarily owners.
- More than one can be listed separated by spaces.
- You may leave this field blank if you do not wish for any additional accounts to be CC'd.
- This field does not accept email addresses, which implies that anyone who wishes to be automatically CC'd on bugs (upstream, perhaps) must obtain a Fedora account.
Pseudo-users for SIGs
The following pseudo-users in packagedb (shown on the left of the table) can be used in InitialCC when appropriate, so that bugzilla and commits mails get CC'ed to the relevant mailing-lists and groups can triage their bugs effectively. Note that the InitialCC field does not accept email addresses; use the username on the left.
New Package SCM Request ======================= Package Name: pkgname Short Description: summary of package Upstream URL: http://pkgname-project.org/pkgname Owners: foo bar Branches: f19 f20 el6 InitialCC: astronomy-sig
Package Change Requests for existing packages
- additional branches for an existing package
- unretirement of a package on specific branches
- other special git requests, etc
please use the existing review ticket for requests, even though it may well be CLOSED (please do not reopen it). If a review ticket does not exist or you really cannot find it, then creating a new bug is acceptable. In this case set component to your package name, and version to rawhide.
You can search for the review by visiting the Review Status page and entering the the package name in the search box.
Please check with the package owner first before requesting a new branch, if you are not the owner.
For new branches, please use the following template to state clearly exactly what you want and why it is justified in your Bugzilla comment. Then set the fedora-cvs flag to ?. Note that there is no need to reopen the bug if it is closed; the package administrators only query on the state of the fedora-cvs flag, and it takes extra time for the administrators to look up the original resolution of the bug so that it can be re-closed properly.
Package Change Request ====================== Package Name: New Branches: Owners: InitialCC: [add any required explanatory text here]
The Package Name field is mandatory. The Owners field is mandatory if new branches are being requested: when the new branch is created, ownership or CC information will not be copied to the new branch, so be sure to specify in the request all of the owners and initialCC members the new branch should have. Please only include other fields which need to be changed or updated. In the Owners field list the branch owner and any comaintainers.
Example, to add EPEL branches:
Package Change Request ====================== Package Name: pkgname New Branches: el5 el6 epel7 Owners: bar foo
For unretirement of branches, please simply state which branches should be unretired (and raise the fedora-cvs flag as usual). You will need to log into pkgdb and claim them after your request is processed. You can also request new branches in the same request using the above change request template, but to avoid delays in processing your request, please don't attempt to add branches which already exist.
If you need other special changes done which cannot be handled by the template field, such as a package that was created with the wrong name that has never been imported or built, or otherwise out of the scope of the template 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 and reviewed before it can be added.