ALHP/ALHP.GO
6
43
Fork 9
Code Issues 25 Pull Requests Projects Releases Wiki Activity

Is ALHP key expired? #274

New Issue
Closed
opened 2025-04-01 20:14:34 +02:00 by zatrit · 14 comments
zatrit commented 2025-04-01 20:14:34 +02:00
Copy Link

I keep getting this error when updating my system:

error: core-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is unknown trust
error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is unknown trust
error: multilib-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is unknown trust

I've tried clearing the synchronization database files manually and completely refreshing it with sudo pacman -Syyu and refreshing the pacman keys with sudo pacman-key --refresh-keys. I'm not sure, but could the ALHP key be expired?

Upd:
It looks like the “g.harting@mailstash.org” key has expired, as shown in this comment: https://aur.archlinux.org/packages/alhp-keyring#comment-1017936

I keep getting this error when updating my system: ``` error: core-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is unknown trust error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is unknown trust error: multilib-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is unknown trust ``` I've tried clearing the synchronization database files manually and completely refreshing it with ``sudo pacman -Syyu`` and refreshing the pacman keys with ``sudo pacman-key --refresh-keys``. I'm not sure, but could the ALHP key be expired? Upd: It looks like the “g.harting@mailstash.org” key has expired, as shown in this comment: https://aur.archlinux.org/packages/alhp-keyring#comment-1017936
zatrit commented 2025-04-01 20:17:10 +02:00
Author
Copy Link

Okay, I checked pacman-key --list-keys cie@harting.dev, it says that the key is not expired.

Okay, I checked ``pacman-key --list-keys cie@harting.dev``, it says that the key is not expired.
PatJK commented 2025-04-01 20:18:09 +02:00
Copy Link

I'm having the issue as well on the v3 repos. Also tried to rebuild the key database entirely to no avail.

I'm having the issue as well on the v3 repos. Also tried to rebuild the key database entirely to no avail.
zatrit commented 2025-04-01 20:22:29 +02:00
Author
Copy Link

There's a discussion of this problem here: https://aur.archlinux.org/packages/alhp-keyring
Upd: also #1

There's a discussion of this problem here: https://aur.archlinux.org/packages/alhp-keyring Upd: also #1
zatrit reopened this issue 2025-04-01 20:26:55 +02:00
zatrit changed title from Are ALHP keys expired? to Is ALHP keys expired? 2025-04-01 20:32:17 +02:00
anonfunc commented 2025-04-01 20:32:34 +02:00
Owner
Copy Link

Seems like the trustdb trust key expired. I'm on it.

Seems like the ~~trustdb~~ trust key expired. I'm on it.
mihalycsaba commented 2025-04-01 20:33:03 +02:00
Copy Link
pacman-key -l cie@harting.dev
gpg: Note: trustdb not writable
pub   rsa4096 2020-08-12 [SC] [expires: 2026-04-24]
      0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
uid           [ unknown] Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>
``` pacman-key -l cie@harting.dev gpg: Note: trustdb not writable pub rsa4096 2020-08-12 [SC] [expires: 2026-04-24] 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 uid [ unknown] Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev> ```
anonfunc commented 2025-04-01 20:54:31 +02:00
Owner
Copy Link

Please test with alhp-keyring 20250401-1.

Please test with `alhp-keyring 20250401-1`.
zatrit commented 2025-04-01 20:57:17 +02:00
Author
Copy Link

It seems to be working now

It seems to be working now
👍 1
zatrit changed title from Is ALHP keys expired? to Is ALHP key expired? 2025-04-01 21:07:42 +02:00
aaronliu0130 commented 2025-04-02 03:08:39 +02:00
Copy Link

No idea why but the new version of the package didn't work for me even after lsigning anonfunc's key (whose fingerprint is in alhp-trusted). I finally just worked around the error by lsigning 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 (the renewed CIE key). Is there something I should be worried about?

No idea why but the new version of the package didn't work for me even after lsigning anonfunc's key (whose fingerprint is in alhp-trusted). I finally just worked around the error by lsigning 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 (the renewed CIE key). Is there something I should be worried about?
dmig commented 2025-04-02 08:53:25 +02:00
Copy Link

Still getting error with core-x86-64-v3 and extra-x86-64-v3 after key update. For core-x86-64-v4, extra-x86-64-v4, core-x86-64-v2 and extra-x86-64-v2 issue is fixed.

Still getting error with `core-x86-64-v3` and `extra-x86-64-v3` after key update. For `core-x86-64-v4`, `extra-x86-64-v4`, `core-x86-64-v2` and `extra-x86-64-v2` issue is fixed.
anonfunc commented 2025-04-02 09:34:44 +02:00
Owner
Copy Link

Signing the cie@ key should not be necessary, since the key should have trust via the master key.

Can someone for whom its not working post the output of the following, please?

pacman-key -l cie@harting.dev 539@idlegandalf.com
Signing the cie@ key should not be necessary, since the key should have trust via the master key. Can someone for whom its not working post the output of the following, please? ``` pacman-key -l cie@harting.dev 539@idlegandalf.com ```
dmig commented 2025-04-02 09:54:22 +02:00
Copy Link

On a system where key still fails:

> pacman-key -l cie@harting.dev 539@idlegandalf.com
gpg: Note: trustdb not writable
pub   rsa4096 2020-08-12 [SC] [expires: 2026-04-24]
      0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
uid           [ unknown] Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>

On one that is fixed:

 pacman-key -l cie@harting.dev 539@idlegandalf.com
gpg: Note: trustdb not writable
pub   rsa4096 2020-08-12 [SC] [expires: 2026-04-24]
      0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
uid           [  full  ] Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>

pub   ed25519 2024-05-19 [SC] [expires: 2029-05-18]
      00B25193054EA4BC7BA870848CA32F8BF3BC8088
uid           [  full  ] Giovanni Harting <539@idlegandalf.com>
sub   cv25519 2024-05-19 [E] [expires: 2029-05-18]
On a system where key still fails: ``` > pacman-key -l cie@harting.dev 539@idlegandalf.com gpg: Note: trustdb not writable pub rsa4096 2020-08-12 [SC] [expires: 2026-04-24] 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 uid [ unknown] Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev> ``` On one that is fixed: ``` pacman-key -l cie@harting.dev 539@idlegandalf.com gpg: Note: trustdb not writable pub rsa4096 2020-08-12 [SC] [expires: 2026-04-24] 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 uid [ full ] Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev> pub ed25519 2024-05-19 [SC] [expires: 2029-05-18] 00B25193054EA4BC7BA870848CA32F8BF3BC8088 uid [ full ] Giovanni Harting <539@idlegandalf.com> sub cv25519 2024-05-19 [E] [expires: 2029-05-18] ```
dmig commented 2025-04-02 09:58:15 +02:00
Copy Link

Ok, seems somehow alhp-keyring reinstall failed first time.

Steps I used to fix:

  1. edit /etc/pacman.conf, comment out core-x86-64-v3 and extra-x86-64-v3
  2. run yay -S alhp-keyring
  3. edit /etc/pacman.conf, uncomment repositories
Ok, seems somehow `alhp-keyring` reinstall failed first time. Steps I used to fix: 1. edit `/etc/pacman.conf`, comment out `core-x86-64-v3` and `extra-x86-64-v3` 2. run `yay -S alhp-keyring` 3. edit `/etc/pacman.conf`, uncomment repositories
👍 1
Psiko commented 2025-04-03 17:49:47 +02:00
Copy Link

The following worked for me with paru:

  1. disable all alhp repositories in /etc/pacman.conf
  2. run paru --mflags --skippgpcheck -S alhp-keyring
  3. enable repositories again
The following worked for me with `paru`: 1. disable all alhp repositories in `/etc/pacman.conf` 2. run `paru --mflags --skippgpcheck -S alhp-keyring` 3. enable repositories again
hanuman commented 2025-06-05 21:14:30 +02:00
Copy Link

I started getting this error.

pacman-key --list-keys cie@harting.dev

gpg: Note: trustdb not writable
pub   rsa4096 2020-08-12 [SC] [expires: 2026-04-24]
0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
uid           [  full  ] Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>

sudo pacman -S alhp-keyring

warning: alhp-keyring-20250509-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)               Old Version  New Version  Net Change

chaotic-aur/alhp-keyring  20250509-1   20250509-1     0.00 MiB

Total Installed Size:  0.00 MiB
Net Upgrade Size:      0.00 MiB

Still...

error: core-x86-64-v3: signature from "ALHP Buildbot buildbot@alhp.dev" is invalid

I started getting this error. ``` pacman-key --list-keys cie@harting.dev gpg: Note: trustdb not writable pub rsa4096 2020-08-12 [SC] [expires: 2026-04-24] 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 uid [ full ] Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev> ``` ``` sudo pacman -S alhp-keyring warning: alhp-keyring-20250509-1 is up to date -- reinstalling resolving dependencies... looking for conflicting packages... Package (1) Old Version New Version Net Change chaotic-aur/alhp-keyring 20250509-1 20250509-1 0.00 MiB Total Installed Size: 0.00 MiB Net Upgrade Size: 0.00 MiB ``` Still... > error: core-x86-64-v3: signature from "ALHP Buildbot <buildbot@alhp.dev>" is invalid
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked upstream
bug
Something is not working
 build-failure
package build fails
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 informational
Provides information about something
 invalid
Something is wrong
 invalid/corrupt package
Package needs to be rebuild
 packaging issue
priority: high
High priority
 question
More information is needed
 support
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
anonfunc
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ALHP/ALHP.GO#274
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?