Apt update error: The repository bullseye-backports Release no longer has a Release file

Hardware Librem 5
1

I get an error when running apt update:

The repository 'https://deb.debian.org/debian bullseye-backports Release' no longer has a Release file.

What could be wrong?

$ sudo apt update
[sudo] password for purism: 
Ign:1 https://deb.debian.org/debian bullseye-backports InRelease
Err:2 https://deb.debian.org/debian bullseye-backports Release
  404  Not Found [IP: 199.232.18.132 443]
Get:3 https://repo.pureos.net/pureos byzantium InRelease [9,641 B]
Get:4 https://repo.pureos.net/pureos byzantium-updates InRelease [9,649 B]
Get:5 https://repo.pureos.net/pureos byzantium-security InRelease [9,650 B]
Reading package lists... Done  
E: The repository 'https://deb.debian.org/debian bullseye-backports Release' no longer has a Release file.
N: Updating from such a repository can t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
1 Like
2

Could it be because it’s EOL and finally got around to removing it to archive?

EOL for bullseye-backports*

as you may know, oldstable is only supported for 1 year. For bookworm this was 2024-06-10. We added a small grace period afterwards, but we will not allow updates after this point. We will also remove the suite from the debian mirrors soon.

Thanks for your attention

Originally posted on debian-backports-announce

Posted Tue Jul 2 11:44:15 2024

Also. https://www.reddit.com/r/debian/comments/1m6gpaf/strange_problem_with_bullseye_backports/

4 Likes
3

Thanks. I think I fixed this now by changing the /etc/apt/sources.list file.

I replaced this line:

deb https://deb.debian.org/debian bullseye-backports main

with this line:

deb https://archive.debian.org/debian bullseye-backports main

I’m surprised there are not more reactions to this thread, as I used the default config as far as I know, and I would expect everybody to get hit by this issue.

@jonathon.hall: Should I create a GitLab issue for this?

1 Like
4

PureOS certainly does not use repositories of another distribution in its default config, so it’s not surprising at all. In fact, it’s not only not a default, it’s not a supported configuration - Debian repos are mostly, but not entirely compatible with PureOS, and using them without knowing exactly what you’re doing may cause various troubles.

4 Likes
5

Thanks! I will refrain from creating an issue in GitLab. Probably I forgot some fiddling I did. Maybe I should start over with a fresh Byzantium image once.

1 Like