On Tue, 2014-12-23 at 15:39 -0700, Mike Ruckman wrote:
I'd be for blocking on a broken netinst (like your example), but
if
the repos are the same used for image creation this shouldn't really
be an issue, right? (Yeah, I know I used the "S" word :p ) AIUI
things would break in other places if this particular issue was to
come up. Is my understanding correct?
Not entirely, no, because the netinst can do much more than any
offline install image, let alone the release-blocking ones. The
release-blocking images cover the environment groups for Workstation,
Server, Cloud, and the KDE desktop, pretty much. netinst can install
any environment group listed in comps, with any of its optional
package groups.
In practice I suspect we'd only be likely to block on the netinst not
being able to install one of the env groups that corresponds to a
release blocking image, and in practice that would be unlikely to
happen without breaking that image, yeah (though there's probably some
corner case or other, e.g. where there's a bug in a package that's
part of the Workstation env group but is stripped from the live image
for space reasons, or whatever).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net