No semantic handling of Ubuntu backport bugs

  affects /products/malone

There are two kinds of backport fixes Mez wants to model in Launchpad:

1. Bug #NNNN should be fixed in Breezy by bringing a new version of
foobar in from Dapper.

2. Requesting that package X.YZ of package be brought into Breezy.

In both cases, getting the backport would involve modifying one's
sources.list.

We have the "Target Fix to Releases" page in Malone, but this was
designed mainly for -updates and -security. This screen doesn't
handle either use case above because:

1. It doesn't capture anything about package versions.

2. It doesn't provide repository information about where the fix is
available. If one sees that a bug is "fixed in Breezy", they would
likely expect that fix is in the official Ubuntu repo.

Currently, backports are managed with a product hack. spiv suggested
maybe they could be modeled using a derivative. I suggested that they
should be modeled as a derivative only if the backports project is
virtually identical to a derivative, but this seems not to be the case.

Cheers,

--
Brad Bollenbach