Just going through the messages, it is clear that the bug originated from mpich2 and arpack.
So when these packages were fixed all the versions of elmerfem were fixed.
How can we fix this wrongly handle bug for elmerfem?
> Date: Tue, 13 Mar 2012 13:12:13 +0000
> From: email@example.com
> To: firstname.lastname@example.org
> CC: email@example.com
> Subject: Re: elmerfem not migrating to testing.
> On 13.03.2012 11:35, Mark-Willem Jansen wrote:
> > There seems to be a problem with bug 652061 . According to the
> > messages the bug is fixed
> > which this is confirmed if you take a look at the bug list. But in
> > the version graph the latest
> > version is still red
> It's marked as fixed and found in the same set of versions. That's
> illogical - either 6.1.0.svn.5396.dfsg-3 and -4 contain the bug, or they
> don't; they can't both contain and not contain the bug simultaneously.
> The BTS errs on the side of assuming that the bug is still present.
> The version information needs fixing up to indicate which versions
> actually contain the bug and which versions it's fixed in.
> To UNSUBSCRIBE, email to debian-release-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
> Archive: http://email@example.com