On Sat, May 9, 2015, at 12:22 PM, Colin Walters wrote: > Hi, > > During the Test day (and before), several people noted this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1219871 > > It now has a patch. I tested it with a local tree compose. It's nominated now for Blocker/FE. So I was initially blocked from doing a build of this by: https://bugzilla.redhat.com/show_bug.cgi?id=1220938 I only realized later that I didn't have to wait for man-db to go stable, I could have tagged it in as an override, which would have made this less of a chain of blockers, but oh well. The thing is - this can't be easily fixed in an update because you really want things like NFS to work when you first boot. Options I see: - Pull it in now (needs rel-eng approval) - If we're talking about doing Atomic images every 2 weeks, then why not just wait one stable cycle and pull in the fix, and do all of the AMIs/mirroring/etc then? I'm not sure how hard this would be, but we could just say "Atomic images are coming in 2 weeks" - Live with it...would be embarrassing but not completely the end of the world _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
