Comment 14 for bug 102684

On Wed, Jun 04, 2008 at 10:21:24AM -0000, Matthew Paul Thomas wrote:
> That this bug hasn't yet been reproduced in 3.0b5 does not mean it
> should be fixed in 2.0 only. (It hasn't yet been reproduced in 2.0
> either!) Besides, it would make very little sense to fix a minor problem
> with installing updates in a version that is unlikely to receive many
> future updates anyway.
>
> If this bug still exists, it should be fixed not in 2.0 specifically, or
> 3.0 specifically, but in whatever the latest version of Firefox happens
> to be at the time it's fixed. So it's appropriate for it to be filed
> against firefox, which "is a meta package that will point to the latest
> firefox package in ubuntu", and not against firefox-3.0.
>
> I look forward to testing with 3.0RC1.
>
> ** Changed in: firefox-3.0 (Ubuntu)
> Status: Incomplete => Invalid
>

Launchpad is quite confusing here. technically, the firefox meta
package is currently produced by the firefox-3.0 source package. thus,
since launchpad uses source packages to associate bugs, firefox-3.0 is
the current target for the latest firefox and firefox is firefox
2. This will change ones firefox 2 is gone long enough and when i can
put the meta package into the firefox package again.

Anyway, for now please adjust the state accordingly.

 - Alexander