Bug 478320
Summary: | New version 3.12 available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fabian Affolter <mail> |
Component: | solfege | Assignee: | Sindre Pedersen Bjørdal <sindrepb> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | sindrepb |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 3.14.2-1.fc10 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-06-16 02:06:00 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: |
Description
Fabian Affolter
2008-12-27 22:54:55 UTC
Any progress on this? 3.12.1 is out. 3.14.1 was released at March 31, 2009 Sorry for the lack of feedback on this. Currently awaiting fix for issue with build requiring X from upstream, which is a show-stopper atm. Will update package as soon as this is resolved. solfege-3.14.2-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/solfege-3.14.2-1.fc10 solfege-3.14.2-1.fc10 has been pushed to the Fedora 10 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 solfege'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-5796 This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping solfege-3.14.2-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |