$summary
arm done
arm64 done
x86 stable
hppa/ppc/ppc64 stable
amd64 done
We probably shouldn't stabilise grep 3.5 on sparc given it doesn't pass tests due to a real issue. See bug 768135 (https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9c56995f410c33050133c71a45da78f4d3ee9868). TL;DR: there's a gnulib set of changes which we need in 3.5 which are a bit much for a backport. Stabilising grep 3.6 on sparc would work but I don't know if the team considers it ready yet, as it's a bit newer.
(In reply to Sam James from comment #6) > We probably shouldn't stabilise grep 3.5 on sparc given it doesn't pass > tests due to a real issue. See bug 768135 > (https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=9c56995f410c33050133c71a45da78f4d3ee9868). > > TL;DR: there's a gnulib set of changes which we need in 3.5 which are a bit > much for a backport. Stabilising grep 3.6 on sparc would work but I don't > know if the team considers it ready yet, as it's a bit newer. Like I told you in IRC, I am fine with sparc stabilizing grep-3.6 instead of 3.5.
(In reply to Lars Wendler (Polynomial-C) from comment #7) > (In reply to Sam James from comment #6) > > We probably shouldn't stabilise grep 3.5 on sparc given it doesn't pass > > tests due to a real issue. See bug 768135 > > (https://gitweb.gentoo.org/repo/gentoo.git/commit/ > > ?id=9c56995f410c33050133c71a45da78f4d3ee9868). > > > > TL;DR: there's a gnulib set of changes which we need in 3.5 which are a bit > > much for a backport. Stabilising grep 3.6 on sparc would work but I don't > > know if the team considers it ready yet, as it's a bit newer. > > Like I told you in IRC, I am fine with sparc stabilizing grep-3.6 instead of > 3.5. I mentioned in -dev that I unfortunately lost my backlog, so I didn't see that! Thank you :)
Obsolete in favour of bug 777963.