wheezy-updates on archive.debian.org returns 404 Not FoundUbuntu cannot resolve unmet dependencyconflict in debian packagesHow to install apt-get on a busybox embedded system?debsecan won't launch on debian wheezyCan a single Apt-Cacher serve multiple Debian versions?Will debian update packages that I've personally build from their official sources?debian wheezy, heartbleed, openssl refuses to updateapt-get update, updated script conditionKerberos 5 won't install on Debian 8.2 or 8.3Unable to install automake1.9
Does the Idaho Potato Commission associate potato skins with healthy eating?
What exploit Are these user agents trying to use?
Is it possible to create a QR code using text?
How can I deal with my CEO asking me to hire someone with a higher salary than me, a co-founder?
Why didn't Miles's spider sense work before?
Personal Teleportation: From Rags to Riches
Is there an expression that means doing something right before you will need it rather than doing it in case you might need it?
What is the most common color to indicate the input-field is disabled?
Ambiguity in the definition of entropy
Venezuelan girlfriend wants to travel the USA to be with me. What is the process?
ssTTsSTtRrriinInnnnNNNIiinngg
How to show a landlord what we have in savings?
Is it acceptable for a professor to tell male students to not think that they are smarter than female students?
Would Slavery Reparations be considered Bills of Attainder and hence Illegal?
Am I breaking OOP practice with this architecture?
Can compressed videos be decoded back to their uncompresed original format?
How can saying a song's name be a copyright violation?
Apex Framework / library for consuming REST services
Is it logically or scientifically possible to artificially send energy to the body?
How do I deal with an unproductive colleague in a small company?
Theorists sure want true answers to this!
Different meanings of こわい
Probability that a draw from a normal distribution is some number greater than another draw from the same distribution
iPad being using in wall mount battery swollen
wheezy-updates on archive.debian.org returns 404 Not Found
Ubuntu cannot resolve unmet dependencyconflict in debian packagesHow to install apt-get on a busybox embedded system?debsecan won't launch on debian wheezyCan a single Apt-Cacher serve multiple Debian versions?Will debian update packages that I've personally build from their official sources?debian wheezy, heartbleed, openssl refuses to updateapt-get update, updated script conditionKerberos 5 won't install on Debian 8.2 or 8.3Unable to install automake1.9
I have an old test machine on Debian Wheezy that I can't really update right now.
Debian Wheezy repositories were archived in February. So I want ahead, and updated my /etc/apt/sources.list from
deb http://ftp.fr.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
to
deb http://archive.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://archive.debian.org/debian wheezy-updates main
But, when running apt-get update, I'm getting this error:
# apt-get update
<snip>
Err http://archive.debian.org wheezy-updates/main i386 Packages
404 Not Found [IP : 193.62.202.28 80]
Other repositories are being updated without issues.
Am I missing something?
debian apt debian-wheezy archive
asked 2 days ago
ZoddoZoddo
104
New contributor
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have an old test machine on Debian Wheezy that I can't really update right now.
Debian Wheezy repositories were archived in February. So I want ahead, and updated my /etc/apt/sources.list from
deb http://ftp.fr.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
to
deb http://archive.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://archive.debian.org/debian wheezy-updates main
But, when running apt-get update, I'm getting this error:
# apt-get update
<snip>
Err http://archive.debian.org wheezy-updates/main i386 Packages
404 Not Found [IP : 193.62.202.28 80]
Other repositories are being updated without issues.
Am I missing something?
debian apt debian-wheezy archive
asked 2 days ago
ZoddoZoddo
104
New contributor
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
wheezy is EOL, please seriously consider upgrading to a supported release.
– gf_
2 days ago
1
There isn't such a repository in the archive. It's years past time to upgrade.
– Michael Hampton♦
2 days ago
Thanks for the remember! It's a test machine which live on my PC (it's a VM) which is not accessible from the Internet (not even from my LAN). I'll probably rebuild it from scratch in the near future with an up-to-date Debian. Of course, if it was a production machine, it would have already been upgraded.
– Zoddo
2 days ago
add a comment |
I have an old test machine on Debian Wheezy that I can't really update right now.
Debian Wheezy repositories were archived in February. So I want ahead, and updated my /etc/apt/sources.list from
deb http://ftp.fr.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
to
deb http://archive.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://archive.debian.org/debian wheezy-updates main
But, when running apt-get update, I'm getting this error:
# apt-get update
<snip>
Err http://archive.debian.org wheezy-updates/main i386 Packages
404 Not Found [IP : 193.62.202.28 80]
Other repositories are being updated without issues.
Am I missing something?
debian apt debian-wheezy archive
asked 2 days ago
ZoddoZoddo
104
New contributor
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have an old test machine on Debian Wheezy that I can't really update right now.
Debian Wheezy repositories were archived in February. So I want ahead, and updated my /etc/apt/sources.list from
deb http://ftp.fr.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
to
deb http://archive.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://archive.debian.org/debian wheezy-updates main
But, when running apt-get update, I'm getting this error:
# apt-get update
<snip>
Err http://archive.debian.org wheezy-updates/main i386 Packages
404 Not Found [IP : 193.62.202.28 80]
Other repositories are being updated without issues.
Am I missing something?
debian apt debian-wheezy archive
debian apt debian-wheezy archive
asked 2 days ago
ZoddoZoddo
104
New contributor
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
ZoddoZoddo
104
New contributor
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
Zoddo
asked 2 days ago
ZoddoZoddo
104
New contributor
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
ZoddoZoddo
104
asked 2 days ago
ZoddoZoddo
104
104
New contributor
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Zoddo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
wheezy is EOL, please seriously consider upgrading to a supported release.
– gf_
2 days ago
1
There isn't such a repository in the archive. It's years past time to upgrade.
– Michael Hampton♦
2 days ago
Thanks for the remember! It's a test machine which live on my PC (it's a VM) which is not accessible from the Internet (not even from my LAN). I'll probably rebuild it from scratch in the near future with an up-to-date Debian. Of course, if it was a production machine, it would have already been upgraded.
– Zoddo
2 days ago
add a comment |
wheezy is EOL, please seriously consider upgrading to a supported release.
– gf_
2 days ago
1
There isn't such a repository in the archive. It's years past time to upgrade.
– Michael Hampton♦
2 days ago
Thanks for the remember! It's a test machine which live on my PC (it's a VM) which is not accessible from the Internet (not even from my LAN). I'll probably rebuild it from scratch in the near future with an up-to-date Debian. Of course, if it was a production machine, it would have already been upgraded.
– Zoddo
2 days ago
wheezy is EOL, please seriously consider upgrading to a supported release.
– gf_
2 days ago
wheezy is EOL, please seriously consider upgrading to a supported release.
– gf_
2 days ago
1
1
There isn't such a repository in the archive. It's years past time to upgrade.
– Michael Hampton♦
2 days ago
There isn't such a repository in the archive. It's years past time to upgrade.
– Michael Hampton♦
2 days ago
Thanks for the remember! It's a test machine which live on my PC (it's a VM) which is not accessible from the Internet (not even from my LAN). I'll probably rebuild it from scratch in the near future with an up-to-date Debian. Of course, if it was a production machine, it would have already been upgraded.
– Zoddo
2 days ago
Thanks for the remember! It's a test machine which live on my PC (it's a VM) which is not accessible from the Internet (not even from my LAN). I'll probably rebuild it from scratch in the near future with an up-to-date Debian. Of course, if it was a production machine, it would have already been upgraded.
– Zoddo
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
Using the Debian archive you shouldn't have an apt source line referring to wheezy-updates. This particular (sub-)distribution is not existing in the archives.
If you just remove the lines:
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
you should be able to run your apt-get commands again.
The whole story
The wheezy-updates repository contained packages that were provided to update the main repository, i.e. wheezy, between minor releases. Over time, when Wheezy got updated to 7.1, 7.2 and eventually to 7.11, the packages contained in wheezy-updates were moved into the main Wheezy repository. When Wheezy got EOLed, in May 2018, no packages were being kept in wheezy-updates, so there was no point in moving wheezy-updates to the Debian archive.
You can see the list of all Debian distributions supported by the archive repository at:
http://archive.debian.org/debian/dists/ Also check the README files at http://archive.debian.org/README and http://archive.debian.org/debian/README to have an even fuller list of the archive content.
The same goes for the security.debian.org repository, as Wheezy is EOL, you'll get no packages from there.
Caution
Like said in the comments to your question, be careful when running a machine using the Debian archive as those packages are not updated and so not secure anymore. It probably is OK if your machine is not directly connected to a network, but otherwise, I would highly recommend upgrading as soon as possible.
answered yesterday
ToninTonin
1,5691429
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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
);
);
Zoddo is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f960970%2fwheezy-updates-on-archive-debian-org-returns-404-not-found%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Using the Debian archive you shouldn't have an apt source line referring to wheezy-updates. This particular (sub-)distribution is not existing in the archives.
If you just remove the lines:
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
you should be able to run your apt-get commands again.
The whole story
The wheezy-updates repository contained packages that were provided to update the main repository, i.e. wheezy, between minor releases. Over time, when Wheezy got updated to 7.1, 7.2 and eventually to 7.11, the packages contained in wheezy-updates were moved into the main Wheezy repository. When Wheezy got EOLed, in May 2018, no packages were being kept in wheezy-updates, so there was no point in moving wheezy-updates to the Debian archive.
You can see the list of all Debian distributions supported by the archive repository at:
http://archive.debian.org/debian/dists/ Also check the README files at http://archive.debian.org/README and http://archive.debian.org/debian/README to have an even fuller list of the archive content.
The same goes for the security.debian.org repository, as Wheezy is EOL, you'll get no packages from there.
Caution
Like said in the comments to your question, be careful when running a machine using the Debian archive as those packages are not updated and so not secure anymore. It probably is OK if your machine is not directly connected to a network, but otherwise, I would highly recommend upgrading as soon as possible.
answered yesterday
ToninTonin
1,5691429
add a comment |
Using the Debian archive you shouldn't have an apt source line referring to wheezy-updates. This particular (sub-)distribution is not existing in the archives.
If you just remove the lines:
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
you should be able to run your apt-get commands again.
The whole story
The wheezy-updates repository contained packages that were provided to update the main repository, i.e. wheezy, between minor releases. Over time, when Wheezy got updated to 7.1, 7.2 and eventually to 7.11, the packages contained in wheezy-updates were moved into the main Wheezy repository. When Wheezy got EOLed, in May 2018, no packages were being kept in wheezy-updates, so there was no point in moving wheezy-updates to the Debian archive.
You can see the list of all Debian distributions supported by the archive repository at:
http://archive.debian.org/debian/dists/ Also check the README files at http://archive.debian.org/README and http://archive.debian.org/debian/README to have an even fuller list of the archive content.
The same goes for the security.debian.org repository, as Wheezy is EOL, you'll get no packages from there.
Caution
Like said in the comments to your question, be careful when running a machine using the Debian archive as those packages are not updated and so not secure anymore. It probably is OK if your machine is not directly connected to a network, but otherwise, I would highly recommend upgrading as soon as possible.
answered yesterday
ToninTonin
1,5691429
add a comment |
Using the Debian archive you shouldn't have an apt source line referring to wheezy-updates. This particular (sub-)distribution is not existing in the archives.
If you just remove the lines:
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
you should be able to run your apt-get commands again.
The whole story
The wheezy-updates repository contained packages that were provided to update the main repository, i.e. wheezy, between minor releases. Over time, when Wheezy got updated to 7.1, 7.2 and eventually to 7.11, the packages contained in wheezy-updates were moved into the main Wheezy repository. When Wheezy got EOLed, in May 2018, no packages were being kept in wheezy-updates, so there was no point in moving wheezy-updates to the Debian archive.
You can see the list of all Debian distributions supported by the archive repository at:
http://archive.debian.org/debian/dists/ Also check the README files at http://archive.debian.org/README and http://archive.debian.org/debian/README to have an even fuller list of the archive content.
The same goes for the security.debian.org repository, as Wheezy is EOL, you'll get no packages from there.
Caution
Like said in the comments to your question, be careful when running a machine using the Debian archive as those packages are not updated and so not secure anymore. It probably is OK if your machine is not directly connected to a network, but otherwise, I would highly recommend upgrading as soon as possible.
answered yesterday
ToninTonin
1,5691429
Using the Debian archive you shouldn't have an apt source line referring to wheezy-updates. This particular (sub-)distribution is not existing in the archives.
If you just remove the lines:
deb http://security.debian.org/ wheezy/updates main
deb http://ftp.fr.debian.org/debian wheezy-updates main
you should be able to run your apt-get commands again.
The whole story
The wheezy-updates repository contained packages that were provided to update the main repository, i.e. wheezy, between minor releases. Over time, when Wheezy got updated to 7.1, 7.2 and eventually to 7.11, the packages contained in wheezy-updates were moved into the main Wheezy repository. When Wheezy got EOLed, in May 2018, no packages were being kept in wheezy-updates, so there was no point in moving wheezy-updates to the Debian archive.
You can see the list of all Debian distributions supported by the archive repository at:
http://archive.debian.org/debian/dists/ Also check the README files at http://archive.debian.org/README and http://archive.debian.org/debian/README to have an even fuller list of the archive content.
The same goes for the security.debian.org repository, as Wheezy is EOL, you'll get no packages from there.
Caution
Like said in the comments to your question, be careful when running a machine using the Debian archive as those packages are not updated and so not secure anymore. It probably is OK if your machine is not directly connected to a network, but otherwise, I would highly recommend upgrading as soon as possible.
answered yesterday
ToninTonin
1,5691429
edited yesterday
answered yesterday
ToninTonin
1,5691429
answered yesterday
ToninTonin
1,5691429
answered yesterday
ToninTonin
1,5691429
1,5691429
add a comment |
add a comment |
Zoddo is a new contributor. Be nice, and check out our Code of Conduct.
Zoddo is a new contributor. Be nice, and check out our Code of Conduct.
Zoddo is a new contributor. Be nice, and check out our Code of Conduct.
Zoddo is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f960970%2fwheezy-updates-on-archive-debian-org-returns-404-not-found%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
wheezy is EOL, please seriously consider upgrading to a supported release.
– gf_
2 days ago
1
There isn't such a repository in the archive. It's years past time to upgrade.
– Michael Hampton♦
2 days ago
Thanks for the remember! It's a test machine which live on my PC (it's a VM) which is not accessible from the Internet (not even from my LAN). I'll probably rebuild it from scratch in the near future with an up-to-date Debian. Of course, if it was a production machine, it would have already been upgraded.
– Zoddo
2 days ago