Works perfect! Thanks for this solution.
Should we change SigLevel config back to original, after completing the update?
Best,
Orkut
Not necessary.
1 Like
I just had trouble updating dropbox where reversing the changes made to /etc/pacman.conf fixed it. So for some cases it might be helpful to “switch back”.
This topic is pacman related not custom packages.
Custom package build from AUR and their package signature and keys are handled manually.
Thank you so much for the in depth explanation and solution. I’ve encountered this issue more than once and the way I fixed it was not even the same across instances.
This seems to be the true solution.
How do you handle a problem with signature and keys with custom package builds from AUR?
See one of the pinned topics in the AUR section:
1 Like
That didnt really help, maybe thats not the problem after all. Thank you.
I also had to remove a directory named
drwx------ 1 alpm alpm 0 26. Nov 20:31 download-t6hQ3O
(wherever this did come from) 
cat /etc/pacman.conf | grep alpm