“No release file†errors when trying to upgrade from version 17.10 to 18.04
Clash Royale CLAN TAG#URR8PPP up vote
4
down vote
favorite
1
While upgrading from ubuntu 17.10 to 18.04 it is showing an error regarding zesty-update release and zesty-security release.
E:The repository 'http://in.archive.ubuntu.com/ubuntu zesty-updates Release'
does not have a Release file.
W:Updating from such a repository can't be done securely,
and is therefore disabled by default.
W:See apt-secure(8) manpage for repository creation and user configuration details.
E:The repository 'http://security.ubuntu.com/ubuntu zesty-security Release'
does not have a Release file.`
The above error is showing and I am also unable to update also for the same reason.
What should I do now to overcome this problem?
updates update-manager repository
edited May 9 at 14:04
Zanna
47.9k13119227
asked May 9 at 12:29
Mohit Gidwani
211
add a comment |Â
up vote
4
down vote
favorite
1
While upgrading from ubuntu 17.10 to 18.04 it is showing an error regarding zesty-update release and zesty-security release.
E:The repository 'http://in.archive.ubuntu.com/ubuntu zesty-updates Release'
does not have a Release file.
W:Updating from such a repository can't be done securely,
and is therefore disabled by default.
W:See apt-secure(8) manpage for repository creation and user configuration details.
E:The repository 'http://security.ubuntu.com/ubuntu zesty-security Release'
does not have a Release file.`
The above error is showing and I am also unable to update also for the same reason.
What should I do now to overcome this problem?
updates update-manager repository
edited May 9 at 14:04
Zanna
47.9k13119227
asked May 9 at 12:29
Mohit Gidwani
211
1
Have you recently upgraded from 17.04 to 17.10?
– Kulfy
May 9 at 12:34
Zesty was Ubuntu 17.04 (2017 April release, EOL 13-Jan-2018), Artful is 17.10 (2017 October release). Your errors as posted imply you are running 17.04 which is EOL, and post-EOL the repositories are moved fromarchive.ubuntu.comtoold-releases.ubuntu.comcausing the errors you've listed (until you modify your system accordingly), and @AmanMittal's question. If you're trying to upgrade 17.04 to 18.04 there is an additional step needed; so please confirm your version.
– guiverc
May 9 at 12:58
1
@guiverc Well there's also a possibility that he recently upgraded to 17.10 from 17.04 and some of his sources weren't updated to that of artful.
– Kulfy
May 9 at 13:02
Thanks @AmanMittal - i've 'improved' my text (i hope)
– guiverc
May 9 at 13:03
add a comment |Â
up vote
4
down vote
favorite
1
up vote
4
down vote
favorite
1
1
While upgrading from ubuntu 17.10 to 18.04 it is showing an error regarding zesty-update release and zesty-security release.
E:The repository 'http://in.archive.ubuntu.com/ubuntu zesty-updates Release'
does not have a Release file.
W:Updating from such a repository can't be done securely,
and is therefore disabled by default.
W:See apt-secure(8) manpage for repository creation and user configuration details.
E:The repository 'http://security.ubuntu.com/ubuntu zesty-security Release'
does not have a Release file.`
The above error is showing and I am also unable to update also for the same reason.
What should I do now to overcome this problem?
updates update-manager repository
edited May 9 at 14:04
Zanna
47.9k13119227
asked May 9 at 12:29
Mohit Gidwani
211
While upgrading from ubuntu 17.10 to 18.04 it is showing an error regarding zesty-update release and zesty-security release.
E:The repository 'http://in.archive.ubuntu.com/ubuntu zesty-updates Release'
does not have a Release file.
W:Updating from such a repository can't be done securely,
and is therefore disabled by default.
W:See apt-secure(8) manpage for repository creation and user configuration details.
E:The repository 'http://security.ubuntu.com/ubuntu zesty-security Release'
does not have a Release file.`
The above error is showing and I am also unable to update also for the same reason.
What should I do now to overcome this problem?
updates update-manager repository
edited May 9 at 14:04
Zanna
47.9k13119227
asked May 9 at 12:29
Mohit Gidwani
211
edited May 9 at 14:04
Zanna
47.9k13119227
edited May 9 at 14:04
Zanna
47.9k13119227
edited May 9 at 14:04
Zanna
47.9k13119227
47.9k13119227
asked May 9 at 12:29
Mohit Gidwani
211
asked May 9 at 12:29
Mohit Gidwani
211
asked May 9 at 12:29
Mohit Gidwani
211
211
1
Have you recently upgraded from 17.04 to 17.10?
– Kulfy
May 9 at 12:34
Zesty was Ubuntu 17.04 (2017 April release, EOL 13-Jan-2018), Artful is 17.10 (2017 October release). Your errors as posted imply you are running 17.04 which is EOL, and post-EOL the repositories are moved fromarchive.ubuntu.comtoold-releases.ubuntu.comcausing the errors you've listed (until you modify your system accordingly), and @AmanMittal's question. If you're trying to upgrade 17.04 to 18.04 there is an additional step needed; so please confirm your version.
– guiverc
May 9 at 12:58
1
@guiverc Well there's also a possibility that he recently upgraded to 17.10 from 17.04 and some of his sources weren't updated to that of artful.
– Kulfy
May 9 at 13:02
Thanks @AmanMittal - i've 'improved' my text (i hope)
– guiverc
May 9 at 13:03
add a comment |Â
1
Have you recently upgraded from 17.04 to 17.10?
– Kulfy
May 9 at 12:34
Zesty was Ubuntu 17.04 (2017 April release, EOL 13-Jan-2018), Artful is 17.10 (2017 October release). Your errors as posted imply you are running 17.04 which is EOL, and post-EOL the repositories are moved fromarchive.ubuntu.comtoold-releases.ubuntu.comcausing the errors you've listed (until you modify your system accordingly), and @AmanMittal's question. If you're trying to upgrade 17.04 to 18.04 there is an additional step needed; so please confirm your version.
– guiverc
May 9 at 12:58
1
@guiverc Well there's also a possibility that he recently upgraded to 17.10 from 17.04 and some of his sources weren't updated to that of artful.
– Kulfy
May 9 at 13:02
Thanks @AmanMittal - i've 'improved' my text (i hope)
– guiverc
May 9 at 13:03
1
1
Have you recently upgraded from 17.04 to 17.10?
– Kulfy
May 9 at 12:34
Have you recently upgraded from 17.04 to 17.10?
– Kulfy
May 9 at 12:34
Zesty was Ubuntu 17.04 (2017 April release, EOL 13-Jan-2018), Artful is 17.10 (2017 October release). Your errors as posted imply you are running 17.04 which is EOL, and post-EOL the repositories are moved from
archive.ubuntu.com to old-releases.ubuntu.com causing the errors you've listed (until you modify your system accordingly), and @AmanMittal's question. If you're trying to upgrade 17.04 to 18.04 there is an additional step needed; so please confirm your version.– guiverc
May 9 at 12:58
Zesty was Ubuntu 17.04 (2017 April release, EOL 13-Jan-2018), Artful is 17.10 (2017 October release). Your errors as posted imply you are running 17.04 which is EOL, and post-EOL the repositories are moved from
archive.ubuntu.com to old-releases.ubuntu.com causing the errors you've listed (until you modify your system accordingly), and @AmanMittal's question. If you're trying to upgrade 17.04 to 18.04 there is an additional step needed; so please confirm your version.– guiverc
May 9 at 12:58
1
1
@guiverc Well there's also a possibility that he recently upgraded to 17.10 from 17.04 and some of his sources weren't updated to that of artful.
– Kulfy
May 9 at 13:02
@guiverc Well there's also a possibility that he recently upgraded to 17.10 from 17.04 and some of his sources weren't updated to that of artful.
– Kulfy
May 9 at 13:02
Thanks @AmanMittal - i've 'improved' my text (i hope)
– guiverc
May 9 at 13:03
Thanks @AmanMittal - i've 'improved' my text (i hope)
– guiverc
May 9 at 13:03
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
This sounds like what happened to me after an interupted do-release-upgrade. Try the following:
sudo dpkg --configure -a
sudo apt update && sudo apt upgrade
If this works, try doing your release upgrade again.
sudo do-release-upgrade
answered May 9 at 15:12
Joshua Besneatte
1,504618
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
This sounds like what happened to me after an interupted do-release-upgrade. Try the following:
sudo dpkg --configure -a
sudo apt update && sudo apt upgrade
If this works, try doing your release upgrade again.
sudo do-release-upgrade
answered May 9 at 15:12
Joshua Besneatte
1,504618
add a comment |Â
up vote
0
down vote
This sounds like what happened to me after an interupted do-release-upgrade. Try the following:
sudo dpkg --configure -a
sudo apt update && sudo apt upgrade
If this works, try doing your release upgrade again.
sudo do-release-upgrade
answered May 9 at 15:12
Joshua Besneatte
1,504618
add a comment |Â
up vote
0
down vote
up vote
0
down vote
This sounds like what happened to me after an interupted do-release-upgrade. Try the following:
sudo dpkg --configure -a
sudo apt update && sudo apt upgrade
If this works, try doing your release upgrade again.
sudo do-release-upgrade
answered May 9 at 15:12
Joshua Besneatte
1,504618
This sounds like what happened to me after an interupted do-release-upgrade. Try the following:
sudo dpkg --configure -a
sudo apt update && sudo apt upgrade
If this works, try doing your release upgrade again.
sudo do-release-upgrade
answered May 9 at 15:12
Joshua Besneatte
1,504618
answered May 9 at 15:12
Joshua Besneatte
1,504618
answered May 9 at 15:12
Joshua Besneatte
1,504618
answered May 9 at 15:12
Joshua Besneatte
1,504618
1,504618
add a comment |Â
add a comment |Â
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034022%2fno-release-file-errors-when-trying-to-upgrade-from-version-17-10-to-18-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
1
Have you recently upgraded from 17.04 to 17.10?
– Kulfy
May 9 at 12:34
Zesty was Ubuntu 17.04 (2017 April release, EOL 13-Jan-2018), Artful is 17.10 (2017 October release). Your errors as posted imply you are running 17.04 which is EOL, and post-EOL the repositories are moved from
archive.ubuntu.comtoold-releases.ubuntu.comcausing the errors you've listed (until you modify your system accordingly), and @AmanMittal's question. If you're trying to upgrade 17.04 to 18.04 there is an additional step needed; so please confirm your version.– guiverc
May 9 at 12:58
1
@guiverc Well there's also a possibility that he recently upgraded to 17.10 from 17.04 and some of his sources weren't updated to that of artful.
– Kulfy
May 9 at 13:02
Thanks @AmanMittal - i've 'improved' my text (i hope)
– guiverc
May 9 at 13:03