Bug 1576918 - Can sigul please be updated for EPEL?
Summary: Can sigul please be updated for EPEL?
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: sigul
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Patrick Uiterwijk
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-10 17:44 UTC by John Florian
Modified: 2020-06-09 11:32 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description John Florian 2018-05-10 17:44:03 UTC 
Description of problem:

My sigul bridge and server are deployed on CentOS (to reduce OS upgrade frequency), but this only gets sigul-0.101 which seems to be quite behind upstream now.  If it were incredibly stable, I wouldn't mind but I find it necessary to frequently restart sigul_server due to broken RPC.

If such an upgrade isn't possible for whatever reason, I'd at least like to know that much so I can consider redeploying on Fedora (assuming that'd work).  I had started there originally but couldn't make it work at all due to some incompatibility I don't remember the details of.
Comment 1 Patrick Uiterwijk 2020-06-09 11:32:57 UTC 
Sigul v0 series will require GPGv1, which is not available for EL7 or any recent Fedora releases.
Sigul v1 works with Python3 and GPGv2(.1+), which means it will work out of the box with EL8 and any recent Fedora release.
Note You need to log in before you can comment on or make changes to this bug.