I was not involved in that decision (which was made by the FTP masters<\/i> team), but since there is some confusion around it, I will try to give my understanding of the resulting issues.<\/p>\n
The typical \/etc\/apt\/sources.list<\/strong> file for a jessie system with backports enabled is:<\/p>\n Debian packages are distributed using suites (which can be understood as channels<\/em>). The global picture looks like this:<\/p>\n (This is slide 42 of the Debian Packaging Tutorial<\/a>.)<\/p>\n stable point releases<\/i> happen every few months (see for example the Debian 8.11 stable point release<\/a>). They consist in updating the So, what happened?<\/p>\n In June 2018…<\/p>\n Debian 8.11 (in June 2018) was the final update for Debian 8. As stated in its announcement<\/a>:<\/p>\n In other words: At about the same time (I think – I could not find an announcement — Update: announcement<\/a>), the maintenance of backports for jessie was also stopped. Which makes sense, because the backports team provides backports for the current release, and stretch was released in June 2017.<\/p>\n In March 2019…<\/p>\n The FTP masters team decided to remove the jessie-updates and jessie-backports suite from the mirrors. This was announced on debian-devel-announce<\/a>, resulting in the errors quoted above.<\/p>\n How to solve this?<\/p>\ndeb http:\/\/ftp.debian.org\/debian jessie main\r\ndeb-src http:\/\/ftp.debian.org\/debian jessie main\r\n\r\ndeb http:\/\/security.debian.org\/debian-security jessie\/updates main\r\ndeb-src http:\/\/security.debian.org\/debian-security jessie\/updates main\r\n\r\ndeb http:\/\/ftp.debian.org\/debian jessie-updates main\r\ndeb-src http:\/\/ftp.debian.org\/debian jessie-updates main\r\n\r\ndeb http:\/\/ftp.debian.org\/debian\/ jessie-backports main contrib non-free\r\ndeb-src http:\/\/ftp.debian.org\/debian\/ jessie-backports main contrib non-free<\/pre>\n
![\"\"](\"https:\/\/www.lucas-nussbaum.net\/blog\/wp-content\/uploads\/2019\/03\/debiansuites.png\")
<\/p>\ndeb http:\/\/deb.debian.org\/debian jessie main<\/code> is the easy one. It contains the bulk of packages. It is initialized by copying the content of the testing<\/code> suite when a new stable release<\/i> happens, approximately every two years. It is then updated from stable-new<\/code> (an internal suite) when stable point releases<\/i> happen (see below).<\/p>\ndeb http:\/\/security.debian.org\/debian-security jessie\/updates main<\/code> is the security<\/code> suite in the figure above. It is used by the Debian security team to provide security updates. They are announced on the debian-security-announce mailing list<\/a>.<\/p>\ndeb http:\/\/ftp.debian.org\/debian jessie-updates main<\/code> (stable-updates<\/code> above) is a suite used to distribute important updates that are unrelated to security, and that cannot wait the next stable point release<\/i>. They are announced on the debian-stable-announce mailing list<\/a>. Interestingly, a large proportion of those updates are related to changes to daylight-saving-time rules that are sometimes made very late by some countries.<\/p>\nstable<\/code> suite by copying important updates that were submitted to stable-proposed-updates<\/code>. Security updates are also included.<\/i><\/p>\nbackports<\/code> follow an entirely different path. They are new versions of packages, based on the version currently in the testing<\/code> suite. See the backports team website<\/a>.<\/p>\nAfter this point release, Debian's Security and Release Teams will no\r\nlonger be producing updates for Debian 8. Users wishing to continue to\r\nreceive security support should upgrade to Debian 9, or see\r\nhttps:\/\/wiki.debian.org\/LTS for details about the subset of\r\narchitectures and packages covered by the Long Term Support project.<\/pre>\n
jessie<\/code> and jessie-updates<\/code> won’t receive any update. The only updates will be through the security suite, by the Debian Long Term Support project<\/a>.<\/p>\n