Description of problem:
gnome-autogen.sh is looking for now-out-of-date components, due notably to the new automake-1.11 package.

Version-Release number of selected component (if applicable):
$ rpm -qf /usr/bin/gnome-autogen.sh 
gnome-common-2.26.0-1.fc11.noarch
$ egrep gnome-common\|automake /var/log/rpmpkgs
automake-1.11-2.fc11.noarch.rpm
automake14-1.4p6-18.fc11.noarch.rpm
automake15-1.5-26.noarch.rpm
automake16-1.6.3-15.noarch.rpm
automake17-1.7.9-12.noarch.rpm
gnome-common-2.26.0-1.fc11.noarch.rpm

How reproducible:
Completely consistently.

Steps to Reproduce:
REQUIRED_AUTOMAKE_VERSION=1.9 . gnome-autogen.sh
  
Actual results:

automake 1.9 and 1.10 are gone, so...

checking for automake >= 1.9...
  testing automake-1.10... not found.
  testing automake-1.9... not found.
***Error***: You must have automake >= 1.9 installed

Expected results:

"duh"

Additional info:

gnome-autogen.sh uses this test for a valid automake version.

case $REQUIRED_AUTOMAKE_VERSION in
    1.4*) automake_progs="automake-1.4" ;;
    1.5*) automake_progs="automake-1.10 automake-1.9 automake-1.8 automake-1.7 automake-1.6 automake-1.5" ;;
    1.6*) automake_progs="automake-1.10 automake-1.9 automake-1.8 automake-1.7 automake-1.6" ;;
    1.7*) automake_progs="automake-1.10 automake-1.9 automake-1.8 automake-1.7" ;;
    1.8*) automake_progs="automake-1.10 automake-1.9 automake-1.8" ;;
    1.9*) automake_progs="automake-1.10 automake-1.9" ;;
    1.10*) automake_progs="automake-1.10" ;;
esac

A temporary hack workaround is to symlink both automake-1.11 and aclocal-1.11 to equivalent 1.10 names.