Bug 230725
Summary: | package manager crashes on startup after install of yum components | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mark Shiffer <mshiffer> | ||||
Component: | yum-utils | Assignee: | Seth Vidal <skvidal> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5 | CC: | tim.lauridsen | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-04-10 16:00:48 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
Mark Shiffer
2007-03-02 15:05:50 UTC
Created attachment 149122 [details]
saved dump from program
I the latest version of yum-utils the versionlock plugin is disabled by default. It is by design it fails when the versionlock if it is enabled and no file exists. If you enable the versionlock plugin by edit the plugin conf file you have to create a versionlock file. (In reply to comment #2) > I the latest version of yum-utils the versionlock plugin is disabled by default. > It is by design it fails when the versionlock if it is enabled and no file exists. > If you enable the versionlock plugin by edit the plugin conf file you have to > create a versionlock file. I'm going to recap what you said to make sure I understand what you said, and then disagree with what it is I think you said. "The latest version of yum-utils is disabled by default." I'm ok with that. "It is by design that it fails when the file isn't there." I'm not ok with that. How is an unhandled exception a designed failure? Since when is it a design to crash when something you're looking for isn't there? "If you enable the versionlock plugin by editing the plugin configuration file, you must create the versionlock file." I'm ok with that, except I ditn' turn on the plugin by editing anything. I turned it on through the Applications->Add/Remove Software frontend to yum. If I do that, it doesn't strike me as user friendly that I have to then add the file or not be able to use my front end to yum anymore. And my final comment/question is what do you gain by forcing the user to create a blank file when they add that component anyway? (In reply to comment #3) > "It is by design that it fails when the file isn't there." I'm not ok with > that. How is an unhandled exception a designed failure? Since when is it a > design to crash when something you're looking for isn't there? > In the latest version, it is just quiting with a message. The author want it to break if the file is missing. Take this this example. One a production system it is vital that a special application is kept on specific version, but the rest should be updated as normal. versionlock is activated and the versionlock file is created. 1. by some error the versionlock file is deleted. it this situation the plugin is design to make yum fail, so it detected there is some thing rotten on the system. > "If you enable the versionlock plugin by editing the plugin configuration file, > you must create the versionlock file." I'm ok with that, except I ditn' turn on > the plugin by editing anything. I turned it on through the > Applications->Add/Remove Software frontend to yum. If I do that, it doesn't > strike me as user friendly that I have to then add the file or not be able to > use my front end to yum anymore. > in the latest versions of yum-utils (1.0.x for yum-3.0.x (FC6) & yum-utils 1.1.x for yum 3.1 (FC7), the plugin is not enabled by default, you have to first install it and the edit the /etc/yum/pluginconf.d/versionlock.conf and set enabled=1 and create a versionlock file to make it work. By make i disabled by installation, it avoid situations where people have installed the plugin without wanting to use it. |