Description:
After installing the version of pacman noted below, pacman-key --init
hangs if the file /etc/pacman.d/gnupg/secring.gpg has zero length. This happened
to me on one machine (for reasons unknown) while upgrading to pacman 4.0.3-2.
The solution on this machine was to copy a correct secring.gpg file from another
(healthy) machine. Pacman-key --init could then do its job and the following
pacman-key --populate archlinux worked fine.

I traced the hang to the %commit command in the routine "generate_master_key()"
in the pacman-key script. Beyond that I could not go, since I don't know
what %commit does.

Since I have no idea what caused the secring.gpg file to be of zero length, I
won't be able to reproduce this sequence, since it happened randomly on one
(64 bit) machine out of three.

Some more sanity checking on input files while running pacman-key --init
might save a lot of trouble if/when this happens to somebody in the future.
Since this problem brings upgrading the system to a halt, I consider it to
be quite serious.


Additional info:
* package version(s)
pacman 4.0.3-2
* config and/or log files etc.
Nothing useful available.

Steps to reproduce:
Make the secring.gpg file of zero length after upgrading
to pacman 4.0.3-2 and run pacman-key --init. (Once pacman-key --init has
been run successfully, it doesn't seem to care anymore.)