Bug 975815

Summary: ENCRYPT_NO_ENCRYPT_TO pubkey_algo and hash_algo missing
Product: [Fedora] Fedora Reporter: Till Maas <opensource>
Component: pygpgmeAssignee: Toshio Ernie Kuratomi <a.badger>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: a.badger, ivazqueznet, mitr, opensource
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pygpgme-0.3-8.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-12 01:57:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Till Maas 2013-06-19 12:10:28 UTC
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...

Comment 1 Till Maas 2013-07-03 08:54:09 UTC
What can be done to get this moving?

Comment 2 Till Maas 2013-08-19 09:24:54 UTC
ping?

Comment 3 Toshio Ernie Kuratomi 2013-08-21 17:39:41 UTC
@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?

Comment 4 Miloslav Trmač 2013-08-21 17:50:38 UTC
(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.)

Comment 5 Fedora Update System 2013-08-22 08:24:16 UTC
pygpgme-0.3-8.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/pygpgme-0.3-8.fc19

Comment 6 Fedora Update System 2013-08-23 00:39:52 UTC
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).

Comment 7 Fedora Update System 2013-09-12 01:57:19 UTC
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.