[gentoo-amd64] Errors when doing an emerge -uD world

[gentoo-amd64] Errors when doing an emerge -uD world

[Jamie Dobbs]

I get an error like this:

>>> Unpacking source...
>>> Unpacking jdepend-2.8.1.zip to /var/tmp/portage/jdepend-2.8.1/work
>>> Source unpacked.
Traceback (most recent call last):
  File "/usr/bin/java-config", line 14, in ?
    from java_config import jc_options
ImportError: No module named java_config
Error: JAVA_HOME is not defined correctly.
  We cannot execute

!!! ERROR: dev-java/jdepend-2.8.1 failed.
!!! Function src_compile, Line 30, Exitcode 1
!!! Failed Compiling
!!! If you need support, post the topmost build error, NOT this status
message.

Relevant environment variables are:

JAVAC=/opt/blackdown-jdk-1.4.2.02/bin/javac
JAVA_HOME=/opt/blackdown-jdk-1.4.2.02
JDK_HOME=/opt/blackdown-jdk-1.4.2.02

I have search on bugs.gentoo.org but can't find anything to help me. Can
anyone offer me any assistance?

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Errors when doing an emerge -uD world

[Hemmann, Volker Armin]

On Monday 17 October 2005 03:14, Jamie Dobbs wrote:
> I get an error like this:
> >>> Unpacking source...
> >>> Unpacking jdepend-2.8.1.zip to /var/tmp/portage/jdepend-2.8.1/work
> >>> Source unpacked.
>
> Traceback (most recent call last):
>   File "/usr/bin/java-config", line 14, in ?
>     from java_config import jc_options
> ImportError: No module named java_config
> Error: JAVA_HOME is not defined correctly.
>   We cannot execute
>
> !!! ERROR: dev-java/jdepend-2.8.1 failed.
> !!! Function src_compile, Line 30, Exitcode 1
> !!! Failed Compiling
> !!! If you need support, post the topmost build error, NOT this status
> message.
>

emm, is not -uD something almost everybody does, but nobody should do?

I had the same error - AFAIR reemerging java-config solved it.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Errors when doing an emerge -uD world

[Hagar]

You're missing a package (for some unknown reason)
Try this: emerge dev-java/java-config

On Monday 17 October 2005 03:14, Jamie Dobbs wrote:
> I get an error like this:
> >>> Unpacking source...
> >>> Unpacking jdepend-2.8.1.zip to /var/tmp/portage/jdepend-2.8.1/work
> >>> Source unpacked.
>
> Traceback (most recent call last):
>   File "/usr/bin/java-config", line 14, in ?
>     from java_config import jc_options
> ImportError: No module named java_config
> Error: JAVA_HOME is not defined correctly.
>   We cannot execute
>
> !!! ERROR: dev-java/jdepend-2.8.1 failed.
> !!! Function src_compile, Line 30, Exitcode 1
> !!! Failed Compiling
> !!! If you need support, post the topmost build error, NOT this status
> message.
>
> Relevant environment variables are:
>
> JAVAC=/opt/blackdown-jdk-1.4.2.02/bin/javac
> JAVA_HOME=/opt/blackdown-jdk-1.4.2.02
> JDK_HOME=/opt/blackdown-jdk-1.4.2.02
>
> I have search on bugs.gentoo.org but can't find anything to help me. Can
> anyone offer me any assistance?
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Errors when doing an emerge -uD world

[Jamie Dobbs]

> You're missing a package (for some unknown reason)
> Try this: emerge dev-java/java-config

Thank-you! That worked perfectly.

That's what I love about Gentoo, the support within the community is
second to none!




-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Errors when doing an emerge -uD world

[John C. Shimek]

>
>
>>emm, is not -uD something almost everybody does, but nobody should do?
>>
>>I had the same error - AFAIR reemerging java-config solved it.
>>    
>>

No, -uD is update deep, -UD is what you should NOT be doing.  the U 
means update only.  The difference is if say package-1.45 was marked 
stable and then found to be buggy, it gets masked in some way.  Then 
package-1.44 would be the most current stable package.  The U flag says 
not to go back to the 1.44 package.  On the other hand, the -u flag will 
"upgrade" to an older package if it is currently the newest unmasked or 
stable package. 

I think the biggest problem, I could be wrong thoug, is that usually 
when packages get remasked like that and upgrades go backwards, it is a 
security problem.  And even that seems to be uncommon.  I have not ever 
seen one of my packages go backwards but I could have missed one or two.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Errors when doing an emerge -uD world

[Sebastian Redl]

John C. Shimek wrote:

> I think the biggest problem, I could be wrong thoug, is that usually 
> when packages get remasked like that and upgrades go backwards, it is 
> a security problem.  And even that seems to be uncommon.  I have not 
> ever seen one of my packages go backwards but I could have missed one 
> or two.

In the other direction, the biggest problem is when you explicitely 
unmask a specific version (echo "=dev-db/mysql-5.0.9-alpha ~amd64" >> 
/etc/portage/package.keywords) and then there's a minor upgrade 
(=dev-db/mysql-5.0.9-beta), and the version you unmasked is thrown out. 
Doing a blind -uD will downgrade to the latest stable version in that case.
Of course, the answer here is to use -p and unmask the new versions 
before proceeding. And you can mask the old ones to guard yourself 
against accidental downgrading. (echo "<dev-db/mysql-5" >> 
/etc/portage/package.mask)

Sebastian Redl
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Errors when doing an emerge -uD world

[Hemmann, Volker Armin]

On Monday 17 October 2005 04:51, John C. Shimek wrote:
> >>emm, is not -uD something almost everybody does, but nobody should do?
> >>
> >>I had the same error - AFAIR reemerging java-config solved it.
>
> No, -uD is update deep, -UD is what you should NOT be doing.  the U
> means update only.  The difference is if say package-1.45 was marked
> stable and then found to be buggy, it gets masked in some way.  Then
> package-1.44 would be the most current stable package.  The U flag says
> not to go back to the 1.44 package.  On the other hand, the -u flag will
> "upgrade" to an older package if it is currently the newest unmasked or
> stable package.

-U is the OTHER flag you should never use ;)

If I remember correctly, a lot of time ago, it was said that you should not 
use -d, and must not use  -U  ....

but ok, everybody chooses his own poison.
I never do --deep updates, but occasionally -U update, because I am not 
willing to fiddle around with /etc/portage/package.mask /-.unmask for 
something that will be/should be marked stable in the next few days....
-- 
gentoo-amd64@gentoo.org mailing list