On Mon, Nov 12, 2018 at 11:50 AM Randy Barlow <bowlofeggs@xxxxxxxxxxxxxxxxx> wrote: > > On Mon, 2018-11-12 at 09:04 -0500, Neal Gompa wrote: > > It is not. Arguably, this check should be blocking across the board. > > I > > personally would rather have this check earlier than Bodhi (mark > > builds in Koji as failed if they aren't installable), but that > > appears > > to be a thing we can't do. > > Sometimes builds depend on other builds, so this would not always be > possible. Bodhi is a good place to check things like this, because it > is the first time you have an opportunity to express "these builds ship > together". > That's not actually possible. Builds depending on other builds already fail today without Koji overrides being done first. > It would be nice if there were a way to express this earlier, such as > Pagure PRs. How would we do this? Scratch build IDs would need to be identified somehow, and the builds would need to be captured for this use. This is actually something I've been doing for packages I personally build on COPR, so it's not particularly difficult to implement, provided we can grab repository configs from koji for a scratch build and pull the RPMs in and do the dep check and the install check. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
