masih nyangkut

end-mysql-3.3.3-101.mr.el6.i386 (mratwork-release-version-arch)
Requires: libmysqlclient.so.18(libmysqlclient_18)
You could try using --skip-broken to work around the problem
** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
pdns-backend-mysql-3.3.1-101.mr.el6.i386 has missing requires of pdns = ('0', '3.3.1', '101.mr.el6')
tengine-2.1.0-3.mr.el6.i386 is a duplicate with tengine-2.1.0-2.mr.el6.i386
[root@property ~]#
ini file /etc/yum.conf bener gk pak?
[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=5
bugtracker_url=http://bugs.centos.org/set_project.php?project_id=19&ref=http://bugs.centos.org/bug_report_page.php?category=yum
distroverpkg=centos-release
# This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
# It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
exclude=MariaDB* mysql56* mysql-