apt-get update is failing in debian
cat /etc/apt/sources.list
deb http://deb.debian.org/debian jessie main
deb http://deb.debian.org/debian jessie-updates main
deb http://security.debian.org jessie/updates main
then apt-get update is failing.
If i remove the second line then above command is working fine.
I checked in the repositories. there is no folder with name jessie-updates.
We have many docker builds which requires apt-get update.
I can't update all the docker files to remove that second line.
What is best approach to go ahead and also if they are removed permanently or a temporary glitch
linux debian docker apt-get
New contributor
add a comment |
cat /etc/apt/sources.list
deb http://deb.debian.org/debian jessie main
deb http://deb.debian.org/debian jessie-updates main
deb http://security.debian.org jessie/updates main
then apt-get update is failing.
If i remove the second line then above command is working fine.
I checked in the repositories. there is no folder with name jessie-updates.
We have many docker builds which requires apt-get update.
I can't update all the docker files to remove that second line.
What is best approach to go ahead and also if they are removed permanently or a temporary glitch
linux debian docker apt-get
New contributor
1
What do you mean it's failing? What do you actually see if it does? Why would you not be able to do this for your docker builds? Especially for those it should be easy. Change your base layer and just rebuild the images.
– Seth
20 hours ago
Try with https. Maybe one of the mirrors is down (it happens). Change url to force to your machine to get (probably) a new mirror.
– Giacomo Catenazzi
15 hours ago
add a comment |
cat /etc/apt/sources.list
deb http://deb.debian.org/debian jessie main
deb http://deb.debian.org/debian jessie-updates main
deb http://security.debian.org jessie/updates main
then apt-get update is failing.
If i remove the second line then above command is working fine.
I checked in the repositories. there is no folder with name jessie-updates.
We have many docker builds which requires apt-get update.
I can't update all the docker files to remove that second line.
What is best approach to go ahead and also if they are removed permanently or a temporary glitch
linux debian docker apt-get
New contributor
cat /etc/apt/sources.list
deb http://deb.debian.org/debian jessie main
deb http://deb.debian.org/debian jessie-updates main
deb http://security.debian.org jessie/updates main
then apt-get update is failing.
If i remove the second line then above command is working fine.
I checked in the repositories. there is no folder with name jessie-updates.
We have many docker builds which requires apt-get update.
I can't update all the docker files to remove that second line.
What is best approach to go ahead and also if they are removed permanently or a temporary glitch
linux debian docker apt-get
linux debian docker apt-get
New contributor
New contributor
New contributor
asked 20 hours ago
vinodh kumar Basavanivinodh kumar Basavani
663
663
New contributor
New contributor
1
What do you mean it's failing? What do you actually see if it does? Why would you not be able to do this for your docker builds? Especially for those it should be easy. Change your base layer and just rebuild the images.
– Seth
20 hours ago
Try with https. Maybe one of the mirrors is down (it happens). Change url to force to your machine to get (probably) a new mirror.
– Giacomo Catenazzi
15 hours ago
add a comment |
1
What do you mean it's failing? What do you actually see if it does? Why would you not be able to do this for your docker builds? Especially for those it should be easy. Change your base layer and just rebuild the images.
– Seth
20 hours ago
Try with https. Maybe one of the mirrors is down (it happens). Change url to force to your machine to get (probably) a new mirror.
– Giacomo Catenazzi
15 hours ago
1
1
What do you mean it's failing? What do you actually see if it does? Why would you not be able to do this for your docker builds? Especially for those it should be easy. Change your base layer and just rebuild the images.
– Seth
20 hours ago
What do you mean it's failing? What do you actually see if it does? Why would you not be able to do this for your docker builds? Especially for those it should be easy. Change your base layer and just rebuild the images.
– Seth
20 hours ago
Try with https. Maybe one of the mirrors is down (it happens). Change url to force to your machine to get (probably) a new mirror.
– Giacomo Catenazzi
15 hours ago
Try with https. Maybe one of the mirrors is down (it happens). Change url to force to your machine to get (probably) a new mirror.
– Giacomo Catenazzi
15 hours ago
add a comment |
3 Answers
3
active
oldest
votes
According to the IRC channel for Debian, Jessie is now not supported:
Debian Jessie, jessie-updates and jessie-backports REMOVED 2019-03-24
Your solution is either to upgrade to Stretch, or update your /etc/apt/sources.list
to the following:
deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ jessie main
deb http://archive.debian.org/debian-security/ jessie/updates main
deb-src http://archive.debian.org/debian-security/ jessie/updates main
deb http://archive.debian.org/debian/ jessie-updates main
deb-src http://archive.debian.org/debian/ jessie-updates main
New contributor
1
Thank you. Do you know why the official wiki says the official end of support is on the 30th of june 2020, in more than one year, then ? That's crazy we couldn't see a mention of jessie going down anywhere before that ! wiki.debian.org/LTS
– Ten
17 hours ago
2
This is all I could find about what they changed: lists.debian.org/debian-devel-announce/2019/03/msg00006.html so LTS is still supported, but -updates has moved to archive.
– Dan Clarke
17 hours ago
add a comment |
The debian Team did not move jessie-updates to the archive repository (yet). But they already removed it from the regular repositories. So you currently have no access to jessie-updates. Therefore you need to remove it from the sources.list.
My currently working sources.list:
deb http://deb.debian.org/debian jessie main
deb http://security.debian.org/debian-security jessie/updates main
New contributor
add a comment |
Jessie is no longer supported. They have taken it off the automatic updates for security reasons.
You need to do a full reinstall of bionic beaver.
At least that’s what I did.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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/3.0/"u003ecc by-sa 3.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
});
}
});
vinodh kumar Basavani is a new contributor. Be nice, and check out our Code of Conduct.
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%2fsuperuser.com%2fquestions%2f1417617%2fapt-get-update-is-failing-in-debian%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
According to the IRC channel for Debian, Jessie is now not supported:
Debian Jessie, jessie-updates and jessie-backports REMOVED 2019-03-24
Your solution is either to upgrade to Stretch, or update your /etc/apt/sources.list
to the following:
deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ jessie main
deb http://archive.debian.org/debian-security/ jessie/updates main
deb-src http://archive.debian.org/debian-security/ jessie/updates main
deb http://archive.debian.org/debian/ jessie-updates main
deb-src http://archive.debian.org/debian/ jessie-updates main
New contributor
1
Thank you. Do you know why the official wiki says the official end of support is on the 30th of june 2020, in more than one year, then ? That's crazy we couldn't see a mention of jessie going down anywhere before that ! wiki.debian.org/LTS
– Ten
17 hours ago
2
This is all I could find about what they changed: lists.debian.org/debian-devel-announce/2019/03/msg00006.html so LTS is still supported, but -updates has moved to archive.
– Dan Clarke
17 hours ago
add a comment |
According to the IRC channel for Debian, Jessie is now not supported:
Debian Jessie, jessie-updates and jessie-backports REMOVED 2019-03-24
Your solution is either to upgrade to Stretch, or update your /etc/apt/sources.list
to the following:
deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ jessie main
deb http://archive.debian.org/debian-security/ jessie/updates main
deb-src http://archive.debian.org/debian-security/ jessie/updates main
deb http://archive.debian.org/debian/ jessie-updates main
deb-src http://archive.debian.org/debian/ jessie-updates main
New contributor
1
Thank you. Do you know why the official wiki says the official end of support is on the 30th of june 2020, in more than one year, then ? That's crazy we couldn't see a mention of jessie going down anywhere before that ! wiki.debian.org/LTS
– Ten
17 hours ago
2
This is all I could find about what they changed: lists.debian.org/debian-devel-announce/2019/03/msg00006.html so LTS is still supported, but -updates has moved to archive.
– Dan Clarke
17 hours ago
add a comment |
According to the IRC channel for Debian, Jessie is now not supported:
Debian Jessie, jessie-updates and jessie-backports REMOVED 2019-03-24
Your solution is either to upgrade to Stretch, or update your /etc/apt/sources.list
to the following:
deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ jessie main
deb http://archive.debian.org/debian-security/ jessie/updates main
deb-src http://archive.debian.org/debian-security/ jessie/updates main
deb http://archive.debian.org/debian/ jessie-updates main
deb-src http://archive.debian.org/debian/ jessie-updates main
New contributor
According to the IRC channel for Debian, Jessie is now not supported:
Debian Jessie, jessie-updates and jessie-backports REMOVED 2019-03-24
Your solution is either to upgrade to Stretch, or update your /etc/apt/sources.list
to the following:
deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ jessie main
deb http://archive.debian.org/debian-security/ jessie/updates main
deb-src http://archive.debian.org/debian-security/ jessie/updates main
deb http://archive.debian.org/debian/ jessie-updates main
deb-src http://archive.debian.org/debian/ jessie-updates main
New contributor
edited 16 hours ago
New contributor
answered 19 hours ago
Dan ClarkeDan Clarke
1414
1414
New contributor
New contributor
1
Thank you. Do you know why the official wiki says the official end of support is on the 30th of june 2020, in more than one year, then ? That's crazy we couldn't see a mention of jessie going down anywhere before that ! wiki.debian.org/LTS
– Ten
17 hours ago
2
This is all I could find about what they changed: lists.debian.org/debian-devel-announce/2019/03/msg00006.html so LTS is still supported, but -updates has moved to archive.
– Dan Clarke
17 hours ago
add a comment |
1
Thank you. Do you know why the official wiki says the official end of support is on the 30th of june 2020, in more than one year, then ? That's crazy we couldn't see a mention of jessie going down anywhere before that ! wiki.debian.org/LTS
– Ten
17 hours ago
2
This is all I could find about what they changed: lists.debian.org/debian-devel-announce/2019/03/msg00006.html so LTS is still supported, but -updates has moved to archive.
– Dan Clarke
17 hours ago
1
1
Thank you. Do you know why the official wiki says the official end of support is on the 30th of june 2020, in more than one year, then ? That's crazy we couldn't see a mention of jessie going down anywhere before that ! wiki.debian.org/LTS
– Ten
17 hours ago
Thank you. Do you know why the official wiki says the official end of support is on the 30th of june 2020, in more than one year, then ? That's crazy we couldn't see a mention of jessie going down anywhere before that ! wiki.debian.org/LTS
– Ten
17 hours ago
2
2
This is all I could find about what they changed: lists.debian.org/debian-devel-announce/2019/03/msg00006.html so LTS is still supported, but -updates has moved to archive.
– Dan Clarke
17 hours ago
This is all I could find about what they changed: lists.debian.org/debian-devel-announce/2019/03/msg00006.html so LTS is still supported, but -updates has moved to archive.
– Dan Clarke
17 hours ago
add a comment |
The debian Team did not move jessie-updates to the archive repository (yet). But they already removed it from the regular repositories. So you currently have no access to jessie-updates. Therefore you need to remove it from the sources.list.
My currently working sources.list:
deb http://deb.debian.org/debian jessie main
deb http://security.debian.org/debian-security jessie/updates main
New contributor
add a comment |
The debian Team did not move jessie-updates to the archive repository (yet). But they already removed it from the regular repositories. So you currently have no access to jessie-updates. Therefore you need to remove it from the sources.list.
My currently working sources.list:
deb http://deb.debian.org/debian jessie main
deb http://security.debian.org/debian-security jessie/updates main
New contributor
add a comment |
The debian Team did not move jessie-updates to the archive repository (yet). But they already removed it from the regular repositories. So you currently have no access to jessie-updates. Therefore you need to remove it from the sources.list.
My currently working sources.list:
deb http://deb.debian.org/debian jessie main
deb http://security.debian.org/debian-security jessie/updates main
New contributor
The debian Team did not move jessie-updates to the archive repository (yet). But they already removed it from the regular repositories. So you currently have no access to jessie-updates. Therefore you need to remove it from the sources.list.
My currently working sources.list:
deb http://deb.debian.org/debian jessie main
deb http://security.debian.org/debian-security jessie/updates main
New contributor
New contributor
answered 14 hours ago
A.K.A.K.
212
212
New contributor
New contributor
add a comment |
add a comment |
Jessie is no longer supported. They have taken it off the automatic updates for security reasons.
You need to do a full reinstall of bionic beaver.
At least that’s what I did.
New contributor
add a comment |
Jessie is no longer supported. They have taken it off the automatic updates for security reasons.
You need to do a full reinstall of bionic beaver.
At least that’s what I did.
New contributor
add a comment |
Jessie is no longer supported. They have taken it off the automatic updates for security reasons.
You need to do a full reinstall of bionic beaver.
At least that’s what I did.
New contributor
Jessie is no longer supported. They have taken it off the automatic updates for security reasons.
You need to do a full reinstall of bionic beaver.
At least that’s what I did.
New contributor
New contributor
answered 3 mins ago
NoobPythonNoobPython
1
1
New contributor
New contributor
add a comment |
add a comment |
vinodh kumar Basavani is a new contributor. Be nice, and check out our Code of Conduct.
vinodh kumar Basavani is a new contributor. Be nice, and check out our Code of Conduct.
vinodh kumar Basavani is a new contributor. Be nice, and check out our Code of Conduct.
vinodh kumar Basavani is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1417617%2fapt-get-update-is-failing-in-debian%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
1
What do you mean it's failing? What do you actually see if it does? Why would you not be able to do this for your docker builds? Especially for those it should be easy. Change your base layer and just rebuild the images.
– Seth
20 hours ago
Try with https. Maybe one of the mirrors is down (it happens). Change url to force to your machine to get (probably) a new mirror.
– Giacomo Catenazzi
15 hours ago