Bug 892556
| Summary: | fritzing-0.7.11b is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | fritzing | Assignee: | Ed Marshall <esm> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | esm |
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-01-20 03:16:36 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
Upstream Release Monitoring
2013-01-07 10:53:23 UTC
*** This bug has been marked as a duplicate of bug 847640 *** Whoops, looks like there was some craziness with the upstream monitoring script. Re-opening. Working on this now. However, there's a new bug introduced at startup: http://code.google.com/p/fritzing/issues/detail?id=2358 This *appears* to be an informational warning only, and there's a workaround that users can apply to correct the issue (although unfortunately, I can't integrate it into the RPM build because of an X dependency in Fritzing). Because the existing version of Fritzing is failing on startup because of what appears to be a Qt update that went out recently, I may just push out the new release with this warning screen as a known issue in the hopes that upstream gets a fix pushed soon. :( fritzing-0.7.11b-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fritzing-0.7.11b-1.fc17 fritzing-0.7.11b-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fritzing-0.7.11b-1.fc18 fritzing-0.7.11b-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/fritzing-0.7.11b-1.fc16 Package fritzing-0.7.11b-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fritzing-0.7.11b-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0422/fritzing-0.7.11b-1.fc18 then log in and leave karma (feedback). fritzing-0.7.11b-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fritzing-0.7.11b-2.fc17 fritzing-0.7.11b-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/fritzing-0.7.11b-2.fc16 fritzing-0.7.11b-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fritzing-0.7.11b-2.fc18 fritzing-0.7.11b-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. fritzing-0.7.11b-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. fritzing-0.7.11b-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |