Bug 856957
| Summary: | URL in xterm.spec has moved permanently | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Bolle <pebolle> |
| Component: | xterm | Assignee: | Miroslav Lichvar <mlichvar> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | mlichvar, pertusus |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-26 16:42:36 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
Paul Bolle
2012-09-13 08:45:28 UTC
xterm-283-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/xterm-283-1.fc18 xterm-283-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/xterm-283-1.fc17 Package xterm-283-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xterm-283-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15860/xterm-283-1.fc17 then log in and leave karma (feedback). xterm-284-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/xterm-284-1.fc18 xterm-284-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/xterm-284-1.fc17 xterm-284-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |