Тестирование Debian — обновление «Buster» до версии «Bullseye», нет сервера для security.debian.org
Ten paciencia. Está descargando.
Si le ayuda, ejecute el siguiente comando para ver el tráfico TCP. Mostrará el tráfico para https (puerto 443 ).
sudo tcpdump port 443 -i en0
00:10:29.291315 IP 74.125.136.190.https > 192.168.1.20.49919: Flags [.], seq 35550648:35552066, ack 606, win 244, options [nop,nop,TS val 1672373960 ecr 50627133], length 1418
00:10:29.291321 IP 74.125.136.190.https > 192.168.1.20.49919: Flags [.], seq 35552066:35553484, ack 606, win 244, options [nop,nop,TS val 1672373960 ecr 50627133], length 1418
00:10:29.298028 IP 74.125.136.190.https > 192.168.1.20.49919: Flags [.], seq 35553484:35554902, ack 606, win 244, options [nop,nop,TS val 1672373966 ecr 50627138], length 1418
00:10:29.298289 IP 74.125.136.190.https > 192.168.1.20.49919: Flags [.], seq 35554902:35556320, ack 606, win 244, options [nop,nop,TS val 1672373966 ecr 50627138], length 1418
00:10:29.298344 IP 192.168.1.20.49919 > 74.125.136.190.https: Flags [.], ack 35556320, win 32590, options [nop,nop,TS val 50627164 ecr 1672373945], length 0
00:10:29.312330 IP 74.125.136.190.https > 192.168.1.20.49919: Flags [.], seq 35556320:35557738, ack 606, win 244, options [nop,nop,TS val 1672373995 ecr 50627164], length 1418
00:10:29.312561 IP 74.125.136.190.https > 192.168.1.20.49919: Flags [.], seq 35557738:35559156, ack 606, win 244, options [nop,nop,TS val 1672373995 ecr 50627164], length 1418
00:10:29.319361 IP 74.125.136.190.https > 192.168.1.20.49919: Flags [.], seq 35559156:35560574, ack 606, win 244, options [nop,nop,TS val 1672373995 ecr 50627164], length 1418
Tomó alrededor de 10 minutos en mi Mac.
Изhttps://wiki.debian.org/Status/Testing
deb http://security.debian.org testing-security main contrib non-free
deb-src http://security.debian.org testing-security main contrib non-free
Записи немного изменились после последней версии.
Для перехода на тестовую версию необходимо отключить обновления безопасности.
Как перейти на Debian (следующий -стабильный )Тестирование
To upgrade to testing from current stable, if you have already installed the stable release:
2.Remove or comment out your stable security updates line(s) (anything with security.debian.org in it).
Это немного сбивает с толку, но
If you are tracking testing or the next-stable code name, you should always have a corresponding deb http://security.debian.org <"testing" or codename>-security main line in your /etc/apt/sources.list. See this FAQ-Item. https://www.debian.org/security/faq#testing:
Q: How is security handled for testing?
A: Security for testing benefits from the security efforts of the entire project for unstable. However, there is a minimum two-day migration delay, and sometimes security fixes can be held up by transitions. The Security Team helps to move along those transitions holding back important security uploads, but this is not always possible and delays may occur. Especially in the months after a new stable release, when many new versions are uploaded to unstable, security fixes for testing may lag behind. If you want to have a secure (and stable) server you are strongly encouraged to stay with stable.
Я думаю, что вам НЕ следует отключать обновления безопасности для тестирования и оставлять строку типа
deb http://security.debian.org testing-security main