If it's too hard to stabilize, we should try to drop the package from gnome 3.8 stabilization that will need this but, otherwise, would be nice to have (since the major breakers were moved to 1.14 if I don't misremember)
why exactly is automake-1.13 *necessary* to make gnome-3.8 stable ? the automake-1.13 bug lists quite a lot broken packages many of which are not even fixed in unstable let alone pushed to stable
Looks like newer versions of gnome-extra/activity-log-manager (will CC jlec as he did the changes, if too hard we probably could go with older versions or completely skip it) Regarding the tracker, most of its blockers are AM_CONFIG_HEADER and AM_PROG_CC_STDC related that should be moved to 1.14 tracker instead
***** automake ***** ***** PWD: /var/tmp/portage/gnome-extra/activity-log-manager-0.9.7/work/activity-log-manager-0.9.7 ***** automake --add-missing --copy configure.ac:13: error: require Automake 1.13, but have 1.12.6 That's why.
(In reply to SpanKY from comment #1) > the automake-1.13 bug lists quite a lot broken packages many of which are > not even fixed in unstable let alone pushed to stable automake-1.13.2 had AM_CONFIG_HEADER as a fatal error in favour of AC_CONFIG_HEADERS, and then again non-fatal in 1.13.4 which is asked to be stabilized here and if you look more closely to the list of reported bugs open in the Tracker: https://bugs.gentoo.org/showdependencytree.cgi?id=451744&hide_resolved=1 you'll find out 99% of them are about AM_CONFIG_HEADER which isn't anymore fatal, but will be in future (was it 1.14 or 2.0, can't remember now) so based on the Tracker, stabilization would be possible
(In reply to Samuli Suominen from comment #4) SGTM then
Stable for HPPA.
amd64 stable
arm stable
x86 stable
alpha stable
ia64 stable
ppc stable
ppc64 stable
sparc stable
Drop arches that will go to testing only