| 1 |
Has anyone here successfully installed 389 Directory Server from the |
| 2 |
ebuilds in the portage tree? |
| 3 |
|
| 4 |
http://bugs.gentoo.org/104554 |
| 5 |
|
| 6 |
While trying to install I run into an issue like this: |
| 7 |
|
| 8 |
-->8-- |
| 9 |
|
| 10 |
[ebuild N ] app-admin/389-console-1.1.6 111 kB |
| 11 |
[ebuild N ] www-apps/389-dsgw-1.1.5 USE="adminserver -debug" 731 kB |
| 12 |
[blocks B ] =sys-devel/libtool-2*:1.5 ("=sys-devel/libtool-2*:1.5" |
| 13 |
is blocking sys-devel/libtool-2.2.10) |
| 14 |
|
| 15 |
Total: 48 packages (43 new, 4 in new slots, 1 reinstall), Size of |
| 16 |
downloads: 101,668 kB |
| 17 |
Conflict: 1 block (1 unsatisfied) |
| 18 |
|
| 19 |
* Error: The above package list contains packages which cannot be |
| 20 |
* installed at the same time on the same system. |
| 21 |
|
| 22 |
(sys-devel/libtool-2.2.10, installed) pulled in by |
| 23 |
>=sys-devel/libtool-2.2.6b required by (dev-libs/apr-1.4.2, ebuild |
| 24 |
scheduled for merge) |
| 25 |
>=sys-devel/libtool-2.2.6b required by |
| 26 |
(net-nds/389-admin-1.1.11_rc1, ebuild scheduled for merge) |
| 27 |
>=sys-devel/libtool-2.2.6b required by (dev-libs/mozldap-6.0.6-r2, |
| 28 |
ebuild scheduled for merge) |
| 29 |
(and 7 more) |
| 30 |
|
| 31 |
(sys-devel/libtool-2.2.6b, ebuild scheduled for merge) pulled in by |
| 32 |
sys-devel/libtool:1.5 required by (net-nds/389-ds-base-1.2.6-r1, |
| 33 |
ebuild scheduled for merge) |
| 34 |
>=sys-devel/libtool-2.2.6b required by |
| 35 |
(net-nds/389-ds-base-1.2.6-r1, ebuild scheduled for merge) |
| 36 |
|
| 37 |
--8<-- |
| 38 |
|
| 39 |
I'm uncertain which of these packages are actually necessary and if |
| 40 |
any of the 389ds packages conflict with each other. But it seems that |
| 41 |
some of the 389ds packages want a certain version of libtool, while |
| 42 |
other packages want a different version. |
| 43 |
|
| 44 |
Any thoughts / ideas would be helpful. |
| 45 |
|
| 46 |
-james |
Archives