[dak/master] dak init-db: properly initialize suite_architectures

[Raphael Hertzog <hertzog@debian.org>]

Using database.get_suite_architectures() here makes no sense since that
function uses the table that we're trying to fill. Instead we should
assume that all suites support all architectures. And it's up to the
admin to adjust the set afterwards if needed.

Signed-off-by: Raphael Hertzog <hertzog@debian.org>
---
 dak/init_db.py |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/dak/init_db.py b/dak/init_db.py
index e1f1bce..fcd108a 100755
--- a/dak/init_db.py
+++ b/dak/init_db.py
@@ -131,7 +131,7 @@ def do_suite():
         projectB.query("INSERT INTO suite (suite_name, version, origin, "
                        "description) VALUES ('%s', %s, %s, %s)"
                        % (suite.lower(), version, origin, description))
-        for architecture in database.get_suite_architectures(suite):
+        for architecture in Cnf.SubTree("Architectures").List():
             architecture_id = database.get_architecture_id (architecture)
             if architecture_id < 0:
                 utils.fubar("architecture '%s' not found in architecture"
-- 
1.5.6.5