On 15.03.2012 09:10, Mark-Willem Jansen wrote:
The version problems have been fixed by sending an e-mail to the bug
control server.
The BTS now gives a green light, only the bug is still present as an
excuse not to migrate elmer to testing.
There were a few issues with the BTS yesterday, so it
; From: a...@adam-barratt.org.uk
> To: markwil...@hotmail.com
> CC: debian-release@lists.debian.org
> Subject: RE: elmerfem not migrating to testing.
>
> On 13.03.2012 14:09, Adam D. Barratt wrote:
> > On 13.03.2012 13:57, Mark-Willem Jansen wrote:
> >> How can we fix
On 13.03.2012 14:09, Adam D. Barratt wrote:
On 13.03.2012 13:57, Mark-Willem Jansen wrote:
How can we fix this wrongly handle bug for elmerfem?
Assuming the assumptions in my previous paragraph are correct, by
removing the fixed versions. See
http://www.debian.org/Bugs/server-control#notfound
[Please don't full-and-top-quote]
On 13.03.2012 13:57, Mark-Willem Jansen wrote:
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.
Well, if it's not a bug in elmerfem, then it
rom: a...@adam-barratt.org.uk
> To: markwil...@hotmail.com
> CC: debian-release@lists.debian.org
> 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 [1]. According to the
&g
On 13.03.2012 11:35, Mark-Willem Jansen wrote:
There seems to be a problem with bug 652061 [1]. 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 s
6 matches
Mail list logo
