404 Not Found [IP: 151.101.194.132 80] apt update Debian 11 Bullseye Solution The repository 'http://security.debian.org bullseye/updates Release' does not have a Release file.

This happens during an apt update and is related to an issue with sources.list, which is particularly troubling, if you are doing a "live-build".

P: Configuring file /etc/apt/sources.list
Hit:1 http://deb.debian.org/debian bullseye InRelease
Get:2 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]
Ign:3 http://security.debian.org bullseye/updates InRelease
Err:4 http://security.debian.org bullseye/updates Release
  404  Not Found [IP: 151.101.194.132 80]
Get:5 http://deb.debian.org/debian bullseye/main Sources [8627 kB]
Get:6 http://deb.debian.org/debian bullseye/main Translation-en [6241 kB]
Get:7 http://deb.debian.org/debian bullseye-updates/main Sources [1868 B]
Get:8 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [2596 B]
Get:9 http://deb.debian.org/debian bullseye-updates/main Translation-en [2343 B]
Reading package lists... Done                  
E: The repository 'http://security.debian.org bullseye/updates Release' does not have 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.
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists... Done
Building dependency tree... Done

Solution

The issue is with bullseye/updates which should be bullseye-security


Change this in sources.list:

deb http://security.debian.org/debian-security/ bullseye/updates main
deb-src http://security.debian.org/debian-security/ bullseye/updates main

To this:

deb http://security.debian.org/debian-security/ bullseye-security main
deb-src http://security.debian.org/debian-security/ bullseye-security main

 

If you are using live-build and don't need the security packages you can just disable it with:

 

--security=false

in your lb config line (eg. lb config --security=false)


Tags:

ip, apt, update, debian, bullseye, repository, http, org, updates, sources, troubling, quot, configuring, etc, deb, inrelease, kb, ign, err, translation, en, amd, packages, lists, updating, securely, disabled, default, manpage, creation, user, configuration, unmounting, filesystems, caches, dependency, src, disable, lb, config, eg,

Latest Articles

  • How to resize a pdf without losing much quality in Linux Mint Ubuntu Debian Redhat Solution
  • qemu: could not load PC BIOS 'bios-256k.bin' solution
  • Proxmox How To Custom Partition During Install
  • Hyper-V Linux VM Boots to Black Screen, Storage, NIC Not Found Issues
  • Ubuntu Mint How to Fix Missing/Broken /dev and /dev/pts which causes terminal to immediately close exit and not work
  • How high can a Xeon CPU get?
  • bash fix PATH environment variable "command not found" solution
  • Ubuntu Linux Mint Debian Redhat Youtube Cannot Play HD or 4K videos, dropped frames or high CPU usage with Nvidia or AMD Driver
  • hostapd example configuration for high speed AC on 5GHz using WPA2
  • hostapd how to enable and use WPS to connect wireless devices like printers
  • Dell Server Workstation iDRAC Dead after Firmware Update Solution R720, R320, R730
  • Cloned VM/Server/Computer in Linux won't boot and goes to initramfs busybox Solution
  • How To Add Windows 7 8 10 11 to GRUB Boot List Dual Booting
  • How to configure OpenDKIM on Linux with Postfix and setup bind zonefile
  • Debian Ubuntu 10/11/12 Linux how to get tftpd-hpa server setup tutorial
  • efibootmgr: option requires an argument -- 'd' efibootmgr version 15 grub-install.real: error: efibootmgr failed to register the boot entry: Operation not permitted.
  • Apache Error Won't start SSL Cert Issue Solution Unable to configure verify locations for client authentication SSL Library Error: 151441510 error:0906D066:PEM routines:PEM_read_bio:bad end line SSL Library Error: 185090057 error:0B084009:x509 certif
  • Linux Debian Mint Ubuntu Bridge br0 gets random IP
  • redis requirements
  • How to kill a docker swarm