Comment 6 for bug 700036

@Alan: launchpad had the ability to list likely duplicates of a bug during the reporting stage, but for some reason it's not working in this case - even if I specify exactly the same title as this one. I will file a bug about it.

In any case, my point about duplicates is not regarding the effort to de-duplicate them or that they take up space on launchpad or anything of the like, but about the number of people that are seeing a problem and have to spend time figuring out whether it affects any of the functionality they were interested in by installing openmpi-bin, and how to fix it.

I remind you that we had a very similar conversation 6 months ago in bug #555729. In the end nothing was done and maverick continues to have a non-working blcr-dkms. Natty is due out in 6 days and I'd be disappointed to see it ship (and hold on to) the broken blcr-dkms again. The dependency change that I suggest would at least ensure that at release time no-one will see an error from an unrequested module that doesn't currently work. When the functionality is restored it would be OK to promote blcr back to "recommends".

(I'm not sure the tone of the above paragraph is unambiguous - I don't mean to be disrespectful, I don't doubt this is being actively worked on, and I trust your criterion that a working blcr should be a "recommends" of openmpi-bin. My point is that there exists a temporary stop-gap measure that is easy to deploy and would avoid inconveniencing a number of users for no good reason.)