1 |
I'm pretty sure this is a bug. I've tried to emerge these packages on |
2 |
a fresh / new system and the 389-ds-base package has a dependency |
3 |
conflict. |
4 |
|
5 |
-->8-- |
6 |
|
7 |
[ebuild N ] net-nds/389-ds-base-1.2.6-r1 USE="bitwise dna |
8 |
kerberos ldapi pam-passthru presence -auto-dn-suffix -autobind -debug |
9 |
-doc (-selinux)" 2,803 kB |
10 |
[blocks B ] =sys-devel/libtool-2*:1.5 ("=sys-devel/libtool-2*:1.5" |
11 |
is blocking sys-devel/libtool-2.2.10) |
12 |
|
13 |
Total: 14 packages (10 new, 3 in new slots, 1 reinstall), Size of |
14 |
downloads: 27,734 kB |
15 |
Conflict: 1 block (1 unsatisfied) |
16 |
|
17 |
* Error: The above package list contains packages which cannot be |
18 |
* installed at the same time on the same system. |
19 |
|
20 |
(sys-devel/libtool-2.2.10, installed) pulled in by |
21 |
>=sys-devel/libtool-2.2.6b required by (dev-libs/svrcore-4.0.4, |
22 |
ebuild scheduled for merge) |
23 |
>=sys-devel/libtool-2.2.6b required by (dev-libs/mozldap-6.0.6-r2, |
24 |
ebuild scheduled for merge) |
25 |
|
26 |
(sys-devel/libtool-2.2.6b, ebuild scheduled for merge) pulled in by |
27 |
sys-devel/libtool:1.5 required by (net-nds/389-ds-base-1.2.6-r1, |
28 |
ebuild scheduled for merge) |
29 |
>=sys-devel/libtool-2.2.6b required by |
30 |
(net-nds/389-ds-base-1.2.6-r1, ebuild scheduled for merge) |
31 |
|
32 |
--8<-- |
33 |
|
34 |
I can't see a way to get around this blocked package issue as the |
35 |
dependencies require different versions of the package than the actual |
36 |
package I'm trying to emerge. |
37 |
|
38 |
-j |
39 |
|
40 |
|
41 |
2010/10/13 李健 <kdlijian@×××××.com>: |
42 |
> I don't know. |
43 |
> Last time when "emerge --update --deep --newuse world" I suffered some |
44 |
> "Blocks", I don't know how to solve that properly. |
45 |
> Then I unmerged all the releated packages(include dependencies) and remerged |
46 |
> the packages I need. It works. |
47 |
> |
48 |
> I mean maybe you can just make this, without knowing everything clearly |
49 |
> right now. Of course, if you are not in a PRODUCTION environment. |
50 |
> |
51 |
> 2010/10/13 James <jtp@×××××.com> |
52 |
>> |
53 |
>> Hi, |
54 |
>> |
55 |
>> Yep -- I have it installed. |
56 |
>> |
57 |
>> [I] sys-devel/libtool (2.2.10(2)@09/26/2010): A shared library tool |
58 |
>> for developers |
59 |
>> |
60 |
>> I've tried unmasking ~amd64 to no avail. I believe the issue is that |
61 |
>> one of the 389ds packages wants an older version of libtool, while |
62 |
>> another package in the list of 389ds wants a newer version. |
63 |
>> |
64 |
>> I guess there really isn't much of a "howto" regarding how to use |
65 |
>> 389ds on Gentoo -- are all of these packages required? If not, which |
66 |
>> ones should I depend on? Several of these packages are named "console" |
67 |
>> -- one is Java, another one "ds" console (whatever that is). |
68 |
>> |
69 |
>> ~ % eix -c 389 |
70 |
>> [N] app-admin/389-admin-console (~1.1.4(1.1)): 389 Server Management |
71 |
>> Console (jar and help files) |
72 |
>> [N] app-admin/389-console (~1.1.6(1.1)): A Java based console for |
73 |
>> remote management 389 server |
74 |
>> [N] app-admin/389-ds-console (~1.2.3-r1(1.2)): Java based remote |
75 |
>> management console used for Managing 389-admin 389-ds |
76 |
>> [N] dev-libs/389-adminutil (~1.1.10): 389 adminutil |
77 |
>> [N] net-nds/389-admin (~1.1.11_rc1): 389 Directory Server (admin) |
78 |
>> [N] net-nds/389-ds-base (~1.2.6-r1): 389 Directory Server (core |
79 |
>> librares and daemons ) |
80 |
>> [N] www-apps/389-dsgw (~1.1.5): 389 Directory Server Gateway Web |
81 |
>> Application |
82 |
>> Found 7 matches. |
83 |
>> |
84 |
>> Thoughts? |
85 |
>> |
86 |
>> -james |
87 |
>> |
88 |
>> On Tue, Oct 12, 2010 at 4:33 AM, 李健 <kdlijian@×××××.com> wrote: |
89 |
>> > Do you have libtool-2*:1.5 installed? ( emerge -pv sys-devel/ibtool ) |
90 |
>> > If so, try unmerging it. ( emerge -av --unmerge sys-devel/libtool-2*:1.5 |
91 |
>> > ) |
92 |
>> > I am not sure.Just have a try. ( newbie ) |
93 |
>> > HTH --lijian |
94 |
>> > |
95 |
>> > 2010/10/12 James <jtp@×××××.com> |
96 |
>> >> |
97 |
>> >> Has anyone here successfully installed 389 Directory Server from the |
98 |
>> >> ebuilds in the portage tree? |
99 |
>> >> |
100 |
>> >> http://bugs.gentoo.org/104554 |
101 |
>> >> |
102 |
>> >> While trying to install I run into an issue like this: |
103 |
>> >> |
104 |
>> >> -->8-- |
105 |
>> >> |
106 |
>> >> [ebuild N ] app-admin/389-console-1.1.6 111 kB |
107 |
>> >> [ebuild N ] www-apps/389-dsgw-1.1.5 USE="adminserver -debug" 731 |
108 |
>> >> kB |
109 |
>> >> [blocks B ] =sys-devel/libtool-2*:1.5 ("=sys-devel/libtool-2*:1.5" |
110 |
>> >> is blocking sys-devel/libtool-2.2.10) |
111 |
>> >> |
112 |
>> >> Total: 48 packages (43 new, 4 in new slots, 1 reinstall), Size of |
113 |
>> >> downloads: 101,668 kB |
114 |
>> >> Conflict: 1 block (1 unsatisfied) |
115 |
>> >> |
116 |
>> >> * Error: The above package list contains packages which cannot be |
117 |
>> >> * installed at the same time on the same system. |
118 |
>> >> |
119 |
>> >> (sys-devel/libtool-2.2.10, installed) pulled in by |
120 |
>> >> >=sys-devel/libtool-2.2.6b required by (dev-libs/apr-1.4.2, ebuild |
121 |
>> >> scheduled for merge) |
122 |
>> >> >=sys-devel/libtool-2.2.6b required by |
123 |
>> >> (net-nds/389-admin-1.1.11_rc1, ebuild scheduled for merge) |
124 |
>> >> >=sys-devel/libtool-2.2.6b required by (dev-libs/mozldap-6.0.6-r2, |
125 |
>> >> ebuild scheduled for merge) |
126 |
>> >> (and 7 more) |
127 |
>> >> |
128 |
>> >> (sys-devel/libtool-2.2.6b, ebuild scheduled for merge) pulled in by |
129 |
>> >> sys-devel/libtool:1.5 required by (net-nds/389-ds-base-1.2.6-r1, |
130 |
>> >> ebuild scheduled for merge) |
131 |
>> >> >=sys-devel/libtool-2.2.6b required by |
132 |
>> >> (net-nds/389-ds-base-1.2.6-r1, ebuild scheduled for merge) |
133 |
>> >> |
134 |
>> >> --8<-- |
135 |
>> >> |
136 |
>> >> I'm uncertain which of these packages are actually necessary and if |
137 |
>> >> any of the 389ds packages conflict with each other. But it seems that |
138 |
>> >> some of the 389ds packages want a certain version of libtool, while |
139 |
>> >> other packages want a different version. |
140 |
>> >> |
141 |
>> >> Any thoughts / ideas would be helpful. |
142 |
>> >> |
143 |
>> >> -james |
144 |
>> >> |
145 |
>> > |
146 |
>> > |
147 |
>> |
148 |
> |
149 |
> |