Bug 1569
Summary: | If 'setup' RPM can't be installed, install should stop. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Daniel Rogers <dan> |
Component: | installer | Assignee: | Matt Wilson <msw> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | ||
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: | 2000-10-04 18:25:33 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
Daniel Rogers
1999-03-17 16:21:35 UTC
This is probably a manifestation of a general RPM bug, where it only statically checks Prereq: and Requires: requirements of RPMs. If one of the packages fails to install, RPM does not notice that some requirements are no longer met and continues to install RPMs. the new RPM transactions require an entire transaction to complete in order to be successful. This means that we should really abort the entire install in a failure like this, but instead well trudge along. We may revisit the problem later. If you've done something where the setup package isn't getting installed, you're _going_ to run into problems (for now) Issue has been added to list of features for future releases. How can we reproduce this problem? I had this problem when trying to do an FTP install where I got the error that the installer was unable to set the FTP server to PASV mode. It then skipped the first package and continued merrily along. Dan. Moving to RESOVLED - DEFERRED from CLOSED - DEFERRED Moving to RESOVLED - DEFERRED from CLOSED - DEFERRED Ok this appears to have been a problem before... |