A Debian user reported the following:

Note: this is a minor problem, but which can greatly increase your blood
pressure when reinstalling backuped files during a crash recovery :)

Attempting to decypher a gpg encrypted file with the private key imported (gpg
--import < my_private_key) but without the public key actually imported leads to
a misleading gpg error message suggesting that the encrypted file is somehow
invalid because it was encrypted using an unsuitable (signing) algorithm:
gpg: Ohhhh jeeee: no decrypt() for 17

Importing the public key solves this minor issue.

Maybe a message such as:
gpg: Ohhhh jeeee: no decrypt() for 17: did you forget to import the public key ?

Would be better.

Please comment.