-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[xenial] fix Unknown status message: u'IMPORT_OK'
related test failures
#4038
Comments
heads up, see |
If I remember correctly, these were due to the |
So @anweshadas provided the solution to fix these, I am running the tests right now. Will submit a PR for the fix. |
And all gpg related tests are passing. Now have to work for a reasonable patch from this. |
kushaldas
added a commit
that referenced
this issue
Jan 17, 2019
For the python-gnupg to work properly on Xenial, we should call `gpg` binary instead of `gpg2` (which we use in Trusty).
This was referenced Jan 17, 2019
25 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Unit tests involving importing an armored key/decryption appear to be failing, possibly related to #4013 (different error message though)
Steps to Reproduce
make test-xenial
Expected Behavior
All is merry and well
Actual Behavior
A bunch of integration test failures, e.g.:
Comments
I would bump to the latest python-gnupg and see if the issue was resolved upstream (I didn't see anything about this issue in the bugtracker, but worth a try), ref: #3622
The text was updated successfully, but these errors were encountered: