Hi,
I'm looking for some documentation (or advice) on how to best manage a -mostly- upstream binary compatible CentOS installation.
I enabled the rpmforge repository in order to install a few packages not available in base/updates/centosplus. But, now when I do a "yum check-update" yum wants to update a whole stack of packages because it's found newer versions at rpmforge.
Is there a way to tell yum to only pull updates from rpmforge for packages that were initially installed from rpmforge?
I've been using the includepkgs directive with some success; although installing a package that has a dozen or so dependancies (from rpmforge) quickly makes this method seem not so elegant.
Is there a better way? I'm going around in circles a bit with the official yum documentation.
Obviously what I'm aiming for is to be as close to 100% binary compatible with the upstream provider as possible, and to also easily pull the latest updates for all my packages.
Thanks in advance, I hope you're all having a good week.
Regards,
LC.
Lucas Chan wrote:
Is there a way to tell yum to only pull updates from rpmforge for packages that were initially installed from rpmforge?
Disable the rpmforge repos by default, then only enable it if you want to update packages you have installed from there. You can then enable it with the command line option to yum.
Not sure there is another way, but I would like to hear it too if it is :)
Is there a way to tell yum to only pull updates from rpmforge for packages that were initially installed from rpmforge?
Disable the rpmforge repos by default, then only enable it if you want to update packages you have installed from there. You can then enable it with the command line option to yum.
This doesn't quite solve the problem, I think. Please stab me with a rusty spork if I'm wrong. :)
Following your method, when I enable rpmforge and then do a "yum update" yum will still try to update packages that were originally installed from base/updates with newer ones that it's found in rpmforge.
Using the "syslinux" package as an example, it exists in the base/ updates repo. A newer version of it also exists in the rpmforge repo. When I do "yum update --enablerepo=rpmforge" it will try to update syslinux with the rpmforge version. I suppose this is somewhat-expected behaviour, but it's not desirable (for me) because the syslinux package will no longer be considered 100% binary compatible.
Again, the goal is to be as close to 100% binary compatible with the upstream provider as possible.
I want some way of telling yum to only download updates from rpmforge for packages that were installed from rpmforge, not packages that were installed from base/updates.
As I alluded to in my original post, this seems possible (but clumsy) by using the "includepkgs" directive to maintain a list of what packages rpmforge should be used for. But, I was hoping there was a better way?
LC.
Lucas Chan wrote:
Following your method, when I enable rpmforge and then do a "yum update" yum will still try to update packages that were originally installed from base/updates with newer ones that it's found in rpmforge.
Saw your other update that should provide a better method. But the method I had in mind was that you would never do a "yum update" with rpmforge enabled. You would have been stuck with a manual "yum update package" for each RPM you had installed from rpmforge. So clearly not an ideal method and a manual process.
The ProtectBase approach is clearly better. Thanks for that link :)
Ref. http://wiki.centos.org/PackageManagement/Yum/ProtectBase
Is there a way to tell yum to only pull updates from rpmforge for packages that were initially installed from rpmforge?
I accidentally stumbled across a good solution after following a link to the CentOS SVN Wiki page (which someone kindly posted to this list earlier).
http://wiki.centos.org/PackageManagement/Yum/ProtectBase
"The purpose of the protectbase plugin is to protect certian repositories from updates from other repositories. Repositories that are to be protected will not be updated by newer files from non protected repositories. This plugin is recommended for anyone who routinely enables 3rd party repositories, as these non-CentOS repositories may update certian system files, potentially causing your CentOS installation to become unstable."
Wicked!
I thought I should post it here in case someone searches the list with the same problem.
Thanks for your help, Morten. I hope this is useful for you?
LC.
-
Lucas Chan -
Morten Torstensen