Arch Linux

STUART

Member

From: Seattle, WA

Registered: 2010-08-19

Posts: 52

Website

[solved] Package invalid errors

I'm trying to fix a system that died in the middle of a `pacman -Syu` (via `pacman -Qenq | -S -`) and I'm having a ton of problems with packages begin invalid. I've set my clock and cleared the cache several times, and I'm still getting invalid signature errors. Here's the debug output from one invalid package:

debug: found cached pkg: /var/cache/pacman/pkg/gcc-4.8.2-8-x86_64.pkg.tar.xz
debug: sig data: iQEcBAABAgAGBQJS9WIIAAoJEPmf/g/q6Zm9av8H+wTWd7jkBVIBLKxdkqr5mFon9pyrh5ArxG5xmEI+mcozz1v1uzC+id35NXySFnb5kK+I5l1P4SO3SGCZeLbmO6ESDa9VVgiK9E5zFvniCcYF1bdRib1bs9i95V009krF6BRyLKRJdegyA6hT4wligU34NdIa/xnh48n3/ONwSe+YavJieY/2eZoSHLO73+4Lv68mzXPzZbUNm1J/XQXVnTLsy7fnpKwP4N2u8MnQI0RC7UGKtCNLTzVMiLXO/Vid4i4vcis/CeoJrdVk2g3HyxrZxZwnTmdygbuCyyAdFEC5F4H6pV4YzQ7QhhlCmrnB0GH+LnC+Vc3aZdJZk88FbZc=
debug: checking signature for /var/cache/pacman/pkg/gcc-4.8.2-8-x86_64.pkg.tar.xz
debug: 1 signatures returned
debug: fingerprint: F99FFE0FEAE999BD
debug: summary: red
debug: status: Bad signature
debug: timestamp: 0
debug: exp_timestamp: 0
debug: validity: unknown; reason: Success
debug: key: 6645B0A8C7005E78DB1D7864F99FFE0FEAE999BD, Allan McRae <me@allanmcrae.com>, owner_trust unknown, disabled 0
debug: signature is not valid

In stdout, that's:

error: gcc: signature from "Allan McRae <me@allanmcrae.com>" is invalid
:: File /var/cache/pacman/pkg/gcc-4.8.2-8-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]

When the validity check doesn't fail, the unpack often will, implying the same package is still bad.

It could be a bad mirror, in theory, except it's intermittent (albeit frequent), and my top mirror is kernel.org.

EDIT: Looks like the failure hosed something basic- reinstalling pacman's dependencies (including glibc) ended up triggering "illegal instruction" errors (and ultimately segfaults), and rebooting caused the same behavior in systemd.

When in doubt, boot install media, mount target and `pacstrap -cM base`.

This (pacstrapping base and then reinstalling everything) appears to have fixed the root problem, although I'm still experiencing echoes of the problem.

Last edited by STUART (2014-04-21 10:55:15)