just a stabilization request Reproducible: Always
Any problems with CCing arches in a week or so? I am not sure if maybe jump from 0.18 to 0.19 is risky, I have been running this version for some time and still didn't see any issue... but :| Thanks
the tracker bug has packages known to have issues, so once those are sorted, shouldn't be a problem stabilizing
If I don't misremember, the change causing the regressions that are tracked at that bug report was reverted in 0.19.1 :/
@vapier, just confirmed that original problem that lead to lots of build failures due some warnings being treated as errors in 0.19 was fixed 0.19.1 and it's still fixed in 0.19.3. On the other hand, we are still affected by problems like this -> bug 512624 And could probably be many more cases still not reported until some user tries to recompile the potentially affected package. I think that the GETTEXT_MACRO_VERSION mismatch problem also affected us a bit in the past with 0.17 -> 0.18 bump (I think at least systemtap was affected at that time) and I am unsure if maybe something could be done in autotools.eclass to prevent that in the future maybe sedding the value when eautoreconf is run... but I am not sure as gettextize is provided by upstream to migrate to newer versions and, then, I guess more stuff than sedding is needed :|
Arches please test and mark stable =sys-devel/gettext-0.19.3 with target KEYWORDS: alpha amd64 arm ~arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~amd64-fbsd ~sparc-fbsd ~x86-fbsd
Stable for HPPA.
amd64 stable
arm stable
x86 stable
ia64 stable. Émeric
+ 04 Feb 2015; Pacho Ramos <pacho@gentoo.org> gettext-0.19.3.ebuild: + ia64 stable, bug #528242 by Émeric Maschino +
ppc stable
ppc64 stable
sparc stable
alpha stable. All done.
