Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1277334

Bug#1124667: linux-image-6.18.3-1 only available as unsigned

From Salvatore Bonaccorso <carnil@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1124667: linux-image-6.18.3-1 only available as unsigned
Date 2026-01-06 20:50 +0100
Message-ID <Male1-8zgQ-3@gated-at.bofh.it> (permalink)
References (2 earlier) <M9Rzj-8ets-9@gated-at.bofh.it> <M9Rzj-8ets-11@gated-at.bofh.it> <MahtM-8wEk-3@gated-at.bofh.it> <M9Rzj-8ets-11@gated-at.bofh.it> <MahtM-8wEk-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Control: reopen -1

Hi Pascal,

On Tue, Jan 06, 2026 at 04:43:19PM +0100, Pascal Hambourg wrote:
> 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 ?

I was I think bit prematurely to close the issue, because I think we
should explain from where the change come (and if we actually want to
cause this situation).

If I'm correct, with the change af3f11740ed9 ("Introduce a base
package for version sync") we now generate again the linux-image-*
packages from src:linux.

 [1] https://salsa.debian.org/kernel-team/linux/-/commit/af3f11740ed9525b0c035f941c86ddc5e10125bb

The downside of this change is exactly as you described, we do not
have anymore the linux-image-* package build only at the time when the
signed packages exists and will cause temporary situations as
described, so in theory reopen #941042.

Bastian, Ben, is this something we should rethink about?

Regards,
Salvatore

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1124667: linux-image-6.18.3-1 only available as unsigned Pascal Hambourg <pascal@plouf.fr.eu.org> - 2026-01-06 16:50 +0100
  Bug#1124667: linux-image-6.18.3-1 only available as unsigned Salvatore Bonaccorso <carnil@debian.org> - 2026-01-06 20:50 +0100
    Bug#1124667: linux-image-6.18.3-1 only available as unsigned Pascal Hambourg <pascal@plouf.fr.eu.org> - 2026-01-07 19:20 +0100

csiph-web