Hey Dan, that is what I checked on the system after the do-release-upgrade - it all looked good. But it's more interesting to see how it looked before starting the upgrade, hence I reinstalled a plucky system, but there it's all fine too:
$ cat /etc/zipl.conf # This has been modified by the MAAS curtin installer [defaultboot] default=ubuntu [ubuntu] target = /boot image = /boot/vmlinuz ramdisk = /boot/initrd.img parameters = root=/dev/disk/by-id/dm-uuid-LVM-yN1IXeTB4tvQfEurSlji4SQRwAEyXwCYUmcW2AeeVnrHorA8YCFeBvCEbPtHwm6M $ ls -la /boot/initrd.img lrwxrwxrwx 1 root root 28 Oct 6 16:40 /boot/initrd.img -> initrd.img-6.14.0-33-generic I thought that something may prevents the system from following the symlink (? coreutils came to my mind), but a manual remove and (re-)install of kdump-tools works flawlessly on questing... Installing of - as well as upgrading to - (the relatively independent) kdump-tools_1.10.7ubuntu2_s390x.deb (from questing) on plucky also worked fine. Having kdump-tools_1.10.7ubuntu2_s390x.deb installed on plucky and doing a do-release-upgrade worked without causing the here mentioned glitch (like assumed). So guess it's smells like coreutils or the way do-release-upgrade upgrades kdump-tools, but I think there is nothin special ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2126934 Title: upgrade to 25.10 fails on kdeump-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2126934/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
