Marco, I apologise, but I do not understand what it is you want to achieve or what it is that you are asking.
Can you please give more explanation? You said: "not leave the 6.12 (upstream LTS) branch and not upgrade to some higher kernel version like 6.13 when they would also become available in backports" What do you think "backports" are ? Have you already installed any backports? Why do you not want to install backports? Are you saying that you only want to use Debian Bookworm packages? And not any packages that are from new releases (e.g. Trixie or Forky) that have been recompiled to be used in Debian Bookworm ? (which I believe is what Backports are). If this is correct, then would removing any mention of Backports from your APT sources.list be what you want to do? (others on this list could comment if my suggestion is correct nor not). I believe (as with previous discussions about rsync on Debian User), that sometimes security updates are: "packages taken from the next Debian release (called "testing"), adjusted and recompiled for usage on Debian stable." Hence if you want to stay secure and use security updates, there will be times when you will be using a package from Testing, ... but it will be "adjusted and recompiled for usage on Debian stable", as are all backports, which is why we use backports and not just download a package from Testing and install it. Maybe you are concerned that your LTS Bookworm will one day just become Debian Trixie? This is not how Debian works. As long as your sources in APT stays "Bookworm", you should always been at the Bookworm release. To change "Bookworm" to "Trixie", you have to manually change your sources and do a full upgrade, then this will change your Debian release. https://backports.debian.org/ https://www.debian.org/releases/ Index of releases Version Code Name Release Date End of Life (EOL) EOL LTS EOL ELTS Status 14 Forky TBA TBA TBA TBA Codename announced 13 Trixie TBA TBA TBA TBA "testing" — no release date has been set 12 Bookworm 2023-06-10 2026-06-10 2028-06-30 2033-06-30 Current "stable" release https://en.wikipedia.org/wiki/Debian_version_history https://wiki.debian.org/SourcesList Example sources.list If you need the contrib, non-free and non-free-firmware components, add contrib non-free non-free-firmware after main. For example, for Debian 12/Bookworm: deb https://deb.debian.org/debian bookworm main contrib non-free non-free-firmware deb-src https://deb.debian.org/debian bookworm main contrib non-free non-free-firmware deb https://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware deb-src https://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware deb https://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware deb-src https://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware If you need the Backports, contrib, and non-free components, add bookworm-backports lines. For example, for Debian 12/Bookworm: deb https://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware deb-src https://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware # nano /etc/apt/sources.list I usually update my Bookworm by one of two methods, which do much the same thing: # apt update && apt update && apt full-upgrade --autoremove -y && apt autoremove && apt clean or # apt update # apt list --upgradable # apt full-upgrade --autoremove -y # systemctl reboot # apt autoremove # apt clean I hope some of this helps, sorry I am confused about what you wanted to ask. George. On Wednesday, 22-01-2025 at 07:17 Marco Möller wrote: > Hello community! > Could you please share with me, or point me to, a howto or receipt for > applying all upgrades to future kernel 6.12.x versions to appear in > Bookworm Backports when doing "apt update && apt upgrade", but to not > leave the 6.12 (upstream LTS) branch and not upgrade to some higher > kernel version like 6.13 when they would also become available in backports? > Thanks a lot in advance! Talby. > >
