Bug 48825
Summary: | "rpm -e --nodeps" ignoring --nodeps | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Panic <mdrew> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-07-12 16:43:32 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
Panic
2001-07-11 23:39:44 UTC
This has always been the behavior of --nodeps and --erase, so not a bug. The slowness is due to verifying data integrity on close if opened R/W, new behavior in rpm-4.0.3 Looking at what I wrote, I wasn't clear. I will reiterate, with additional information: the option --nodeps does not function in any of the following cases (test case was installing wvdial without the PPP package installed): rpm -Uvh --nodeps wvdial-1.41-13.i386.rpm rpm -ivh --nodeps wvdial-1.41-13.i386.rpm In both cases, the package refused to install due to dependency errors (the PPP package). The expected case is that the package will be installed regardless of dependencies, and functions exactly as expected on a 7.1 system. The --nodeps option also fails to function when trying to remove a package with this command: rpm -e --nodeps zip The result is that the package is not removed, and there is a dependency error returned even though I specified the --nodeps option. Does this make more sense? Is this rpm-4.0.3-0.66 or later? If earlier, then there was known CLI breakage there. Otherwise, please try (read: the CLI was very broken) rpm-4.0.3-0.66 or later. It was the 4.0.3-0.66 version. I tried 4.0.3-0.68 from 7.2-HEAD, same symptoms. Thanks Jeff. Works like a charm. |