[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Anaconda threads and Yum with rpm backend



On Wed, 2012-12-12 at 13:27 -0500, Chris Lumens wrote:
> > It happens between somewhere late in the "Starting package
> > installation process" and installing the first package. I was not able
> > to pinpoint it better since RPM is not holding the chroot stable (it
> > is releasing it and acquiring as needed) and Python threads got
> > switched at inconvenient moments so my debug prints were telling me I
> > am chrooted and unchrooted at the "same time"..
> 
> > 1) Workaround the chroot in anaconda
> > - if we do this, Yum and RPM would loose the motivation to fix it at their side :)
> 
> Hah, I like it.
> 
> > - we will have to invent a pipe based protocol for progress and error
> > reporting + user's choices (bidirectional)
> 
> Yes, this is going to be difficult and was one thing I was really hoping
> to avoid having to do by going with threads in the first place.  I guess
> it could be done though.
> 
> > 2) Disable dictionary checks in password spoke
> > - the chroot will still happen, but it won't show
> > - obviously our password checking would get worse
> > - we would get some time to fix this for next release at the proper place
> 
> For F18, this is probably what we are going to have to do.  I don't
> think a lack of dictionary checks would be a blocker bug, but the
> current behavior probably is.  I don't see that we have enough time to
> do a proper fix for F18.
> 
> What about the missing icons and those sorts of problems?  Are they
> being caused by this same bug, and will they still be present if we go
> through with this?  It seems to me like they would.
Yeah, you are right, they are caused by that bug and would be still
present.

-- 
Vratislav Podzimek

Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]