(→Other requests: move to pagure)
(add a big fat warning that this information is obsolete after Pkgdb decommission)
|Line 1:||Line 1:|
== Introduction ==
== Introduction ==
Revision as of 00:59, 18 August 2017
PackageDB has been decommissioned
PLEASE NOTE that PackageDB was decommissioned on 4 August 2017. You should now use the fedrepo-req tool to request new package git repositories and new git branches.
For more information about the PackageDB decommission, see: Infrastructure/WhatHappenedToPkgdb
The original instructions for using PackageDB are preserved below for historical interest.
Pkgdb2 allows maintainers to request changes to their packages and then have those requests processed by admins. This completely replaces the previous process that used a template placed in bugzilla bugs and a script to scrape that information out.
For new packages, login to pkgdb and click on 'request new package'. Fill in the form with the required information and submit. Your request will be processed by admins usually within 24 hours.
Note that a bugzilla ticket number is required. Generally this will be the review request ticket, but if the package has been granted an exception by the packaging committee (see Packaging_Committee#Review_Process_Exemption_Procedure) or the package falls under one of the general exception criteria (see Packaging:ReviewGuidelines#Package_Review_Process) then there won't be a pre-existing review ticket.
In this case, simply file a bugzilla ticket. In that ticket, indicate that you believe the package qualifies for an exemption from the review process. If the Packaging Committee has granted an exception, please include a link to the ticket which was filed with the FPC. If the package is for a different version of an existing package, please indicate the original package name.
Additional branches for existing packages
To request additional branches for an existing package, simply search for and go to that package's pkgdb page, while logged in. Click on "request new branch" and submit.
If you have commit acls for the package your branch will be granted, if you do not (for example you wish to maintain a existing package in EPEL), the owner will be given 7 days to approve or reject your request and then (or earlier if approved) it will be processed.
All other requests, such as unretiring a package or other changes should be filed as a ticket in the rel-eng bugtracker for handling by a release engineer. Note that with unretire requests you MUST include a link to the packages re-review if needed.
Bug reports or issues
Pseudo-users and Groups for SIGs
The following groups and pseudo-users in packagedb (shown on the left of the table) can be used as main contacts or watchers 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 field does not accept email addresses; use the username on the left.