Le lundi 14 juin 2010 à 13:25 +0200, Jarek Kamiński a écrit :
> Na grupie linux.debian.devel napisałe(a)ś:
> > I believe that now we fixed ~everything which can be fixed, so this
> > leaves us with the proprietary Java implementation which apparently Sun
> > is unwilling to fix.
> > Unless the maintainer believes that we can get a fixed version before
> > the release then I propose to stop setting bindv6only=3D1 by default.
> > While it was a useful experiment, since it allowed to expose and fix a
> > fair number of bugs, it should not compromise the general usability of
> > Debian systems.
> 
> I see only two ways of fixing proprietary Java (apart from fixing it
> upstream or ignoring the problem):
> * wrap java and java_vm binaries in some scripts setting LD_PRELOAD (in
>   Debian package)
This won't work in some cases. Some native programs instantiate a JVM
from C/C++. 

> or
> * allow sun-java6-* packages to override bindv6only sysctl.
Is it allowed by the Debian policy ?

> I can't say I like any of these approaches (although I currently do the
> first on my systems).
> 
> I hope Oracle will eventually fix the bug in Java allowing the change in
> (some) stable Debian release 
There is no interest from Oracle on this issue:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6342561

> (or OpenJDK will replace Sun's Java completely).
Last time I heard, Java 7 was expected for September 2010 but I am not
counting on it.

Sylvestre



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1276516044.21869.19032.ca...@korcula.inria.fr

Reply via email to