The one oops I get is:
"/var/tmp/lperr/2011-12-08/OOPS-ba20d8ded4e8e05363d5ea7fcec26c88" may be a binary file. See it anyway?
Changes file must be signed with a valid GPG signature: Verification failed 3 times: ['No data', 'No data', 'No data']
Unhandled Error
Traceback (most recent call last):
Failure: twisted.protocols.ftp.PermissionDeniedError: Changes file must be signed with a valid GPG signature: Verification failed 3 times: ['No data', 'No data', 'No data']
So the first useful observation I have is that this shouldn't really be an OOPS, nor even logged - its sent directly to the user anyway, and we expect this to occur in production when users are muppets.
The one oops I get is: lperr/2011- 12-08/OOPS-ba20d8ded4e8e05363d5ea7fcec26c88" may be a binary file. See it anyway?
"/var/tmp/
Changes file must be signed with a valid GPG signature: Verification failed 3 times: ['No data', 'No data', 'No data']
Unhandled Error protocols. ftp.PermissionD eniedError: Changes file must be signed with a valid GPG signature: Verification failed 3 times: ['No data', 'No data', 'No data']
Traceback (most recent call last):
Failure: twisted.
So the first useful observation I have is that this shouldn't really be an OOPS, nor even logged - its sent directly to the user anyway, and we expect this to occur in production when users are muppets.