Package Details: linux-lqx-docs 6.12.1.lqx1-1

Git Clone URL: https://aur.archlinux.org/linux-lqx.git (read-only, click to copy)
Package Base: linux-lqx
Description: Documentation for the Linux Liquorix kernel
Upstream URL: https://liquorix.net/
Keywords: bbr2 bfq futex pds proton zen
Licenses: GPL-2.0-only
Submitter: akurei
Maintainer: sir_lucjan (damentz)
Last Packager: damentz
Votes: 161
Popularity: 1.51
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2024-12-01 17:30 (UTC)

Pinned Comments

damentz commented on 2020-08-31 15:22 (UTC) (edited on 2021-12-21 18:25 (UTC) by damentz)

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 121 Next › Last »

lnoferin commented on 2022-05-08 13:16 (UTC)

@damentz yes, I found the problem was in my configuration for the keyservers. Thanks the same!

damentz commented on 2022-05-07 23:31 (UTC)

@lnoferin, sounds like the keyserver was down or your network connection is blocking access. The ability pull down keys is also required for adding third party repos unless you disable signing.

We can't solve your network issues, so that's something you'll need to figure out on your end.

lnoferin commented on 2022-04-28 10:34 (UTC) (edited on 2022-04-28 10:34 (UTC) by lnoferin)

@sir_lucjan Tried but it failed:

gpg --recv-keys 9AE4078033F8024D && gpg --lsign-key 9AE4078033F8024D
gpg: keyserver receive failed: Connection refused

sir_lucjan commented on 2022-04-28 09:41 (UTC) (edited on 2022-04-28 09:41 (UTC) by sir_lucjan)

@lnoferin

Try gpg --recv-keys 9AE4078033F8024D && gpg --lsign-key 9AE4078033F8024D as normal user.

lnoferin commented on 2022-04-28 09:37 (UTC)

I cannot build the package on a manjaro because this error:

pamac build linux-lqx                          1 ✘  1m 3s  
Preparing...
Cloning linux-lqx build files...
Generating linux-lqx information...
Checking linux-lqx dependencies...
Resolving dependencies...
Checking inter-conflicts...

To build (1):
  linux-lqx  5.17.5.lqx1-1    AUR


Edit build files : [e] 
Apply transaction ? [e/y/N] y


Building linux-lqx...
==> Making package: linux-lqx 5.17.5.lqx1-1 (gio 28 apr 2022, 11:00:20)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found linux-5.17.tar.xz
  -> Found linux-5.17.tar.sign
  -> Found 5.17-9.tar.gz
==> Validating source files with sha512sums...
    linux-5.17.tar.xz ... Passed
    linux-5.17.tar.sign ... Skipped
    5.17-9.tar.gz ... Passed
==> Verifying source file signatures with gpg...
    linux-5.17.tar ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!
Error: Failed to build linux-lqx

I followed the pinned comment in this page but nothing changed:

pacman-key --keyserver hkps://keyserver.ubuntu.com --recv-keys 9AE4078033F8024D && pacman-key --lsign-key 9AE4078033F8024D
gpg: key 9AE4078033F8024D: "Steven Barrett <steven@liquorix.net>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
  -> Locally signed 1 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-05-02

damentz commented on 2022-04-08 22:37 (UTC)

I failed over to using my build scripts on my local system. Liquorix repo is up-to-date again. Builds are performed clean room in docker and produce the same artifacts as my cloud build project.

damentz commented on 2022-04-08 20:33 (UTC)

If anyone's wondering why the official packages are not updated, I'm working with AWS support on my account that does the binary builds, my ability to run CodeBuild projects got randomly revoked. I'll post a notification once the builds are back online and liquorix.net repository updated.

damentz commented on 2022-03-09 13:00 (UTC)

Sorry about that, I had a short deadline to push out an update and this one was more complicated due to a breakage with PDS. In my rush, I missed adding the patch in git itself, but didn't notice due to the way my docker builds work for Debian and Ubuntu.

New update is out, appears to be building. Builds for Debian and Ubuntu ran yesterday successfully so I'm assuming this one is good too.

AlPiotrowicz commented on 2022-03-09 11:54 (UTC)

Confirming the error reported by @Borov

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 121 Next › Last »