Bug 563970 - RFE: New version of fldigi available
Summary: RFE: New version of fldigi available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fldigi
Version: 12
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Robert 'Bob' Jensen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-11 16:42 UTC by eric
Modified: 2010-05-04 06:21 UTC (History)
3 users (show)

Fixed In Version: fldigi-3.12.5-1.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-04 06:21:16 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description eric 2010-02-11 16:42:12 UTC 
Description of problem: There is a newer version of fldigi available at http://www.w1hkj.com/Downloads.html.
Comment 1 Randy Berry 2010-04-18 19:47:32 UTC 
3.12.5 is on the bench now. I am currently working on the Fails To Build From Source (FTBFS) issues for Fedora 13 before I can push it to the repos. See bug 565116 (https://bugzilla.redhat.com/show_bug.cgi?id=565116) which also effects the newer version of fldigi as well.
Comment 2 Fedora Update System 2010-04-23 00:26:47 UTC 
fldigi-3.12.5-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/fldigi-3.12.5-1.fc13
Comment 3 Randy Berry 2010-04-23 01:11:43 UTC 
Removed blocker FTBFS now fixed.
Comment 4 Fedora Update System 2010-04-23 06:05:02 UTC 
fldigi-3.12.5-1.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update fldigi'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/fldigi-3.12.5-1.fc13
Comment 5 Fedora Update System 2010-05-04 06:21:06 UTC 
fldigi-3.12.5-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.