eclean-kernel has met the following issue: Invalid magic for kernel file /boot/vmlinuz-4.19.0-rc1-00117-g5b32735eb348 (!= HdrS) If you believe that the mentioned issue is a bug, please report it to https://bitbucket.org/mgorny/eclean-kernel/issues. If possible, please attach the output of 'eclean-kernel --list-kernels' and your regular eclean-kernel call with additional '--debug' argument. Reproducible: Always Steps to Reproduce: 1. Possibly need EFI stub in the kernel Expected Results: Old kernels are removed I'm running this on ARM64
ok, it looks like 1.99.4 does not complain about magic numbers. Although, it did remove some of the files from my currently running kernel, so I had to reinstall it before rebooting...
I'll reopen this, since 1.99.4 also doesn't behave correctly. It's just that instead of refusing to run due to invalid magic, it tries to remove other files and leaves only vmlinuz in place. eclean-kernel -p The following kernels would be removed: == 4.19.0-rc6-16400-g23adc26c1ac2 == Rationale: [-] stale files (no matching kernel) Files: - /boot/System.map-4.19.0-rc6-16400-g23adc26c1ac2 - /boot/config-4.19.0-rc6-16400-g23adc26c1ac2 - /boot/initramfs-4.19.0-rc6-16400-g23adc26c1ac2.img The following command would be run: grub-mkconfig -o /boot/grub/grub.cfg
Thank you for the report. Please recompile and *attach* the logfiles and paste the emerge info as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket The logs must be part of the ticket, but not on external websites. We need to have all information at hand before ticket assignment, so that the maintainer can look after it in one session with minimal number of callbacks. Explain exactly, how we can reproduce it. Please reopen this ticket (Status:unconfirmed) afterwards.
I can't attach the kernel here. It's jut too big (23 MB). There are no other logs besides what I provided in commit #2. So what exactly do you want me to provide?
