From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020314 Description of problem: If a previously started up2date session is aborted for any reason, it does not check to see if packages selected for download are already present, forcing all packages to be redownloaded. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Run up2date 2. Abort session, experience crash, etc. 3. Restart up2date and download everything again Expected Results: Up2date should check for presence of packages in local spool directory prior to downloading. Additional info: This is more of an issue for modem users than anything else, but it would save some bandwidth, especially given how its so easy to accidently abort a session if you're doing anything else on the system and up2date pops up a window with a cancel dialog right as you hit "enter" to get a file list or something.
Hmm, well. up2date is supposed to be doing this (and does as best I can tell). I'll take a look and verify that there isnt something wrong in the newest versions preventing this.
Can't get up2date to re-use already downloaded packages either. It aborted on a missing GPG signature on today's imlib-devel-1.9.13-3.7.x.i3 and I had to disable GPG sig checks and retry "update -u". It started to download from the beginning, ignoring the already downloaded but new 40+ packages in /var/spool/up2date. $ rpm -q up2date up2date-2.7.65-7.x.3 $ cat /etc/redhat-release Red Hat Linux release 7.2.93 (Skipjack)
I just see today's Skipjack-beta2 up2date update is supposed to fix this: * Thu Apr 11 2002 Adrian Likins <alikins> 2.7.76 - fix the "packages always get redownloaded bug"
Seems to work now, at least for up2date. I haven't determined if up2date-gnome still has the problem or not.
Verified as working (2.7.76-7.x.3 and 2.7.77-7.x.3, both CLI and GUI).