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

Bad signature on extra-x86-64-v3 DB #35

New Issue
Closed
opened 2021-07-29 22:16:48 +02:00 by moviuro · 4 comments
moviuro commented 2021-07-29 22:16:48 +02:00
Copy Link

I tried updating my system, and it failed:

# pacman -Syu
error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is invalid
:: Synchronizing package databases...
 core-x86-64-v3 is up to date
 extra-x86-64-v3                                                              1406,7 KiB  3,71 MiB/s 00:00 [----------------------------------------------------------------] 100%
 community-x86-64-v3 is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 repo-ck is up to date
 custom 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)

I tried updating the GPG key:

# pacman-key --keyserver keyserver.ubuntu.com --recv-keys 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
gpg: key E3D0D2CD3952E298: "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

I tried manually testing the DB:

/var/lib/pacman/sync # gpg --homedir /etc/pacman.d/gnupg/ --verify extra-x86-64-v3.db.sig
gpg: WARNING: unsafe permissions on homedir '/etc/pacman.d/gnupg'
gpg: assuming signed data in 'extra-x86-64-v3.db'
gpg: Signature made 2021-07-29T20:33:35 CEST
gpg:                using RSA key 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
gpg: BAD signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" [full]

I tried removing the offending files:

/var/lib/pacman/sync # mkdir broken
/var/lib/pacman/sync # mv extra-x86-64-v3.db* broken
/var/lib/pacman/sync # pacman -Syu
:: Synchronizing package databases...
 core-x86-64-v3 is up to date
 extra-x86-64-v3                                                              1406,7 KiB  4,58 MiB/s 00:00 [----------------------------------------------------------------] 100%
 community-x86-64-v3 is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 repo-ck is up to date
 custom 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)

However the rest seems to be OK:

/var/lib/pacman/sync # gpg --homedir /etc/pacman.d/gnupg/ --verify core-x86-64-v3.db.sig 
gpg: WARNING: unsafe permissions on homedir '/etc/pacman.d/gnupg'
gpg: assuming signed data in 'core-x86-64-v3.db'
gpg: Signature made 2021-07-29T11:14:56 CEST
gpg:                using RSA key 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298
gpg: Good signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" [full]
I tried updating my system, and it failed: ``` # pacman -Syu error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" is invalid :: Synchronizing package databases... core-x86-64-v3 is up to date extra-x86-64-v3 1406,7 KiB 3,71 MiB/s 00:00 [----------------------------------------------------------------] 100% community-x86-64-v3 is up to date core is up to date extra is up to date community is up to date multilib is up to date repo-ck is up to date custom 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) ``` I tried updating the GPG key: ``` # pacman-key --keyserver keyserver.ubuntu.com --recv-keys 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 gpg: key E3D0D2CD3952E298: "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 ``` I tried manually testing the DB: ``` /var/lib/pacman/sync # gpg --homedir /etc/pacman.d/gnupg/ --verify extra-x86-64-v3.db.sig gpg: WARNING: unsafe permissions on homedir '/etc/pacman.d/gnupg' gpg: assuming signed data in 'extra-x86-64-v3.db' gpg: Signature made 2021-07-29T20:33:35 CEST gpg: using RSA key 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 gpg: BAD signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" [full] ``` I tried removing the offending files: ``` /var/lib/pacman/sync # mkdir broken /var/lib/pacman/sync # mv extra-x86-64-v3.db* broken /var/lib/pacman/sync # pacman -Syu :: Synchronizing package databases... core-x86-64-v3 is up to date extra-x86-64-v3 1406,7 KiB 4,58 MiB/s 00:00 [----------------------------------------------------------------] 100% community-x86-64-v3 is up to date core is up to date extra is up to date community is up to date multilib is up to date repo-ck is up to date custom 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) ``` However the rest seems to be OK: ``` /var/lib/pacman/sync # gpg --homedir /etc/pacman.d/gnupg/ --verify core-x86-64-v3.db.sig gpg: WARNING: unsafe permissions on homedir '/etc/pacman.d/gnupg' gpg: assuming signed data in 'core-x86-64-v3.db' gpg: Signature made 2021-07-29T11:14:56 CEST gpg: using RSA key 0D4D2FDAF45468F3DDF59BEDE3D0D2CD3952E298 gpg: Good signature from "Archlinux CIE Repos (Build 2020/2021) <cie@harting.dev>" [full] ```
Gontier-Julien commented 2021-07-29 22:18:07 +02:00
Copy Link

Same as #34

Same as #34
moviuro commented 2021-07-29 22:26:59 +02:00
Author
Copy Link

I was probably typing the detailled report while @lxgr-linux was posting his issue

I was probably typing the detailled report while @lxgr-linux was posting his issue
👍 1
anonfunc commented 2021-07-29 22:31:52 +02:00
Owner
Copy Link

Please try again, should be fixed.

Please try again, should be fixed.
👍 1
anonfunc commented 2021-07-29 22:32:41 +02:00
Owner
Copy Link

closing this as dup of #34

closing this as dup of #34
anonfunc added the
duplicate
 label 2021-07-29 22:32:47 +02:00
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
duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
anonfunc
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ALHP/ALHP.GO#35
No description provided.
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?