Debian wheezy, update repository [duplicate]
Clash Royale CLAN TAG#URR8PPP
This question already has an answer here:
Is there a way to get security updates for wheezy after EOL
1 answer
I'm working with a Debian GNU/Linux 7.5 (wheezy)
When I check the file /etc/apt/sources.list The file has this line:
# Line commented out by installer because it failed to verify:
#deb http://security.debian.org/ wheezy/updates main
I tried to replaces for another repo line, but each time I replace it and run the command apt-get update after a while, I get:
E: Some index files failed to download. They have been ignored, or old ones used instead.
What should I do to solve this problem?
debian
asked Jan 24 at 20:14
MrMinsMrMins
14515
marked as duplicate by Stephen Kitt debian
Users with the debian badge can single-handedly close debian questions as duplicates and reopen them as needed.
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
Jan 24 at 21:26
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
Is there a way to get security updates for wheezy after EOL
1 answer
I'm working with a Debian GNU/Linux 7.5 (wheezy)
When I check the file /etc/apt/sources.list The file has this line:
# Line commented out by installer because it failed to verify:
#deb http://security.debian.org/ wheezy/updates main
I tried to replaces for another repo line, but each time I replace it and run the command apt-get update after a while, I get:
E: Some index files failed to download. They have been ignored, or old ones used instead.
What should I do to solve this problem?
debian
asked Jan 24 at 20:14
MrMinsMrMins
14515
marked as duplicate by Stephen Kitt debian
Users with the debian badge can single-handedly close debian questions as duplicates and reopen them as needed.
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
Jan 24 at 21:26
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
Is there a way to get security updates for wheezy after EOL
1 answer
I'm working with a Debian GNU/Linux 7.5 (wheezy)
When I check the file /etc/apt/sources.list The file has this line:
# Line commented out by installer because it failed to verify:
#deb http://security.debian.org/ wheezy/updates main
I tried to replaces for another repo line, but each time I replace it and run the command apt-get update after a while, I get:
E: Some index files failed to download. They have been ignored, or old ones used instead.
What should I do to solve this problem?
debian
asked Jan 24 at 20:14
MrMinsMrMins
14515
This question already has an answer here:
Is there a way to get security updates for wheezy after EOL
1 answer
I'm working with a Debian GNU/Linux 7.5 (wheezy)
When I check the file /etc/apt/sources.list The file has this line:
# Line commented out by installer because it failed to verify:
#deb http://security.debian.org/ wheezy/updates main
I tried to replaces for another repo line, but each time I replace it and run the command apt-get update after a while, I get:
E: Some index files failed to download. They have been ignored, or old ones used instead.
What should I do to solve this problem?
This question already has an answer here:
Is there a way to get security updates for wheezy after EOL
1 answer
debian
debian
asked Jan 24 at 20:14
MrMinsMrMins
14515
asked Jan 24 at 20:14
MrMinsMrMins
14515
asked Jan 24 at 20:14
MrMinsMrMins
14515
asked Jan 24 at 20:14
MrMinsMrMins
14515
asked Jan 24 at 20:14
MrMinsMrMins
14515
14515
marked as duplicate by Stephen Kitt debian
Users with the debian badge can single-handedly close debian questions as duplicates and reopen them as needed.
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
Jan 24 at 21:26
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by Stephen Kitt debian
Users with the debian badge can single-handedly close debian questions as duplicates and reopen them as needed.
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
Jan 24 at 21:26
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
EDIT: You maybe able to follow the advice in this linuxquestions thread and uncomment the relevant entries in your sources.list and try to run apt update.
Debian 7 reached EOL as of May 31, 2018. Those repositories are no longer active. You can still receive support for Wheezy but it is going to be a lot less painful and expensive on your part to make moves to migrate to Jessie or even Stretch.
On the Debian Wiki there is advice on what to do now that Debian Wheezy is EOL. You may also want to check out this entry to get more information on what to do.
If you are upgrading to Jessie, your sources.list needs to changed to the following:
deb http://deb.debian.org/debian/ jessie main contrib non-free
deb-src http://deb.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free
Then run apt update, apt-get install apt -t jessie, apt upgrade, and finally apt dist-upgrade to update and upgrade to Jessie.
If you absolutely need to stay on Wheezy and cannot change to Jessie, either due to issues outlined here or because of some other limitations on your environment then you may need to change over to the archive mirrors or look into paid ELTS support.
Archive mirrors will look something like this:
deb http://archive.debian.org/debian/ wheezy main contrib non-free
answered Jan 24 at 21:21
kemotepkemotep
2,1963620
add a comment |
https://www.debian.org/security/ has some information on it, about updating it to:
deb http://security.debian.org/debian-security wheezy/updates
answered Jan 24 at 21:10
FabioMFabioM
513
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
EDIT: You maybe able to follow the advice in this linuxquestions thread and uncomment the relevant entries in your sources.list and try to run apt update.
Debian 7 reached EOL as of May 31, 2018. Those repositories are no longer active. You can still receive support for Wheezy but it is going to be a lot less painful and expensive on your part to make moves to migrate to Jessie or even Stretch.
On the Debian Wiki there is advice on what to do now that Debian Wheezy is EOL. You may also want to check out this entry to get more information on what to do.
If you are upgrading to Jessie, your sources.list needs to changed to the following:
deb http://deb.debian.org/debian/ jessie main contrib non-free
deb-src http://deb.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free
Then run apt update, apt-get install apt -t jessie, apt upgrade, and finally apt dist-upgrade to update and upgrade to Jessie.
If you absolutely need to stay on Wheezy and cannot change to Jessie, either due to issues outlined here or because of some other limitations on your environment then you may need to change over to the archive mirrors or look into paid ELTS support.
Archive mirrors will look something like this:
deb http://archive.debian.org/debian/ wheezy main contrib non-free
answered Jan 24 at 21:21
kemotepkemotep
2,1963620
add a comment |
EDIT: You maybe able to follow the advice in this linuxquestions thread and uncomment the relevant entries in your sources.list and try to run apt update.
Debian 7 reached EOL as of May 31, 2018. Those repositories are no longer active. You can still receive support for Wheezy but it is going to be a lot less painful and expensive on your part to make moves to migrate to Jessie or even Stretch.
On the Debian Wiki there is advice on what to do now that Debian Wheezy is EOL. You may also want to check out this entry to get more information on what to do.
If you are upgrading to Jessie, your sources.list needs to changed to the following:
deb http://deb.debian.org/debian/ jessie main contrib non-free
deb-src http://deb.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free
Then run apt update, apt-get install apt -t jessie, apt upgrade, and finally apt dist-upgrade to update and upgrade to Jessie.
If you absolutely need to stay on Wheezy and cannot change to Jessie, either due to issues outlined here or because of some other limitations on your environment then you may need to change over to the archive mirrors or look into paid ELTS support.
Archive mirrors will look something like this:
deb http://archive.debian.org/debian/ wheezy main contrib non-free
answered Jan 24 at 21:21
kemotepkemotep
2,1963620
add a comment |
EDIT: You maybe able to follow the advice in this linuxquestions thread and uncomment the relevant entries in your sources.list and try to run apt update.
Debian 7 reached EOL as of May 31, 2018. Those repositories are no longer active. You can still receive support for Wheezy but it is going to be a lot less painful and expensive on your part to make moves to migrate to Jessie or even Stretch.
On the Debian Wiki there is advice on what to do now that Debian Wheezy is EOL. You may also want to check out this entry to get more information on what to do.
If you are upgrading to Jessie, your sources.list needs to changed to the following:
deb http://deb.debian.org/debian/ jessie main contrib non-free
deb-src http://deb.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free
Then run apt update, apt-get install apt -t jessie, apt upgrade, and finally apt dist-upgrade to update and upgrade to Jessie.
If you absolutely need to stay on Wheezy and cannot change to Jessie, either due to issues outlined here or because of some other limitations on your environment then you may need to change over to the archive mirrors or look into paid ELTS support.
Archive mirrors will look something like this:
deb http://archive.debian.org/debian/ wheezy main contrib non-free
answered Jan 24 at 21:21
kemotepkemotep
2,1963620
EDIT: You maybe able to follow the advice in this linuxquestions thread and uncomment the relevant entries in your sources.list and try to run apt update.
Debian 7 reached EOL as of May 31, 2018. Those repositories are no longer active. You can still receive support for Wheezy but it is going to be a lot less painful and expensive on your part to make moves to migrate to Jessie or even Stretch.
On the Debian Wiki there is advice on what to do now that Debian Wheezy is EOL. You may also want to check out this entry to get more information on what to do.
If you are upgrading to Jessie, your sources.list needs to changed to the following:
deb http://deb.debian.org/debian/ jessie main contrib non-free
deb-src http://deb.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free
Then run apt update, apt-get install apt -t jessie, apt upgrade, and finally apt dist-upgrade to update and upgrade to Jessie.
If you absolutely need to stay on Wheezy and cannot change to Jessie, either due to issues outlined here or because of some other limitations on your environment then you may need to change over to the archive mirrors or look into paid ELTS support.
Archive mirrors will look something like this:
deb http://archive.debian.org/debian/ wheezy main contrib non-free
answered Jan 24 at 21:21
kemotepkemotep
2,1963620
edited Jan 24 at 21:52
answered Jan 24 at 21:21
kemotepkemotep
2,1963620
answered Jan 24 at 21:21
kemotepkemotep
2,1963620
answered Jan 24 at 21:21
kemotepkemotep
2,1963620
2,1963620
add a comment |
add a comment |
https://www.debian.org/security/ has some information on it, about updating it to:
deb http://security.debian.org/debian-security wheezy/updates
answered Jan 24 at 21:10
FabioMFabioM
513
add a comment |
https://www.debian.org/security/ has some information on it, about updating it to:
deb http://security.debian.org/debian-security wheezy/updates
answered Jan 24 at 21:10
FabioMFabioM
513
add a comment |
https://www.debian.org/security/ has some information on it, about updating it to:
deb http://security.debian.org/debian-security wheezy/updates
answered Jan 24 at 21:10
FabioMFabioM
513
https://www.debian.org/security/ has some information on it, about updating it to:
deb http://security.debian.org/debian-security wheezy/updates
answered Jan 24 at 21:10
FabioMFabioM
513
answered Jan 24 at 21:10
FabioMFabioM
513
answered Jan 24 at 21:10
FabioMFabioM
513
answered Jan 24 at 21:10
FabioMFabioM
513
513
add a comment |
add a comment |