Failed to fetch jessie backports repositoryThe repository jessie-backports Release does no longer have a Release fileW: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found [IP: 151.101.140.204 80]How to work around “Release file expired” problem on a local mirrorDockerfile - debian Jessie 404: packages not foundI can't use or find the google debian unstable/sid repositoryHow to update Debian kernel to latest in backportsLinux Mint Rebecca - Packages 404 Not Foundapt pinning priority restricted`apt update` failed on Debian LinuxUnable to find expected entry 'main/binary-mipsel/Packages' in Release fileI installed the kernel and some drivers from jessie-backports. Should I leave the backports repo in /etc/apt/sources.list?How to install a package from a repository which is missing some architectures?How to get rid of a PPA?Debian 9 stretch-backports signature couldn't be verified

What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?

Difference between sprint backlog and sprint goal?

Is the Joker left-handed?

What is the most common color to indicate the input-field is disabled?

I'm going to France and my passport expires June 19th

How can I tell some body that I want to be his or her friend?

Watching something be piped to a file live with tail

Why was the shrinking from 8″ made only to 5.25″ and not smaller (4″ or less)?

Does a druid starting with a bow start with no arrows?

Is it possible to create a QR code using text?

Why would the Red Woman birth a shadow if she worshipped the Lord of the Light?

Why doesn't using multiple commands with a || or && conditional work?

GFCI outlets - can they be repaired? Are they really needed at the end of a circuit?

Why can't we play rap on piano?

Why are the 737's rear doors unusable in a water landing?

How do I deal with an unproductive colleague in a small company?

One verb to replace 'be a member of' a club

Is there a way to turn 1.0 into a integer (1) while the same function ignores 1.5 and leaves it as a float

Avoiding the "not like other girls" trope?

Unlock My Phone! February 2018

Should I tell management that I intend to leave due to bad software development practices?

How would I stat a creature to be immune to everything but the Magic Missile spell? (just for fun)

Is it inappropriate for a student to attend their mentor's dissertation defense?

What reasons are there for a Capitalist to oppose a 100% inheritance tax?



Failed to fetch jessie backports repository


The repository jessie-backports Release does no longer have a Release fileW: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found [IP: 151.101.140.204 80]How to work around “Release file expired” problem on a local mirrorDockerfile - debian Jessie 404: packages not foundI can't use or find the google debian unstable/sid repositoryHow to update Debian kernel to latest in backportsLinux Mint Rebecca - Packages 404 Not Foundapt pinning priority restricted`apt update` failed on Debian LinuxUnable to find expected entry 'main/binary-mipsel/Packages' in Release fileI installed the kernel and some drivers from jessie-backports. Should I leave the backports repo in /etc/apt/sources.list?How to install a package from a repository which is missing some architectures?How to get rid of a PPA?Debian 9 stretch-backports signature couldn't be verified













71















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?










share|improve this question
























  • See also unix.stackexchange.com/questions/2544/…

    – user343761
    Mar 26 at 18:25











  • This is essentially the same question as apt-get update is failing in debian on Super User.

    – a CVn
    Mar 27 at 10:10















71















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?










share|improve this question
























  • See also unix.stackexchange.com/questions/2544/…

    – user343761
    Mar 26 at 18:25











  • This is essentially the same question as apt-get update is failing in debian on Super User.

    – a CVn
    Mar 27 at 10:10













71












71








71


14






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?










share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 26 at 13:59









GAD3R

27.9k1958114




27.9k1958114










asked Mar 26 at 12:39









user12345user12345

361124




361124












  • See also unix.stackexchange.com/questions/2544/…

    – user343761
    Mar 26 at 18:25











  • This is essentially the same question as apt-get update is failing in debian on Super User.

    – a CVn
    Mar 27 at 10:10

















  • See also unix.stackexchange.com/questions/2544/…

    – user343761
    Mar 26 at 18:25











  • This is essentially the same question as apt-get update is failing in debian on Super User.

    – a CVn
    Mar 27 at 10:10
















See also unix.stackexchange.com/questions/2544/…

– user343761
Mar 26 at 18:25





See also unix.stackexchange.com/questions/2544/…

– user343761
Mar 26 at 18:25













This is essentially the same question as apt-get update is failing in debian on Super User.

– a CVn
Mar 27 at 10:10





This is essentially the same question as apt-get update is failing in debian on Super User.

– a CVn
Mar 27 at 10:10










4 Answers
4






active

oldest

votes


















74














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



The jessie-updates repository has been removed: all the updates have been merged with the main repository, and there will be no further non-security updates. So any references to jessie-updates in sources.list or sources.list.d files need to be removed. Security updates will continue to be provided, on LTS-supported architectures, in the security repository, until June 30, 2020.



Since you’re building a container image, I highly recommend basing it on Debian 9 instead.



To say on Debian 8 (Jessie), your repositories should end up looking like



deb http://cdn-fastly.deb.debian.org/debian/ jessie main
deb-src http://cdn-fastly.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


without the jessie-updates repository, and you’ll need to disable validity checks in /etc/apt/apt.conf:



Acquire::Check-Valid-Until "false";


(which will apply to all repositories).






share|improve this answer




















  • 1





    Sorry, my answer was perhaps not all that clear; the line I gave was only for backports. jessie-updates doesn’t exist any more, so you should delete that altogether, and the Jessie security updates are still on security.debian.org.

    – Stephen Kitt
    Mar 26 at 15:15






  • 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
    Mar 26 at 15:57






  • 1





    Not working for me: ``` E: Release file for archive.debian.org/debian/dists/jessie-backports/InRelease is expired (invalid since 34d 20h 7min 12s). Updates for this repository will not be applied. ```

    – Avi Kivity
    Mar 26 at 16:34






  • 2





    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
    Mar 26 at 21:01






  • 2





    @sumitsu thanks, setting that in apt.conf should work too (see my update).

    – Stephen Kitt
    Mar 26 at 22:39


















20














After trying solutions suggested by @inostia and @Stephen Kitt I was still getting the following error:



W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.


I figured out that it can be solved by removing the line deb http://deb.debian.org/debian jessie-updates main from /etc/apt/sources.list.



I ended up with the following snippet in my Dockerfile:



RUN echo "deb [check-valid-until=no] http://cdn-fastly.deb.debian.org/debian jessie main" > /etc/apt/sources.list.d/jessie.list
RUN echo "deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
RUN sed -i '/deb http://deb.debian.org/debian jessie-updates main/d' /etc/apt/sources.list
RUN apt-get -o Acquire::Check-Valid-Until=false update





share|improve this answer




















  • 1





    I had the same issue as you did and your snippet worked for me!

    – cafemike
    Mar 27 at 14:45






  • 1





    I had to teak sed part as In my case docker image (postgres) was using httpredir.debian.org instead of deb.debian.org.

    – harrybvp
    Mar 27 at 22:19







  • 1





    Thank you!!! I've been struggling for two days to fix my Dockerfile after the Debian jessie change, I pasted your snippet in and it's all working again.

    – wpjmurray
    Mar 28 at 15:57











  • sorry, but still same issue ....

    – user1722245
    Mar 28 at 16:31






  • 2





    Here is an updated version of your sed command that did the trick for me: sed -i '/deb http://(deb|httpredir).debian.org/debian jessie.* main/d' /etc/apt/sources.list

    – speedplane
    Mar 29 at 0:26



















8














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





share|improve this answer




















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







  • 1





    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
    Mar 27 at 2:53



















2














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.






share|improve this answer























  • Hi Glen, thanks for posting. I think I'm running into same issue in dockerfile as I have "RUN apt-get update -y && apt-get install supervisor python python-dev curl -y --force-yes". I'm using FROM node:6.11.2, what must I do to get past this?

    – Aaron
    2 days ago









protected by Jeff Schaller Mar 27 at 13:01



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?














4 Answers
4






active

oldest

votes








4 Answers
4






active

oldest

votes









active

oldest

votes






active

oldest

votes









74














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



The jessie-updates repository has been removed: all the updates have been merged with the main repository, and there will be no further non-security updates. So any references to jessie-updates in sources.list or sources.list.d files need to be removed. Security updates will continue to be provided, on LTS-supported architectures, in the security repository, until June 30, 2020.



Since you’re building a container image, I highly recommend basing it on Debian 9 instead.



To say on Debian 8 (Jessie), your repositories should end up looking like



deb http://cdn-fastly.deb.debian.org/debian/ jessie main
deb-src http://cdn-fastly.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


without the jessie-updates repository, and you’ll need to disable validity checks in /etc/apt/apt.conf:



Acquire::Check-Valid-Until "false";


(which will apply to all repositories).






share|improve this answer




















  • 1





    Sorry, my answer was perhaps not all that clear; the line I gave was only for backports. jessie-updates doesn’t exist any more, so you should delete that altogether, and the Jessie security updates are still on security.debian.org.

    – Stephen Kitt
    Mar 26 at 15:15






  • 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
    Mar 26 at 15:57






  • 1





    Not working for me: ``` E: Release file for archive.debian.org/debian/dists/jessie-backports/InRelease is expired (invalid since 34d 20h 7min 12s). Updates for this repository will not be applied. ```

    – Avi Kivity
    Mar 26 at 16:34






  • 2





    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
    Mar 26 at 21:01






  • 2





    @sumitsu thanks, setting that in apt.conf should work too (see my update).

    – Stephen Kitt
    Mar 26 at 22:39















74














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



The jessie-updates repository has been removed: all the updates have been merged with the main repository, and there will be no further non-security updates. So any references to jessie-updates in sources.list or sources.list.d files need to be removed. Security updates will continue to be provided, on LTS-supported architectures, in the security repository, until June 30, 2020.



Since you’re building a container image, I highly recommend basing it on Debian 9 instead.



To say on Debian 8 (Jessie), your repositories should end up looking like



deb http://cdn-fastly.deb.debian.org/debian/ jessie main
deb-src http://cdn-fastly.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


without the jessie-updates repository, and you’ll need to disable validity checks in /etc/apt/apt.conf:



Acquire::Check-Valid-Until "false";


(which will apply to all repositories).






share|improve this answer




















  • 1





    Sorry, my answer was perhaps not all that clear; the line I gave was only for backports. jessie-updates doesn’t exist any more, so you should delete that altogether, and the Jessie security updates are still on security.debian.org.

    – Stephen Kitt
    Mar 26 at 15:15






  • 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
    Mar 26 at 15:57






  • 1





    Not working for me: ``` E: Release file for archive.debian.org/debian/dists/jessie-backports/InRelease is expired (invalid since 34d 20h 7min 12s). Updates for this repository will not be applied. ```

    – Avi Kivity
    Mar 26 at 16:34






  • 2





    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
    Mar 26 at 21:01






  • 2





    @sumitsu thanks, setting that in apt.conf should work too (see my update).

    – Stephen Kitt
    Mar 26 at 22:39













74












74








74







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



The jessie-updates repository has been removed: all the updates have been merged with the main repository, and there will be no further non-security updates. So any references to jessie-updates in sources.list or sources.list.d files need to be removed. Security updates will continue to be provided, on LTS-supported architectures, in the security repository, until June 30, 2020.



Since you’re building a container image, I highly recommend basing it on Debian 9 instead.



To say on Debian 8 (Jessie), your repositories should end up looking like



deb http://cdn-fastly.deb.debian.org/debian/ jessie main
deb-src http://cdn-fastly.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


without the jessie-updates repository, and you’ll need to disable validity checks in /etc/apt/apt.conf:



Acquire::Check-Valid-Until "false";


(which will apply to all repositories).






share|improve this answer















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



The jessie-updates repository has been removed: all the updates have been merged with the main repository, and there will be no further non-security updates. So any references to jessie-updates in sources.list or sources.list.d files need to be removed. Security updates will continue to be provided, on LTS-supported architectures, in the security repository, until June 30, 2020.



Since you’re building a container image, I highly recommend basing it on Debian 9 instead.



To say on Debian 8 (Jessie), your repositories should end up looking like



deb http://cdn-fastly.deb.debian.org/debian/ jessie main
deb-src http://cdn-fastly.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


without the jessie-updates repository, and you’ll need to disable validity checks in /etc/apt/apt.conf:



Acquire::Check-Valid-Until "false";


(which will apply to all repositories).







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 days ago

























answered Mar 26 at 12:48









Stephen KittStephen Kitt

179k25407485




179k25407485







  • 1





    Sorry, my answer was perhaps not all that clear; the line I gave was only for backports. jessie-updates doesn’t exist any more, so you should delete that altogether, and the Jessie security updates are still on security.debian.org.

    – Stephen Kitt
    Mar 26 at 15:15






  • 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
    Mar 26 at 15:57






  • 1





    Not working for me: ``` E: Release file for archive.debian.org/debian/dists/jessie-backports/InRelease is expired (invalid since 34d 20h 7min 12s). Updates for this repository will not be applied. ```

    – Avi Kivity
    Mar 26 at 16:34






  • 2





    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
    Mar 26 at 21:01






  • 2





    @sumitsu thanks, setting that in apt.conf should work too (see my update).

    – Stephen Kitt
    Mar 26 at 22:39












  • 1





    Sorry, my answer was perhaps not all that clear; the line I gave was only for backports. jessie-updates doesn’t exist any more, so you should delete that altogether, and the Jessie security updates are still on security.debian.org.

    – Stephen Kitt
    Mar 26 at 15:15






  • 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
    Mar 26 at 15:57






  • 1





    Not working for me: ``` E: Release file for archive.debian.org/debian/dists/jessie-backports/InRelease is expired (invalid since 34d 20h 7min 12s). Updates for this repository will not be applied. ```

    – Avi Kivity
    Mar 26 at 16:34






  • 2





    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
    Mar 26 at 21:01






  • 2





    @sumitsu thanks, setting that in apt.conf should work too (see my update).

    – Stephen Kitt
    Mar 26 at 22:39







1




1





Sorry, my answer was perhaps not all that clear; the line I gave was only for backports. jessie-updates doesn’t exist any more, so you should delete that altogether, and the Jessie security updates are still on security.debian.org.

– Stephen Kitt
Mar 26 at 15:15





Sorry, my answer was perhaps not all that clear; the line I gave was only for backports. jessie-updates doesn’t exist any more, so you should delete that altogether, and the Jessie security updates are still on security.debian.org.

– Stephen Kitt
Mar 26 at 15:15




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
Mar 26 at 15:57





@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
Mar 26 at 15:57




1




1





Not working for me: ``` E: Release file for archive.debian.org/debian/dists/jessie-backports/InRelease is expired (invalid since 34d 20h 7min 12s). Updates for this repository will not be applied. ```

– Avi Kivity
Mar 26 at 16:34





Not working for me: ``` E: Release file for archive.debian.org/debian/dists/jessie-backports/InRelease is expired (invalid since 34d 20h 7min 12s). Updates for this repository will not be applied. ```

– Avi Kivity
Mar 26 at 16:34




2




2





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
Mar 26 at 21:01





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
Mar 26 at 21:01




2




2





@sumitsu thanks, setting that in apt.conf should work too (see my update).

– Stephen Kitt
Mar 26 at 22:39





@sumitsu thanks, setting that in apt.conf should work too (see my update).

– Stephen Kitt
Mar 26 at 22:39













20














After trying solutions suggested by @inostia and @Stephen Kitt I was still getting the following error:



W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.


I figured out that it can be solved by removing the line deb http://deb.debian.org/debian jessie-updates main from /etc/apt/sources.list.



I ended up with the following snippet in my Dockerfile:



RUN echo "deb [check-valid-until=no] http://cdn-fastly.deb.debian.org/debian jessie main" > /etc/apt/sources.list.d/jessie.list
RUN echo "deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
RUN sed -i '/deb http://deb.debian.org/debian jessie-updates main/d' /etc/apt/sources.list
RUN apt-get -o Acquire::Check-Valid-Until=false update





share|improve this answer




















  • 1





    I had the same issue as you did and your snippet worked for me!

    – cafemike
    Mar 27 at 14:45






  • 1





    I had to teak sed part as In my case docker image (postgres) was using httpredir.debian.org instead of deb.debian.org.

    – harrybvp
    Mar 27 at 22:19







  • 1





    Thank you!!! I've been struggling for two days to fix my Dockerfile after the Debian jessie change, I pasted your snippet in and it's all working again.

    – wpjmurray
    Mar 28 at 15:57











  • sorry, but still same issue ....

    – user1722245
    Mar 28 at 16:31






  • 2





    Here is an updated version of your sed command that did the trick for me: sed -i '/deb http://(deb|httpredir).debian.org/debian jessie.* main/d' /etc/apt/sources.list

    – speedplane
    Mar 29 at 0:26
















20














After trying solutions suggested by @inostia and @Stephen Kitt I was still getting the following error:



W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.


I figured out that it can be solved by removing the line deb http://deb.debian.org/debian jessie-updates main from /etc/apt/sources.list.



I ended up with the following snippet in my Dockerfile:



RUN echo "deb [check-valid-until=no] http://cdn-fastly.deb.debian.org/debian jessie main" > /etc/apt/sources.list.d/jessie.list
RUN echo "deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
RUN sed -i '/deb http://deb.debian.org/debian jessie-updates main/d' /etc/apt/sources.list
RUN apt-get -o Acquire::Check-Valid-Until=false update





share|improve this answer




















  • 1





    I had the same issue as you did and your snippet worked for me!

    – cafemike
    Mar 27 at 14:45






  • 1





    I had to teak sed part as In my case docker image (postgres) was using httpredir.debian.org instead of deb.debian.org.

    – harrybvp
    Mar 27 at 22:19







  • 1





    Thank you!!! I've been struggling for two days to fix my Dockerfile after the Debian jessie change, I pasted your snippet in and it's all working again.

    – wpjmurray
    Mar 28 at 15:57











  • sorry, but still same issue ....

    – user1722245
    Mar 28 at 16:31






  • 2





    Here is an updated version of your sed command that did the trick for me: sed -i '/deb http://(deb|httpredir).debian.org/debian jessie.* main/d' /etc/apt/sources.list

    – speedplane
    Mar 29 at 0:26














20












20








20







After trying solutions suggested by @inostia and @Stephen Kitt I was still getting the following error:



W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.


I figured out that it can be solved by removing the line deb http://deb.debian.org/debian jessie-updates main from /etc/apt/sources.list.



I ended up with the following snippet in my Dockerfile:



RUN echo "deb [check-valid-until=no] http://cdn-fastly.deb.debian.org/debian jessie main" > /etc/apt/sources.list.d/jessie.list
RUN echo "deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
RUN sed -i '/deb http://deb.debian.org/debian jessie-updates main/d' /etc/apt/sources.list
RUN apt-get -o Acquire::Check-Valid-Until=false update





share|improve this answer















After trying solutions suggested by @inostia and @Stephen Kitt I was still getting the following error:



W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.


I figured out that it can be solved by removing the line deb http://deb.debian.org/debian jessie-updates main from /etc/apt/sources.list.



I ended up with the following snippet in my Dockerfile:



RUN echo "deb [check-valid-until=no] http://cdn-fastly.deb.debian.org/debian jessie main" > /etc/apt/sources.list.d/jessie.list
RUN echo "deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
RUN sed -i '/deb http://deb.debian.org/debian jessie-updates main/d' /etc/apt/sources.list
RUN apt-get -o Acquire::Check-Valid-Until=false update






share|improve this answer














share|improve this answer



share|improve this answer








edited 11 hours ago









Andrez

31




31










answered Mar 27 at 11:01









henadzithenadzit

3013




3013







  • 1





    I had the same issue as you did and your snippet worked for me!

    – cafemike
    Mar 27 at 14:45






  • 1





    I had to teak sed part as In my case docker image (postgres) was using httpredir.debian.org instead of deb.debian.org.

    – harrybvp
    Mar 27 at 22:19







  • 1





    Thank you!!! I've been struggling for two days to fix my Dockerfile after the Debian jessie change, I pasted your snippet in and it's all working again.

    – wpjmurray
    Mar 28 at 15:57











  • sorry, but still same issue ....

    – user1722245
    Mar 28 at 16:31






  • 2





    Here is an updated version of your sed command that did the trick for me: sed -i '/deb http://(deb|httpredir).debian.org/debian jessie.* main/d' /etc/apt/sources.list

    – speedplane
    Mar 29 at 0:26













  • 1





    I had the same issue as you did and your snippet worked for me!

    – cafemike
    Mar 27 at 14:45






  • 1





    I had to teak sed part as In my case docker image (postgres) was using httpredir.debian.org instead of deb.debian.org.

    – harrybvp
    Mar 27 at 22:19







  • 1





    Thank you!!! I've been struggling for two days to fix my Dockerfile after the Debian jessie change, I pasted your snippet in and it's all working again.

    – wpjmurray
    Mar 28 at 15:57











  • sorry, but still same issue ....

    – user1722245
    Mar 28 at 16:31






  • 2





    Here is an updated version of your sed command that did the trick for me: sed -i '/deb http://(deb|httpredir).debian.org/debian jessie.* main/d' /etc/apt/sources.list

    – speedplane
    Mar 29 at 0:26








1




1





I had the same issue as you did and your snippet worked for me!

– cafemike
Mar 27 at 14:45





I had the same issue as you did and your snippet worked for me!

– cafemike
Mar 27 at 14:45




1




1





I had to teak sed part as In my case docker image (postgres) was using httpredir.debian.org instead of deb.debian.org.

– harrybvp
Mar 27 at 22:19






I had to teak sed part as In my case docker image (postgres) was using httpredir.debian.org instead of deb.debian.org.

– harrybvp
Mar 27 at 22:19





1




1





Thank you!!! I've been struggling for two days to fix my Dockerfile after the Debian jessie change, I pasted your snippet in and it's all working again.

– wpjmurray
Mar 28 at 15:57





Thank you!!! I've been struggling for two days to fix my Dockerfile after the Debian jessie change, I pasted your snippet in and it's all working again.

– wpjmurray
Mar 28 at 15:57













sorry, but still same issue ....

– user1722245
Mar 28 at 16:31





sorry, but still same issue ....

– user1722245
Mar 28 at 16:31




2




2





Here is an updated version of your sed command that did the trick for me: sed -i '/deb http://(deb|httpredir).debian.org/debian jessie.* main/d' /etc/apt/sources.list

– speedplane
Mar 29 at 0:26






Here is an updated version of your sed command that did the trick for me: sed -i '/deb http://(deb|httpredir).debian.org/debian jessie.* main/d' /etc/apt/sources.list

– speedplane
Mar 29 at 0:26












8














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





share|improve this answer




















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







  • 1





    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
    Mar 27 at 2:53
















8














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





share|improve this answer




















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







  • 1





    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
    Mar 27 at 2:53














8












8








8







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





share|improve this answer















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






share|improve this answer














share|improve this answer



share|improve this answer








edited Mar 27 at 3:05

























answered Mar 26 at 21:38









inostiainostia

1814




1814







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







  • 1





    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
    Mar 27 at 2:53













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







  • 1





    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
    Mar 27 at 2:53








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






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





1




1





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
Mar 27 at 2:53






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
Mar 27 at 2:53












2














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.






share|improve this answer























  • Hi Glen, thanks for posting. I think I'm running into same issue in dockerfile as I have "RUN apt-get update -y && apt-get install supervisor python python-dev curl -y --force-yes". I'm using FROM node:6.11.2, what must I do to get past this?

    – Aaron
    2 days ago















2














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.






share|improve this answer























  • Hi Glen, thanks for posting. I think I'm running into same issue in dockerfile as I have "RUN apt-get update -y && apt-get install supervisor python python-dev curl -y --force-yes". I'm using FROM node:6.11.2, what must I do to get past this?

    – Aaron
    2 days ago













2












2








2







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.






share|improve this answer













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.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 26 at 23:40









Glen C.Glen C.

212




212












  • Hi Glen, thanks for posting. I think I'm running into same issue in dockerfile as I have "RUN apt-get update -y && apt-get install supervisor python python-dev curl -y --force-yes". I'm using FROM node:6.11.2, what must I do to get past this?

    – Aaron
    2 days ago

















  • Hi Glen, thanks for posting. I think I'm running into same issue in dockerfile as I have "RUN apt-get update -y && apt-get install supervisor python python-dev curl -y --force-yes". I'm using FROM node:6.11.2, what must I do to get past this?

    – Aaron
    2 days ago
















Hi Glen, thanks for posting. I think I'm running into same issue in dockerfile as I have "RUN apt-get update -y && apt-get install supervisor python python-dev curl -y --force-yes". I'm using FROM node:6.11.2, what must I do to get past this?

– Aaron
2 days ago





Hi Glen, thanks for posting. I think I'm running into same issue in dockerfile as I have "RUN apt-get update -y && apt-get install supervisor python python-dev curl -y --force-yes". I'm using FROM node:6.11.2, what must I do to get past this?

– Aaron
2 days ago





protected by Jeff Schaller Mar 27 at 13:01



Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?



Popular posts from this blog

Adding axes to figuresAdding axes labels to LaTeX figuresLaTeX equivalent of ConTeXt buffersRotate a node but not its content: the case of the ellipse decorationHow to define the default vertical distance between nodes?TikZ scaling graphic and adjust node position and keep font sizeNumerical conditional within tikz keys?adding axes to shapesAlign axes across subfiguresAdding figures with a certain orderLine up nested tikz enviroments or how to get rid of themAdding axes labels to LaTeX figures

Tähtien Talli Jäsenet | Lähteet | NavigointivalikkoSuomen Hippos – Tähtien Talli

Do these cracks on my tires look bad? The Next CEO of Stack OverflowDry rot tire should I replace?Having to replace tiresFishtailed so easily? Bad tires? ABS?Filling the tires with something other than air, to avoid puncture hassles?Used Michelin tires safe to install?Do these tyre cracks necessitate replacement?Rumbling noise: tires or mechanicalIs it possible to fix noisy feathered tires?Are bad winter tires still better than summer tires in winter?Torque converter failure - Related to replacing only 2 tires?Why use snow tires on all 4 wheels on 2-wheel-drive cars?