On Thu, May 5, 2011 at 12:45 PM, Tony Graziano <[email protected]> wrote: > wasn't there a 4.05 release/patch that you needed to go to to properly > get to 4.2.1? > > In any case, why not just erase the offending package/dependency and > then update and let it fix things?
Tony, that was my quick response too, but you'll notice he's not getting a conflict, rather a missing package altogether. Keith, I don't know where yum builds $releasever variable, but check these commands [root@finch ~]# head -2 /etc/issue CentOS release 5.5 (Final) Kernel \r on an \m [root@finch ~]# cat /etc/redhat-release CentOS release 5.6 (Final) [root@finch ~]# rpm -qa | grep release centos-release-5-6.el5.centos.1 centos-release-notes-5.6-0 ( as you see, mine are a little off but it seems ok) _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
