RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Fedora contains patches to provide access to more attributes/constants from gpgme. However since upstream is dead, they are not shipped there. Is it possible to ship them in RHEL? The patches are:

http://pkgs.fedoraproject.org/cgit/pygpgme.git/tree/pygpgme-no-encrypt-to.patch
http://pkgs.fedoraproject.org/cgit/pygpgme.git/tree/pygpgme-pubkey-hash-algo.patch

Thanks for your report.

Do you have a specific use case in mind?

RHEL updates are limited in number and scope, and prioritized by technical and customer need.  Having a customer case attached to this bug (through the Customer Portal, access.redhat.com, or perhaps your organization’s TAM) would make it more likely that these patches can be included.

(For the record, the corresponding Fedora chanage is #975815.)

Unfortunately I do not have a customer case for this. I use for custom scripts to check signatures and make sure that signatures are using a good algorithm. And the no-encrypt-to hash allows to encrypt files to certain keys only ignoring keys that are set in the gpg.conf file. I falsely remembered that the package was in EPEL and now noticed when trying my script on EPEL7 that it is not and therefore does not contain the patches.

Please close this ticket. I will not use pygpgme in the future but migrate to python-gpg.