On Sun 03 Jan 2021 at 11:56:49 (-0500), Cindy Sue Causey wrote: > On 1/3/21, David Wright <deb...@lionunicorn.co.uk> wrote: > > On Sun 03 Jan 2021 at 14:56:26 (+0000), shadowma...@logorroici.org wrote: > >> I have no idea how to solve this problem: I installed a Debian 10 in > >> my computer. > > > >> I don't know how to configure correctly the sources.list > >> file so I just changed all the 'buster' for 'bullseye' and it upgraded > >> well (but the Debian-security failed I don't know why. It would be > >> interesting if someone helps me with that). > > > > Because there is no security support for testing. > > My apologies in advance if I've misinterpreted the question and thus > am about to waste space. :) > > When I bumped from Buster to Bullseye, it took "a few seconds" of > digging to figure out why the previous security repository > declarations failed. I now have this in my user CHOICE of a > /etc/apt/sources.list.d/debian.sources file: > > Types: deb deb-src > URIs: http://security.debian.org/debian-security > Suites: bullseye-security > Components: main contrib non-free > > It has been so long since I used the /etc/apt/sources.list file method > that it just now took "a few more seconds" to fall back into it, After > multiple stabs at it, this FINALLY worked correctly *for me*: > > deb http://security.debian.org/debian-security bullseye-security main > contrib non-free > deb-src http://security.debian.org/debian-security bullseye-security > main contrib non-free > > That's all based on going back to packages.debian.org to refresh my > brain that I had stable, testing, and unstable all assigned to the > proper project names (Buster, Bullseye, and Sid, respectively).
I don't follow testing, so the existence of http://security.debian.org/debian-security/dists/bullseye-security/ was of interest. I would attach its Release file, but it's a 42k waste of bandwidth for list members, so here's a command for taking a look: $ wget http://security.debian.org/debian-security/dists/bullseye-security/Release The Release file consists mainly of the well-known string e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 as would be generated by sha256sum /dev/null. Cheers, David.