Ok I think I have it Fedora Community working again on appXX.stg and app01 [tested.] It looks like the version that is working on bapp01 requires various versions of applications not available in EPEL anymore so I had to grab a bunch of old stuff out of koji, and hope that what other differences occured were minor (there are some things in koji What I had to do: Get bunch of stuff out of koji where possible sudo yum remove TurboGears2 python-babel python-repoze-what python-tw-jquery python-webhelpers moksha fedoracommunity sudo yum --nogpgcheck --disablerepo=epel-test localinstall TurboGears2-2.0.3-3.el5.noarch.rpm python-babel-0.9.4-1.el5.noarch.rpm python-basemap-data-0.9.5-3.el5.noarch.rpm python-repoze-what-1.0.8-4.el5.noarch.rpm python-tw-jquery-0.9.5-1.el5.noarch.rpm python-webhelpers-0.6.4-4.el5.noarch.rpm sudo yum install moksha-0.4.3-1.el5.fedora.infra.noarch fedoracommunity-0.3.13-1.noarch Tada it now loads on app servers and does not give the errors it was about various bad apps. Lessons learned: 1) yum downgrade is nice in principle but not univerally good. 2) having epel-test on production servers may not be the best idea always 3) actually having direct epel/etc mirrors may be bad for web applications since they can be darn parsnickety about the exact version they need to work and when. 4) EPEL packages get updated all the time in wild ways. Only people who ask for permission seem to get told not to update. -- Stephen J Smoogen. “The core skill of innovators is error recovery, not failure avoidance.” Randy Nelson, President of Pixar University. "We have a strategic plan. It's called doing things."" — Herb Kelleher, founder Southwest Airlines _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
