On Monday 24 March 2008, Sam Drinkard wrote:
> I suppose it's more of a frustration with myself, but can some kind soul
> please help me with the procedure to tell yum a package is in fact
> installed? Here is the output from the command "yum update".
>
> # yum update
> Setting up Update Process
> Setting up repositories
> kbs-CentOS-Extras 100% |=========================| 951 B 00:00
> kbs-CentOS-Misc 100% |=========================| 951 B 00:00
> update 100% |=========================| 951 B 00:00
> rpmforge 100% |=========================| 1.1 kB 00:00
> base 100% |=========================| 1.1 kB 00:00
> addons 100% |=========================| 951 B 00:00
> extras 100% |=========================| 1.1 kB 00:00
> Reading repository metadata in from local files
> Resolving Dependencies
> --> Populating transaction set with selected packages. Please wait.
> ---> Package kernel-devel.i686 0:2.6.9-67.0.7.EL set to be installed
> ---> Package kernel.i686 0:2.6.9-67.0.7.EL set to be installed
> ---> Package tzdata.noarch 0:2007k-2.el4 set to be updated
> ---> Package krb5-devel.i386 0:1.3.4-54.el4_6.1 set to be updated
> ---> Package krb5-workstation.i386 0:1.3.4-54.el4_6.1 set to be updated
> ---> Package clamav-data.i386 0:0.88.2-2.el4.kb set to be updated
> ---> Package clamav-server.i386 0:0.88.2-2.el4.kb set to be updated
> ---> Package krb5-libs.i386 0:1.3.4-54.el4_6.1 set to be updated
> ---> Package kernel-hugemem-devel.i686 0:2.6.9-67.0.7.EL set to be updated
> ---> Package kernel-smp-devel.i686 0:2.6.9-67.0.7.EL set to be updated
> ---> Package lftp.i386 0:3.7.0-1.el4.rf set to be updated
> ---> Package evolution.i386 0:2.0.2-35.0.4.el4_6.1 set to be updated
> --> Running transaction check
> --> Processing Dependency: clamav-db = 0.92.1-1.el4.rf for package: clamav
> --> Processing Dependency: clamav-lib = 0.88.2-2.el4.kb for package:
> clamav-server
> --> Processing Dependency: libclamav.so.1 for package: clamav-server
> --> Processing Dependency: clamd = 0.92.1-1.el4.rf for package:
> clamav-milter
> --> Restarting Dependency Resolution with new changes.
> --> Populating transaction set with selected packages. Please wait.
> ---> Package clamav-lib.i386 0:0.88.2-2.el4.kb set to be updated
> --> Running transaction check
> --> Processing Dependency: clamav-db = 0.92.1-1.el4.rf for package: clamav
> --> Processing Dependency: clamd = 0.92.1-1.el4.rf for package:
> clamav-milter
> --> Finished Dependency Resolution
> Error: Missing Dependency: clamav-db = 0.92.1-1.el4.rf is needed by
> package clamav
> Error: Missing Dependency: clamd = 0.92.1-1.el4.rf is needed by package
> clamav-milter
>
>
> As you can see in the last two lines, clamav-db and clamd appear to be
> missing, but I assure you, clamav-milter and clamav as well as the
> database are here, and running quite well. I even went so far as to do
> an erase of both, and both times, yum shows them as being installed. Of
> course I did not erase them, but if it finds them to be installed, why
> does it say they are missing during an update attempt?
The problem is that you are mixing repositories that provide different
versions of the same package which is impossible to sanely support. the
easiest way would be to temporarily disable one repo and run your update
again.
Dennis
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
