Failed to fetch jessie backports repository
I'm using a docker image as a base for my own development that adds the jessie backports repository in its Dockerfile and uses that to install a dependency. This image uses the following command to add the repository:
echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
The problem is that fetching packages from the backports repository now fails with the following error (this used to work previously):
W: Failed to fetch
http://ftp.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages
404 Not Found
W: Failed to fetch
http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages
404 Not Found
I looked on that server, and those paths are indeed not present there.
I tried to figure out on the Debian backports site whether this particular repository should still be available, and I didn't find any indication that this was deprecated or something like that.
Is this a temporary issue with the repository, or is the jessie-backports repository not available anymore? And if this is not a temporary issue, what options do I have to use this or an equivalent repository without upgrading to the newer Debian stable version?
debian repository
New contributor
add a comment |
I'm using a docker image as a base for my own development that adds the jessie backports repository in its Dockerfile and uses that to install a dependency. This image uses the following command to add the repository:
echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
The problem is that fetching packages from the backports repository now fails with the following error (this used to work previously):
W: Failed to fetch
http://ftp.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages
404 Not Found
W: Failed to fetch
http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages
404 Not Found
I looked on that server, and those paths are indeed not present there.
I tried to figure out on the Debian backports site whether this particular repository should still be available, and I didn't find any indication that this was deprecated or something like that.
Is this a temporary issue with the repository, or is the jessie-backports repository not available anymore? And if this is not a temporary issue, what options do I have to use this or an equivalent repository without upgrading to the newer Debian stable version?
debian repository
New contributor
See also unix.stackexchange.com/questions/2544/…
– user343761
11 hours ago
add a comment |
I'm using a docker image as a base for my own development that adds the jessie backports repository in its Dockerfile and uses that to install a dependency. This image uses the following command to add the repository:
echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
The problem is that fetching packages from the backports repository now fails with the following error (this used to work previously):
W: Failed to fetch
http://ftp.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages
404 Not Found
W: Failed to fetch
http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages
404 Not Found
I looked on that server, and those paths are indeed not present there.
I tried to figure out on the Debian backports site whether this particular repository should still be available, and I didn't find any indication that this was deprecated or something like that.
Is this a temporary issue with the repository, or is the jessie-backports repository not available anymore? And if this is not a temporary issue, what options do I have to use this or an equivalent repository without upgrading to the newer Debian stable version?
debian repository
New contributor
I'm using a docker image as a base for my own development that adds the jessie backports repository in its Dockerfile and uses that to install a dependency. This image uses the following command to add the repository:
echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
The problem is that fetching packages from the backports repository now fails with the following error (this used to work previously):
W: Failed to fetch
http://ftp.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages
404 Not Found
W: Failed to fetch
http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages
404 Not Found
I looked on that server, and those paths are indeed not present there.
I tried to figure out on the Debian backports site whether this particular repository should still be available, and I didn't find any indication that this was deprecated or something like that.
Is this a temporary issue with the repository, or is the jessie-backports repository not available anymore? And if this is not a temporary issue, what options do I have to use this or an equivalent repository without upgrading to the newer Debian stable version?
debian repository
debian repository
New contributor
New contributor
edited 15 hours ago
GAD3R
27.5k1858114
27.5k1858114
New contributor
asked 16 hours ago
user12345user12345
13824
13824
New contributor
New contributor
See also unix.stackexchange.com/questions/2544/…
– user343761
11 hours ago
add a comment |
See also unix.stackexchange.com/questions/2544/…
– user343761
11 hours ago
See also unix.stackexchange.com/questions/2544/…
– user343761
11 hours ago
See also unix.stackexchange.com/questions/2544/…
– user343761
11 hours ago
add a comment |
3 Answers
3
active
oldest
votes
Wheezy and Jessie were recently removed from the mirror network, so if you want to continue fetching Jessie backports, you need to use archive.debian.org
instead:
deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main
(Validity checks need to be disabled since the repository is no longer being updated. Jessie’s apt
doesn’t support the check-valid-until
flag, see inostia’s answer for details, and the configuration summary further down in this answer.)
Since you’re building a container image, I highly recommend basing it on Debian 9 instead.
Until June 30, 2020, on LTS architectures, the main Jessie repositories and LTS security updates will continue to be available from the usual repositories, so your repositories should end up looking like
deb http://deb.debian.org/debian/ jessie main
deb-src http://deb.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
deb http://archive.debian.org/debian jessie-backports main
deb-src http://archive.debian.org/debian jessie-backports main
and you’ll need to disable validity checks in /etc/apt/apt.conf
:
Acquire::Check-Valid-Until "false";
(which will apply to all repositories).
Thanks, I'll try that. Upgrading Debian is certainly something I will do in the future, it's just not as simple as my dependency has another dependency that is the actual base image that determines the Debian version. Upgrading that needs a a bit more testing.
– user12345
16 hours ago
Oh I understand it’s not straightforward ;-). I felt it would be dishonest of me not to recommend it though (despite your mention in your question that it wasn’t an option).
– Stephen Kitt
16 hours ago
I am still getting error even after updating /etc/apt/sources.list as following : root@2664d9755cee:/# cat /etc/apt/sources.list deb archive.debian.org/debian jessie main deb archive.debian.org/debian jessie-updates main deb archive.debian.org/debian-security jessie/updates main
– Rafael
14 hours ago
2
@Ian no, security updates are provided onsecurity.debian.org
, not through backports or updates. There won’t be any more non-LTS stable updates, sojessie-updates
is no longer useful on the main mirror network, and there won’t be any more backports either, so the same goes forjessie-backports
.
– Stephen Kitt
13 hours ago
1
Have found that subsequentapt
commands also seem to require-o Acquire::Check-Valid-Until=false
(per unix.stackexchange.com/a/45973/186565) in order to avoid the expiration error.
– sumitsu
8 hours ago
|
show 6 more comments
This happened to me provisioning a Vagrant box that was using Debian "Jessie".
Following Stephen Kitt's answer, switching to archive.debian.org worked for me, but I had to add it to /etc/apt/sources.list.d/jessie-backports.list
, rather than to /etc/apt/sources.list
.
echo "deb http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
I then also got a security error running apt-get update
.
Following How to work around "Release file expired" problem on a local mirror, this fixed that error:
apt-get -o Acquire::Check-Valid-Until=false update
New contributor
1
it didn't work when i only included[check-valid-until=no]
injessie-backports.list
as the other answer suggested, i had to add the-o
flag when runningapt-update
to get it to work for whatever reason. updated answer to exclude it from*.list
configuration as it turned out to not work on its own without including-o
when running apt.
– inostia
7 hours ago
comments in Stephen Kitt's answer suggest that you may be able to get around the-o
flag issue if you set it inapt.conf
– inostia
2 hours ago
add a comment |
For those using NodeJS with older docker image foundations. I had some frozen images that had these older sources for the compilation of extra libs.
Context: if you wanted to install python during a docker build you ran into this issue during a build of the image (within the last 24 hours) as it failed to source dependencies during a docker build.
I tried the archive path recommendations in this post but couldn't get past the 404's. (also coming from the archive.debian.org location as of today)
Solution: I ended up switching to the latest container version of node (which has python libs already pre-installed) that, and updating some libs in the package json (which now also include binary libs that used to want pythyon) made the issue obsolete.
In the end, updating the foundation image for the container stack (node:latest) seemed to be the most straight-forward path to resolution.
Be wary of stale image stacks with binary dependencies included, they'll probably take a while to update the core OS layer.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
user12345 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%2funix.stackexchange.com%2fquestions%2f508724%2ffailed-to-fetch-jessie-backports-repository%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
Wheezy and Jessie were recently removed from the mirror network, so if you want to continue fetching Jessie backports, you need to use archive.debian.org
instead:
deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main
(Validity checks need to be disabled since the repository is no longer being updated. Jessie’s apt
doesn’t support the check-valid-until
flag, see inostia’s answer for details, and the configuration summary further down in this answer.)
Since you’re building a container image, I highly recommend basing it on Debian 9 instead.
Until June 30, 2020, on LTS architectures, the main Jessie repositories and LTS security updates will continue to be available from the usual repositories, so your repositories should end up looking like
deb http://deb.debian.org/debian/ jessie main
deb-src http://deb.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
deb http://archive.debian.org/debian jessie-backports main
deb-src http://archive.debian.org/debian jessie-backports main
and you’ll need to disable validity checks in /etc/apt/apt.conf
:
Acquire::Check-Valid-Until "false";
(which will apply to all repositories).
Thanks, I'll try that. Upgrading Debian is certainly something I will do in the future, it's just not as simple as my dependency has another dependency that is the actual base image that determines the Debian version. Upgrading that needs a a bit more testing.
– user12345
16 hours ago
Oh I understand it’s not straightforward ;-). I felt it would be dishonest of me not to recommend it though (despite your mention in your question that it wasn’t an option).
– Stephen Kitt
16 hours ago
I am still getting error even after updating /etc/apt/sources.list as following : root@2664d9755cee:/# cat /etc/apt/sources.list deb archive.debian.org/debian jessie main deb archive.debian.org/debian jessie-updates main deb archive.debian.org/debian-security jessie/updates main
– Rafael
14 hours ago
2
@Ian no, security updates are provided onsecurity.debian.org
, not through backports or updates. There won’t be any more non-LTS stable updates, sojessie-updates
is no longer useful on the main mirror network, and there won’t be any more backports either, so the same goes forjessie-backports
.
– Stephen Kitt
13 hours ago
1
Have found that subsequentapt
commands also seem to require-o Acquire::Check-Valid-Until=false
(per unix.stackexchange.com/a/45973/186565) in order to avoid the expiration error.
– sumitsu
8 hours ago
|
show 6 more comments
Wheezy and Jessie were recently removed from the mirror network, so if you want to continue fetching Jessie backports, you need to use archive.debian.org
instead:
deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main
(Validity checks need to be disabled since the repository is no longer being updated. Jessie’s apt
doesn’t support the check-valid-until
flag, see inostia’s answer for details, and the configuration summary further down in this answer.)
Since you’re building a container image, I highly recommend basing it on Debian 9 instead.
Until June 30, 2020, on LTS architectures, the main Jessie repositories and LTS security updates will continue to be available from the usual repositories, so your repositories should end up looking like
deb http://deb.debian.org/debian/ jessie main
deb-src http://deb.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
deb http://archive.debian.org/debian jessie-backports main
deb-src http://archive.debian.org/debian jessie-backports main
and you’ll need to disable validity checks in /etc/apt/apt.conf
:
Acquire::Check-Valid-Until "false";
(which will apply to all repositories).
Thanks, I'll try that. Upgrading Debian is certainly something I will do in the future, it's just not as simple as my dependency has another dependency that is the actual base image that determines the Debian version. Upgrading that needs a a bit more testing.
– user12345
16 hours ago
Oh I understand it’s not straightforward ;-). I felt it would be dishonest of me not to recommend it though (despite your mention in your question that it wasn’t an option).
– Stephen Kitt
16 hours ago
I am still getting error even after updating /etc/apt/sources.list as following : root@2664d9755cee:/# cat /etc/apt/sources.list deb archive.debian.org/debian jessie main deb archive.debian.org/debian jessie-updates main deb archive.debian.org/debian-security jessie/updates main
– Rafael
14 hours ago
2
@Ian no, security updates are provided onsecurity.debian.org
, not through backports or updates. There won’t be any more non-LTS stable updates, sojessie-updates
is no longer useful on the main mirror network, and there won’t be any more backports either, so the same goes forjessie-backports
.
– Stephen Kitt
13 hours ago
1
Have found that subsequentapt
commands also seem to require-o Acquire::Check-Valid-Until=false
(per unix.stackexchange.com/a/45973/186565) in order to avoid the expiration error.
– sumitsu
8 hours ago
|
show 6 more comments
Wheezy and Jessie were recently removed from the mirror network, so if you want to continue fetching Jessie backports, you need to use archive.debian.org
instead:
deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main
(Validity checks need to be disabled since the repository is no longer being updated. Jessie’s apt
doesn’t support the check-valid-until
flag, see inostia’s answer for details, and the configuration summary further down in this answer.)
Since you’re building a container image, I highly recommend basing it on Debian 9 instead.
Until June 30, 2020, on LTS architectures, the main Jessie repositories and LTS security updates will continue to be available from the usual repositories, so your repositories should end up looking like
deb http://deb.debian.org/debian/ jessie main
deb-src http://deb.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
deb http://archive.debian.org/debian jessie-backports main
deb-src http://archive.debian.org/debian jessie-backports main
and you’ll need to disable validity checks in /etc/apt/apt.conf
:
Acquire::Check-Valid-Until "false";
(which will apply to all repositories).
Wheezy and Jessie were recently removed from the mirror network, so if you want to continue fetching Jessie backports, you need to use archive.debian.org
instead:
deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main
(Validity checks need to be disabled since the repository is no longer being updated. Jessie’s apt
doesn’t support the check-valid-until
flag, see inostia’s answer for details, and the configuration summary further down in this answer.)
Since you’re building a container image, I highly recommend basing it on Debian 9 instead.
Until June 30, 2020, on LTS architectures, the main Jessie repositories and LTS security updates will continue to be available from the usual repositories, so your repositories should end up looking like
deb http://deb.debian.org/debian/ jessie main
deb-src http://deb.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
deb http://archive.debian.org/debian jessie-backports main
deb-src http://archive.debian.org/debian jessie-backports main
and you’ll need to disable validity checks in /etc/apt/apt.conf
:
Acquire::Check-Valid-Until "false";
(which will apply to all repositories).
edited 6 hours ago
answered 16 hours ago
Stephen KittStephen Kitt
178k24403481
178k24403481
Thanks, I'll try that. Upgrading Debian is certainly something I will do in the future, it's just not as simple as my dependency has another dependency that is the actual base image that determines the Debian version. Upgrading that needs a a bit more testing.
– user12345
16 hours ago
Oh I understand it’s not straightforward ;-). I felt it would be dishonest of me not to recommend it though (despite your mention in your question that it wasn’t an option).
– Stephen Kitt
16 hours ago
I am still getting error even after updating /etc/apt/sources.list as following : root@2664d9755cee:/# cat /etc/apt/sources.list deb archive.debian.org/debian jessie main deb archive.debian.org/debian jessie-updates main deb archive.debian.org/debian-security jessie/updates main
– Rafael
14 hours ago
2
@Ian no, security updates are provided onsecurity.debian.org
, not through backports or updates. There won’t be any more non-LTS stable updates, sojessie-updates
is no longer useful on the main mirror network, and there won’t be any more backports either, so the same goes forjessie-backports
.
– Stephen Kitt
13 hours ago
1
Have found that subsequentapt
commands also seem to require-o Acquire::Check-Valid-Until=false
(per unix.stackexchange.com/a/45973/186565) in order to avoid the expiration error.
– sumitsu
8 hours ago
|
show 6 more comments
Thanks, I'll try that. Upgrading Debian is certainly something I will do in the future, it's just not as simple as my dependency has another dependency that is the actual base image that determines the Debian version. Upgrading that needs a a bit more testing.
– user12345
16 hours ago
Oh I understand it’s not straightforward ;-). I felt it would be dishonest of me not to recommend it though (despite your mention in your question that it wasn’t an option).
– Stephen Kitt
16 hours ago
I am still getting error even after updating /etc/apt/sources.list as following : root@2664d9755cee:/# cat /etc/apt/sources.list deb archive.debian.org/debian jessie main deb archive.debian.org/debian jessie-updates main deb archive.debian.org/debian-security jessie/updates main
– Rafael
14 hours ago
2
@Ian no, security updates are provided onsecurity.debian.org
, not through backports or updates. There won’t be any more non-LTS stable updates, sojessie-updates
is no longer useful on the main mirror network, and there won’t be any more backports either, so the same goes forjessie-backports
.
– Stephen Kitt
13 hours ago
1
Have found that subsequentapt
commands also seem to require-o Acquire::Check-Valid-Until=false
(per unix.stackexchange.com/a/45973/186565) in order to avoid the expiration error.
– sumitsu
8 hours ago
Thanks, I'll try that. Upgrading Debian is certainly something I will do in the future, it's just not as simple as my dependency has another dependency that is the actual base image that determines the Debian version. Upgrading that needs a a bit more testing.
– user12345
16 hours ago
Thanks, I'll try that. Upgrading Debian is certainly something I will do in the future, it's just not as simple as my dependency has another dependency that is the actual base image that determines the Debian version. Upgrading that needs a a bit more testing.
– user12345
16 hours ago
Oh I understand it’s not straightforward ;-). I felt it would be dishonest of me not to recommend it though (despite your mention in your question that it wasn’t an option).
– Stephen Kitt
16 hours ago
Oh I understand it’s not straightforward ;-). I felt it would be dishonest of me not to recommend it though (despite your mention in your question that it wasn’t an option).
– Stephen Kitt
16 hours ago
I am still getting error even after updating /etc/apt/sources.list as following : root@2664d9755cee:/# cat /etc/apt/sources.list deb archive.debian.org/debian jessie main deb archive.debian.org/debian jessie-updates main deb archive.debian.org/debian-security jessie/updates main
– Rafael
14 hours ago
I am still getting error even after updating /etc/apt/sources.list as following : root@2664d9755cee:/# cat /etc/apt/sources.list deb archive.debian.org/debian jessie main deb archive.debian.org/debian jessie-updates main deb archive.debian.org/debian-security jessie/updates main
– Rafael
14 hours ago
2
2
@Ian no, security updates are provided on
security.debian.org
, not through backports or updates. There won’t be any more non-LTS stable updates, so jessie-updates
is no longer useful on the main mirror network, and there won’t be any more backports either, so the same goes for jessie-backports
.– Stephen Kitt
13 hours ago
@Ian no, security updates are provided on
security.debian.org
, not through backports or updates. There won’t be any more non-LTS stable updates, so jessie-updates
is no longer useful on the main mirror network, and there won’t be any more backports either, so the same goes for jessie-backports
.– Stephen Kitt
13 hours ago
1
1
Have found that subsequent
apt
commands also seem to require -o Acquire::Check-Valid-Until=false
(per unix.stackexchange.com/a/45973/186565) in order to avoid the expiration error.– sumitsu
8 hours ago
Have found that subsequent
apt
commands also seem to require -o Acquire::Check-Valid-Until=false
(per unix.stackexchange.com/a/45973/186565) in order to avoid the expiration error.– sumitsu
8 hours ago
|
show 6 more comments
This happened to me provisioning a Vagrant box that was using Debian "Jessie".
Following Stephen Kitt's answer, switching to archive.debian.org worked for me, but I had to add it to /etc/apt/sources.list.d/jessie-backports.list
, rather than to /etc/apt/sources.list
.
echo "deb http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
I then also got a security error running apt-get update
.
Following How to work around "Release file expired" problem on a local mirror, this fixed that error:
apt-get -o Acquire::Check-Valid-Until=false update
New contributor
1
it didn't work when i only included[check-valid-until=no]
injessie-backports.list
as the other answer suggested, i had to add the-o
flag when runningapt-update
to get it to work for whatever reason. updated answer to exclude it from*.list
configuration as it turned out to not work on its own without including-o
when running apt.
– inostia
7 hours ago
comments in Stephen Kitt's answer suggest that you may be able to get around the-o
flag issue if you set it inapt.conf
– inostia
2 hours ago
add a comment |
This happened to me provisioning a Vagrant box that was using Debian "Jessie".
Following Stephen Kitt's answer, switching to archive.debian.org worked for me, but I had to add it to /etc/apt/sources.list.d/jessie-backports.list
, rather than to /etc/apt/sources.list
.
echo "deb http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
I then also got a security error running apt-get update
.
Following How to work around "Release file expired" problem on a local mirror, this fixed that error:
apt-get -o Acquire::Check-Valid-Until=false update
New contributor
1
it didn't work when i only included[check-valid-until=no]
injessie-backports.list
as the other answer suggested, i had to add the-o
flag when runningapt-update
to get it to work for whatever reason. updated answer to exclude it from*.list
configuration as it turned out to not work on its own without including-o
when running apt.
– inostia
7 hours ago
comments in Stephen Kitt's answer suggest that you may be able to get around the-o
flag issue if you set it inapt.conf
– inostia
2 hours ago
add a comment |
This happened to me provisioning a Vagrant box that was using Debian "Jessie".
Following Stephen Kitt's answer, switching to archive.debian.org worked for me, but I had to add it to /etc/apt/sources.list.d/jessie-backports.list
, rather than to /etc/apt/sources.list
.
echo "deb http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
I then also got a security error running apt-get update
.
Following How to work around "Release file expired" problem on a local mirror, this fixed that error:
apt-get -o Acquire::Check-Valid-Until=false update
New contributor
This happened to me provisioning a Vagrant box that was using Debian "Jessie".
Following Stephen Kitt's answer, switching to archive.debian.org worked for me, but I had to add it to /etc/apt/sources.list.d/jessie-backports.list
, rather than to /etc/apt/sources.list
.
echo "deb http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
I then also got a security error running apt-get update
.
Following How to work around "Release file expired" problem on a local mirror, this fixed that error:
apt-get -o Acquire::Check-Valid-Until=false update
New contributor
edited 2 hours ago
New contributor
answered 8 hours ago
inostiainostia
1314
1314
New contributor
New contributor
1
it didn't work when i only included[check-valid-until=no]
injessie-backports.list
as the other answer suggested, i had to add the-o
flag when runningapt-update
to get it to work for whatever reason. updated answer to exclude it from*.list
configuration as it turned out to not work on its own without including-o
when running apt.
– inostia
7 hours ago
comments in Stephen Kitt's answer suggest that you may be able to get around the-o
flag issue if you set it inapt.conf
– inostia
2 hours ago
add a comment |
1
it didn't work when i only included[check-valid-until=no]
injessie-backports.list
as the other answer suggested, i had to add the-o
flag when runningapt-update
to get it to work for whatever reason. updated answer to exclude it from*.list
configuration as it turned out to not work on its own without including-o
when running apt.
– inostia
7 hours ago
comments in Stephen Kitt's answer suggest that you may be able to get around the-o
flag issue if you set it inapt.conf
– inostia
2 hours ago
1
1
it didn't work when i only included
[check-valid-until=no]
in jessie-backports.list
as the other answer suggested, i had to add the -o
flag when running apt-update
to get it to work for whatever reason. updated answer to exclude it from *.list
configuration as it turned out to not work on its own without including -o
when running apt.– inostia
7 hours ago
it didn't work when i only included
[check-valid-until=no]
in jessie-backports.list
as the other answer suggested, i had to add the -o
flag when running apt-update
to get it to work for whatever reason. updated answer to exclude it from *.list
configuration as it turned out to not work on its own without including -o
when running apt.– inostia
7 hours ago
comments in Stephen Kitt's answer suggest that you may be able to get around the
-o
flag issue if you set it in apt.conf
– inostia
2 hours ago
comments in Stephen Kitt's answer suggest that you may be able to get around the
-o
flag issue if you set it in apt.conf
– inostia
2 hours ago
add a comment |
For those using NodeJS with older docker image foundations. I had some frozen images that had these older sources for the compilation of extra libs.
Context: if you wanted to install python during a docker build you ran into this issue during a build of the image (within the last 24 hours) as it failed to source dependencies during a docker build.
I tried the archive path recommendations in this post but couldn't get past the 404's. (also coming from the archive.debian.org location as of today)
Solution: I ended up switching to the latest container version of node (which has python libs already pre-installed) that, and updating some libs in the package json (which now also include binary libs that used to want pythyon) made the issue obsolete.
In the end, updating the foundation image for the container stack (node:latest) seemed to be the most straight-forward path to resolution.
Be wary of stale image stacks with binary dependencies included, they'll probably take a while to update the core OS layer.
New contributor
add a comment |
For those using NodeJS with older docker image foundations. I had some frozen images that had these older sources for the compilation of extra libs.
Context: if you wanted to install python during a docker build you ran into this issue during a build of the image (within the last 24 hours) as it failed to source dependencies during a docker build.
I tried the archive path recommendations in this post but couldn't get past the 404's. (also coming from the archive.debian.org location as of today)
Solution: I ended up switching to the latest container version of node (which has python libs already pre-installed) that, and updating some libs in the package json (which now also include binary libs that used to want pythyon) made the issue obsolete.
In the end, updating the foundation image for the container stack (node:latest) seemed to be the most straight-forward path to resolution.
Be wary of stale image stacks with binary dependencies included, they'll probably take a while to update the core OS layer.
New contributor
add a comment |
For those using NodeJS with older docker image foundations. I had some frozen images that had these older sources for the compilation of extra libs.
Context: if you wanted to install python during a docker build you ran into this issue during a build of the image (within the last 24 hours) as it failed to source dependencies during a docker build.
I tried the archive path recommendations in this post but couldn't get past the 404's. (also coming from the archive.debian.org location as of today)
Solution: I ended up switching to the latest container version of node (which has python libs already pre-installed) that, and updating some libs in the package json (which now also include binary libs that used to want pythyon) made the issue obsolete.
In the end, updating the foundation image for the container stack (node:latest) seemed to be the most straight-forward path to resolution.
Be wary of stale image stacks with binary dependencies included, they'll probably take a while to update the core OS layer.
New contributor
For those using NodeJS with older docker image foundations. I had some frozen images that had these older sources for the compilation of extra libs.
Context: if you wanted to install python during a docker build you ran into this issue during a build of the image (within the last 24 hours) as it failed to source dependencies during a docker build.
I tried the archive path recommendations in this post but couldn't get past the 404's. (also coming from the archive.debian.org location as of today)
Solution: I ended up switching to the latest container version of node (which has python libs already pre-installed) that, and updating some libs in the package json (which now also include binary libs that used to want pythyon) made the issue obsolete.
In the end, updating the foundation image for the container stack (node:latest) seemed to be the most straight-forward path to resolution.
Be wary of stale image stacks with binary dependencies included, they'll probably take a while to update the core OS layer.
New contributor
New contributor
answered 5 hours ago
Glen C.Glen C.
11
11
New contributor
New contributor
add a comment |
add a comment |
user12345 is a new contributor. Be nice, and check out our Code of Conduct.
user12345 is a new contributor. Be nice, and check out our Code of Conduct.
user12345 is a new contributor. Be nice, and check out our Code of Conduct.
user12345 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f508724%2ffailed-to-fetch-jessie-backports-repository%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
See also unix.stackexchange.com/questions/2544/…
– user343761
11 hours ago