[master] Two ways how to fix the #1008788 blocker

Brian C. Lane bcl at redhat.com
Tue Sep 17 23:37:04 UTC 2013


On Tue, Sep 17, 2013 at 11:38:48AM +0200, Vratislav Podzimek wrote:
> My commit 5634449a1645343f3be340aa39faebdd5436ab35 causes that the TUI
> ProgressHub is not scheduled/run because it provides no spokes and the result is
> that the actual installation is skipped, because it is triggered by the hub.
> There are two ways how to fix this issue:
> 1. always schedule the TUI ProgressHub
> 2. make ProgressHub a standalone spoke
> 
> I'm for 2. because the ProgressHub really is not a hub. It outputs a lot of text
> to the standard output and thus it cannot provide any spokes as those would be
> rolled off soon after the installation begins. However, 1. is much shorter and
> probably less invasive.

I agree, 2 is the better way to do this. I've tested this with text
kickstart and livemedia-creator. Ack.

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 482 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/anaconda-patches/attachments/20130917/00a744cd/attachment.sig>


More information about the anaconda-patches mailing list