Bug 1711027

Summary: Sphinxtrain cannot be installed: nothing provides libsphinxbase.so.1
Product: [Fedora] Fedora Reporter: David <davidmenhur>
Component: sphinxtrainAssignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: extras-orphan, loganjerry, mike
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-26 17:31:26 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 David 2019-05-16 18:38:41 UTC
Sphinxtrain cannot be installed from the repos because of missing dependencies.

# dnf install sphinxtrain
Error: 
 Problem: conflicting requests
  - nothing provides libsphinxbase.so.1()(64bit) needed by sphinxtrain-1.0.8-46.fc29.x86_64
  - nothing provides libsphinxad.so.0()(64bit) needed by sphinxtrain-1.0.8-46.fc29.x86_64
(try to add '--skip-broken' to skip uninstallable packages)

Comment 1 Jerry James 2019-05-17 01:11:59 UTC
I turned over all of the CMU sphinx related packages to another maintainer last August.  I meant to remove myself from the packages, but obviously forgot to do so since I received email about this bug.  It looks like that other maintainer then proceeded to break pretty much the entire set of packages, then orphaned them.  Some, but not all, have subsequently been removed from Fedora Rawhide due to lack of a maintainer.

I'm not sure what to suggest here.  I have neither interest in bringing these packages back, nor time to do so.  Unless someone else steps up to adopt the CMU sphinx packages, they're going to remain broken in F29 and later, and will probably be removed from Rawhide entirely in the near future.

Comment 2 David 2019-05-17 05:36:34 UTC
That would be a real shame. Is there any requirements to become a maintainer?

Comment 3 W. Michael Petullo 2019-10-13 17:12:43 UTC
The problem appears related to the deprecating of Python 2. I am working to get this fixed. See also #1736448 and #1747650.

Comment 4 W. Michael Petullo 2019-10-17 11:03:38 UTC
The sphinxbase package is back in Rawhide, so someone could rebuild sphinxtrain. I have updated the sphinxbase and pocketsphinx pacakges to use Python 3.

Comment 5 Ben Cotton 2020-04-30 20:56:13 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 6 Ben Cotton 2020-05-26 17:31:26 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.