Bug 572794
| Summary: | service argument completion is broken | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Todd Zullinger <tmz> | ||||
| Component: | bash-completion | Assignee: | Ville Skyttä <ville.skytta> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | el5 | CC: | alekcejk, sheltren, ville.skytta | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | bash-completion-1.1-6.el5 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-04-02 02:42:34 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: | |||||||
| Attachments: |
|
||||||
Agreed, I had a nagging feeling that there was something important I should have already backported from upstream git but it kept eluding me (and I personally mostly use bleeding edge upstream code so I didn't notice myself), thanks. A new upstream release isn't that far away but it is possible that it'll come with some incompatibilities that wouldn't be suitable to do in EPEL. Anyway, will push this to all active distro versions. bash-completion-1.1-6.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/bash-completion-1.1-6.fc13 bash-completion-1.1-6.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/bash-completion-1.1-6.el5 bash-completion-1.1-6.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/bash-completion-1.1-6.fc12 bash-completion-1.1-6.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/bash-completion-1.1-6.fc11 (In reply to comment #1) > Agreed, I had a nagging feeling that there was something important I should > have already backported from upstream git but it kept eluding me (and I > personally mostly use bleeding edge upstream code so I didn't notice myself), > thanks. Oh, I hate that feeling. > A new upstream release isn't that far away but it is possible that it'll come > with some incompatibilities that wouldn't be suitable to do in EPEL. Anyway, > will push this to all active distro versions. Many thanks Ville. bash-completion-1.1-6.el5 has been pushed to the Fedora EPEL 5 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 bash-completion'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/bash-completion-1.1-6.el5 bash-completion-1.1-6.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. bash-completion-1.1-6.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. bash-completion-1.1-6.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. bash-completion-1.1-6.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 546379 has been marked as a duplicate of this bug. *** |
Created attachment 399519 [details] Apply upstream post 1.1 service argument fix. I noticed when some EL-5 systems updated recently that the service argument completion was broken. I had fixed this locally a while back on many of my daily use boxes and saw it was fixed upstream so I didn't expect to find it broken in the latest EPEL push. Apologies for not catching this while it was in epel-testing. I think this one is worthy of a patch release, unless a new upstream release is imminent, as it is a decent regression from the previous release. Attached is a patch against the devel branch to apply your upstream fix for the bug.