Bug 752908
Summary: | fldigi will not install on Fedora 16 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John J. McDonough <wb8rcr> |
Component: | fldigi | Assignee: | Randy Berry <randyn3lrx> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | brianmury, juhani.jaakola, maurizio.antillon, randyn3lrx |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | fldigi-3.21.34-2.fc16 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-01-04 01:55:18 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 716125 | ||
Bug Blocks: |
Description
John J. McDonough
2011-11-10 18:54:24 UTC
Fldigi uses fltk 1.1, F16 uses fltk 1.3. There is some code still in fldigi currently that makes 1.3 puke so no package can be built against the new fltk libraries. Upstream is aware of the problem. Hopefully it will be resolved soon. There is an open bug for the FTBFS https://bugzilla.redhat.com/show_bug.cgi?id=716125 fldigi-3.21.34-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/fldigi-3.21.34-2.fc16 (In reply to comment #2) > fldigi-3.21.34-2.fc16 has been submitted as an update for Fedora 16. > https://admin.fedoraproject.org/updates/fldigi-3.21.34-2.fc16 Fldigi finally builds for F16. This is a VERY important bug for allot of people. Please be sure to add karma if it works for you to speed up the journey to stable. Thanks, de Randy, N3LRX Working for me (using the x86_64 package), karma added. fldigi-3.21.34-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |