Bug 66533
Summary: | upgrade from RH7.1 to RH7.3 failed when loading LPRng-3.8.9-3.i386 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | hugh a. duguid <hugh> |
Component: | installer | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:49:04 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
hugh a. duguid
2002-06-11 20:41:52 UTC
For privacy reasons this public bugtracking system is not connected to our support systems. Could you please summarize the nature of the problem you are experiencing? We were trying to upgrade from RH7.1 to 7.3. Install went ok until we got an error message "The file /mnt/source/RedHat/RPMS/LPRng-3.8.9-3.i386 cannon be opened. This is due to a misssing file, a bad package or bad media. Press <return> to try again." Which we did, to no avail. Contacted support concerning this, but they replied that it looked like an installer problem and that we should contact bugzilla so the developers could look at it. Ran the media check on the CD (#1), which didn't report any errors; also looked at the CD under Windoz to see if the file was there. It was and we could load it up into WordPad. Is the solution as simple as sending us a new CD? Or do we need to redo the floopy disk used for the install process. Thank you for your attention to this I would recommend requesting new CDs. Closing due to inactivity - please reopen if you have additional information regarding this issue report. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |