Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k
Hi! On 4/17/19 10:48 PM, Ben Hutchings wrote: >> Just as a heads-up: I'm going to switch sparc and sparc64 over to an >> uncompressed kernel as well since compressed kernels are not >> officially >> supported and actually don't work with GRUB 2.04~rc1 when I tested >> on sparc64 [1]. > > It might be worth adding a versioned dependency on linux-base for the > affected architectures. Sure. I'm just waiting for the Buster release now before I'll be pushing changes to debian-installer and components and sending merge requests for src:linux and src:linux-base. I have already accumulated a couple of patches. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k
On Wed, 2019-04-17 at 14:30 +0200, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 3/24/19 1:28 AM, Thorsten Glaser wrote:
> > This is because /usr/share/perl5/DebianLinux.pm was not updated
> > accordingly:
> >
> > # Find kernel image name stem for this architecture
> > my $image_stem;
> > if ((uname())[4] =~ /^(?:mips|parisc|powerpc|ppc)/) {
> > $image_stem = 'vmlinux';
> > } else {
> > $image_stem = 'vmlinuz';
> > }
> Just as a heads-up: I'm going to switch sparc and sparc64 over to an
> uncompressed kernel as well since compressed kernels are not
> officially
> supported and actually don't work with GRUB 2.04~rc1 when I tested
> on sparc64 [1].
It might be worth adding a versioned dependency on linux-base for the
affected architectures.
Ben.
--
Ben Hutchings
Make three consecutive correct guesses and you will be considered
an expert.
signature.asc
Description: This is a digitally signed message part
Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k
Hi!
On 3/24/19 1:28 AM, Thorsten Glaser wrote:
> This is because /usr/share/perl5/DebianLinux.pm was not updated
> accordingly:
>
> # Find kernel image name stem for this architecture
> my $image_stem;
> if ((uname())[4] =~ /^(?:mips|parisc|powerpc|ppc)/) {
> $image_stem = 'vmlinux';
> } else {
> $image_stem = 'vmlinuz';
> }
Just as a heads-up: I'm going to switch sparc and sparc64 over to an
uncompressed kernel as well since compressed kernels are not officially
supported and actually don't work with GRUB 2.04~rc1 when I tested
on sparc64 [1].
Adrian
> [1] http://lists.gnu.org/archive/html/grub-devel/2019-04/msg00071.html
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k
On 3/24/19 1:28 AM, Thorsten Glaser wrote:
> Some time between 4.1.0-2 and 4.19.0-3, m68k kernels switched
> from vmlinuz-* to vmlinux-*:
I think on hppa, we switched the other way around. Putting in
debian-hppa@ into the loop.
> -rwxr-xr-x 1 root root 5933276 Feb 11 16:55 vmlinux-4.19.0-3-m68k*
> -rwxr-xr-x 1 root root 5933284 Mar 15 02:16 vmlinux-4.19.0-4-m68k*
> -rw-r--r-- 1 root root 1769849 Aug 26 2015 vmlinuz-4.1.0-2-m68k
>
> I was surprised by that 4.1.0-2 was the initrd updated by the
> initramfs-tools trigger on e2fsprogs update, before I purged
> (apt-get --purge autoremove) the 4.1.0-2 kernel, having just
> received the 4.19.0-4 one in a dist-upgrade.
>
> This is because /usr/share/perl5/DebianLinux.pm was not updated
> accordingly:
>
> # Find kernel image name stem for this architecture
> my $image_stem;
> if ((uname())[4] =~ /^(?:mips|parisc|powerpc|ppc)/) {
> $image_stem = 'vmlinux';
> } else {
> $image_stem = 'vmlinuz';
> }
>
> Since architectures can have both vmlinux-* and vmlinuz-*,
> I think this logic should be reconsidered and removed, as
> to instead take kernel images from both basenames.
>
> At the absolutely very least, it must be brought in line
> with current practicēs… however, that may break during
> upgrades, so, please redo it taking both names into account.
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unreleased
> APT policy: (500, 'unreleased'), (500, 'unstable')
> Architecture: m68k
>
> Kernel: Linux 4.19.0-3-m68k
> Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/lksh
> Init: sysvinit (via /sbin/init)
>
> Versions of packages linux-base depends on:
> ii debconf [debconf-2.0] 1.5.71
>
> linux-base recommends no packages.
>
> linux-base suggests no packages.
>
> -- debconf information:
> * linux-base/disk-id-convert-auto: true
> linux-base/removing-title:
> * linux-base/disk-id-manual-boot-loader:
> linux-base/disk-id-convert-plan-no-relabel: true
> * linux-base/disk-id-convert-plan: true
> linux-base/removing-running-kernel: true
> linux-base/disk-id-manual:
> linux-base/do-bootloader-default-changed:
> linux-base/disk-id-update-failed:
>
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k
Package: linux-base
Version: 4.5
Severity: important
Control: affects -1 initramfs-tools
Some time between 4.1.0-2 and 4.19.0-3, m68k kernels switched
from vmlinuz-* to vmlinux-*:
-rwxr-xr-x 1 root root 5933276 Feb 11 16:55 vmlinux-4.19.0-3-m68k*
-rwxr-xr-x 1 root root 5933284 Mar 15 02:16 vmlinux-4.19.0-4-m68k*
-rw-r--r-- 1 root root 1769849 Aug 26 2015 vmlinuz-4.1.0-2-m68k
I was surprised by that 4.1.0-2 was the initrd updated by the
initramfs-tools trigger on e2fsprogs update, before I purged
(apt-get --purge autoremove) the 4.1.0-2 kernel, having just
received the 4.19.0-4 one in a dist-upgrade.
This is because /usr/share/perl5/DebianLinux.pm was not updated
accordingly:
# Find kernel image name stem for this architecture
my $image_stem;
if ((uname())[4] =~ /^(?:mips|parisc|powerpc|ppc)/) {
$image_stem = 'vmlinux';
} else {
$image_stem = 'vmlinuz';
}
Since architectures can have both vmlinux-* and vmlinuz-*,
I think this logic should be reconsidered and removed, as
to instead take kernel images from both basenames.
At the absolutely very least, it must be brought in line
with current practicēs… however, that may break during
upgrades, so, please redo it taking both names into account.
-- System Information:
Debian Release: buster/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: m68k
Kernel: Linux 4.19.0-3-m68k
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages linux-base depends on:
ii debconf [debconf-2.0] 1.5.71
linux-base recommends no packages.
linux-base suggests no packages.
-- debconf information:
* linux-base/disk-id-convert-auto: true
linux-base/removing-title:
* linux-base/disk-id-manual-boot-loader:
linux-base/disk-id-convert-plan-no-relabel: true
* linux-base/disk-id-convert-plan: true
linux-base/removing-running-kernel: true
linux-base/disk-id-manual:
linux-base/do-bootloader-default-changed:
linux-base/disk-id-update-failed:
