Yum Configuration

Home » CentOS » Yum Configuration
CentOS 5 Comments

As it stands now (or at least that is what I think) when CentOS moves from one minor version to another (6.3 to 6.4)
the 6.3 version machines automatically pick up the upgrade and the next time you do yum upgrade all of the upgrades are applied.

This happens because in the repo configs (in our case) we have baseurl=ftp://yum.xx.xx.xx.xx/pub/linux/CentOS/$releasever/os/$basearch/
Is there a way to force a 6.3 machine to remain at 6.3 until a human being decides that is is time to do so?

thanx

5 thoughts on - Yum Configuration

  • thanks for replying. I was hoping ot a more dynamic approach though since the number of affected machines is in excess of 150. For example simply changing the $releasever to 6.3
    and then to 6.4
    and then to 6.5 every time a new version come along is not practical. Looking into the ‘man yum.conf’ I find that

    $releasever This will be replaced with the value of the version of the package listed in distroverpkg. This defaults to the version of
    ‘redhat-release’ package.

    distroverpkg The package used by yum to determine the “version” of the distribution. This can be any installed package. Default is
    ‘redhat-release’. You can see what provides this manually by using: “yum whatprovides redhat-release”.

    Doing

    [root@cs6979 yum.repos.d]# yum whatprovides redhat-release
    …………….. CentOS-release-6-4.el6.CentOS.10.x86_64 : CentOS release file Repo : CS-base Matched from:
    Other : redhat-release

    CentOS-release-6-3.el6.CentOS.9.x86_64 : CentOS release file Repo : installed Matched from:
    Other : Provides-match: redhat-release

    So the installed package is version 6.3. Am I overlooking/misinterpreting something?

    Andreas

  • If you’re dealing with that number of machines you may wish to consider setting up your own internal repo. Then you can sync your repo to the mirrors on your schedule, move to a later version on your schedule, and so on.


    Ron Loftin reloftin@twcny.rr.com

    “God, root, what is difference ?” Piter from UserFriendly

  • Ron Loftin wrote:
    Is there a way to force a 6.3 machine to remain at 6.3 until a human being decides that is is time to do so?
    might refer to it.

    affected machines is in excess of 150. setting up your own internal repo. Then you can sync your repo to the mirrors on your schedule, move to a later version on your schedule, and so on.

    Seconded. And in the repo, all you’d have to do is have a symlink of 6 -> 6.3.

    mark

  • Configuration management. ex: puppet

    An internal repo would suffice, but arguably not the simplest. But for
    150+ machines the OP should have one.

LEAVE A COMMENT