Arch Linux User Repository

Official binaries of linux-lqx, linux-lqx-headers, and linux-lqx-docs are now available: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#liquorix

Signing key import instructions: sudo pacman-key --keyserver hkps://keyserver.ubuntu.com --recv-keys 9AE4078033F8024D && sudo pacman-key --lsign-key 9AE4078033F8024D

@tydynrain, I have the same problem. I don't know what this affects, but I just commented out line 270 in PKGBUILD and the kernel builds without errors

@damentz, I appreciate your answer and suggestion. The thing is that I build custom kernels all the time, several of them (linux-cachyos, linux-ck, linux-xanmod, linux-xanmod-rt, and this one), and most build fine. This kernel too used to build fine for years, then recently the headers, but not the kernel, began failing to build successfully. So more than anything I want to understand what changed, so that I can adapt how I do things, and also why it only affects this kernel's headers.

@tydynrain, you probably won't like this answer, but there's something tainting your environment causing the build to fail. The binaries are still building successfully using a docker clean room environment on stateless build nodes.

My only advice is try getting the package to build in a docker container since there may be a common thing you're changing on your system, even on new installations, that's causing the failure.

If you need a starting Dockerfile that sets up the makepkg.conf file for you and dependencies, you can use the one used for CI in the cloud here: https://github.com/damentz/liquorix-package/blob/6.2/master/scripts/archlinux/Dockerfile. The GPG commands at the end expect that you define your local signing key, so maybe you can omit the gpg import and conf file changes for purposes of testing your build.

I'm still trying to get the headers to build successfully, but no luck so far. So far I've tried across two separate Arch installations and across two kernel versions, all with the same result that I posted below. I've usually not had a problem in the past, and I've used this kernel for quite a while now, so I don't know yet why it keeps failing.

I tried building this multiple times last night and again today, clearing everything and starting over, all with the same result. It usually builds fine. The kernel builds OK, but it fails on the headers. I used git clone and makepkg -si to build.

==> Starting package_linux-lqx-headers()...

Installing build files...

install: cannot stat 'tools/bpf/resolve_btfids/resolve_btfids': No such file or directory

==> ERROR: A failure occurred in package_linux-lqx-headers().

Aborting...

the linux-lqx kernel is the only one that doesn't boot in refind except by setting boot\initramfs-linux-lqx.img

I have problem with refind I use this setting root=\boot\initramfs-linux-lqx.img for run Linux-lqx, if I use normal setting for custom kernel this no work and the setting is root=\boot\initramfs-%v.img

Unflagged the "out-of-date" marker. This package is only out of date if the latest tag for the official project on github is newer than this AUR: https://github.com/damentz/liquorix-package

Liquorix will switch to 6.2 when it's ready, which depends primarily on Project-C to be ported forward, either by the upstream developer or by community.

@menkaur Official clean room builds completed successfully for last release. Most likely you have something tainted in your environment. If you can't figure it out, you can install binaries from website: curl 'https://liquorix.net/install-liquorix.sh' | sudo bash

I'm getting following error after successful compilation:

error: could not set install reason for package linux-lqx (could not find or read package)