apt-get update is failing in debianCannot install mc using apt-get Reinstalling Debian Squeeze via APT after significant core package removalHow to install Valgrind on debian 6 ARM processor?Debian: why are the suggested upgrades from apt-get and synaptic different?debian install package bittwistapt-get update still doesn't find autoconfDebian Scripting to remove the logging during apt-get installCannot install SSH server on Debian JessieHow to check which programs are related to a distribution of a specific repositoryapt-get throws 400 URI failure when trying to download docker-ce
Is exact Kanji stroke length important?
How to be diplomatic in refusing to write code that breaches the privacy of our users
How did Arya survive the stabbing?
What does "I’d sit this one out, Cap," imply or mean in the context?
Lay out the Carpet
How does it work when somebody invests in my business?
Why are there no referendums in the US?
What does the word "Atten" mean?
CREATE opcode: what does it really do?
Large drywall patch supports
Increase performance creating Mandelbrot set in python
Are student evaluations of teaching assistants read by others in the faculty?
Avoiding estate tax by giving multiple gifts
Term for the "extreme-extension" version of a straw man fallacy?
I'm in charge of equipment buying but no one's ever happy with what I choose. How to fix this?
Trouble understanding the speech of overseas colleagues
How to safely derail a train during transit?
How to write papers efficiently when English isn't my first language?
Is this version of a gravity generator feasible?
How did Doctor Strange see the winning outcome in Avengers: Infinity War?
Why didn't Theresa May consult with Parliament before negotiating a deal with the EU?
Is HostGator storing my password in plaintext?
Fastening aluminum fascia to wooden subfascia
Unreliable Magic - Is it worth it?
apt-get update is failing in debian
Cannot install mc using apt-get Reinstalling Debian Squeeze via APT after significant core package removalHow to install Valgrind on debian 6 ARM processor?Debian: why are the suggested upgrades from apt-get and synaptic different?debian install package bittwistapt-get update still doesn't find autoconfDebian Scripting to remove the logging during apt-get installCannot install SSH server on Debian JessieHow to check which programs are related to a distribution of a specific repositoryapt-get throws 400 URI failure when trying to download docker-ce
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
asked yesterday
vinodh kumar Basavanivinodh kumar Basavani
10913
New contributor
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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
asked yesterday
vinodh kumar Basavanivinodh kumar Basavani
10913
New contributor
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
3
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
yesterday
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
yesterday
1
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
13 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
asked yesterday
vinodh kumar Basavanivinodh kumar Basavani
10913
New contributor
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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
asked yesterday
vinodh kumar Basavanivinodh kumar Basavani
10913
New contributor
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
vinodh kumar Basavanivinodh kumar Basavani
10913
New contributor
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
vinodh kumar Basavanivinodh kumar Basavani
10913
New contributor
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
vinodh kumar Basavanivinodh kumar Basavani
10913
asked yesterday
vinodh kumar Basavanivinodh kumar Basavani
10913
10913
New contributor
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
vinodh kumar Basavani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
3
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
yesterday
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
yesterday
1
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
13 hours ago
add a comment |
3
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
yesterday
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
yesterday
1
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
13 hours ago
3
3
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
yesterday
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
yesterday
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
yesterday
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
yesterday
1
1
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
13 hours ago
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
13 hours ago
add a comment |
3 Answers
3
active
oldest
votes
According to the IRC channel for Debian, jessie-updates is now not supported:
Oldstable: 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://security.debian.org jessie/updates main
deb-src http://security.debian.org jessie/updates main
jessie-updates has been removed and jessie-backports has been archived
Thanks to comments from Stephen Kitt & Daniel below.
answered yesterday
Dan ClarkeDan Clarke
33814
New contributor
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
7
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
yesterday
4
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
yesterday
1
Only the first two lines work, the updates are not in the archive!
– Daniel
13 hours ago
1
This is incorrect, at least for architectures which are still supported in Jessie LTS. Those are still served by the main archive, exceptjessie-updateswhich has been removed andjessie-backportswhich has been archived.
– Stephen Kitt
4 hours ago
1
@DanClarke I think you didn't fully edit in Stephen Kitt's suggestion. Please keepdeb http://security.debian.org jessie/updates main— that is where Jessie LTS updates come from.
– derobert
1 hour ago
|
show 2 more comments
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
answered yesterday
A.K.A.K.
412
New contributor
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Why would they do that :O
– Lightness Races in Orbit
11 hours ago
1
@Lightness because all the updates have been merged into the main archive, and there will be no further updates so the updates repository is no longer necessary.
– Stephen Kitt
4 hours ago
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
4 hours ago
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
4 hours ago
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.
answered 18 hours ago
NoobPythonNoobPython
1
New contributor
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
Bionic Beaver is Ubuntu, whereas the question is related to Debian, whilst Ubuntu does use the Debian architecture, installing cross OSs can get complicated. If you need to update within Debian, Stretch (9.x) is the best route to go.
– Dan Clarke
14 hours ago
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-updates is now not supported:
Oldstable: 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://security.debian.org jessie/updates main
deb-src http://security.debian.org jessie/updates main
jessie-updates has been removed and jessie-backports has been archived
Thanks to comments from Stephen Kitt & Daniel below.
answered yesterday
Dan ClarkeDan Clarke
33814
New contributor
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
7
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
yesterday
4
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
yesterday
1
Only the first two lines work, the updates are not in the archive!
– Daniel
13 hours ago
1
This is incorrect, at least for architectures which are still supported in Jessie LTS. Those are still served by the main archive, exceptjessie-updateswhich has been removed andjessie-backportswhich has been archived.
– Stephen Kitt
4 hours ago
1
@DanClarke I think you didn't fully edit in Stephen Kitt's suggestion. Please keepdeb http://security.debian.org jessie/updates main— that is where Jessie LTS updates come from.
– derobert
1 hour ago
|
show 2 more comments
According to the IRC channel for Debian, jessie-updates is now not supported:
Oldstable: 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://security.debian.org jessie/updates main
deb-src http://security.debian.org jessie/updates main
jessie-updates has been removed and jessie-backports has been archived
Thanks to comments from Stephen Kitt & Daniel below.
answered yesterday
Dan ClarkeDan Clarke
33814
New contributor
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
7
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
yesterday
4
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
yesterday
1
Only the first two lines work, the updates are not in the archive!
– Daniel
13 hours ago
1
This is incorrect, at least for architectures which are still supported in Jessie LTS. Those are still served by the main archive, exceptjessie-updateswhich has been removed andjessie-backportswhich has been archived.
– Stephen Kitt
4 hours ago
1
@DanClarke I think you didn't fully edit in Stephen Kitt's suggestion. Please keepdeb http://security.debian.org jessie/updates main— that is where Jessie LTS updates come from.
– derobert
1 hour ago
|
show 2 more comments
According to the IRC channel for Debian, jessie-updates is now not supported:
Oldstable: 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://security.debian.org jessie/updates main
deb-src http://security.debian.org jessie/updates main
jessie-updates has been removed and jessie-backports has been archived
Thanks to comments from Stephen Kitt & Daniel below.
answered yesterday
Dan ClarkeDan Clarke
33814
New contributor
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
According to the IRC channel for Debian, jessie-updates is now not supported:
Oldstable: 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://security.debian.org jessie/updates main
deb-src http://security.debian.org jessie/updates main
jessie-updates has been removed and jessie-backports has been archived
Thanks to comments from Stephen Kitt & Daniel below.
answered yesterday
Dan ClarkeDan Clarke
33814
New contributor
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 1 hour ago
answered yesterday
Dan ClarkeDan Clarke
33814
New contributor
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
Dan ClarkeDan Clarke
33814
answered yesterday
Dan ClarkeDan Clarke
33814
33814
New contributor
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Dan Clarke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
7
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
yesterday
4
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
yesterday
1
Only the first two lines work, the updates are not in the archive!
– Daniel
13 hours ago
1
This is incorrect, at least for architectures which are still supported in Jessie LTS. Those are still served by the main archive, exceptjessie-updateswhich has been removed andjessie-backportswhich has been archived.
– Stephen Kitt
4 hours ago
1
@DanClarke I think you didn't fully edit in Stephen Kitt's suggestion. Please keepdeb http://security.debian.org jessie/updates main— that is where Jessie LTS updates come from.
– derobert
1 hour ago
|
show 2 more comments
7
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
yesterday
4
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
yesterday
1
Only the first two lines work, the updates are not in the archive!
– Daniel
13 hours ago
1
This is incorrect, at least for architectures which are still supported in Jessie LTS. Those are still served by the main archive, exceptjessie-updateswhich has been removed andjessie-backportswhich has been archived.
– Stephen Kitt
4 hours ago
1
@DanClarke I think you didn't fully edit in Stephen Kitt's suggestion. Please keepdeb http://security.debian.org jessie/updates main— that is where Jessie LTS updates come from.
– derobert
1 hour ago
7
7
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
yesterday
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
yesterday
4
4
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
yesterday
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
yesterday
1
1
Only the first two lines work, the updates are not in the archive!
– Daniel
13 hours ago
Only the first two lines work, the updates are not in the archive!
– Daniel
13 hours ago
1
1
This is incorrect, at least for architectures which are still supported in Jessie LTS. Those are still served by the main archive, except
jessie-updates which has been removed and jessie-backports which has been archived.– Stephen Kitt
4 hours ago
This is incorrect, at least for architectures which are still supported in Jessie LTS. Those are still served by the main archive, except
jessie-updates which has been removed and jessie-backports which has been archived.– Stephen Kitt
4 hours ago
1
1
@DanClarke I think you didn't fully edit in Stephen Kitt's suggestion. Please keep
deb http://security.debian.org jessie/updates main — that is where Jessie LTS updates come from.– derobert
1 hour ago
@DanClarke I think you didn't fully edit in Stephen Kitt's suggestion. Please keep
deb http://security.debian.org jessie/updates main — that is where Jessie LTS updates come from.– derobert
1 hour ago
|
show 2 more comments
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
answered yesterday
A.K.A.K.
412
New contributor
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Why would they do that :O
– Lightness Races in Orbit
11 hours ago
1
@Lightness because all the updates have been merged into the main archive, and there will be no further updates so the updates repository is no longer necessary.
– Stephen Kitt
4 hours ago
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
4 hours ago
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
4 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
answered yesterday
A.K.A.K.
412
New contributor
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Why would they do that :O
– Lightness Races in Orbit
11 hours ago
1
@Lightness because all the updates have been merged into the main archive, and there will be no further updates so the updates repository is no longer necessary.
– Stephen Kitt
4 hours ago
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
4 hours ago
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
4 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
answered yesterday
A.K.A.K.
412
New contributor
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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
answered yesterday
A.K.A.K.
412
New contributor
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
A.K.A.K.
412
New contributor
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
A.K.A.K.
412
answered yesterday
A.K.A.K.
412
412
New contributor
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
A.K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Why would they do that :O
– Lightness Races in Orbit
11 hours ago
1
@Lightness because all the updates have been merged into the main archive, and there will be no further updates so the updates repository is no longer necessary.
– Stephen Kitt
4 hours ago
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
4 hours ago
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
4 hours ago
add a comment |
Why would they do that :O
– Lightness Races in Orbit
11 hours ago
1
@Lightness because all the updates have been merged into the main archive, and there will be no further updates so the updates repository is no longer necessary.
– Stephen Kitt
4 hours ago
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
4 hours ago
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
4 hours ago
Why would they do that :O
– Lightness Races in Orbit
11 hours ago
Why would they do that :O
– Lightness Races in Orbit
11 hours ago
1
1
@Lightness because all the updates have been merged into the main archive, and there will be no further updates so the updates repository is no longer necessary.
– Stephen Kitt
4 hours ago
@Lightness because all the updates have been merged into the main archive, and there will be no further updates so the updates repository is no longer necessary.
– Stephen Kitt
4 hours ago
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
4 hours ago
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
4 hours ago
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
4 hours ago
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
4 hours ago
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.
answered 18 hours ago
NoobPythonNoobPython
1
New contributor
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
Bionic Beaver is Ubuntu, whereas the question is related to Debian, whilst Ubuntu does use the Debian architecture, installing cross OSs can get complicated. If you need to update within Debian, Stretch (9.x) is the best route to go.
– Dan Clarke
14 hours ago
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.
answered 18 hours ago
NoobPythonNoobPython
1
New contributor
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
Bionic Beaver is Ubuntu, whereas the question is related to Debian, whilst Ubuntu does use the Debian architecture, installing cross OSs can get complicated. If you need to update within Debian, Stretch (9.x) is the best route to go.
– Dan Clarke
14 hours ago
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.
answered 18 hours ago
NoobPythonNoobPython
1
New contributor
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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.
answered 18 hours ago
NoobPythonNoobPython
1
New contributor
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 18 hours ago
NoobPythonNoobPython
1
New contributor
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 18 hours ago
NoobPythonNoobPython
1
answered 18 hours ago
NoobPythonNoobPython
1
1
New contributor
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
NoobPython is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
Bionic Beaver is Ubuntu, whereas the question is related to Debian, whilst Ubuntu does use the Debian architecture, installing cross OSs can get complicated. If you need to update within Debian, Stretch (9.x) is the best route to go.
– Dan Clarke
14 hours ago
add a comment |
2
Bionic Beaver is Ubuntu, whereas the question is related to Debian, whilst Ubuntu does use the Debian architecture, installing cross OSs can get complicated. If you need to update within Debian, Stretch (9.x) is the best route to go.
– Dan Clarke
14 hours ago
2
2
Bionic Beaver is Ubuntu, whereas the question is related to Debian, whilst Ubuntu does use the Debian architecture, installing cross OSs can get complicated. If you need to update within Debian, Stretch (9.x) is the best route to go.
– Dan Clarke
14 hours ago
Bionic Beaver is Ubuntu, whereas the question is related to Debian, whilst Ubuntu does use the Debian architecture, installing cross OSs can get complicated. If you need to update within Debian, Stretch (9.x) is the best route to go.
– Dan Clarke
14 hours ago
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
-apt-get, debian, docker, linux
3
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
yesterday
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
yesterday
1
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
13 hours ago