Both @ACase suggestions of
yum erase apr and
yum downgrade apr are good, however if you wanted to do a little more investigation and see what is the offending app you can do the following;
You can check which installed packages require the blocking "apr-1.3.12-1.jason.1.x86_64" package like so;
# rpm -q --whatrequires apr
**apr-devel-1.2.7-11.el5_6.5** <--(this or something else in the list)
apr is the "apache portable runtime", and was presumably installed as a library by some other httpd related software package transaction.
And then you can see the dependencies of that offending package by using the following command;
# rpm -v -q --requires apr-devel
To see what dependencies are required by the new package that you are trying to install from repository you can use;
# yum deplist apr
package: apr.i386 1.2.7-11.el5_6.5
provider: glibc.i686 2.5-65
provider: glibc.i686 2.5-65.el5_7.
In more general terms, the problem is that the old and the new packages conflict and you will have to solve the problem by deciding which set of packages you are going keep and which to remove.
I personally would prefer to keep the use the distro version of the apr package, as it is used by a bunch of apache based softwares.
To see crazy verbose output of yum trying to find the deps for you, add the -v flag;
# yum -v deplist apr
pkgsack time: 3.261
rpmdb time: 0.000
Searching pkgSack for dep: /sbin/ldconfig
Potential match for /sbin/ldconfig from glibc-2.5-65.i686
Potential match for /sbin/ldconfig from glibc-2.5-65.x86_64