Re: Bug#1088605: installation-reports: No installable kernel was found in the defined APT sources

Daniel Lewart <[email protected]>
Newsgroups gmane.linux.debian.devel.cd
Message-ID <CALE_k2GhccgynER1T7mC4w8eV=5Y-EeTOziR_ESRh2boyRPLQA@mail.gmail.com>
Cyril, et al,

On Thu, Nov 28, 2024 at 7:50 AM Cyril Brulebois <[email protected]> wrote:
> Daniel Lewart <[email protected]> (2024-11-28):
> > Package: installation-reports
> > Severity: grave
> > Tags: d-i
> > Justification: renders package unusable
> >
> > (Please provide enough information to help the Debian
> > maintainers evaluate the report efficiently - e.g., by filling
> > in the sections below.)
> >
> > Boot method: CD
> > Image version: https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso 2024-11-25
> > Date: 2024-11-28
>
> > ┌───────────────────┤ [!] Install the base system ├────────────────────┐
> > │                                                                      │
> > │ No installable kernel was found in the defined APT sources.          │
> > │                                                                      │
> > │ You may try to continue without a kernel, and manually install your  │
> > │ own kernel later. This is only recommended for experts, otherwise    │
> > │ you will likely end up with a machine that doesn't boot.             │
> > │                                                                      │
> > │ Continue without installing a kernel?                                │
> > │                                                                      │
> > │ <Go Back>                                          <Yes>    <No>     │
> > │                                                                      │
> > └──────────────────────────────────────────────────────────────────────┘
> >
> > <Description of the install, in prose, and any thoughts, comments
> >       and ideas you had during the initial install.>
> >
> > Everything went fine until base-installer failed.
> > I think the cause is that this directory:
> >       pool/main/l/linux-signed-amd64
> > is missing the following files:
> >       linux-image-x.y.z-amd64_x.y.z-1_amd64.deb
> >       linux-image-amd64_x.y.z-1_amd64.deb
> > This should be easy to reproduce.
>
> Looping in debian-cd@, who is responsible for image builds. There are no
> linux-image* debs mentioned in list-cd indeed. linux got uploaded on
> Saturday, but linux-signed-* only came in on Monday, which is weekly
> image build day. Not sure that explains everything though.
>
> Cheers,
> --
> Cyril Brulebois ([email protected])            <https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant

The Fri Nov 29 first Daily build fails in the same fashion:
    https://cdimage.debian.org/cdimage/daily-builds/daily/20241129-1/amd64/iso-cd/debian-testing-amd64-netinst.iso
and its list-cd also has no linux-image-* debs:
    https://cdimage.debian.org/cdimage/daily-builds/daily/20241129-1/amd64/list-cd/debian-testing-amd64-netinst.list.gz
So I don't think it is a timing issue.

Thank you!
Daniel Lewart
Urbana, Illinois
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.