Archive:Using the package database

Using the Fedora Package Database

The Package Database is the place where we track ownership of packages and permissions on who is allowed to commit to a package.

Accessing the Interface

Where is the Package Database?

The packagedb is located at https://admin.fedoraproject.org/pkgdb/

Where should I go from there?

The links on the left side of the main page give you access to the major views of the information in the Package Database.

• The View Collections and View Packages links allow you to browse through a list of packages, looking for information on them.
• Orphan Packages displays a list of packages which are orphaned in one or more active branches.
• Project Page and Report Bugs Take you to the Package Database's project page for getting involved with development of the PkgDB2 code.

What's the fastest way to find a package?

To directly access a package you're interested in simply replace PACKAGENAME in the following URL with the name of the package:

https://admin.fedoraproject.org/pkgdb/package/PACKAGENAME

There is also an OpenSearch extension offering to search packages or packagers directly in your browser.

Logging in

The upper right hand corner of the Package Database has a brief message that says You are not logged in yet Login. When you click on Login, you are asked to enter your Fedora username and password. Once these are entered, you will be able to make changes in the Package Database.

Signing up for packages

How do I sign up for a package?

Navigate to the package's page in the Package Database. If you have not logged in, go ahead and do that now. At this point you should be back at the package's page and have a button labeled Add myself to Packages that you can press to request access to a certain package on a certain branch. Once you've selected that button, you can check off the checkboxes for each acl you're interested in.

• watchcommits and watchbugzilla are for receiving email notifications for package changes.
• commit is for access to commit to the SCM.
• approveacls is to be allowed to approveacls just like the package owner.

I'm the package maintainer, how do I give someone commit access to my package?

Go to the page of the package and click on Manage the committers. There you have a grey button to Add someone and give him/her the ACLs you want on one or more branches.

How do I find orphaned packages that I can take over?

This main source of information is: https://admin.fedoraproject.org/pkgdb/orphaned/

But information is currently also present in the wiki: http://fedoraproject.org/wiki/PackageMaintainers/OrphanedPackages http://fedoraproject.org/wiki/PackageMaintainers/RetiredPackages

If you'd like to work on migrating this information into the PackageDB, please see this ticket .

Working with your packages

How can I find my packages?

The easiest way to find the packages you work with is to search your name in the list of packagers, or simply to log-in and click on your name at the top right corner of the page.

This view shows you every package for which you have an acl in a non-EOL branch. (So a package for which you only have watchbugzilla in EPEL4 will show up. A package for which you are the owner in Fedora Core 3 will not.)

How can I only list packages I'm comaintainer of?

The page makes the distinction between package where you have the commit ACL and packages where you are the point of contact and finally packages where you have one of the watch* ACLs.

How can I list packages which I was interested in on an EOL branch?

Add EOL=True to the end of the url.

Here's an example that lists packages that pingou was the point of contact including EOL branches:

https://admin.fedoraproject.org/pkgdb/packager/pingou/?eol=True

This is implemented in 1.9

How can I add a new package or add a package to a new branch?

These actions require manual work to be done by an administrator so follow the steps in package SCM admin requests .

Eventually we hope to make these steps more automated with a form to request a new branch and another form to request a new package. If you'd like to work on this, please see this ticket

PackageDB API

Some of the PackageDB data can be accessed by scripts as JSON or plain text data. This data is made available to make scripting easier. If a page supports plain text, it can be retrieved that way by appending ?tg_format=plain to the Base URL. If it can be retrieved as JSON data, appending ?tg_format=json will retrieve the information in that way.

The best way to retrieve this data is by using the client library present in python-fedora. yum install python-fedora then setup a pkgdb client object and call methods on it like this:

from fedora.client import PackageDB
# username and password are optional -- in general, only methods that
# modify data will need them to have been specified
pkgdb = PackageDB(username='me', password='XXXX')
pkgdb.get_bugzilla_acls()

Documentation for the pkgdb module of python-fedora is here: https://fedorahosted.org/releases/p/y/python-fedora/doc/existing.html#pkgdb

If, for some reason, you must retrieve the information without the help of the client library, you can use the urls directly like this. For instance, Bugzilla Acls can be retrieved in the following ways:

HTML:
https://admin.fedoraproject.org/pkgdb/lists/bugzilla

Plain Text:
https://admin.fedoraproject.org/pkgdb/lists/bugzilla?tg_format=plain

JSON:
https://admin.fedoraproject.org/pkgdb/lists/bugzilla?tg_format=json

Each method exposed to the user has a different rating for stability depending on several criteria:

• Stable: The format of data, URL location, and query parameters are not expected to change. If changes occur, they will be announced and deprecated ahead of time.
• Proven: The data format is stable. URL location and query parameters may change but a method of retrieving the data in its current form will remain available. API with this status will have notes to explain just how much it can be depended on.
• In Flux: The data being exposed by this method will continue but the URL location, format, or query parameters to retrieve it may change.
• Unstable: Anything about this method could change including disappearing entirely.

Note that using python-fedora remains the best method of accessing this data. We can add compatibility shims to that even when the server code changes. The server code is undergoing some redesigns that may make things change -- in particular, we are moving away from returning representations of the database tables directly and making changes to the database schema. These may cause changes to even the Proven API.

Bugzilla Acls

Base URL	https://admin.fedoraproject.org/pkgdb/lists/bugzilla
Plain Format	Stable
JSON Format	Stable

The bugzilla acl page returns information about package ownership, summary information, and initialcclist that bugzilla needs to know. At present (and unless a change occurs in bugzilla that would obviate this), the information is based on the information for the latest release of the product. At the moment Nov, 19, 2007, those are Fedora Devel, Fedora EPEL 5, and Fedora OLPC 2.

VCS Acls

Base Url	https://admin.fedoraproject.org/pkgdb/lists/vcs
Plain Format	Stable
JSON Format	Stable

The VCS Acls page returns information about who can commit to a package.

Package Information

Base Url	https://admin.fedoraproject.org/pkgdb/acls/name/PKGNAME
JSON Format	Proven

Package Buglist

Base Url	https://admin.fedoraproject.org/pkgdb/acls/bugs/PKGNAME
JSON Format	In flux

User Package List

Base Url	https://admin.fedoraproject.org/pkgdb/users/packages/USERNAME
JSON Format	In flux

Returns a list of packages belonging to the user with the ability to filter on certain acls via query params. The query params may be added to in the future and the URL location may change as well.