From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

Description of problem:
When rebuilding autoconf on a barebones chrooted box, I noticed that apt-get build-dep for autoconf213 didn't pull in m4 .  However, the build of autoconf213 bails early on if m4 isn't included.

m4 >= 1.1 should go into the build-dep list.

Version-Release number of selected component (if applicable):
autoconf213-2.13-9

How reproducible:
Always

Steps to Reproduce:
1. set up super barebones install
2. set up apt, rpm-build
3. apt-get source autoconf213
4. apt-get build-dep autoconf213
5. as the non-root account, rpmbuild --rebuild autoconf213  

Actual Results:  the build bailed with a message that m4 >= 1.1 was missing.

Expected Results:  the apt-get build-dep should have seen the m4 dep and grabbed m4 for the build.

Additional info:

This makes it go all perfectly.

--- autoconf213-rhes4/autoconf213.spec  2004-09-23 14:12:40.000000000 -0700
+++ autoconf213-ts/autoconf213.spec     2006-02-16 03:00:41.000000000 -0800
@@ -17,7 +17,7 @@
 Patch8:                autoconf-2.13-make-defs-62361.patch
 Patch9:                autoconf-2.13-versioning.patch
 Requires:      gawk, m4, mktemp, perl, textutils
-Buildrequires: texinfo
+Buildrequires: texinfo m4 >= 1.1
 BuildArchitectures: noarch
 BuildRoot:     %{_tmppath}/%{name}-%{version}-root