perl-DBI has a buildreq of perl(SQL::Statement) >= 1.28, which is used in the test suite if available. However, SQL::Statement itself requires DBI, so this creates a circular build dependency, which will be a problem when we come to build everything for perl 5.16. Suggested fix is to not buildrequire SQL::Statement when bootstrapping:

diff --git a/perl-DBI.spec b/perl-DBI.spec
index 0dc2f0c..3039553 100644
--- a/perl-DBI.spec
+++ b/perl-DBI.spec
@@ -38,8 +38,10 @@ BuildRequires:  perl(RPC::PlClient) >= 0.2000
 # RPC::PlServer is optional
 BuildRequires:  perl(RPC::PlServer)
 BuildRequires:  perl(Scalar::Util)
-# SQL::Statement is optional
+# SQL::Statement is optional, and it requires DBI
+%if 0%{!?perl_bootstrap:1}
 BuildRequires:  perl(SQL::Statement) >= 1.28
+%endif
 BuildRequires:  perl(Storable)
 BuildRequires:  perl(Symbol)
 BuildRequires:  perl(threads)