From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
Description of problem: Installation of RH7.3 failed at LPRng-3.8.9-3.i386
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install upgrade to RH7.3
Actual Results: Locked up
This is the reply from Support to my ticket #207500
This seems to be a problem with the installer. I'd advise that you address this
our developers so that they could be aware of this problem with the installer.
This could be a possible bug with our installer. Our developers are the ones
who are currently working on new issues and possible bugs. You can get in touch
with them through our bugzilla site:
Before addressing this issue to our developers, try to access the file that
cannot be opened. You can do this on a windows machine. If you were able to
copy the file, it's really with the installer that's the problem.
Should you have other concerns, please feel free to write us back.
File was found on CD#1 via Windoz.
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
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.