Launchpad should not allow also affects for different packages

[Scott Kitterman]

Based on https://lists.ubuntu.com/archives/ubuntu-devel/2008-July/025910.html the current also affects functionality is fundamentally wrong and broken.

"In Launchpad, if a bug is fixed in one context but not fixed in another
context, that means there's easy work to do: the fix can be picked up
from the former, and applied to the latter. But that's not true (I
assume) for library/language transitions: it wouldn't make sense to take
the patch that fixed one package, and apply it to a package of
completely different software.

Launchpad's "bugs fixed elsewhere" list shows bugs that are fixed in one
context but still open in others, to help people share fixes. It would
be misleading for in-progress transitions to show up on that list."

Given this definition, a bug can never also affect anything other than a related code base (e.g. upstream or another distro). So please remove the ability to have Launchpad relate multiple Ubuntu packages via also affects so we stop using it wrong.

[Matthew Paul Thomas (mpt)]

This would be a helpful error-prevention technique. However, it wouldn't work well with software that has multiple versions packaged in a distribution simultaneously. Current examples include firefox-2 and firefox-3.0, and amarok and amarok-kde4. In those cases it seems quite possible that a fix for a bug in one package could be applied to fix the same bug in another package in the same distribution.