Description of problem:
Version-Release number of selected component (if applicable):
4 repeat failures
Steps to Reproduce:
1. Run up2date
2. Get list of updates
3. Check for dependencies
Shows only 131k files to d/l. 30 minutes later, still stuck on
Completion of updates.
I have broadband, so d/l should complete in less than 1 minute.
Same problem here. First its shows that only 192kb of files will be
downloaded. This, even though there are dozens of updates, from
kernel thru gcc, since FC2T1 was released a few days ago (perhaps very
prematurely, even for testers). When it gets to computing the package
dependencies, it just hangs.
When run from the command line, I get a completely useless traceback
error from (ugh!) python. I've attached it as a file.
There are so many things new bugs introduced with FC2T1 (vs. say RH8)
that I don't even want to start filing bug reports against it until I
am completely up2date. But I am quickly burning out.
Created attachment 97685 [details]
up2date and/or python chucking its cookies
Maybe I better ask... Just how long should it take to test the
packages and resolve inter-dependencies ??
After restarting the Up2date process a few times, it appears to
downloading something from the net, but I don't get any progress
indicated on the progress bar.
I've let it run for about 20 minutes this time. My hub indicates
traffic to the port going to my test machine, but still seems to be
Is it still bad with test2, or latest rawhide?
Have not installed test2 yet. I have d/l it, but haven't found the
time to do a fresh install on the test machine. I'll try this weekend
and let you know the progress.
Rick, Les -- did you test with current Rawhide?
Installed FC2-T2 this weekend, and had issues with up2date. Was not
able to launch from taskbar, but would launch from terminal session.
There were about 14 packages that failed key signatures.
I've been working wierd hours for the last 3 days and haven't had a
chance to continue testing, but will try a re-install to see if I get
different results. It could be the server was too busy, and I didn't
get a good connection to the server. Up2date did take almost 2 hours
to complete the d/l process before it started the actual update.
fyi, in installed a fresh test3 install may 3rd and initial up2date
usage to install updates seemed to work fine. Sorry didn't time how
long it takes.
Did a second round of updates this evening, 34 updates, on a k6-2 400
MHz 192 Megs ram. Its taking a few minutes to do the dep resolution on
this system, but certaintly not 10 minutes. I'm watching the up2date
process in top, and its keeping the cpu active so whatever time its
taking seem legit.
I shelved the Athlon for further testing and replaced it with a
Celeron 633 and 128MB ram. The install was standard, and without
errors. Up2date did run from the taskbar, and the dependencies process
completed in about an hour. Moving to the "Installing packages"
started, but after an hour of thrashing the hard drive with no
progress, I had to pull the plug on it.
Tried up2date selecting all packages with same stopped responding.
Tried again with only 2 packages selected, ok. Will try again to
select all packages once I get below 16 packages available.
This behaviour has been mitigated with the 4.4.x releases.
Closing since behavior has been mitigated, and up2date has been replaced by
pirut/pup on the still fully supported FC releases, FC5 and FC6.