Bug Tracking for PPAs Is Now Available in Launchpad

İlker Emre Koç — Wed, 21 Oct 2026 13:21:32 +0000

Launchpad now supports bug tracking for Personal Package Archives (PPAs). You can report and track issues against a PPA, individual source packages within it, and specific Ubuntu releases.

This brings bug reports closer to the packages they concern, giving users a place to report problems and maintainers a clearer picture of what is affected.

Why Track Bugs Against a PPA?

PPAs let maintainers distribute packages outside Ubuntu’s official archives. Those packages might contain a newer upstream release, an experimental feature, a patch that is not available in Ubuntu’s version, or even exist solely in PPAs without being in the primary Ubuntu archive at all.

These differences matter when something goes wrong. A bug affecting a package from a PPA does not necessarily affect the package in Ubuntu’s official archive. Likewise, an issue might affect one PPA’s package without affecting another.

PPA bug tracking lets a report capture that distinction directly.

A Practical Example

Suppose a team publishes a new version of an application called Example Editor in its testing PPA. A user installs it on Ubuntu 24.04 LTS and discovers that opening a large document causes a crash. The version in Ubuntu’s official archive works correctly.

The user can report the issue against the source package in the team’s PPA and identify the affected Ubuntu release. This gives the maintainers a report tied to the package they distribute, without treating it as a confirmed problem in Ubuntu’s version.

If investigation shows that other targets are affected, the same Launchpad bug can track those too, with a separate status for each target.

Tracking Issues at the Right Level

PPA bug tracking supports different levels of detail:

PPA: for issues concerning the archive as a whole.
A source package: for issues affecting a particular package within the PPA.
An Ubuntu release: to distinguish which release is affected, including for a particular source package.

This allows reports to start with the information available and become more specific as maintainers investigate.

Getting Started

Open the PPA’s page in Launchpad and select View bugs to browse its bug reports.

The bugs page lists reports affecting the PPA or its source packages. You can search existing reports or select Report a bug to create a new one.

On a bug report, the Affects table identifies the PPA and its owning person or team. Each target has its own status, importance, and assignee, so you can track progress for the PPA separately from other affected targets.

You can also add a PPA or one of its source packages as an affected target on an existing bug report. Select Also affects PPA/package beneath the Affects table.

In the form that opens, select the affected PPA. If you know which source package is affected, enter its name; otherwise, leave that field blank. Select Continue to proceed.

To change an existing bug target, expand its row in the Affects table. Select PPA, choose the archive, and optionally specify a source package. Select Save Changes to update the target.

For PPA Maintainers

With the new PPA bugs, bug reports now have another target to better reflect where your packages are published. You can use Launchpad’s bug-tracking workflow to triage issues and track their status for the relevant PPA, source package, or Ubuntu release.

When a report also affects Ubuntu’s official package or an upstream project, use the appropriate additional bug targets to record that scope. Keeping those targets accurate helps everyone understand where investigation or a fix is still needed.

Available Now

PPA bug tracking is now enabled in Launchpad. Visit your PPA and select View bugs to explore it.