lynix / linux-aarch64-lts Goto Github PK

Hello to you,

I finally got around to installing your linux-aarch64-lts on my Globalscale Mochabin. My firmware is configure to boot off of boot/Image and in the past my linux packages and IIRC yours too, were configure to install /boot/Image.

The screenshot shows it had a bad day without its beloved Image file.

Not to worry, I just made a symlink and everything is peachy now.

lrwxrwxrwx 1 root root 25 Nov 26 11:43 /boot/Image -> vmlinuz-linux-aarch64-lts

You might want to consider adjusting your package to include making such a symlink.

Other than that, I'm utterly delighted with your excellent work!

Please update to 6.1.47. Thanks.

Like Arch, linux-aarch64 and linux-aarch64-lts should not be in conflict.
For example, right now my ARM server is running well with linux-aarch64. When I tried to install linux-aarch64-lts, it requires to remove linux-aarch64. Scary!! It could break my system if anything goes wrong, so I think it's best to let users decide whether or not to remove linux-aarch64 after installing and sucessfully booting into linux-aarch64-lts.

Hello to you,

Your PKGBUILD has:

_package-headers() {
  pkgdesc="Headers and scripts for building modules for the $pkgdesc kernel"
  provides=("linux-headers=$pkgver")
  conflicts=(linux-headers)

But my ALARM deployment has a different name for the kernel header package. Instead of linux-headers it has linux-aarch64-headers. This resulted in having both kernel header packages installed after I installed your kernel package:

$ yay -Qo /lib/modules/6.2.10-1-aarch64-ARCH/build/vmlinux
/usr/lib/modules/6.2.10-1-aarch64-ARCH/build/vmlinux is owned by linux-aarch64-headers 6.2.10-1

$ yay -Qo /lib/modules/6.1.63-1-aarch64-lts-ARCH/vmlinuz
/usr/lib/modules/6.1.63-1-aarch64-lts-ARCH/vmlinuz is owned by linux-aarch64-lts 6.1.63-1

Not to worry, I can just yay -R linux-aarch64-headers on my own.

Thanks again and again.