Triaging Bugs with Patches

Evan eapache at
Thu Feb 18 03:42:34 UTC 2010

I've been triaging a few bugs, and I came across a pair of bugs in libpcap
which had patches [1][2].
I found and checked the wiki page on triaging bugs with patches [3], and
after completing the available steps, I ran into a wall.

The complete text of the section describing what to do with a bug that has a
patch reads as follows:

> In the event that [the patch] is not a debdiff one could incorporate the
> patch into a debdiff for the latest release of Ubuntu or apply the patch to
> a bzr branch of the package and link the branch to the bug report.
> If an attachment is a debdiff and applies to a recent version of the
> package the bug report needs to be sponsored<>to the appropriate archive. This is done by subscribing (NOT assigning) the
> appropriate sponsorship team to the bug. For packages in main and restricted
> the ubuntu-main-sponsors team should be subscribed. For packages in the
> universe and multiverse repositories the ubuntu-universe-sponsors team
> should be subscribed. You can view their queues at main-sponsors<>and
> universe-sponsors<>
> .

1) The two attached patches are simple diffs, not debdiffs - is there a way
to convert them, and could it be added to this page?
2) As a triager, how is one expected to be able to apply a patch to a bzr
branch, and what if the project isn't hosted on launchpad/bzr? This seems
more dev-related then triager-related.
3) Is there a way to tell from a bug page which repository the package is
in? I eventually found it on the launchpad libpcap package page, but I
couldn't find any obvious indicator on the bug page itself. This should
probably be mentioned as well.

To my mind, once a bug has an attached patch which the triager can verify as
at least being potentially useful, there should be a simple button "flag as
This flag should ping the maintainer with something like: "Project X has a
ticket with a patch!".
The maintainer (or another dev) should then check the patch, commit it, and
close the bug.

I'm not a workflow expert, so there may be reasons for the way the system is
currently set up, but it doesn't make sense to me.
If the general consensus is that my points on the wiki are valid, I'll take
a shot at rewriting that section.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Ubuntu-devel-discuss mailing list