I strongly suggest that discipline, and please do not complain, if you break your main system just because you wanted the latest, unfinished program. You know, there's stable, and then there's really stable! Why do we always assume Debian devs don't have a good balance, or that they are just dragging their feet? Stable is not just for servers, and getting the latest point release numbers is not what you want unless you are alpha, and beta testing, such as developing, on a hopefully separate dev installation. Rule of thumb: If it is not available for stable, it's probably not stable. Use back-ports for stable, else it's super easy to compile (very, very rarely needed) most stuff, into "stable".
Kids, do not install mixed Debian releases on your production systems. There is absolutely no reason that openjdk should depend on any de/wm. Wonder if anyone filled a bug report because this is just stupid. Gnome-mime-data gvfs gvfs-common gvfs-daemons gvfs-libs libavahi-glib1 libbonobo2-0 libbonobo2-common libgdu0 libgnome2-0 libgnome2-common libgnomevfs2-0 libgnomevfs2-common libidl0 liborbit2 openjdk-7-jre openjdk-7-jre-headless openjdk-7-jre-libĠ upgraded, 18 newly installed, 0 to remove and 33 not upgraded. The following NEW packages will be installed: Policykit-1-gnome libgnomevfs2-extra icedtea-7-jre-cacao icedtea-7-jre-jamvm Ttf-wqy-microhei ttf-wqy-zenhei ttf-indic-fonts
Gvfs-backends libbonobo2-bin libgnomevfs2-bin fam libnss-mdns sun-java6-fonts fonts-ipafont-gothic fonts-ipafont-mincho Gnome-mime-data gvfs gvfs-common gvfs-daemons gvfs-libs libavahi-glib1 libbonobo2-0 libbonobo2-common libgdu0 libgnome2-0 libgnome2-common libgnomevfs2-0 libgnomevfs2-common libidl0 liborbit2 openjdk-7-jre-headless openjdk-7-jre-lib The following extra packages will be installed: So don't depend on the relevance to the real current situation! Keep also in mind that locking is deactivated, Code: Select all $ apt-get install openjdk-7-jre -sĪpt-get needs root privileges for real execution.