| 1 |
Kevin O'Gorman schreef: |
| 2 |
> On 12/30/05, Jason Stubbs <jstubbs@g.o> wrote: |
| 3 |
> |
| 4 |
>> On Saturday 31 December 2005 13:58, Kevin O'Gorman wrote: |
| 5 |
>> |
| 6 |
>>> Or should I say portage as a whole. Anyway, my latest emerge |
| 7 |
>>> world failed because of sun-jdk-1.4.2.10 (!!!). The current one |
| 8 |
>>> is 1.5 something. The weird part is that I cannot find any reason |
| 9 |
>>> for that |
| 10 |
>> |
| 11 |
>> package |
| 12 |
>> |
| 13 |
>>> to be emerged. 1) the world file contains just "sun-jdk" 2) |
| 14 |
>>> "equery depends =sun-jdk-1.4.2.10" shows nothing at all 3) |
| 15 |
>>> sun-jdk does not appear at all in /etc/portage/package.* files |
| 16 |
>>> |
| 17 |
>>> How should I explore this further? |
| 18 |
>> |
| 19 |
>> Whatever command you used to update, add --tree --pretend to it. |
| 20 |
> |
| 21 |
> This is interesting. sys-libs/db causes the old Java to be emerged. |
| 22 |
> However, I've deleted that version, and then I re-emerged |
| 23 |
> sys-libs/db. It still is calling for the old Java version. |
| 24 |
|
| 25 |
If you look at the output |
| 26 |
|
| 27 |
> [nomerge ] sys-libs/db-4.2.52_p2-r1 -bootstrap +doc +java |
| 28 |
> -nocxx +tcltk |
| 29 |
|
| 30 |
the reason db is calling for java is because you have the "java" USE |
| 31 |
flag set for db. |
| 32 |
|
| 33 |
Do you really need db to use Java? If not, disable the flag (# echo |
| 34 |
'sys-libs/db -java' >>/etc/portage/package.use); problem solved. |
| 35 |
|
| 36 |
Holly |
| 37 |
-- |
| 38 |
gentoo-user@g.o mailing list |
Archives