this would be funny if I hadn't wasted hours already, trying to build a kernel from a local fork of the kernel (you would think this would be simpler than generating + applying patches, for iterative development...), and I end up with :
- a package named linux-git-6.18.r4.25ea[....].pkg.tar
- this package installs files into /usr/lib/modules/6.18.0-1-git-00004-.....
- also installs vmlinuz into /usr/lib/modules/6.19.0-rc1-1-git-03904-....
- /usr/lib/modules/6.18.0-1-git-00004-..../build/version contains the string '6.19.0-rc1-1-git-03904-....'
- grub-mkconfig has no hope of finding the kernel this way.
I have no suggestion or precise complaint, I guess this is just a warning to the unwary: if you're trying to do something even slightly non-standard, beware...
Pinned Comments
osimarr commented on 2023-05-07 22:27 (UTC) (edited on 2023-05-12 04:05 (UTC) by osimarr)
Hi. Since the package became an orphan, I adopted it to continue what I actively maintain on https://aur.archlinux.org/pkgbase/linux-mainline-git, now on this AUR package.
The build script and config file will be up-to-date with Arch's official Linux package unless an update is required to be functional.
But I intentionally removed the documentation package because it consumes too much building time.
This package supports certain customization if compiled by the user. Check for the README file inside the package repo, or the .INSTALL message after package installation to learn how.