$ sudo apt install linux-image-6.1.0-23-amd64
Lendo listas de pacotes... Pronto
Construindo árvore de dependências... Pronto
Lendo informação de estado... Pronto
linux-image-6.1.0-23-amd64 is already the newest version (6.1.99-1).
linux-image-6.1.0-23-amd64 configurado para instalar manualmente.
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
$ sudo apt install linux-image-6.1.0-25-amd64
Lendo listas de pacotes... Pronto
Construindo árvore de dependências... Pronto
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote linux-image-6.1.0-25-amd64
E: Couldn't find any package by glob 'linux-image-6.1.0-25-amd64'
One of my pc's has this strange thing, I can't upgrade to latest kernel 6.1.0-25, running 6.1.0-23 now. On other machines the upgrade to 25 came as normal as always. What could it be?
Last edited by fch on 2024-10-02 17:05, edited 1 time in total.
Pinning, or a hold on linux-image-amd64 is nonsensical being a meta package. If linux-image-amd64 is not installed then the existing kernel is essentially on hold, and if you want to stay on a kernel that's how to do it. You can install or remove linux-image-amd64 as often as you want to suite. Installed, it will install the latest candidate without removing the last.
apt-mark showhold will not reveal a package held by synaptic. If we're not doing this the easy way with syanptic, then the easiest check is with apt policy linux-image-amd64. That will show the installed and the candidate. If the candidate does not show the current repo choice, then the package database is out of date and needs an apt update.
Rarely does the incremental kernel updates contain a critical ingredient relevant to every user.
CwF wrote: ↑2024-10-01 17:15
Pinning, or a hold on linux-image-amd64 is nonsensical being a meta package. If linux-image-amd64 is not installed then the existing kernel is essentially on hold, and if you want to stay on a kernel that's how to do it. You can install or remove linux-image-amd64 as often as you want to suite. Installed, it will install the latest candidate without removing the last.
apt-mark showhold will not reveal a package held by synaptic. If we're not doing this the easy way with syanptic, then the easiest check is with apt policy linux-image-amd64. That will show the installed and the candidate. If the candidate does not show the current repo choice, then the package database is out of date and needs an apt update.
Rarely does the incremental kernel updates contain a critical ingredient relevant to every user.
It is isntalled, and have ran apt update as I often do, but still:
deb http://deb.debian.org/debian/ bookworm non-free-firmware main contrib
deb http://deb.debian.org/debian/ bookworm-updates non-free-firmware main contrib
deb http://security.debian.org/debian-security/ bookworm-security non-free-firmware main contrib
# deb http://deb.debian.org/debian/ bookworm-backports main non-free-firmware
deb http://deb.debian.org/debian/ bookworm non-free-firmware main contrib
deb http://deb.debian.org/debian/ bookworm-updates non-free-firmware main contrib
deb http://security.debian.org/debian-security/ bookworm-security non-free-firmware main contrib
# deb http://deb.debian.org/debian/ bookworm-backports main non-free-firmware
deb http://ftp.debian.org/debian/ bookworm main non-free non-free-firmware contrib
deb http://deb.debian.org/debian-security bookworm-security main non-free non-free-firmware contrib
deb http://deb.debian.org/debian bookworm-updates main non-free non-free-firmware contrib
$ sudo apt update
[sudo] senha para user:
Atingido:1 http://deb.debian.org/debian bookworm InRelease
Atingido:2 http://security.debian.org/debian-security bookworm-security InRelease
Atingido:3 http://deb.debian.org/debian bookworm-updates InRelease
Lendo listas de pacotes... Pronto
Construindo árvore de dependências... Pronto
Lendo informação de estado... Pronto
All packages are up to date.
I can't see why apt does not show the latest kernel in your apt database!?!? although I do not think it is because of slightly different sources.list as they should both work (yours and mrmazda's) but in case there is a difference here is mine.
deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
deb http://security.debian.org/ bookworm-security main contrib non-free non-free-firmware
deb http://deb.debian.org/debian/ bookworm-proposed-updates main contrib non-free non-free-firmware
Share your Debian SCRIPTS There will be neither barrier nor walls, neither official nor guard, there will be no more desert and the entire world will become a garden. — Anacharsis Cloots
CwF wrote: ↑2024-10-02 17:35
There have been a handful of locked package database threads in the past few months, no we need to figure out what action is causing this?
I tested on other PCs here and they don't have any locked packages. I only had the problem in one of them.