Forums before death by AOL, social media and spammers... "We can't have nice things"
|    linux.debian.kernel    |    Debian kernel discussions    |    2,884 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,205 of 2,884    |
|    Pascal Hambourg to All    |
|    Bug#1124667: linux-image-6.18.3-1 only a    |
|    06 Jan 26 16:50:02    |
      XPost: linux.debian.bugs.dist       From: pascal@plouf.fr.eu.org              On Mon, 5 Jan 2026 13:05:59 +0100 Salvatore Bonaccorso wrote:       > On Mon, Jan 05, 2026 at 11:10:22AM +0100, Roland Clobus wrote:       >>       >> The package linux-image-amd64 for 6.18.3-1 depends only on the signed kernel       >> package [1]. At this moment the signed version is (not yet?) available, so       >> the installation will fail.       >>       >> For sid, the source package appears to have been changed from       >> 'linux-signed-amd64' to 'linux'. Could that be causing this issue?              I guess so. What is the reason of this change ?              >> Would it be possible to change the dependency to:       >> linux-image-6.18.3+deb14-amd64 | linux-image-6.18.3+deb14-amd64-unsigned       >> instead?              Not sure it is a good idea. It could lead to the installation of an       unsigned kernel while a signed kernel was expected. This would make the       system unbootable with secure boot.              > This is normal for short while. FTP master will need to trigger the       > codesigning service, at which point then we will get the signed images       > as well.              Is it really normal to update the kernel meta-package before the signed       kernel package the new version depends on is available ?              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca