On Wed, Nov 19, 2014 at 03:16:19PM -0500, Colin Walters wrote: > I tested this one, it boots. However, I screwed up with: > https://git.fedorahosted.org/cgit/fedora-atomic.git/commit/?h=f21&id=70c9fbf49d85d183405b7e39753a79e1797dc0ac > Fixed by: > https://git.fedorahosted.org/cgit/fedora-atomic.git/commit/?h=f21&id=5d545a55223e024db28d393e678862d3753a2c6d > Basically that AMI is OK, but the next one will be broken unless it picks up the latest commit there. Currently, what causes a compose to pick up a given commit? -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
