On 03/19/2010 03:41 PM, John Reiser wrote:
>> It's an http install to a local server, and there is no access during
>> that stage (after is has all of the repodata files) until it starts
>> fetching package headers. So, it seems like filing a bug is in order.
>> Anaconda or yum?
>
> Anaconda, the
> "OP" == Orion Poplawski writes:
OP> The install spends a long time displaying "Checking dependencies in
OP> packages selected for installation" with no movement of the progress
OP> bar.
My kickstart installs used to sit showing that for ages; I ended up
using pungi -G to gather an install
> It's an http install to a local server, and there is no access during
> that stage (after is has all of the repodata files) until it starts
> fetching package headers. So, it seems like filing a bug is in order.
> Anaconda or yum?
Anaconda, the program that you invoked. If anaconda can pass th
On 03/19/2010 01:57 PM, John Reiser wrote:
>> ... stripped down kickstart server install of about 389 packages:
>
>> enablefilesystems 3:10s
>> postselection24:27s
>> installpackages 14:30s
>
>> The install spends a long time displaying "Checking dependencies in
>> packages selecte
> ... stripped down kickstart server install of about 389 packages:
> enablefilesystems 3:10s
> postselection24:27s
> installpackages 14:30s
> The install spends a long time displaying "Checking dependencies in
> packages selected for installation" with no movement of the progres
I don't know if it is too early to do install timings (due to debugging
be on in the kernel, elsewhere?) but here are the longest steps from a
fairly stripped down kickstart server install of about 389 packages:
F-13:
enablefilesystems 3:10s
postselection24:27s
installpackages
