Bug 1433367 - port sigul from pygpgme
Summary: port sigul from pygpgme
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: sigul
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Patrick Uiterwijk
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1400848
TreeView+ depends on / blocked
 
Reported: 2017-03-17 13:19 UTC by Igor Gnatenko
Modified: 2020-06-09 11:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-09 11:23:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Igor Gnatenko 2017-03-17 13:19:25 UTC
pygpgme is completely dead and will be retired ASAP. You can use official Python bindings from gpgme (packages are called pythonX-gpg).

Comment 1 Patrick Uiterwijk 2017-06-19 06:20:41 UTC
Well, those bindings are not available in RHEL/EPEL 7:

[root@6bb08cfa72b4 /]# cat /etc/redhat-release 
CentOS Linux release 7.3.1611 (Core) 
[root@6bb08cfa72b4 /]# yum list python-gpg python2-gpg
Error: No matching Packages to list

What would you suggest to use there, since building an additional package is easier than adding subpackages for packages that are already in RHEL?

Comment 2 Igor Gnatenko 2017-06-19 07:49:37 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=1412310 for RHEL part ;)

I recommend to switch to gpgme (which is already in Fedora for long time, and possible soon will be in RHEL7 but that's not up to me).

Comment 3 Jan Kurik 2017-08-15 08:21:30 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 4 Igor Gnatenko 2017-09-30 11:44:44 UTC
ping?

I'm planning to retire pygpgme in F28.

Comment 5 Ben Cotton 2018-11-27 18:25:21 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2018-11-30 17:57:56 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 7 Neal Gompa 2018-12-11 13:36:28 UTC
This is now an urgent problem, since pygpgme is _gone_ in Fedora.

Comment 8 Ben Cotton 2019-02-19 17:11:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

Comment 9 Ben Cotton 2020-04-30 22:05:05 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Ben Cotton 2020-05-26 15:06:10 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 11 Neal Gompa 2020-06-04 01:25:01 UTC
Still potentially a problem...

Comment 12 Patrick Uiterwijk 2020-06-09 11:23:37 UTC
This is now fixed in Sigul v1.0, of which Alpha 1 is now released and built in Rawhide.


Note You need to log in before you can comment on or make changes to this bug.