Bug 905438
Summary: | yum & yum-plugin-downloadonly: conflicting commandline option --downloadonly | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | junior <juninho_91> | ||||||||||
Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | urgent | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 18 | CC: | admiller, amcnabb, a.thiaville, bucknich, claudiorimmele, ffesti, kevin, madko, packaging-team-maint, ramindeh, sergio, tim.lauridsen, travneff, zpavlas | ||||||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||||||
Target Release: | --- | ||||||||||||
Hardware: | i686 | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | abrt_hash:3116587fbae1e274ed8686574472ec9d8d60fd94 | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2013-04-05 00:01:35 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: |
|
Description
junior
2013-01-29 12:58:03 UTC
Created attachment 689812 [details]
File: backtrace
Created attachment 689813 [details]
File: core_backtrace
Created attachment 689814 [details]
File: dso_list
Created attachment 689815 [details]
File: environ
You probably have yum-plugin-downloadonly installed and enabled. Uninstall it or disable in /etc/yum/pluginconf.d/downloadonly.conf. Now I've noticed that Yum obsoletes this plugin, maybe we should conflict instead. I ran into this error, too. It's a critical problem because it means that _all_ yum commands now fail, and security updates are impossible until the problem is fixed. Did setting "enabled=0" in /etc/yum/pluginconf.d/fastestmirror.conf fix your issue? after installation yum-plugin-downloadonly Package: yum-3.4.3-48.fc18 Architecture: x86_64 OS Release: Fedora release 18 (Spherical Cow) (In reply to comment #7) > Did setting "enabled=0" in /etc/yum/pluginconf.d/fastestmirror.conf fix your > issue? I did `rpm -e yum-plugin-downloadonly` to workaround the problem, but this seems like a problem that will make it so inexperienced users will just stop getting any security updates. in reply to comment #9 : I did exactly the same workaround (i.e rpm -e yum-plugin-downloadonly). After reading Comment 9. I reinstalled this faulty plugin (just for a while) and verified that "enabled=0" did the the trick too. -------------------------------- The plugin is buggy but the workaround "enabled=0" is not a good a solution, ----------------------------------------------- until the bug is corrected. (because yum update, yum install yum-plugin\* ...). To "download only" i use "yumdownloader" from "rpm-utils" yum-3.4.3-49.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/yum-3.4.3-49.fc18 Package yum-3.4.3-49.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 yum-3.4.3-49.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2076/yum-3.4.3-49.fc18 then log in and leave karma (feedback). yum-3.4.3-49.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. I have yum-3.4.3-49.fc18. It was still necessary to disable the "downloadonly" plugin as per comment #5 above. After that, it worked. Hi. yum install yum-plugin-downloadonly Processing Conflict: yum-3.4.3-49.fc18.noarch conflicts yum-plugin-downloadonly <= 1.1.31-7.fc18 IMHO. is not right , should done yum-3.4.3-49 provides yum-plugin-downloadonly you should add to .spec Provides: yum-plugin-downloadonly = 1.1.31-7 to delete yum-plugin-downloadonly on update of yum Conflicts doesn't make sense here! The Obsoletes that was there before was already correct, it just needed to be bumped to Obsolete the current yum-plugins. PS: The Conflicts is going to make it particularly hard to upgrade from F17 to F18 using the: yum --releasever=18 --downloadonly distro-sync telinit 3 yum --releasever=18 -C distro-sync method, so please fix/revert this! yum-3.4.3-50.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/yum-3.4.3-50.fc18 (In reply to comment #16) > Conflicts doesn't make sense here! The Obsoletes that was there before was > already correct, it just needed to be bumped to Obsolete the current > yum-plugins. Right : Obsoletes: yum-plugin-downloadonly < 1.1.31-7 but add Provides, is also cool to: yum install yum-plugin-downloadonly will say "already installed" so please add: Provides: yum-plugin-downloadonly = 1.1.31-7 Also is documented in : https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages Package yum-3.4.3-50.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 yum-3.4.3-50.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2711/yum-3.4.3-50.fc18 then log in and leave karma (feedback). (In reply to comment #17) Just caught that. Solved with manual update of yum to f18 version before all another. Seems like all went fine, but this isn't the best case of course. yum-3.4.3-53.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/yum-3.4.3-53.fc18 yum-3.4.3-53.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |