Bug 55505
Summary: | Do not allow required packages (like kudzu) to be unselected | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | manuel wolfshant <wolfy> |
Component: | anaconda | Assignee: | Matt Wilson <msw> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-03-22 00:50:31 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
manuel wolfshant
2001-11-01 14:48:11 UTC
Note that if running kudzu in the post-install fails, or is not done, any HW not configured by the install will remain unconfigured. Not only that hardware is not configured but even doing an 'upgrade' install over the crashed one will not fix the problem(s). Kudzu will NOT be automatically selected in the list of packages to be added (actually no package was autoselected), and even after manually adding it, the end result of the instalation is non functional. In my case, lilo was not run and I ended up with the lilo configuration from the previous (RH 7.1) lilo configuration, which was not valid any more, since the partition was formatted. Additional data: I did NOT choose to use grub, sticking to the good old lilo. Last minute idea: maybe forcing reinstall of lilo would have been kind of a fix ? Well, the short answer is that you should pretty much always install kudzu. If you don't the hardware on the system will not be detected. The reason that the upgrade failed is that you were trying to do something that upgrades were not designed to do. You were trying to do more of a rescue than an upgrade, which isn't going to work. When the installer saw that the installed version of lilo installed was the same as the version on the cd, then the installer didn't try to upgrade a version to the same version. Kudzu is part of the base Red Hat Linux installation. The user removes packages from base at their own risk. Don't be surprised if things fail if you unselect packages from base. Well, I _KNOW_ what hardware is in my router and _I_do_not_need_ it installed. And if it is needed by the installer, then I think it should have complained after verifying the dependencies And last.. there is no documentation anywhere stating that installing kudzu is mandatory Ok. Reopening. *** Bug 57085 has been marked as a duplicate of this bug. *** *** Bug 56378 has been marked as a duplicate of this bug. *** I had the same problem and I opened bug # 57085 which is a dup of this issue. What I found was it didn't complain about kudzu and I also noticed that when it resolved dependencies after unchecking kudzu it wouldn't find any dependencies even though there were still a few packages I didn't resolve manually by going back and unchecking them in the flat view required. 1. Uncheck a package that has a dependency 2. run the dependencies checker 3. Go back into the flat view and uncheck kudzu & kudzu dependent 4. run the dependencies checker There you go, no more dependencies, even though there still are... I was told the ISO I DL from redhat.com was corrupted maybe maybe not, still worth checking out? Fixed in CVS |