Description of problem: Please make libuser automake 1.10-aware, because currently it isn't (try to run aclocal && automake in the libuser sources). Version-Release number of selected component (if applicable): libuser-0.55-1 How reproducible: Everytime, see above. Expected results: libuser automake 1.10-aware
I'm not running complete rawhide here, could you please briefly describe what's the actual problem? (e.g. "the package doesn't build under rawhide"). Thanks.
libuser-0.55 # automake configure.in:5: version mismatch. This is Automake 1.10, configure.in:5: but the definition used by this AM_INIT_AUTOMAKE configure.in:5: comes from Automake 1.9.6. You should recreate configure.in:5: aclocal.m4 with aclocal and run automake again. configure.in: required file `admin/ylwrap' not found configure.in: `automake --add-missing' can install `ylwrap' libuser-0.55 # aclocal libuser-0.55 # automake --add-missing docs/reference/gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL docs/reference/Makefile.am:53: `docs/reference/gtk-doc.make' included from here docs/reference/gtk-doc.make:43: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:53: `docs/reference/gtk-doc.make' included from here docs/reference/gtk-doc.make:136: ENABLE_GTK_DOC does not appear in AM_CONDITIONAL docs/reference/Makefile.am:53: `docs/reference/gtk-doc.make' included from here configure.in: installing `admin/ylwrap' libuser-0.55 # autoconf libuser-0.55 # I'm just wondering about the warnings and that I've got to use --add-missing. Maybe this isn't a bug for you, then it's also okay. Just noticed this. IMHO on devel systems, the files should be created using the latest automake/autoconf version to avoid such a "version mismatch". But it's up to you of course.
I'm sorry about the late response. * admin/ylwrap is missing because automake 1.10 always uses admin/ylwrap, but automake 1.9 didn't use it for libuser * The version mismatch warnings are caused by incorrect command ordering: it should be "... aclocal; autoconf; autoheader; automake". I usually rely on the Makefile rules to run the necessary tools in order; if that isn't enough, CVS contains an autogen.sh (which is not shipped in the released tarball, though). * The version of autotools used to generate a tarball is completely independent of the version of autotools installed on the system the tarball is compiled. Unless the rpm needs to patch the autotool input files, there is therefore no need to use the latest autotool versions. libuser will switch to the F7 autotool versions around the time F7 is released.