This is a reopen of <a href="https://bugs.centos.org/view.php?id=8200">https://bugs.centos.org/view.php?id=8200</a> [<a href="https://bugs.centos.org/view.php?id=8200" target="_blank">^</a>]<br />
<br />
The composed tree still fails to produce a working image when built via Anaconda. <br />
<br />
Per walters, this is most likely because the compose script is using JSON that does not contain this update:<br />
<br />
<a href="https://github.com/CentOS/sig-atomic-buildscripts/pull/12">https://github.com/CentOS/sig-atomic-buildscripts/pull/12</a> [<a href="https://github.com/CentOS/sig-atomic-buildscripts/pull/12" target="_blank">^</a>]<br />
<br />
Per a Feb 17 chat with kbsingh in #centos-devel, it seems that his compose script is using a "community-stable" branch in the usptream SIG repo. This branch is not publicly visible. All SIG activity and modifications have been occurring in master.<br />
<br />
<a href="https://github.com/CentOS/sig-atomic-buildscripts">https://github.com/CentOS/sig-atomic-buildscripts</a> [<a href="https://github.com/CentOS/sig-atomic-buildscripts" target="_blank">^</a>]<br />
<br />
The action requested in this bug is to begin building the composed tree from master or to clearly establish with the Atomic SIG where, precisely, the JSON used for the public stable tree compose is supposed to live, and how changes can flow into it.
↧