I'm having a strange issue with PGP signature

I’m trying to update my system and when i do it gives me a corrupted data base error, I have tried the pacman wiki and scripts that i found on the forum from both megavolt and cscs. none of which worked, on top of that it only seems to effect AUR packages, which makes me think it might not be the pgp signatures but i’m not sure.

Hi @razz,

If you try the update without the AUR:

pamac upgrade --no-aur

And please provide complete output from the terminal, not just what you deem relevant.

Try refreshing your database… :point_down:

pamac update --force-refresh
1 Like

I mean this works, but it doesn’t solve the fact that I can’t update any of my AUR packages.

Never said it would. It is not recommended to update everything at once. The repository software should be updated first an then if there wasn’t trouble the AUR packages is to be updates. Also note that the AUR is unsupported and not recommended is you use the stable branch. That said, try updating the AUR and all databases:

pamac upgrade --aur --force-refresh

Error: Failed to prepare transaction: invalid or corrupted database
Edit build files : [e]
Apply transaction ? [e/y/N] y
Transaction cancelled.

this is the result i got.

Error: Failed to prepare transaction: invalid or corrupted database
Edit build files : [e]
Apply transaction ? [e/y/N] y
Transaction cancelled.

it didn’t work, i understand the AUR is unsupported, it’s just a shame to not be able to use it as it’s such a large and helpful resource.

Try to clean your cache, first:

sudo pacman -Scc
1 Like

clearing the cache first has not changed anything, it still results in the same error.

Does this help? :point_down:

1 Like

Try clearing the pamac databases. They are located in /tmp/pamac-<your-username>/dbs/sync/ (for example, mine are stored in /tmp/pamac-scotty/dbs/sync/):

rm -fr /tmp/pamac-<your-username>/dbs/sync/

You should be able to do that as a normal user. If that doesn’t work, then use sudo.

Then run:

pamac update --force-refresh

to rebuild the databases.

But make sure that all future pamac transactions are done as a normal user - database errors seem to most often occur after sudo has been incorrectly used with pamac.

2 Likes

yes, this seems to have fixed the issue, thank you.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.