Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to figure out why exactly this isn't working correctly. Currently there is no way supported by yum to set a milestone in time (install all packages up to point in time T). To get around this for our QA purposes, we would like to use the yum-downloadonly plugin. We are able to use the plugin in tandem with yum update to pull down all packages that would be included in the update.

However, when we try to run rpm -ivh *.rpm where all of the files have been downloaded, there are tons of errors about dependencies. If you force it, you end up getting tons of errors on the next boot. Trying to do a yum localinstall produces similar problems.

Is there an easy way to do this that I'm not quite getting? Is there any way to preserve the order to install as yum would do? It's not like I'm missing packages - downloadonly pulls down everything a normal update would, including all dependencies.

share|improve this question
up vote 3 down vote accepted

After running yum -y update --downloadonly, instead of rpm -ivh *.rpm, try yum localupdate *.rpm.

share|improve this answer
Fantastic, that seems to work like a charm! Thank you! – Matthew Jun 1 '12 at 2:05

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.