Bug 727788
| Summary: | Error autoremove not available on every uninstall using kpackagekit | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fabien Archambault <marbolangos> |
| Component: | kpackagekit | Assignee: | Steven M. Parrish <smparrish> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | kevin, ltinkl, rdieter, rhughes, richard, smparrish |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | apper-0.7.1-0.3.20111021.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-22 08:24:20 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
Fabien Archambault
2011-08-03 08:58:24 UTC
kpackagekit probably shouldn't be setting autoremove=true by default; that option was designed for embedded systems like mobile phones. FWIW, current versions of yum track the information required to support autoremove in their database, so at least in theory it should now be possible to implement. Now, whether it makes sense to use it in KPK in the first place is another question. Yes, I know. The two big problems with turning on autoremove in yum as as follows: * If the user uses raw rpm then the yumdb does not get updated and bad things happen * That the user is not expecting tons of packages (that they might still be using) to also be removed. The only way to solve that, is with a little checkbox in the UI ([x] also remove other software installed with this package) but the designers would shoot me for that. The KDE folks might actually go with the extra checkbox though. :-) (I'd have to ask Daniel what he thinks.) In any case, the backend should support it; whether the UI supports it or not is the UI's business. If the yum database has no information about a package, the safe thing to do is to not autoremove it. But for now, the best thing to do is probably to just patch out the use of autoremove from KPK. Overheard someone on irc report seeing this. I can't seem to reproduce this, I can add/remove apps, and not see any such errors. $ rpm -q PackageKit kpackagekit PackageKit-0.6.17-1.fc15.x86_64 kpackagekit-0.6.3.3-2.fc15.x86_64 kpackagekit-0.6.3.3-4.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kpackagekit-0.6.3.3-4.fc15 kpackagekit-0.6.3.3-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kpackagekit-0.6.3.3-4.fc16 Package kpackagekit-0.6.3.3-4.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 kpackagekit-0.6.3.3-4.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14262 then log in and leave karma (feedback). kpackagekit-0.6.3.3-4.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. apper-0.7.1-0.3.20111021.fc16, kde-settings-4.7-13.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |