Description of problem: some fields/constants from gpgme are not exposed in pygpgme. I proposed patches to upstream, but got no response for the second bug within one month. The first bug report is not that old. https://bugs.launchpad.net/pygpgme/+bug/1192545 https://bugs.launchpad.net/pygpgme/+bug/1192545/+attachment/3707307/+files/pygpgme-no-encrypt-to.patch https://bugs.launchpad.net/pygpgme/+bug/1002421 https://bugs.launchpad.net/pygpgme/+bug/1002421/+attachment/3676331/+files/gpgme-pubkey-hash-algo.patch Is it possible to get these patches included into Fedora? They are pretty simple and likely to applied by upstream if it becomes responsive. Alternatively, can you maybe ping upstream, maybe you have better channels...
What can be done to get this moving?
ping?
@mitr -- hey, I don't use this at all anymore. Are you okay if I make tyll a comaintainer on the package and he can apply the patches?
(In reply to Toshio Ernie Kuratomi from comment #3) > @mitr -- hey, I don't use this at all anymore. Are you okay if I make tyll > a comaintainer on the package and he can apply the patches? I was hoping to leave this up to you :) I have now approved Till as a comaintainer. (I've also finally taken the time to look at the patches, they look fine.)
pygpgme-0.3-8.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/pygpgme-0.3-8.fc19
Package pygpgme-0.3-8.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pygpgme-0.3-8.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15185/pygpgme-0.3-8.fc19 then log in and leave karma (feedback).
pygpgme-0.3-8.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.