1 |
On 17/04/12 19:39, Alan McKinnon wrote: |
2 |
> On Tue, 17 Apr 2012 18:41:55 +0300 |
3 |
> Nikos Chantziaras<realnc@×××××.com> wrote: |
4 |
> |
5 |
>> On 17/04/12 18:34, Nikos Chantziaras wrote: |
6 |
>>> On 17/04/12 18:10, Alan McKinnon wrote: |
7 |
>>>> On Tue, 17 Apr 2012 18:01:43 +0300 |
8 |
>>>> Nikos Chantziaras<realnc@×××××.com> wrote: |
9 |
>>>> |
10 |
>>>>> emerge --depclean seems to have bugged out for me: |
11 |
>>>>> |
12 |
>>>>> * Dependencies could not be completely resolved due to |
13 |
>>>>> * the following required packages not being installed: |
14 |
>>>>> * |
15 |
>>>>> * =dev-libs/openssl-0.9.8* pulled in by: |
16 |
>>>>> * app-emulation/vmware-workstation-8.0.2.591240 |
17 |
>>>>> * |
18 |
>>>>> * dev-libs/openssl:0.9.8 pulled in by: |
19 |
>>>>> * www-client/google-chrome-19.0.1084.24_beta131971 |
20 |
>>>>> |
21 |
>>>>> It says to do a "emerge --update --newuse --deep --with-bdeps=y |
22 |
>>>>> @world". Which is what I just did to begin with (and running it |
23 |
>>>>> again doesn't result in anything getting emerged.) |
24 |
>>>>> [...] |
25 |
> |
26 |
> One thing that strikes me as a possibility is that the highest numbered |
27 |
> version has the lower slot number (0). I know that SLOT names are |
28 |
> just names and not supposed to be treated like they form an order, but |
29 |
> I've seen odd things like this before. I think KDE did it to me once. |
30 |
> |
31 |
> What happens if you emerge openssl:0.9.8, let it go into world, then |
32 |
> run depclean? The build takes 2 minutes and you can easily remove it |
33 |
> from world later. |
34 |
|
35 |
Nope, nothing changed. |