[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#924129: marked as done (debian-installer: Kernel for armhf for stretch unbootable)

Your message dated Sun, 27 Dec 2020 09:59:40 +0100
with message-id <20201227085938.GA12742@debian.org>
and subject line Re: Bug#924129: debian-installer: Kernel for armhf for stretch unbootable
has caused the Debian Bug report #924129,
regarding debian-installer: Kernel for armhf for stretch unbootable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
924129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924129
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Version: 20170615+deb9u5+b2
Severity: grave
Justification: renders package unusable

Dear maintainers,

Debian kernel bug #922478 renders armhf systems unbootable. This bug was
fixed, but the debian-installer images still use (I presume) kernel
version 4.9.144-3, the unbootable version. I noticed this today while
trying to install a new system using:

http://http.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/firmware.Wandboard.img.gz

The installer worked when I overwrote the /vmlinuz in that image with
the one from the new 4.9.144-3.1.

Thanks,

Peter.

-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.9.0-8-armmp (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Version: 20170615+deb9u6

Hi,

I noticed this bug is still open.

On Wed, Mar 27, 2019 at 04:51:06PM +0100, Cyril Brulebois wrote:
> Adam D. Barratt <adam@adam-barratt.org.uk> (2019-03-26):
> > As I mentioned on IRC, we can't "push it into stretch" without a point
> > release, and the whole point of this exercise was to avoid having to
> > schedule another short-notice point release.
> 
> FTAOD: That's exactly in line with what I think I tried to convey over
> the last few days/weeks, I'm sorry if I failed to get this point
> through.
> 
> > However, assuming KiBi has no objections, it sounds like we can go
> > ahead with getting the -9 ABI kernel into p-u in preparation for the
> > 9.9 point release in a few weeks time. Assuming I haven't missed
> > anything, the d-i version in p-u should continue to be suitable for
> > installing stretch on armhf in the meantime (at least until the p-u
> > freeze hits, at which point d-i will get rebuilt against the new
> > kernel).
> 
> Accepting the bump should be fine at this point, thanks and sorry for
> the wait.

Version 20170615+deb9u6 has the -9 ABI kernel, and has been in stretch for a
while now. I think this bug can be closed. It was probably already fixed in
the +deb9u5+b3 build, but the BTS version tracking doesn't really handle
binNMUs.

Thanks,

Ivo

--- End Message ---
Reply to: