Related: https://pagure.io/koji/issue/426
We support arbitrary btypes, not just legacy.
1 new commit added
This will cause the next check to give a misleading error if the btype is known. I don't think we need to add this. The check after that (if btype not in self.typeinfo) should be sufficient to validate btype value. Note that the keys in self.typeinfo are themselves validated in prep_build().
rebased onto 29859e61112052a5c8ffc08cf4eeaf760799f6fe
rebased onto 408d9406a2c718c2840d7b47689cf0c1f92e8d38
rebased here with minor fix added
https://github.com/mikem23/koji-playground/commits/pagure/pr/446
Looks ok apart from the needing to move the open() call
+1
Commit c1d8ca8e fixes this pull-request
Pull-Request has been merged by mikem
Related: https://pagure.io/koji/issue/426