Hi Rich,
I got the same result after doing
yum clean all
yum repolist
yum install 389-ds
# yum clean all
Loaded plugins: rhnplugin
Cleaning repos: epel epel-389-ds-base rhel-x86_64-server-6 vmware-tools
Cleaning up Everything
# yum repolist
Loaded plugins: rhnplugin
epel/metalink
| 7.6 kB 00:00
epel
| 4.3 kB 00:00
epel/primary_db
| 4.1 MB 00:00
epel-389-ds-base
| 1.3 kB 00:00
epel-389-ds-base/primary
| 3.1 kB 00:00
epel-389-ds-base
4/4
rhel-x86_64-server-6
| 1.8 kB 00:00
rhel-x86_64-server-6/primary
| 4.8 MB 00:28
rhel-x86_64-server-6
5351/5351
vmware-tools
| 951 B 00:00
vmware-tools/primary
| 2.6 kB 00:00
vmware-tools
10/10
repo id repo name
status
epel Extra Packages for Enterprise Linux 6
- x86_64 6401
epel-389-ds-base 389-ds-base package for EL6
4
rhel-x86_64-server-6 Red Hat Enterprise Linux Server (v. 6
for 64-bit x86_64) 5351
vmware-tools VMware Tools
10
repolist: 11766
# yum install 389-ds
Loaded plugins: rhnplugin
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed
--> Processing Dependency: 389-ds-console for package:
389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-console-doc for package:
389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin-console-doc for package:
389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-base for package:
389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin-console for package:
389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-dsgw for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-console for package:
389-ds-1.2.2-1.el6.noarch
--> Running transaction check
---> Package 389-admin.x86_64 0:1.1.23-1.el6 will be installed
--> Processing Dependency: libadminutil.so.0()(64bit) for package:
389-admin-1.1.23-1.el6.x86_64
--> Processing Dependency: libadmsslutil.so.0()(64bit) for package:
389-admin-1.1.23-1.el6.x86_64
---> Package 389-admin-console.noarch 0:1.1.8-1.el6 will be installed
---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el6 will be installed
---> Package 389-console.noarch 0:1.1.7-1.el6 will be installed
---> Package 389-ds-base.x86_64 0:1.2.8.3-1.el6 will be installed
--> Processing Dependency: 389-ds-base-libs = 1.2.8.3-1.el6 for package:
389-ds-base-1.2.8.3-1.el6.x86_64
--> Processing Dependency: libslapd.so.0()(64bit) for package:
389-ds-base-1.2.8.3-1.el6.x86_64
---> Package 389-ds-console.noarch 0:1.2.6-1.el6 will be installed
---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el6 will be installed
---> Package 389-dsgw.x86_64 0:1.1.7-1.el6 will be installed
--> Running transaction check
---> Package 389-adminutil.x86_64 0:1.1.14-2.el6 will be installed
---> Package 389-ds-base-libs.x86_64 0:1.2.8.3-1.el6 will be installed
--> Processing Conflict: 389-ds-base-1.2.8.3-1.el6.x86_64 conflicts
selinux-policy-base < 3.9.7-11
--> Finished Dependency Resolution
Error: 389-ds-base conflicts with selinux-policy-targeted
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Default /etc/yum.conf:
# cat /etc/yum.conf
[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=3
# 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
Please advise...
--thang
On 9/15/11 3:59 PM, Rich Megginson wrote:
> On 09/15/2011 05:43 PM, Thang Nguyen wrote:
>> I can't seem to install 389-ds-base 1.2.9.9 on RHEL6.1 using yum. I
>> follow the instructions from
>> http://directory.fedoraproject.org/wiki/Download by
>>
>> 1. Download and copy epel-389-ds-base.repo to /etc/yum.reposd
>> 2. rpm -Uvh epel-release-6-5.noarch.rpm
> try
> yum clean all
> then
> yum repolist
> then
> yum install 389-ds
>> When I run 'yum install 389-ds' which by default pointing to
>> epel-389-ds-base repo. I get selinux-policy-base conflict:
>>
>> # yum install 389-ds
>> Loaded plugins: rhnplugin
>> Setting up Install Process
>> Resolving Dependencies
>> --> Running transaction check
>> ---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed
>> --> Processing Dependency: 389-ds-console for package:
>> 389-ds-1.2.2-1.el6.noarch
>> --> Processing Dependency: 389-ds-console-doc for package:
>> 389-ds-1.2.2-1.el6.noarch
>> --> Processing Dependency: 389-admin-console-doc for package:
>> 389-ds-1.2.2-1.el6.noarch
>> --> Processing Dependency: 389-ds-base for package:
>> 389-ds-1.2.2-1.el6.noarch
>> --> Processing Dependency: 389-admin-console for package:
>> 389-ds-1.2.2-1.el6.noarch
>> --> Processing Dependency: 389-admin for package:
>> 389-ds-1.2.2-1.el6.noarch
>> --> Processing Dependency: 389-dsgw for package:
>> 389-ds-1.2.2-1.el6.noarch
>> --> Processing Dependency: 389-console for package:
>> 389-ds-1.2.2-1.el6.noarch
>> --> Running transaction check
>> ---> Package 389-admin.x86_64 0:1.1.23-1.el6 will be installed
>> --> Processing Dependency: libadminutil.so.0()(64bit) for package:
>> 389-admin-1.1.23-1.el6.x86_64
>> --> Processing Dependency: libadmsslutil.so.0()(64bit) for package:
>> 389-admin-1.1.23-1.el6.x86_64
>> ---> Package 389-admin-console.noarch 0:1.1.8-1.el6 will be installed
>> ---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el6 will be installed
>> ---> Package 389-console.noarch 0:1.1.7-1.el6 will be installed
>> ---> Package 389-ds-base.x86_64 0:1.2.8.3-1.el6 will be installed
>> --> Processing Dependency: 389-ds-base-libs = 1.2.8.3-1.el6 for package:
>> 389-ds-base-1.2.8.3-1.el6.x86_64
>> --> Processing Dependency: libslapd.so.0()(64bit) for package:
>> 389-ds-base-1.2.8.3-1.el6.x86_64
>> ---> Package 389-ds-console.noarch 0:1.2.6-1.el6 will be installed
>> ---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el6 will be installed
>> ---> Package 389-dsgw.x86_64 0:1.1.7-1.el6 will be installed
>> --> Running transaction check
>> ---> Package 389-adminutil.x86_64 0:1.1.14-2.el6 will be installed
>> ---> Package 389-ds-base-libs.x86_64 0:1.2.8.3-1.el6 will be installed
>> --> Processing Conflict: 389-ds-base-1.2.8.3-1.el6.x86_64 conflicts
>> selinux-policy-base< 3.9.7-11
>> --> Finished Dependency Resolution
>> Error: 389-ds-base conflicts with selinux-policy-targeted
>> You could try using --skip-broken to work around the problem
>> You could try running: rpm -Va --nofiles --nodigest
>>
>> It doesn't automatically install version 1.2.9.9 instead it tries to
>> install version 1.2.8.3.
>>
>> I was able to install 389-ds-base 1.2.9.0 when pointing to
>> "epel-testing-389-ds-base" I can only install 389-ds-base-1.2.9.0 and
>> can't seem to upgrade to 1.2.9.9.
>>
>> Anyone know why I can't install 389-ds-base 1.2.9.9 using yum even
>> though the rpm is in the epel-389-ds-base repository?
>>
>> thank you.
>>
>> --thang
>>
>>
>>
>
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
