From a0418aa4a0c60deac2107ec9cc400f03100703b7 Mon Sep 17 00:00:00 2001
From: Stephan Kulow <coolo@suse.de>
Date: Tue, 29 Mar 2022 13:03:21 +0200
Subject: [PATCH] Use all staging archs in adi projects

This replaces #1304 with a more brute force approach to fix not only
32bit libs but all failures we see on i586. We waste so much energy
retrying failed builds, it's really not worth it not trying i586 on
adi.
---
 osclib/stagingapi.py | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/osclib/stagingapi.py b/osclib/stagingapi.py
index 92f2d9cd..e8392e6e 100644
--- a/osclib/stagingapi.py
+++ b/osclib/stagingapi.py
@@ -1431,12 +1431,16 @@ class StagingAPI(object):
           {repository}
             <path project="{self.cstaging}" repository="standard"/>
             <path project="{self.project}" repository="standard"/>
-            <arch>x86_64</arch>
           </repository>
           {images_repo}
           {containerfile_repo}
         </project>"""
 
+        root = ET.fromstring(meta)
+        repository = root.find('.//repository[@name="standard"]')
+        for arch in self.cstaging_archs:
+            a = ET.SubElement(repository, 'arch')
+            a.text = arch
         url = make_meta_url('prj', name, self.apiurl)
         http_PUT(url, data=meta)
         # put twice because on first put, the API adds useless maintainer