[arch-general] error: GPGME error: Invalid crypto engine
Carsten Mattner
carstenmattner at gmail.com
Fri Apr 4 05:40:58 EDT 2014
Does someone else have problems upgrading with testing enabled since
yesterday? Checked the mailing list and there's not warning that
testing is broken.
:: Synchronizing package databases...
testing is up to date
core is up to date
extra is up to date
community-testing is up to date
community is up to date
:: Starting full system upgrade...
warning: bash: local (4.3.008-1) is newer than core (4.3-3)
warning: readline: local (6.3.003-1) is newer than core (6.3-3)
resolving dependencies...
looking for inter-conflicts...
Packages (1): linux-3.14-3
Total Installed Size: 69.37 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [...] 100%
error: GPGME error: Invalid crypto engine
(1/1) checking package integrity [...] 100%
error: GPGME error: Invalid crypto engine
error: linux: missing required signature
:: File /var/cache/pacman/pkg/linux-3.14-3-x86_64.pkg.tar.xz is
corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
Same problem if I try to downgrade readline and bash
:: File /var/cache/pacman/pkg/readline-6.3-3-x86_64.pkg.tar.xz is
corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: bash: missing required signature
:: File /var/cache/pacman/pkg/bash-4.3-3-x86_64.pkg.tar.xz is
corrupted (invalid or corrupted package (PGP signature)).
More information about the arch-general
mailing list