>=20 > read the yum.conf manpage. >=20 > pkgpolicy does this: >=20 > the serverids are sorted alphabetically (as it says in the man page) >=20 > so if you have this in your conf file: >=20 > [a] > name=3Dmy repo a > baseurl=3Dsomepath >=20 > [z] > name=3Dmy repo z > baseurl=3Dsomeotherpath >=20 >=20 > now if repo 'a' has xinetd 2.3.11-81 > and repo 'b' has xinetd 2.3.11-24 > and pkgpolicy=3Dlast > then xinetd 2.3.11-24 is the one that yum will claim is most current > available in your repositories. that's what i did.=20 let me explain it: i have redhat 7.3 base repository on lokal server [a_base] name=3DRed Hat Linux 7.3 base baseurl=3Dhttp://gt1adm1.gt.da-ag.local/pub/RedHat/7.3/ including header.info: 0:cups-drivers-1.1-0.20020313.3.i386=3DRedHat/RPMS/cups-drivers-1.1-0.200= 20313.3.i386.rpm 0:cups-drivers-hpijs-1.1-0.20020313.3.i386=3DRedHat/RPMS/cups-drivers-hpi= js-1.1-0.20020313.3.i386.rpm 1:cups-libs-1.1.14-15.i386=3DRedHat/RPMS/cups-libs-1.1.14-15.i386.rpm 1:cups-1.1.14-15.i386=3DRedHat/RPMS/cups-1.1.14-15.i386.rpm 0:cups-drivers-pnm2ppa-1.1-0.20020313.3.i386=3DRedHat/RPMS/cups-drivers-p= nm2ppa-1.1-0.20020313.3.i386.rpm 1:cups-devel-1.1.14-15.i386=3DRedHat/RPMS/cups-devel-1.1.14-15.i386.rpm then the is one update repository for redhat updates [b_updates] name=3DRed Hat Linux 7.3 updates baseurl=3Dhttp://mirror.dulug.duke.edu/pub/yum-repository/redhat/updates/= 7.3/ inculing header.info: 1:cups-devel-1.1.14-15.2.i386=3Dx86/i386/cups-devel-1.1.14-15.2.i386.rpm 1:cups-libs-1.1.14-15.2.i386=3Dx86/i386/cups-libs-1.1.14-15.2.i386.rpm 1:cups-1.1.14-15.2.i386=3Dx86/i386/cups-1.1.14-15.2.i386.rpm third i have some self made rpm , for example newer cups (1.1.18) [c_fractales] name=3DRed Hat d|a Fractales Updates baseurl=3Dhttp://gt1adm1.gt.da-ag.local/pub/fractales/Software/RedHat/7.3= / including header.info: 0:cups-devel-1.1.18-1.i386=3Dcups-devel-1.1.18-1.i386.rpm 0:cups-1.1.18-1.i386=3Dcups-1.1.18-1.i386.rpm i don't know, what first number in every line means, its automaticly = created by using yum-arch.=20 1. if i use pkgpolicy=3Dnewest, install cups from 7.3 original and try = yum update, it shows me the version from dulug server, not my own. ------------------ snip -------------------------- Gathering package information from servers Getting headers from: Red Hat Linux 7.3 base Getting headers from: Red Hat Linux 7.3 updates Getting headers from: Red Hat d|a Fractales Updates Finding updated packages Downloading needed headers Looking in Available Packages: Name Arch Version -------------------------------------------------------------------------= ------- cups-devel i386 1.1.14-15.2 Looking in Installed Packages: Name Arch Version -------------------------------------------------------------------------= ------- cups-libs i386 1.1.14-15.2 ---------------- snap ---------------------------- 2. if i use pkgpolicy=3Dlast, install cups from 7.3 original and try yum = update, it shows my own compiled version.=20 ------------------- snip ------------------------- Gathering package information from servers Getting headers from: Red Hat Linux 7.3 base Getting headers from: Red Hat Linux 7.3 updates Getting headers from: Red Hat d|a Fractales Updates Finding updated packages Downloading needed headers Looking in Available Packages: Name Arch Version -------------------------------------------------------------------------= ------- cups-devel i386 1.1.18-1 Looking in Installed Packages: Name Arch Version -------------------------------------------------------------------------= ------- cups-libs i386 1.1.14-15.2 ----------------- snap ----------------------------- --> thats the reasen why i use pkgpolicy=3Dlast. -> but there is another problem, if i use this method, some packages = from the dulug update server don't apear in the update list. (e.g. the = xinetd package). so i can't use the method, as long as i'm not sure = about the yum update brings all packages up to date. Regards=20 Stephan
