signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is invalid #254

Closed
opened 2024-07-24 20:28:16 +02:00 by mihalycsaba · 11 comments
error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is invalid
:: Synchronizing package databases...
 endeavouros is up to date
 core-x86-64-v3 is up to date
 extra-x86-64-v3                                                 1027.9 KiB  1162 KiB/s 00:01 [-------------------------------------------------------] 100%
 multilib-x86-64-v3 is up to date
 core is up to date
 extra is up to date
 multilib is up to date
error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is invalid
error: failed to synchronize all databases (unexpected error)
 -> error refreshing databases - exit status 1

``` error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is invalid :: Synchronizing package databases... endeavouros is up to date core-x86-64-v3 is up to date extra-x86-64-v3 1027.9 KiB 1162 KiB/s 00:01 [-------------------------------------------------------] 100% multilib-x86-64-v3 is up to date core is up to date extra is up to date multilib is up to date error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is invalid error: failed to synchronize all databases (unexpected error) -> error refreshing databases - exit status 1 ```
Owner

Little more info please:

  • what mirror do you use
  • output of pacman-key -l cie@harting.dev
  • did you try pacman -Suyy
Little more info please: - what mirror do you use - output of `pacman-key -l cie@harting.dev` - did you try `pacman -Suyy`
anonfunc added the
support
label 2024-07-24 21:02:33 +02:00
Author

thank you pacman -Suyy solved it, I tried -Syy and -Syu they didn't work. Pacman is confusing sometimes.

thank you `pacman -Suyy` solved it, I tried -Syy and -Syu they didn't work. Pacman is confusing sometimes.
Author

Sorry I closed before finish update

:: Retrieving packages...
 dbus-broker-units-36-4.1-x86_64                                    2.4 KiB  31.7 KiB/s 00:00 [-------------------------------------------------------] 100%
 dbus-broker-36-4.1-x86_64                                        169.2 KiB  1301 KiB/s 00:00 [-------------------------------------------------------] 100%
 Total (2/2)                                                      171.6 KiB   943 KiB/s 00:00 [-------------------------------------------------------] 100%
(29/29) checking keys in keyring                                                              [-------------------------------------------------------] 100%
(29/29) checking package integrity                                                            [-------------------------------------------------------] 100%
:: File /var/cache/pacman/pkg/dbus-broker-36-4.1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (checksum)).
Do you want to delete it? [Y/n] y
:: File /var/cache/pacman/pkg/dbus-broker-units-36-4.1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (checksum)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
Sorry I closed before finish update ``` :: Retrieving packages... dbus-broker-units-36-4.1-x86_64 2.4 KiB 31.7 KiB/s 00:00 [-------------------------------------------------------] 100% dbus-broker-36-4.1-x86_64 169.2 KiB 1301 KiB/s 00:00 [-------------------------------------------------------] 100% Total (2/2) 171.6 KiB 943 KiB/s 00:00 [-------------------------------------------------------] 100% (29/29) checking keys in keyring [-------------------------------------------------------] 100% (29/29) checking package integrity [-------------------------------------------------------] 100% :: File /var/cache/pacman/pkg/dbus-broker-36-4.1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (checksum)). Do you want to delete it? [Y/n] y :: File /var/cache/pacman/pkg/dbus-broker-units-36-4.1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (checksum)). Do you want to delete it? [Y/n] y error: failed to commit transaction (invalid or corrupted package) Errors occurred, no packages were upgraded. ```
Author

I have no idea how to check which mirror is being used

pacman-key -l 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>

I have no idea how to check which mirror is being used ``` pacman-key -l 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> ```
Owner

Is the problem still there after you deleted the files and redownloaded them?

Is the problem still there after you deleted the files and redownloaded them?

I got the same corruption errors for dbus-broker and dbus-broker-units. Deleting and redownloading didn't help. So I reordered my alhp-mirrorlist, moving the Europe mirrors to the top.

Before it was:

  1. Worldwide
  2. Asia
  3. Europe

I changed it to:

  1. Europe
  2. Worldwide
  3. Asia

The full mirrorlist now:

##
## ALHP repository mirrorlist
## Updated on 2024-06-15
## https://somegit.dev/ALHP/alhp-mirrorlist
##
## There is an IPFS mirror available.
## Setup instructions in /etc/pacman.d/alhp-mirrorlist.ipfs.
##

## Europe
Server = https://mirror.sunred.org/alhp/$repo/os/$arch/
Server = https://alhp.nox.panibrez.com/$repo/os/$arch/
Server = https://alhp.dev/$repo/os/$arch/
Server = https://mirrors.dotsrc.org/alhp/$repo/os/$arch/

## Worldwide (CDN)
Server = https://cdn.alhp.dev/$repo/os/$arch/
Server = https://alhp.krautflare.de/$repo/os/$arch/

## Asia
Server = https://mirrors.shanghaitech.edu.cn/alhp/$repo/os/$arch/
Server = https://mirror.nju.edu.cn/alhp/$repo/os/$arch/
Server = https://mirror.sjtu.edu.cn/alhp/$repo/os/$arch/

This fixed the issue for me.

I got the same corruption errors for `dbus-broker` and `dbus-broker-units`. Deleting and redownloading didn't help. So I reordered my `alhp-mirrorlist`, moving the Europe mirrors to the top. Before it was: 1. Worldwide 1. Asia 1. Europe I changed it to: 1. Europe 1. Worldwide 1. Asia The full mirrorlist now: ``` ## ## ALHP repository mirrorlist ## Updated on 2024-06-15 ## https://somegit.dev/ALHP/alhp-mirrorlist ## ## There is an IPFS mirror available. ## Setup instructions in /etc/pacman.d/alhp-mirrorlist.ipfs. ## ## Europe Server = https://mirror.sunred.org/alhp/$repo/os/$arch/ Server = https://alhp.nox.panibrez.com/$repo/os/$arch/ Server = https://alhp.dev/$repo/os/$arch/ Server = https://mirrors.dotsrc.org/alhp/$repo/os/$arch/ ## Worldwide (CDN) Server = https://cdn.alhp.dev/$repo/os/$arch/ Server = https://alhp.krautflare.de/$repo/os/$arch/ ## Asia Server = https://mirrors.shanghaitech.edu.cn/alhp/$repo/os/$arch/ Server = https://mirror.nju.edu.cn/alhp/$repo/os/$arch/ Server = https://mirror.sjtu.edu.cn/alhp/$repo/os/$arch/ ``` This fixed the issue for me.

You don't need to do that for the entire region. Just move the cdn.alhp.dev mirror below the other one and it'll verify correctly.

Checking the files from that mirror, the checksums are indeed incorrect.

@mihalycsaba Would you like to change the title of this issue?

You don't need to do that for the entire region. Just move the `cdn.alhp.dev` mirror below the other one and it'll verify correctly. Checking the files from that mirror, the checksums are indeed incorrect. @mihalycsaba Would you like to change the title of this issue?
Owner

Probably a bad cache then? I'll purge these files, maybe that will help.

Probably a bad cache then? I'll purge these files, maybe that will help.
Owner

I have purged the affected URLs. If someone can still reproduce, please let me know if its fixed.

I have purged the affected URLs. If someone can still reproduce, please let me know if its fixed.

@anonfunc seems to fixed on my end, my packages were upgraded

@anonfunc seems to fixed on my end, my packages were upgraded
Author

Yes it's fixed now.

Yes it's fixed now.
Sign in to join this conversation.
No description provided.