Red Hat Bugzilla – Bug 178715
total download transaction summary ignores already downloaded rpms
Last modified: 2014-01-21 17:53:27 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Fedora/1.7.12-1.5.1
Description of problem:
The yum download process statistics don't take into account that some packages might alread be downloaded (eg from a fast private mirror, or another machine that is getting rsync from etc). This gives an impression that it might have to do a large download, when it may even have all the files downloaded through some other method (eg local/private mirroring/downloading).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum update
2. kill the update half way though the numner of packages it needs to download
3. yum update
Actual Results: Initial summary showed eg 448M, 286 packages.
Second summary showed the same.
Expected Results: Download size and count of already downloaded packages should reduce the above values.
Summary could be like:
=== (umm need to fit nicely in w=80)
Install 11 Packages(s) (25M). (Download of 6 packages (11M) needed.
Update 275 Packages(s) (420M). (Download of 85 packages (63M) needed.
Do download (y) or (n) [(d) download only - new item!]
y or d
Also check disk just before each download to avoid downloading / overwriting files that appear between start of yum download and starting a particular file. Currently, an ftp or rsync that happens between the beginning of yum downloading packages and the yum download means that a rpm may be erased if yum gets to that same package. The file is erased and redownloaded from the yum mirror (at slower speed and not a free download).
When attempting to run yum from the cache (yum -C update), errors such as this
logwatch - 7.2.1-1.fc5.noarch: Caching enabled but no local cache of
The file does exist, but notice the // at the begining of the file path. Could
this be the reason yum fails to detect packages that are already downloaded?
no, it's not.
multiple slashes are allowed by the posix specification.
The packages are checked for validity at the download step and if they're
corrupted/not complete, then they could be downloaded. Think of it as the
amount that may need to be downloaded.