This bug has been opened now so that I can setit up to block the openrc stabilization tracker. When you are ready to stabilize a version of mdadm >= 3.1.1-r1, please use this bug as the stabilization request. Thanks, William
the grow regression doesnt sound like something we want to stabilize (Bug 301396)
Can we go with 3.1.1-r1? I _also_ hit #322711 so I'd rather not see this reach stable just yet...
I think #324185 may also be a serious bug in 3.1.2
(In reply to comment #3) > I think #324185 may also be a serious bug in 3.1.2 > Looks like it already fixed in 3.1.3, as described in comment 9, bug 324185.
*mdadm-3.1.3 (07 Aug 2010) 30 days since addition to the tree - time for stabilization? or is #331745 blocking?
i think we've squashed everything with 3.1.4. so once that hits 30 days, let's run for it.
*mdadm-3.1.4 (04 Sep 2010) 04 Sep 2010; Mike Frysinger <vapier@gentoo.org> -mdadm-3.1.2.ebuild, +mdadm-3.1.4.ebuild: Version bump #335979 by Samuli Suominen. 30 days gone. :)
Ok, so what's holding back mdadm-3.1.4 still? Just curious, since it blocks openrc/baselayout2 stabilization.
people dont actively watch every bug
Ok on amd64. (*)sed and dodoc need die.
die on dodoc is stupid
(In reply to comment #11) > die on dodoc is stupid > I'm not here to judge if it is stupid or not. If I'm not mistaken with EAPI<4 all do* functions require 'die'. I have only reported, but is the maintainer to decide ;)
and the decision to make erroneous do* related doc commands fatal in newer EAPIs is also stupid
x86 stable
ppc stable
Such QA problems don't affect stabilizations. amd64 done. Thanks Agostino
With this version lvm2 shows different number of blocks in vg raid disk and as result lvm2 is not working, i need to recreate it. May i need to change mdadm conf? With 3.0 all works ok. amd64
Stable on alpha.
Stable for HPPA.
ppc64 done
Tested on SPARC64, no new regressions from mdadm 3.0.
Sparc/ia64, what is your status for this bug? Thanks, William
ia64/sparc stable, closing