Package Details: alhp-keyring 20250401-1

Git Clone URL: https://aur.archlinux.org/alhp-keyring.git (read-only, click to copy)
Package Base: alhp-keyring
Description: ALHP PGP keyring
Upstream URL: https://somegit.dev/ALHP/alhp-keyring
Licenses: GPL-3.0-or-later
Submitter: anonfunc
Maintainer: anonfunc
Last Packager: anonfunc
Votes: 31
Popularity: 1.02
First Submitted: 2021-11-25 19:49 (UTC)
Last Updated: 2025-04-01 18:53 (UTC)

Pinned Comments

anonfunc commented on 2025-04-01 18:56 (UTC)

Should be fixed with 20250401-1. Also, for ref: https://somegit.dev/ALHP/ALHP.GO/issues/274

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

anonfunc commented on 2023-05-04 13:44 (UTC)

@sant0s Still investigating why that subkey appears as unknown trust. It's signed by the master key, so there should be trust.

sant0s commented on 2023-05-04 13:34 (UTC)

@whoami pacman-key --refresh-keys seems to have fixed it :)

whoami commented on 2023-05-04 13:25 (UTC)

@sant0s

$ curl -LO https://somegit.dev/ALHP/alhp-keyring/raw/branch/master/alhp.gpg
# pacman-key --add alhp.gpg

sant0s commented on 2023-05-04 13:23 (UTC)

@anonfunc I am still getting signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is unknown trust even after updating

whoami commented on 2023-05-04 13:09 (UTC)

    alhp-keyring-20230504.tar.gz ... FAILED
    alhp-keyring-20230504.tar.gz.sig ..

dataprolet commented on 2023-05-04 12:27 (UTC)

Thanks, seems you have forgotten to update the checksum.

anonfunc commented on 2023-05-04 12:12 (UTC) (edited on 2023-05-04 12:14 (UTC) by anonfunc)

For anyone experiencing signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is unknown trust: Update alhp-keyring first, then the error should be gone.

If pacman refuses to install it, disable the ALHP entries in your pacman.conf, install it, then reenable them.

LeoKesler commented on 2022-09-05 00:33 (UTC)

@Neko-san , how you fixed ? I am having the same issue.

Neko-san commented on 2022-07-12 03:30 (UTC)

I did try this with makepkg and still ahve this issue, that's why I came here. Regardless, I've solved my issue.

anonfunc commented on 2022-07-11 20:17 (UTC) (edited on 2022-07-11 20:18 (UTC) by anonfunc)

If you build & install this package with makepkg, pacman will not complain, since there is no signing involved locally. This package's source is also signed with a different pgp key as these used in ALHP, no overlap.