apt-get update is failing in debian

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

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

asked Mar 26 at 7:54

vinodh kumar Basavani

12923

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

1

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

asked Mar 26 at 7:54

vinodh kumar Basavani

12923

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

1

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

asked Mar 26 at 7:54

vinodh kumar Basavani

12923

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 Basavani

12923

asked Mar 26 at 7:54

vinodh kumar Basavani

12923

asked Mar 26 at 7:54

vinodh kumar Basavani

12923

asked Mar 26 at 7:54

vinodh kumar Basavani

12923

asked Mar 26 at 7:54

vinodh kumar Basavani

12923

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

1

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

1

This is essentially the same question as Failed to fetch jessie backports repository on Unix & Linux.

– a CVn
Mar 27 at 10:10

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

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.

edited Mar 27 at 22:04

answered Mar 26 at 9:44

Dan Clarke

37825

8

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, except jessie-updates which has been removed and jessie-backports which 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 keep deb http://security.debian.org jessie/updates main — that is where Jessie LTS updates come from.

– derobert
Mar 27 at 21:59

|
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 Mar 26 at 14:22

A.K.

312

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 |

-5

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

AndiAna

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
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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

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

Name

Required, but never shown

3 Answers
3

active

oldest

votes

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.

edited Mar 27 at 22:04

answered Mar 26 at 9:44

Dan Clarke

37825

8

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, except jessie-updates which has been removed and jessie-backports which 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 keep deb http://security.debian.org jessie/updates main — that is where Jessie LTS updates come from.

– derobert
Mar 27 at 21:59

|
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.

edited Mar 27 at 22:04

answered Mar 26 at 9:44

Dan Clarke

37825

8

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, except jessie-updates which has been removed and jessie-backports which 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 keep deb http://security.debian.org jessie/updates main — that is where Jessie LTS updates come from.

– derobert
Mar 27 at 21:59

|
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.

edited Mar 27 at 22:04

answered Mar 26 at 9:44

Dan Clarke

37825

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.

edited Mar 27 at 22:04

answered Mar 26 at 9:44

Dan Clarke

37825

edited Mar 27 at 22:04

answered Mar 26 at 9:44

Dan Clarke

37825

answered Mar 26 at 9:44

Dan Clarke

37825

answered Mar 26 at 9:44

Dan Clarke

37825

8

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, except jessie-updates which has been removed and jessie-backports which 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 keep deb http://security.debian.org jessie/updates main — that is where Jessie LTS updates come from.

– derobert
Mar 27 at 21:59

|
show 2 more comments

8

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, except jessie-updates which has been removed and jessie-backports which 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 keep deb http://security.debian.org jessie/updates main — that is where Jessie LTS updates come from.

– derobert
Mar 27 at 21:59

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

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

Only the first two lines work, the updates are not in the archive!

– Daniel
Mar 27 at 9: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

@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 2 more comments

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.

312

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 |

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.

312

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 |

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.

312

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.

312

answered Mar 26 at 14:22

A.K.

312

answered Mar 26 at 14:22

A.K.

312

answered Mar 26 at 14:22

A.K.

312

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

@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 |

-5

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

AndiAna

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
Mar 27 at 8:48

add a comment |

-5

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

AndiAna

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
Mar 27 at 8:48

add a comment |

-5

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

AndiAna

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

AndiAna

answered Mar 27 at 4:44

AndiAna

answered Mar 27 at 4:44

AndiAna

answered Mar 27 at 4:44

AndiAna

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
Mar 27 at 8:48

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
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 |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfrgtkky