You wouldn't by some chance be storing your [updates] and [base] in seperate config files would you? Indeed, yum should (and generally does) consult all the available repositories when resolving dependancies. So, something odd must be going on. Do your repositories have the "headers" directories in place? Have the repositories had yum-arch run against them? --Chris On Sat, 26 Jun 2004 20:15:33 -0700, Garrick Staples <garrick@xxxxxxx> wrote: > > On Sun, Jun 27, 2004 at 05:56:58AM +0530, Sanjay Arora alleged: > > I recently tried to update, using yum update, a RH9 server, where yum > > reported three-four missing dependencies. These dependencies were of > > course missing from the [updates] base url but were available in the > > [base] base url. > > > > How do I get yum to look in the [base] url after it does not find them > > in the [updates] url. > > Assuming I'm understanding your correctly, this is exactly what yum does. It > will satisfy dependencies for packages in any repo from any other repo. > > > > Same thing would happen when I create an additional mirror from > > fedoralegacy.org. The updates issued after EOL would reside in a > > different url in the repository. If a dependency is not found there yum > > needs to go back to the [updates] url and again if it is not found there > > yum needs to satisfy it from the [base] url. > > > > I am assuming yum would not force the repository maintainer to the task > > of maintaining a single repository url getting updates from all these > > sources? or would it? > > > > What is the best practice in this case, keeping in mind, all updates > > must happen from the local repository at one go and the job of > > repository maintainence is to be seperate. > > I'd have to guess you have an rpm installed or in a repo that has deps that > can't be satisfied. > > -- > Garrick Staples, Linux/HPCC Administrator > University of Southern California > > > > noname - 1K > noname - 1K Download >
