| Summary: | Get an error message when installing the gpm package via yum. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Hinson <oppiet35> |
| Component: | gpm | Assignee: | Nikola Pajkovsky <npajkovs> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dhoward, jhutar, john.mellor, loganjerry, npajkovs, pertusus |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gpm-1.20.6-21.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-02 17:28:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Robert Hinson
2011-11-13 20:58:23 UTC
If it helps, this is on a system that is using the multi-user.target instead of graphical target. This is because of the chkconfig invocation in %post. That should be removed. While you're at it, %postun is missing the final "fi", which causes a different error when gpm is uninstalled. I'm going to fix it and submit an update today gpm-1.20.6-21.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gpm-1.20.6-21.fc16 Package gpm-1.20.6-21.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gpm-1.20.6-21.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0898/gpm-1.20.6-21.fc16 then log in and leave karma (feedback). gpm-1.20.6-21.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 830681 has been marked as a duplicate of this bug. *** *** Bug 830616 has been marked as a duplicate of this bug. *** |