Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: micropitt on June 26, 2007, 04:30:10 PM

Title: Yum update (7.2)
Post by: micropitt on June 26, 2007, 04:30:10 PM
Hi all,
I got the run-around by the latest update for 7.2

<snip>

--> Populating transaction set with selected packages. Please wait.
---> Package mysql-libs.i386 0:5.0.42-1.el4.centos set to be updated
---> Package nss_ldap.i386 0:226-18 set to be updated
---> Package e-smith-base.noarch 0:4.18.0-25.el4.sme set to be updated
---> Package pdns-recursor.i386 0:3.1.2-2.el4.sme set to be updated
--> Running transaction check
--> Processing Dependency: nscd for package: nss_ldap
--> Processing Dependency: e-smith-dnscache for package: smeserver-support
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Package nscd.i386 0:2.3.4-2.36 set to be updated
--> Running transaction check
--> Processing Dependency: e-smith-dnscache for package: smeserver-support
--> Finished Dependency Resolution
Error: Missing Dependency: e-smith-dnscache is needed by package smeserver-support
================================================================
No new rpms were installed. No additional commands are required.
================================================================
[root@office files]#

I do believe that I have the latest versions of dnscache and smeserver-support installed.
Did anybody (with 7.2) run in to the same problem lately?
Title: Re: Yum update (7.2)
Post by: CharlieBrady on June 26, 2007, 04:37:48 PM
Quote from: "micropitt"

Did anybody (with 7.2) run in to the same problem lately?


If they did, they should have reported it via the Bug Tracker, so you should search there. If you don't find a similar report, make one yourself.
Title: Yum update (7.2)
Post by: micropitt on June 26, 2007, 04:46:03 PM
will do, thanks.
Title: Yum update (7.2)
Post by: byte on June 27, 2007, 06:39:30 PM
Quote from: "micropitt"
will do, thanks.


Please post bug number back in case someone else hits your issue. Thanks.