On Thu, Nov 10, 2016 at 07:09:39PM -0800, Adam Williamson wrote:
It's also worth noting that there's a possible scenario where
completely nerf the OS X install here. It's a fairly *unlikely*
scenario - the user would have to manually disable journalling on the
macOS partition - but it is *possible*. For instance, they may have
disabled it so they could write to the partition in Linux, for some
reason, and then forgotten to re-enable it. So this bug, at least in
that case, can be even worse than just 'Fedora doesn't boot'. It can be
'the Fedora installer ate my OS X kernel'.
Yeah -- that's what pushed me over the edge on this.
That and I'm not *super* keen on the practice of removing blocker
criteria whenever we hit them....
I don't really *like* the thing where we suddenly decide at the
the release cycle that we don't like a criterion that *just happens* to
be standing in the way of release after all, and magically say it's not
a criterion any more. It's crappy process. But we have done it before
Yeah, that :)
Fedora Project Leader