Hi ,If an update is on only testing and unstable branch ,then that means that those updates are not yet ready for stable branch and must be in testing phase where the code and optimised and stabilized for public use after days of testing
On Sun, 17 Apr 2022 at 15:30, phil995511 - <phil995...@gmail.com> wrote: > Hello, > > Chromium is on version 99 on Debian 11 Stable : > > bullseye (stable) (web): navigateur web > 99.0.4844.74-1~deb11u1: amd64 arm64 armhf i386 > > https://packages.debian.org/search?suite=default§ion=all&arch=any&lang=fr&searchon=names&keywords=chromium > > 2 highlest security updates have been released since. > > The Testing and Unstable branches each get one of these 2 updates > (100.0.4896.88-1 & 100.0.4896.127-1), but not Stable (99.0.4844.74-1) !?! > > Debian 11 Stable users are exposed to these major security flaws. > > They risk having important confidential information stolen, whether their > computer systems are hacked remotely ;-( > > Your solution of pushing browser updates first through Unstable, then > through Testing and finally pushing them to the Stable branch more than a > 1/2 month later has the consequence that you leave your Debian Stable users > become potential victims of hackers. > > This way of doing things is wrong and needs to be changed urgently for the > good of Debian Stable users !!! > > You must immediately publish all new updates to the Stable branch, > immediately after they have been released !!! > > The current situation just makes you want to abandon Debian for a > distribution with better monitoring of updates... > > Regards. >
