java-config can get called during boot(bash-completion,tomcat conf.d script), when vars like HOME are not set, it wrongly assumes those will always be present
The question is... what should java-config do if it can't find $HOME ? Producing an error seems sensible and easy.
it doesn't need $HOME for alot of options (-L to just name one) for the ones it does need it a nice error message would be sensible
That may be true, but to resolve the problem, there should only be an error if the HOME env-var is actually needed by the specific command that java-config is executing. This would prevent the error/failure when java-config is being run at boot. The problem actually exists in the jc_options.py script, which plainly states in the comments that the script assumes that os.environ will always contain the HOME key.
*** Bug 56795 has been marked as a duplicate of this bug. ***
In version 1.2.8, just released.
i've installed 1.2., but i got the *SAME* error.
The one traceback of this error I was able to see, that part of the code doesn't exist anymore, so it's impossible to get the exact same tracback. I need to the see new traceback in order to fix this problem. Hopefully you did in fact install *1.2.8* ?
Also... under the situations where HOME supposedly isn't set, i.e. tomcat conf.d, and bash completion, I'm not seeing the traceback happen with 1.2.8, so more information about how things are set up, and with what packages, so that I can reproduce the error would be very helpful too.
Sorry, I was still waking up when I wrote the last comments, information on when the errors are happenning would still be very useful. But ``unset HOME'' works too. http://dev.gentoo.org/~aether/jc_options.py.diff Seems to be what was the problem... in 1.2.9 soon.
Patrizio Bassi: There's not much point in you commenting on a bug if you aren't going to respond to my questions.
sorry... i mistyped. i installed 1.2.8, of course and i have the same backtrack of 1.2.7 i read that code is no more in java-config. ehhehe that's impossibile. i got same error. or ebuild has some problems...or code has it. if u need more info, just ask!
Hello Had this problem at boot time to. The jc_options.py.diff solved the problem. Thanks Thomas
nice nice. waiting for new release or a -r1
Fixed, again, in version 1.2.9 just released.
works fine with 1.2.9
