apt-get update is failing in debianIssue with fetching http://deb.debian.org/debian/dists/jessie-updates/InRelease with dockerHow to solve 404 Error in AWS apg-get for debian jessie fetch?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 repositoryDocker - Service 'php' failed to build: The command '/bin/sh
How can I deal with someone that wants to kill something that isn't supposed to be killed?
Trivial non-dark twist in dark fantasy
Acoustic guitar chords' positions vs those of a Bass guitar
"It is what it is"
Stellen - Putting, or putting away?
Do I have to mention my main character's age?
I have a domain, static IP and many devices I'd like to access outside my house. How to route them?
What do Unicorns want?
Strange LED behavior
MITM on HTTPS traffic in Kazakhstan 2019
Is there an English word to describe when a sound "protrudes"?
What does a Nintendo Game Boy do when turned on without a game cartridge inserted?
On a Gameboy, what happens when attempting to read/write external RAM while RAM is disabled?
Is there any direct train from LHR Airport to Newcastle Gateshead?
Can the caster of Time Stop still use their bonus action or reaction?
As the Ferris wheel turns
My current job follows "worst practices". How can I talk about my experience in an interview without giving off red flags?
Considerations when providing money to only one child out of two
How should I handle a question regarding my regrets during an interview?
You have no, but can try for yes
Why didn't NASA launch communications relay satellites for the Apollo missions?
what does the term highest qualification mean?
Piece of fabric in planter, how to use it?
Why is the UH-60 tail rotor canted?
apt-get update is failing in debian
Issue with fetching http://deb.debian.org/debian/dists/jessie-updates/InRelease with dockerHow to solve 404 Error in AWS apg-get for debian jessie fetch?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 repositoryDocker - Service 'php' failed to build: The command '/bin/sh
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
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 Mar 26 at 7:54
vinodh kumar Basavanivinodh kumar Basavani
1591 gold badge2 silver badges3 bronze badges
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 Mar 26 at 7:54
vinodh kumar Basavanivinodh kumar Basavani
1591 gold badge2 silver badges3 bronze badges
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
Mar 26 at 8:12
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
Mar 26 at 13:21
2
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
Mar 27 at 10:10
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 Mar 26 at 7:54
vinodh kumar Basavanivinodh kumar Basavani
1591 gold badge2 silver badges3 bronze badges
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 Mar 26 at 7:54
vinodh kumar Basavanivinodh kumar Basavani
1591 gold badge2 silver badges3 bronze badges
asked Mar 26 at 7:54
vinodh kumar Basavanivinodh kumar Basavani
1591 gold badge2 silver badges3 bronze badges
asked Mar 26 at 7:54
vinodh kumar Basavanivinodh kumar Basavani
1591 gold badge2 silver badges3 bronze badges
asked Mar 26 at 7:54
vinodh kumar Basavanivinodh kumar Basavani
1591 gold badge2 silver badges3 bronze badges
asked Mar 26 at 7:54
vinodh kumar Basavanivinodh kumar Basavani
1591 gold badge2 silver badges3 bronze badges
1591 gold badge2 silver badges3 bronze badges
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
Mar 26 at 8:12
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
Mar 26 at 13:21
2
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
Mar 27 at 10:10
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
Mar 26 at 8:12
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
Mar 26 at 13:21
2
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
Mar 27 at 10:10
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
Mar 26 at 8:12
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
Mar 26 at 8:12
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
Mar 26 at 13:21
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
Mar 26 at 13:21
2
2
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
Mar 27 at 10:10
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
Mar 27 at 10:10
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 Mar 26 at 9:44
Dan ClarkeDan Clarke
4883 silver badges5 bronze badges
9
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
Mar 26 at 11:01
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
Mar 26 at 11:47
1
Only the first two lines work, the updates are not in the archive!
– Daniel
Mar 27 at 9:27
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
Mar 27 at 18:27
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
Mar 27 at 21:59
|
show 3 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 Mar 26 at 14:22
A.K.A.K.
412 bronze badges
Why would they do that :O
– Lightness Races in Orbit
Mar 27 at 11:34
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
Mar 27 at 18:19
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
Mar 27 at 18:59
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
Mar 27 at 19:07
I have no problem with it being moved, but this answer suggests that they deleted the original before they brought the archived version online, leaving the contents completely inaccessible for this particular version of this particular distribution. If that's true, that's terrible and short-sighted. If it's not, we can edit the answer.
– Lightness Races in Orbit
Mar 28 at 0:36
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 Mar 27 at 4:44
AndiAnaAndiAna
1
3
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
Mar 27 at 8:48
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
);
);
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 Mar 26 at 9:44
Dan ClarkeDan Clarke
4883 silver badges5 bronze badges
9
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
Mar 26 at 11:01
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
Mar 26 at 11:47
1
Only the first two lines work, the updates are not in the archive!
– Daniel
Mar 27 at 9:27
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
Mar 27 at 18:27
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
Mar 27 at 21:59
|
show 3 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 Mar 26 at 9:44
Dan ClarkeDan Clarke
4883 silver badges5 bronze badges
9
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
Mar 26 at 11:01
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
Mar 26 at 11:47
1
Only the first two lines work, the updates are not in the archive!
– Daniel
Mar 27 at 9:27
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
Mar 27 at 18:27
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
Mar 27 at 21:59
|
show 3 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 Mar 26 at 9:44
Dan ClarkeDan Clarke
4883 silver badges5 bronze badges
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 Mar 26 at 9:44
Dan ClarkeDan Clarke
4883 silver badges5 bronze badges
edited Mar 27 at 22:04
answered Mar 26 at 9:44
Dan ClarkeDan Clarke
4883 silver badges5 bronze badges
answered Mar 26 at 9:44
Dan ClarkeDan Clarke
4883 silver badges5 bronze badges
answered Mar 26 at 9:44
Dan ClarkeDan Clarke
4883 silver badges5 bronze badges
4883 silver badges5 bronze badges
9
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
Mar 26 at 11:01
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
Mar 26 at 11:47
1
Only the first two lines work, the updates are not in the archive!
– Daniel
Mar 27 at 9:27
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
Mar 27 at 18:27
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
Mar 27 at 21:59
|
show 3 more comments
9
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
Mar 26 at 11:01
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
Mar 26 at 11:47
1
Only the first two lines work, the updates are not in the archive!
– Daniel
Mar 27 at 9:27
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
Mar 27 at 18:27
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
Mar 27 at 21:59
9
9
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
Mar 26 at 11:01
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
Mar 26 at 11:01
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
Mar 26 at 11:47
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
Mar 26 at 11:47
1
1
Only the first two lines work, the updates are not in the archive!
– Daniel
Mar 27 at 9:27
Only the first two lines work, the updates are not in the archive!
– Daniel
Mar 27 at 9:27
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
Mar 27 at 18:27
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
Mar 27 at 18:27
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
Mar 27 at 21:59
@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
Mar 27 at 21:59
|
show 3 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 Mar 26 at 14:22
A.K.A.K.
412 bronze badges
Why would they do that :O
– Lightness Races in Orbit
Mar 27 at 11:34
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
Mar 27 at 18:19
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
Mar 27 at 18:59
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
Mar 27 at 19:07
I have no problem with it being moved, but this answer suggests that they deleted the original before they brought the archived version online, leaving the contents completely inaccessible for this particular version of this particular distribution. If that's true, that's terrible and short-sighted. If it's not, we can edit the answer.
– Lightness Races in Orbit
Mar 28 at 0:36
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 Mar 26 at 14:22
A.K.A.K.
412 bronze badges
Why would they do that :O
– Lightness Races in Orbit
Mar 27 at 11:34
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
Mar 27 at 18:19
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
Mar 27 at 18:59
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
Mar 27 at 19:07
I have no problem with it being moved, but this answer suggests that they deleted the original before they brought the archived version online, leaving the contents completely inaccessible for this particular version of this particular distribution. If that's true, that's terrible and short-sighted. If it's not, we can edit the answer.
– Lightness Races in Orbit
Mar 28 at 0:36
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 Mar 26 at 14:22
A.K.A.K.
412 bronze badges
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 Mar 26 at 14:22
A.K.A.K.
412 bronze badges
answered Mar 26 at 14:22
A.K.A.K.
412 bronze badges
answered Mar 26 at 14:22
A.K.A.K.
412 bronze badges
answered Mar 26 at 14:22
A.K.A.K.
412 bronze badges
412 bronze badges
Why would they do that :O
– Lightness Races in Orbit
Mar 27 at 11:34
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
Mar 27 at 18:19
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
Mar 27 at 18:59
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
Mar 27 at 19:07
I have no problem with it being moved, but this answer suggests that they deleted the original before they brought the archived version online, leaving the contents completely inaccessible for this particular version of this particular distribution. If that's true, that's terrible and short-sighted. If it's not, we can edit the answer.
– Lightness Races in Orbit
Mar 28 at 0:36
add a comment |
Why would they do that :O
– Lightness Races in Orbit
Mar 27 at 11:34
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
Mar 27 at 18:19
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
Mar 27 at 18:59
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
Mar 27 at 19:07
I have no problem with it being moved, but this answer suggests that they deleted the original before they brought the archived version online, leaving the contents completely inaccessible for this particular version of this particular distribution. If that's true, that's terrible and short-sighted. If it's not, we can edit the answer.
– Lightness Races in Orbit
Mar 28 at 0:36
Why would they do that :O
– Lightness Races in Orbit
Mar 27 at 11:34
Why would they do that :O
– Lightness Races in Orbit
Mar 27 at 11:34
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
Mar 27 at 18:19
@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
Mar 27 at 18:19
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
Mar 27 at 18:59
@StephenKitt This answer says they have not been moved to the archive yet
– Lightness Races in Orbit
Mar 27 at 18:59
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
Mar 27 at 19:07
@Lightness oh, you were implying that they shouldn’t move the repository, and that deleting it was fine? Sorry, I misunderstood.
– Stephen Kitt
Mar 27 at 19:07
I have no problem with it being moved, but this answer suggests that they deleted the original before they brought the archived version online, leaving the contents completely inaccessible for this particular version of this particular distribution. If that's true, that's terrible and short-sighted. If it's not, we can edit the answer.
– Lightness Races in Orbit
Mar 28 at 0:36
I have no problem with it being moved, but this answer suggests that they deleted the original before they brought the archived version online, leaving the contents completely inaccessible for this particular version of this particular distribution. If that's true, that's terrible and short-sighted. If it's not, we can edit the answer.
– Lightness Races in Orbit
Mar 28 at 0:36
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 Mar 27 at 4:44
AndiAnaAndiAna
1
3
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
Mar 27 at 8:48
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 Mar 27 at 4:44
AndiAnaAndiAna
1
3
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
Mar 27 at 8:48
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 Mar 27 at 4:44
AndiAnaAndiAna
1
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 Mar 27 at 4:44
AndiAnaAndiAna
1
answered Mar 27 at 4:44
AndiAnaAndiAna
1
answered Mar 27 at 4:44
AndiAnaAndiAna
1
answered Mar 27 at 4:44
AndiAnaAndiAna
1
1
3
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
Mar 27 at 8:48
add a comment |
3
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
Mar 27 at 8:48
3
3
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
Mar 27 at 8:48
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
Mar 27 at 8:48
add a comment |
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
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
Mar 26 at 8:12
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
Mar 26 at 13:21
2
This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.
– a CVn
Mar 27 at 10:10