Ubuntu: Java packages in Partner archive to be removed on 2012-02-16
lists.ubuntu.com
lists.ubuntu.com
I never use the latter, ever.
Here is an excerpt describing what's eligible for an upgrade-
"Stable release updates will, in general, only be issued in order to fix high-impact bugs. Examples of such bugs include:
Bugs which may, under realistic circumstances, directly cause a security vulnerability. These are done by the security team and are documented at SecurityTeam/UpdateProcedures.
Bugs which represent severe regressions from the previous release of Ubuntu. This includes packages which are totally unusable, like being uninstallable or crashing on startup.
Bugs which may, under realistic circumstances, directly cause a loss of user data
Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel)."
If you don't trust the packages Ubuntu provides as updates, why do you trust the packages they initially provided with the release? I think that in most cases the updates are going through a more rigorous QA process than the initial packages.
Perhaps it is time to revive the java-package debian package:
http://wiki.debian.org/JavaPackage http://packages.debian.org/lenny/java-package
I forked it here and will be looking into it later today: https://github.com/philips/java-package
The process of doing a Linux install / upgrade of Java from the packages provided on the Oracle website is a real pain since they don't have their own apt repo or even provide a .deb.
OpenJDK may be a fine replacement for many use cases but it's really not a 100% drop in replacement. Minecraft requires Oracle Java for one , and I'd hate to think what would happen if you were using ubuntu to host anything important that required it.
This is the sort of stuff that ruins the ubuntu's UX.
1. Download from Oracles' site http://www.oracle.com/java. extract, and copy the extracted folder to /usr/lib/jvm (where openjdk is installed by default).
2. Change the default-jvm soft link to the new jdk:
> cd /usr/lib/jvm
> sudo rm default-jvm
> sudo ln -s jdk1.6.0_30 default-jvm
3. In .profile or .bash_profile add:
export JAVA_HOME=/usr/lib/jvm/default-jvm
(no need to add $JAVA_HOME/bin to your PATH, update-alternatives takes care of that by linking it to /usr/bin)
4. Add the new JDK to /etc/alternatives with update-alternatives command. The trick here is to slave all the jdk1.6.0_30/bin supporting programs to jdk1.6.0_30/bin/java, so that changing from one java to another also changes all the supporting programs as well. Without slaving them, you have to call update-alternatives --config on all of them separately, and there are quite a few as can be seen in the scripts below.
https://raw.github.com/byrongibson/scripts/master/install/ja...
https://raw.github.com/byrongibson/scripts/master/install/ja...
https://raw.github.com/byrongibson/scripts/master/install/ja...
That's it. This lets you install JDK6 and JDK7 side-by-side with OpenJDK (which I apt-get installed first, fwiw), and switch between them with a quick update-alternatives --config, and changing of the default-java soft link.
Doing it this way lets you install any number of JDK versions or minor versions side-by-side, and easily switch among them, or upgrade from one to another, and switch back if the new version borked whatever you were running on it.
Of course, no more automatic security updates, so you have to keep an eye on that and download the new Oracle JDK minor/update versions when they're released, but on the other hand it's much easier to roll back if an update breaks something, since the prior working version is still there and just and update-alternatives away.
I remembered there was an unofficial repository for Mandrake once upon a time (about Mandrake 8 or so) which had a bunch of software that allowed you to watch DVDs, play MP3s, etc. (They also had hotgirl). It was hosted by a bunch of crazy people (I seem to recall them being French).
So what I just really want to know is if anybody knows of an alternative repository?
The best solution is to get somebody Oracle can't block to put them into a repository.
At least this way it isn't ubuntu specific and you don't have to know about update-alternatives (first time for me hearing of that).
Presuming that, in addition to what you said, you also add your new $JAVA_HOME/bin to your $PATH, then you'll have a namespace collision in your PATH between $JAVA_HOME/bin/java and /usr/bin/java (OpenJDK linked via /etc/alternatives/java via /usr/lib/jvm/openjdk/bin/java, which is the default install setup for openjdk, on 11.10 at least).
If you're installing OpenJDK manually too, instead of via repo, or not at all, then keeping all your jdk's in ~/lib might be a better option overall.
As of August 24th 2011, we no longer have permission to redistribute new Java packages as Oracle has retired the "Operating System Distributor License for Java".
In theory it shouldn't matter which JVM interprent the code. In practice those that are not OracleJDK crash.
If a Ruby VM were to change its behaviour so to cause crashes, dozens of project will start to see red in one or two test cases. From that, it is easy to pin down the problem to 10 lines of code and report it upstream. In Java-land (and, sadly, many other lands) applications suddenly crash and nobody knows why.
In this case it is simply that a bunch of groups (especially gcj but properly also icedtea) published half-completed implementations of a standard and declared it was good enough to use because it didn't come from Sun.
As of now, IcedTea is lagging behind Oracle JDK 7u2 and it's not clear when it'll catch up. 7u2 has some important bug fixes and invokedynamic performance enhancements. So, it seems like the better release to go with.
Note that back in December they were planning to push "empty packages to the archive, so that the Sun JDK will be removed from all users machines when they do a software update". Now they've changed their minds: "In order to prevent unexpected failures, we will not be pushing out empty packages before removing them from the archive."
I've heard of Java-based production systems that were broken by a minor point-release of the official Java binaries, so it's not surprising to me that people would be skittish about switching to an entire other implementation.
So OpenJDK may be adequate as a RI, but will be unstable to use in a production environment.
Urgh... Couldn't they have phrased this any differently? The only thing that's missing is "Please hold. Your call is important to us."
How many times have we heard that sentence and thought that the speaker was not sincere at all? Now, when a somebody uses it, all those insincere utterances will come to your mind with all the accompanying bad feelings.
It is good to see people apologising for inconveniences but, please, take fifteen seconds to think of a sentence that does not sound like a canned reply.
Just tried it earlier today on 11.10. Worked fine.