Why was Java 8 left out from Debian Buster?OpenJDK 8 support period in Debian Stretch 9Invoke Syscalls from JavaChange PATH in Debian 7.1.0 for JavaJava location from /usr/bin/javaWhy was ffmpeg removed from Debian?Compiled (?) java packages on DebianInstall Java JDK and JRE on Debian 8Install Java 6 to Debian LennyInstall Java 6 from Oracle to Debian Lennyinstall ssmtp in Debian buster
As a discovery writer, how to complete unfinished novel (which is highly diverted from original plot ) after a time-gap
What do solvers like Gurobi and CPLEX do when they run into hard instances of MIP
Weapon class firing logic in JavaScript
Who was Chief Poking Fire?
Escape the labyrinth!
How could artificial intelligence harm us?
What did the controller say during my approach to land (audio clip)?
Why are there two bearded faces wearing red hats on my stealth bomber icon?
Did slaves have slaves?
As an employer, can I compel my employees to vote?
Tips for remembering the order of parameters for ln?
Does battery condition have anything to do with macbook pro performance?
Twelve Minesweeper mines that make twelve 4s
Microservices and Stored Procedures
Did HaShem ever command a Navi (Prophet) to break a law?
EU compensation - fire alarm at the Flight Crew's hotel
Is it possible that the shadow of The Moon is a single dot during solar eclipse?
Can I separate garlic into cloves for storage?
What is the rail connection between Paris Charles de Gaulle Airport and Gare de Lyon like?
Dear Fellow PSE Users,
What can I actually do with a high credit score?
Integrability of log of distance function
Why was Java 8 left out from Debian Buster?
Is Zack Morris's 'time stop' ability in "Saved By the Bell" a supernatural ability?
Why was Java 8 left out from Debian Buster?
OpenJDK 8 support period in Debian Stretch 9Invoke Syscalls from JavaChange PATH in Debian 7.1.0 for JavaJava location from /usr/bin/javaWhy was ffmpeg removed from Debian?Compiled (?) java packages on DebianInstall Java JDK and JRE on Debian 8Install Java 6 to Debian LennyInstall Java 6 from Oracle to Debian Lennyinstall ssmtp in Debian buster
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Recent stable version of Debian, Debian Buster, does not have Java 8 any more.
However, Java 8 is still widely used in productive settings, and doing this is a huge fallback before any upgrade.
Anybody knowing better the internals of the Debian mailing lists, and their communication, what could be their reason to do that?
Is there any hope, that Java 8 will once re-appear in the form of some upgrade?
Of course, installing Java 8 from a different source (Oracle, Ubuntu), or even from the Stretch package repository, is a viable alternative. But doing that, we lose exactly the advantages of the official repos.
debian java
|
show 1 more comment
Recent stable version of Debian, Debian Buster, does not have Java 8 any more.
However, Java 8 is still widely used in productive settings, and doing this is a huge fallback before any upgrade.
Anybody knowing better the internals of the Debian mailing lists, and their communication, what could be their reason to do that?
Is there any hope, that Java 8 will once re-appear in the form of some upgrade?
Of course, installing Java 8 from a different source (Oracle, Ubuntu), or even from the Stretch package repository, is a viable alternative. But doing that, we lose exactly the advantages of the official repos.
debian java
Comments are not for extended discussion; this conversation has been moved to chat.
– Jeff Schaller♦
7 hours ago
Have a look at the Debian OpenJDK Team Package overview site and the openjdk-8 package tracker. Packageopenjdk-8-jdkis available in sid (unstable), but didn't make it into buster, because there were (and still are) bugs.
– Freddy
6 hours ago
@Freddy Could you make it an answer?
– peterh
5 hours ago
@Freddy in particular bugs.debian.org/cgi-bin/bugreport.cgi?bug=929650 — that's a bug to make sure it does not enter testing (and thus eventually stable). In a sense, that's not a real bug — it's not going to be fixed, can't be fixed, it will only be closed by eventually removing openjdk-8 from unstable. It's just how Debian implements "never release this package" (without fully removing it).
– derobert
3 hours ago
Ah, okay. Thanks for the clarification @derobert. But I still don't get what they mean by saying "It is used to prepare updates for stable-security".
– Freddy
3 hours ago
|
show 1 more comment
Recent stable version of Debian, Debian Buster, does not have Java 8 any more.
However, Java 8 is still widely used in productive settings, and doing this is a huge fallback before any upgrade.
Anybody knowing better the internals of the Debian mailing lists, and their communication, what could be their reason to do that?
Is there any hope, that Java 8 will once re-appear in the form of some upgrade?
Of course, installing Java 8 from a different source (Oracle, Ubuntu), or even from the Stretch package repository, is a viable alternative. But doing that, we lose exactly the advantages of the official repos.
debian java
Recent stable version of Debian, Debian Buster, does not have Java 8 any more.
However, Java 8 is still widely used in productive settings, and doing this is a huge fallback before any upgrade.
Anybody knowing better the internals of the Debian mailing lists, and their communication, what could be their reason to do that?
Is there any hope, that Java 8 will once re-appear in the form of some upgrade?
Of course, installing Java 8 from a different source (Oracle, Ubuntu), or even from the Stretch package repository, is a viable alternative. But doing that, we lose exactly the advantages of the official repos.
debian java
debian java
edited 6 hours ago
peterh
asked 8 hours ago
peterhpeterh
4,58011 gold badges35 silver badges65 bronze badges
4,58011 gold badges35 silver badges65 bronze badges
Comments are not for extended discussion; this conversation has been moved to chat.
– Jeff Schaller♦
7 hours ago
Have a look at the Debian OpenJDK Team Package overview site and the openjdk-8 package tracker. Packageopenjdk-8-jdkis available in sid (unstable), but didn't make it into buster, because there were (and still are) bugs.
– Freddy
6 hours ago
@Freddy Could you make it an answer?
– peterh
5 hours ago
@Freddy in particular bugs.debian.org/cgi-bin/bugreport.cgi?bug=929650 — that's a bug to make sure it does not enter testing (and thus eventually stable). In a sense, that's not a real bug — it's not going to be fixed, can't be fixed, it will only be closed by eventually removing openjdk-8 from unstable. It's just how Debian implements "never release this package" (without fully removing it).
– derobert
3 hours ago
Ah, okay. Thanks for the clarification @derobert. But I still don't get what they mean by saying "It is used to prepare updates for stable-security".
– Freddy
3 hours ago
|
show 1 more comment
Comments are not for extended discussion; this conversation has been moved to chat.
– Jeff Schaller♦
7 hours ago
Have a look at the Debian OpenJDK Team Package overview site and the openjdk-8 package tracker. Packageopenjdk-8-jdkis available in sid (unstable), but didn't make it into buster, because there were (and still are) bugs.
– Freddy
6 hours ago
@Freddy Could you make it an answer?
– peterh
5 hours ago
@Freddy in particular bugs.debian.org/cgi-bin/bugreport.cgi?bug=929650 — that's a bug to make sure it does not enter testing (and thus eventually stable). In a sense, that's not a real bug — it's not going to be fixed, can't be fixed, it will only be closed by eventually removing openjdk-8 from unstable. It's just how Debian implements "never release this package" (without fully removing it).
– derobert
3 hours ago
Ah, okay. Thanks for the clarification @derobert. But I still don't get what they mean by saying "It is used to prepare updates for stable-security".
– Freddy
3 hours ago
Comments are not for extended discussion; this conversation has been moved to chat.
– Jeff Schaller♦
7 hours ago
Comments are not for extended discussion; this conversation has been moved to chat.
– Jeff Schaller♦
7 hours ago
Have a look at the Debian OpenJDK Team Package overview site and the openjdk-8 package tracker. Package
openjdk-8-jdk is available in sid (unstable), but didn't make it into buster, because there were (and still are) bugs.– Freddy
6 hours ago
Have a look at the Debian OpenJDK Team Package overview site and the openjdk-8 package tracker. Package
openjdk-8-jdk is available in sid (unstable), but didn't make it into buster, because there were (and still are) bugs.– Freddy
6 hours ago
@Freddy Could you make it an answer?
– peterh
5 hours ago
@Freddy Could you make it an answer?
– peterh
5 hours ago
@Freddy in particular bugs.debian.org/cgi-bin/bugreport.cgi?bug=929650 — that's a bug to make sure it does not enter testing (and thus eventually stable). In a sense, that's not a real bug — it's not going to be fixed, can't be fixed, it will only be closed by eventually removing openjdk-8 from unstable. It's just how Debian implements "never release this package" (without fully removing it).
– derobert
3 hours ago
@Freddy in particular bugs.debian.org/cgi-bin/bugreport.cgi?bug=929650 — that's a bug to make sure it does not enter testing (and thus eventually stable). In a sense, that's not a real bug — it's not going to be fixed, can't be fixed, it will only be closed by eventually removing openjdk-8 from unstable. It's just how Debian implements "never release this package" (without fully removing it).
– derobert
3 hours ago
Ah, okay. Thanks for the clarification @derobert. But I still don't get what they mean by saying "It is used to prepare updates for stable-security".
– Freddy
3 hours ago
Ah, okay. Thanks for the clarification @derobert. But I still don't get what they mean by saying "It is used to prepare updates for stable-security".
– Freddy
3 hours ago
|
show 1 more comment
1 Answer
1
active
oldest
votes
Debian's general policy is to only have one version of a software package in a release. So, absent exceptional circumstances, there would only be one version of OpenJDK; buster has OpenJDK 11.
Details can be found in an email to debian-java and on various Java web sites but in short:
- OpenJDK 8 security support (already from third parties, e.g., Red Hat) ends before Buster's EOL. So sticking with it would risk that the Debian maintainers and/or security team would have to maintain Java (which is well beyond the manpower they have) or alternatively drop security support before buster EOL. (And well before Buster LTS EOL).
- If you need to stick with OpenJDK 8, you can stick with Stretch, which will be supported until 2020 and until 2022 via LTS. OpenJDK 8 will be supported for the lifetime of Stretch, including LTS.
- OpenJDK 11 is the current, upstream-supported LTS release.
You might also consider moving your Java app into a container of some sort, to make it easier to deploy a non-packaged version of Java. That's what I've done for a proprietary app I have to keep running.
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f542270%2fwhy-was-java-8-left-out-from-debian-buster%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Debian's general policy is to only have one version of a software package in a release. So, absent exceptional circumstances, there would only be one version of OpenJDK; buster has OpenJDK 11.
Details can be found in an email to debian-java and on various Java web sites but in short:
- OpenJDK 8 security support (already from third parties, e.g., Red Hat) ends before Buster's EOL. So sticking with it would risk that the Debian maintainers and/or security team would have to maintain Java (which is well beyond the manpower they have) or alternatively drop security support before buster EOL. (And well before Buster LTS EOL).
- If you need to stick with OpenJDK 8, you can stick with Stretch, which will be supported until 2020 and until 2022 via LTS. OpenJDK 8 will be supported for the lifetime of Stretch, including LTS.
- OpenJDK 11 is the current, upstream-supported LTS release.
You might also consider moving your Java app into a container of some sort, to make it easier to deploy a non-packaged version of Java. That's what I've done for a proprietary app I have to keep running.
add a comment
|
Debian's general policy is to only have one version of a software package in a release. So, absent exceptional circumstances, there would only be one version of OpenJDK; buster has OpenJDK 11.
Details can be found in an email to debian-java and on various Java web sites but in short:
- OpenJDK 8 security support (already from third parties, e.g., Red Hat) ends before Buster's EOL. So sticking with it would risk that the Debian maintainers and/or security team would have to maintain Java (which is well beyond the manpower they have) or alternatively drop security support before buster EOL. (And well before Buster LTS EOL).
- If you need to stick with OpenJDK 8, you can stick with Stretch, which will be supported until 2020 and until 2022 via LTS. OpenJDK 8 will be supported for the lifetime of Stretch, including LTS.
- OpenJDK 11 is the current, upstream-supported LTS release.
You might also consider moving your Java app into a container of some sort, to make it easier to deploy a non-packaged version of Java. That's what I've done for a proprietary app I have to keep running.
add a comment
|
Debian's general policy is to only have one version of a software package in a release. So, absent exceptional circumstances, there would only be one version of OpenJDK; buster has OpenJDK 11.
Details can be found in an email to debian-java and on various Java web sites but in short:
- OpenJDK 8 security support (already from third parties, e.g., Red Hat) ends before Buster's EOL. So sticking with it would risk that the Debian maintainers and/or security team would have to maintain Java (which is well beyond the manpower they have) or alternatively drop security support before buster EOL. (And well before Buster LTS EOL).
- If you need to stick with OpenJDK 8, you can stick with Stretch, which will be supported until 2020 and until 2022 via LTS. OpenJDK 8 will be supported for the lifetime of Stretch, including LTS.
- OpenJDK 11 is the current, upstream-supported LTS release.
You might also consider moving your Java app into a container of some sort, to make it easier to deploy a non-packaged version of Java. That's what I've done for a proprietary app I have to keep running.
Debian's general policy is to only have one version of a software package in a release. So, absent exceptional circumstances, there would only be one version of OpenJDK; buster has OpenJDK 11.
Details can be found in an email to debian-java and on various Java web sites but in short:
- OpenJDK 8 security support (already from third parties, e.g., Red Hat) ends before Buster's EOL. So sticking with it would risk that the Debian maintainers and/or security team would have to maintain Java (which is well beyond the manpower they have) or alternatively drop security support before buster EOL. (And well before Buster LTS EOL).
- If you need to stick with OpenJDK 8, you can stick with Stretch, which will be supported until 2020 and until 2022 via LTS. OpenJDK 8 will be supported for the lifetime of Stretch, including LTS.
- OpenJDK 11 is the current, upstream-supported LTS release.
You might also consider moving your Java app into a container of some sort, to make it easier to deploy a non-packaged version of Java. That's what I've done for a proprietary app I have to keep running.
edited 6 hours ago
answered 6 hours ago
derobertderobert
79.9k8 gold badges178 silver badges235 bronze badges
79.9k8 gold badges178 silver badges235 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f542270%2fwhy-was-java-8-left-out-from-debian-buster%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Comments are not for extended discussion; this conversation has been moved to chat.
– Jeff Schaller♦
7 hours ago
Have a look at the Debian OpenJDK Team Package overview site and the openjdk-8 package tracker. Package
openjdk-8-jdkis available in sid (unstable), but didn't make it into buster, because there were (and still are) bugs.– Freddy
6 hours ago
@Freddy Could you make it an answer?
– peterh
5 hours ago
@Freddy in particular bugs.debian.org/cgi-bin/bugreport.cgi?bug=929650 — that's a bug to make sure it does not enter testing (and thus eventually stable). In a sense, that's not a real bug — it's not going to be fixed, can't be fixed, it will only be closed by eventually removing openjdk-8 from unstable. It's just how Debian implements "never release this package" (without fully removing it).
– derobert
3 hours ago
Ah, okay. Thanks for the clarification @derobert. But I still don't get what they mean by saying "It is used to prepare updates for stable-security".
– Freddy
3 hours ago