Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63687 > unrolled thread
| Started by | Thorsten Glaser <tg@mirbsd.de> |
|---|---|
| First post | 2019-03-24 01:40 +0100 |
| Last post | 2019-04-17 23:00 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.kernel
Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k Thorsten Glaser <tg@mirbsd.de> - 2019-03-24 01:40 +0100
Bug#925379: marked as done (linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-04-07 19:30 +0200
Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k Ben Hutchings <ben@decadent.org.uk> - 2019-04-17 23:00 +0200
| From | Thorsten Glaser <tg@mirbsd.de> |
|---|---|
| Date | 2019-03-24 01:40 +0100 |
| Subject | Bug#925379: linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k |
| Message-ID | <xEZl7-2Em-1@gated-at.bofh.it> |
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:
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2019-04-07 19:30 +0200 |
| Subject | Bug#925379: marked as done (linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k) |
| Message-ID | <xKjMd-3Rj-7@gated-at.bofh.it> |
| In reply to | #63687 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sun, 07 Apr 2019 17:18:37 +0000 with message-id <E1hDBRF-0004lU-3A@fasolo.debian.org> and subject line Bug#925379: fixed in linux-base 4.6 has caused the Debian Bug report #925379, regarding linux-base: linux-version vmlinuz/vmlinux dichotomy, breaks at least m68k 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.) -- 925379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925379 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2019-04-17 23:00 +0200 |
| Message-ID | <xNZOV-2BX-5@gated-at.bofh.it> |
| In reply to | #63687 |
[Multipart message — attachments visible in raw view] — view raw
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.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web