From Fedora Project Wiki

It has been requested that this page be deleted.
PackageDB has been decommissioned

PackageDB has been decommissioned

PLEASE NOTE that PackageDB was decommissioned on 4 August 2017. You should now use the fedpkg 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.

New packages

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

A maintainer can request additional branches using fedpkg request-branch <BRANCH>.

This will create a ticket at and Release Engineering will process these requests.

If you are not maintainer, please review Getting_a_Fedora_package_in_EPEL#The_procedure_for_getting_a_package_in_EPEL and start by contacting the maintainer to see if they can request and maintain the branch.

Other requests

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

Please report issues with pkgdb to or

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.

Multiple comaintainers recommended
When the primary owner of the package is a pseudo-user, it's recommended that there are multiple comaintainers (people with approveacls) on the package. That way, if one person leaves the project, the comaintainers are still able to approve acl requests for others
username email
anaconda-maint anaconda-maint-list[AT]
astronomy-sig astronomy[AT]
cloud-sig cloud[AT]
ctrl-center-team control-center-maint[AT]
design-sw design-devel[AT]
group::fedora-atomic-sig fedora-atomic-sig[AT]
fonts-sig fonts-bugs[AT]
gecko-maint gecko-maint[AT]
group::gnome-sig gnome-sig[AT]
group::kde-sig kde-sig[AT]
hams-sig fedora-hams[AT]
haskell-sig haskell-devel[AT]
i18n-team i18n-bugs[AT]
java-sig java-sig-commits[AT]
kernel-maint kernel-maint[AT]
lvm-team lvm-team[AT]
ml-sig ml[AT]
mono-sig fedora-mono[AT]
orphan extras-orphan[AT]
perl-sig perl-devel[AT]
group::python-sig python-sig[AT]
group::qpid-sig qpid-sig[AT]
retired retired-packages[AT]
xen-maint xen-maint[AT]
xgl-maint xgl-maint[AT]
group::qa-toools-sig qa-tools-sig[AT]