[Yum] xinetd-problem
stephan.helas at e-7.com
stephan.helas at e-7.com
Fri May 23 11:57:15 UTC 2003
>
> read the yum.conf manpage.
>
> pkgpolicy does this:
>
> the serverids are sorted alphabetically (as it says in the man page)
>
> so if you have this in your conf file:
>
> [a]
> name=my repo a
> baseurl=somepath
>
> [z]
> name=my repo z
> baseurl=someotherpath
>
>
> now if repo 'a' has xinetd 2.3.11-81
> and repo 'b' has xinetd 2.3.11-24
> and pkgpolicy=last
> 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.
let me explain it:
i have redhat 7.3 base repository on lokal server
[a_base]
name=Red Hat Linux 7.3 base
baseurl=http://gt1adm1.gt.da-ag.local/pub/RedHat/7.3/
including header.info:
0:cups-drivers-1.1-0.20020313.3.i386=RedHat/RPMS/cups-drivers-1.1-0.20020313.3.i386.rpm
0:cups-drivers-hpijs-1.1-0.20020313.3.i386=RedHat/RPMS/cups-drivers-hpijs-1.1-0.20020313.3.i386.rpm
1:cups-libs-1.1.14-15.i386=RedHat/RPMS/cups-libs-1.1.14-15.i386.rpm
1:cups-1.1.14-15.i386=RedHat/RPMS/cups-1.1.14-15.i386.rpm
0:cups-drivers-pnm2ppa-1.1-0.20020313.3.i386=RedHat/RPMS/cups-drivers-pnm2ppa-1.1-0.20020313.3.i386.rpm
1:cups-devel-1.1.14-15.i386=RedHat/RPMS/cups-devel-1.1.14-15.i386.rpm
then the is one update repository for redhat updates
[b_updates]
name=Red Hat Linux 7.3 updates
baseurl=http://mirror.dulug.duke.edu/pub/yum-repository/redhat/updates/7.3/
inculing header.info:
1:cups-devel-1.1.14-15.2.i386=x86/i386/cups-devel-1.1.14-15.2.i386.rpm
1:cups-libs-1.1.14-15.2.i386=x86/i386/cups-libs-1.1.14-15.2.i386.rpm
1:cups-1.1.14-15.2.i386=x86/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=Red Hat d|a Fractales Updates
baseurl=http://gt1adm1.gt.da-ag.local/pub/fractales/Software/RedHat/7.3/
including header.info:
0:cups-devel-1.1.18-1.i386=cups-devel-1.1.18-1.i386.rpm
0:cups-1.1.18-1.i386=cups-1.1.18-1.i386.rpm
i don't know, what first number in every line means, its automaticly created by using yum-arch.
1. if i use pkgpolicy=newest, 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=last, install cups from 7.3 original and try yum update, it shows my own compiled version.
------------------- 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=last.
-> 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
Stephan
More information about the Yum
mailing list