[Centos] Re: UPDATED: resolved caching-nameserver network install failure

Sat Jan 15 21:42:08 UTC 2005
donavan nelson <donavan at 4wx.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

|>>Since people have both updates and os in their yum.conf files, how are
|>>they _NOT_ going to get the update.
|>
|>I didn't think 7.3 was accessible unless you enabled the testing
|>repository.  I'll verify and hit lance if that's NOT the case as it
|>would invalidate what I've just said.
|>

This was intended to imply via a yum command.

|>
|>>It seems to me they will still get the newer version via yum and
|>>dependency resolution regardless of where in the directory structure it
|>>is.
|>
|>If 7.3 is infact in updates, they are getting it.
|>
|
| No ... if it is in centos/3.4/os/i386/RedHat/RPMS/ they are getting
| it ...

this is such a mess....but for everyone who may have this question.
caching-nameserver-7.2 and caching-name-server-7.3 both exist in the
centos/3.4/os/i386/RedHat/RPMS (new installs and network installs will
get 7.3 due to the package list).  System doing upgrades will only see
7.2 because 7.2 is the only package populated in
centos/3.4/os/i386/headers/ .

| yum.conf has an entry like this:
|
| [base]
| name=CentOS-$releasever - Base
| baseurl=mirror.../centos/$releasever/os/$basearch/
|
| SO ... any RPM in centos/3.4/os/i386/RedHat/RPMS/ is going to also be in
| package resolution...since 7.3 is in centos/3.4/os/i386/RedHat/RPMS/ and
| since 7.2 is in updates, 7.3 will be installed.
|

See about regarding the location of both packages.  Also yum only uses
the headers it finds (as a result of using yum-arch).  It doesn't NOT
examine the actual files in the directory.

.dn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB6Y4wCRFXD+VcGBkRAp6VAJ9YGUZF39lZtXESwF3Dps7IgKFlqACfYJZl
hI4hZSUangOBEkNZ1Yr+BB0=
=MTdH
-----END PGP SIGNATURE-----