This is documented behaviour; see below. GPA ignores this status line.

• KEYEXPIRED <expire-timestamp> The key has expired. expire-timestamp is the expiration time in seconds since Epoch. This status line is not very useful because it will also be emitted for expired subkeys even if this subkey is not used. To check whether a key used to sign a message has expired, the EXPKEYSIG status line is to be used. Note, that the TIMESTAMP may either be a number of seconds since Epoch or an ISO 8601 string which can be detected by the presence of the letter 'T'.

D366: 825_fix-in-gpgmepp.patch

Note to self.

The problem is that editinteractor in edit_interactor_callback_impl checks
status_to_error before the GpgSignKeyEditInteractor::nextState implementation
has the chance to ignore that status with needsNoResponse.

A fix in GpgMEpp could be to ignore the error if the state machine was not
started. E.g. we have not yet send any command.

Attached patch fixes the problem. But I'm not sure that this does not cause
regressions e.g. when trying to add a uid to an expired key or trying to
actually sign expired uid's. :-/

1.5.5 has been released. Closing.

Oops. Long standing bug.

Fix in commit
0d28a696163677d6b34a802b6beddecd805d0fc7

Fix has been released.

Should be fixed with the current stable GnuPG and GPGME versions.

Fixed with commit 2bb2618 for master. Will go into 1.5.0.
Thanks.

D193: 427_patch-src_posix-io_c

Duplicate of T1493

Please see T1493 - it is very likely the same reasons. I am not abale to
replicate it, though. The workaround is to configure gpgme with
--disable-fd-passing