Description of problem: Building RPM from the FC4 branch in the fedora CVS fails. Version-Release number of selected component (if applicable): rpm-4.4.1-21 How reproducible: Always Steps to Reproduce: 1. cvs co FC-4 2. cd rpm 3. make i386 Actual results: Build fails with an error message ending in the following: Making all in popt make[3]: Entering directory `/home/roozbeh/FC-4/rpm/rpm-4.4.1/popt' cd . && /bin/sh /home/roozbeh/FC-4/rpm/rpm-4.4.1/popt/missing --run aclocal-1.9 aclocal:configure.ac:90: warning: macro `AM_GNU_GETTEXT' not found in library cd . && /bin/sh /home/roozbeh/FC-4/rpm/rpm-4.4.1/popt/missing --run automake-1.9 --foreign cd . && /bin/sh /home/roozbeh/FC-4/rpm/rpm-4.4.1/popt/missing --run autoconf configure.ac:90: error: possibly undefined macro: AM_GNU_GETTEXT If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. make[3]: *** [configure] Error 1 make[3]: *** Waiting for unfinished jobs.... configure.ac:4: not enough arguments for AC_CONFIG_HEADERS make[3]: Leaving directory `/home/roozbeh/FC-4/rpm/rpm-4.4.1/popt' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/roozbeh/FC-4/rpm/rpm-4.4.1' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/roozbeh/FC-4/rpm/rpm-4.4.1' error: Bad exit status from /var/tmp/rpm-tmp.97529 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.97529 (%build) make: *** [i386] Error 1
It seems that this is actually a missing BuildReq on gettext-devel.
1) I can confirm this is just a missing BuildRequires on gettext-devel. 2) This bug is still present in FC4 (as it also has rpm-4.4.1-21). 3) Should I file a bug against FC4 to make sure this bug also shows up when querying on FC4 (just as I did before finding this report)? That report could be closed as a dupe right away, of course ... 4) Anyway, should be trivial to patch (which I still would be happy to do).
Changing Version to FC4, based on pebolle's comment.
OT: can't all testing bugs be automatically upgraded to their successor (test1->test2->test3->release) whenever a new test release and/or (just) the final release is available? At least, I assume that test releases are only (really) useful until the next (test) release.
*** Bug 164681 has been marked as a duplicate of this bug. ***
rawhide rpm.spec has this BuildReq.