Kevin O'Gorman schreef: > On 12/30/05, Jason Stubbs <[EMAIL PROTECTED]> wrote: > >> On Saturday 31 December 2005 13:58, Kevin O'Gorman wrote: >> >>> Or should I say portage as a whole. Anyway, my latest emerge >>> world failed because of sun-jdk-1.4.2.10 (!!!). The current one >>> is 1.5 something. The weird part is that I cannot find any reason >>> for that >> >> package >> >>> to be emerged. 1) the world file contains just "sun-jdk" 2) >>> "equery depends =sun-jdk-1.4.2.10" shows nothing at all 3) >>> sun-jdk does not appear at all in /etc/portage/package.* files >>> >>> How should I explore this further? >> >> Whatever command you used to update, add --tree --pretend to it. > > This is interesting. sys-libs/db causes the old Java to be emerged. > However, I've deleted that version, and then I re-emerged > sys-libs/db. It still is calling for the old Java version.
If you look at the output > [nomerge ] sys-libs/db-4.2.52_p2-r1 -bootstrap +doc +java > -nocxx +tcltk the reason db is calling for java is because you have the "java" USE flag set for db. Do you really need db to use Java? If not, disable the flag (# echo 'sys-libs/db -java' >>/etc/portage/package.use); problem solved. Holly -- gentoo-user@gentoo.org mailing list
