FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would run 'yum clean all' before using a new yum.conf. Also, I've sometimes seen yum leave behind the old cache directories after I've changed repositories - after you've successfully run yum with the new conf it's worth going into /var/cache/yum and deleting any orphan cache directories.
If you define a repository and download packages from it these go into a directory in /var/cache/yum with the same name that the repository has in yum.conf. If you then delete the repository in yum.conf then the directory in /var/cache/yum is still there, but isn't going to do anything any more, so it's 'orphaned'. Changing the URLs is OK, as you are doing. You'll only see this problem if you decide to get rid of one of the repositories later.
BTW, is it's a good idea to use the variables ($basearch, $releasever), rather than specify the arch and version. Using variables means that the yum.conf will be valid if you upgrade to a new version of Fedora, or copy configuration on to another machine.
On running
# yum clean all
Gathering header information file(s) from server(s)
Server: Fedora Core 2 - i386 - Base
Server: Fedora.us Extras (Stable)
Error - /var/cache/yum/fedora-stable/header.info cannot be found
Please run yum in non-caching mode to correct this header.
Please advise how to run yum in non-caching mode. What is 'non-caching mode'
That sounds like yum has not been run with this repository before, so there is nothing to 'clean'. So don't worry about it. Run 'yum list' to update the "header" files without actually triggering any updates. If the 'yum list' runs OK then everything is fine.
It's true that Livna packages don't necessarily depend on Testing or Unstable - I don't currently have those repositories in my yum.conf to get Livna packages. On the other hand, I've seen Livna packages that do. I chose to keep the list short and take the chance because this machine is on a slow connection.
That sounds like yum has not been run with this repository before, so there is nothing to 'clean'. So don't worry about it. Run 'yum list' to update the "header" files without actually triggering any updates. If the 'yum list' runs OK then everything is fine.
Which will be erased later before running "yum list".
Quote:
[/b]It's true that Livna packages don't necessarily depend on Testing or Unstable - I don't currently have those repositories in my yum.conf to get Livna packages. On the other hand, I've seen Livna packages that do. I chose to keep the list short and take the chance because this machine is on a slow connection. [/B]
Noted with tks.
I will erase Livna Testing and Unstable before running
Don't worry too much about running 'clean'. It's a precaution, but the fact that you got a message basically saying that there was nothing to clean for a repository is fine. Clear error messages are not a feature of the current version of yum.
Again, it's a precaution to run 'yum list' once. It means that the header files will be downloaded or errors will show up without worrying about a bad upgrade or install. I tend to be cautious with a software management system until I've tested that it's working right.
This means that the URL was wrong (or is no longer active), so the next site in the list for that repository was used. You learn what the messages mean by experience :-)
As for the cache directories - all of those correspond to repository names in your yum.conf. If you decide to delete the repository entries that you've commented out, like "macromedia.mplug.org", then you might want to delete the corresponding directory. Nothing will happen if you don't, it's just good housekeeping.
Schmurff - there are various documents on yum, none of which give the complete story. It's really a technology still in development. Hopefully the next generation of yum will be ready for Fedora Core 3 and things will stabilise more after that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
