Bug 189412

Summary: Faulty name on CD - "FC/5 x86_64" instead of "FC_5 x86_64"
Product: [Fedora] Fedora Reporter: Luya Tshimbalanga <luya_tfz>
Component: distributionAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact: Bill Nottingham <notting>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: dcantrell, dgregor, katzj, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-18 21:34:29 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 Luya Tshimbalanga 2006-04-19 20:09:04 UTC 
Description of problem:
This problem occured after donwloading a torrent fro torrent.fedoraproject.org.
I was not sure where to submit this of bug so I thought to submit in Fedora
Infrastrucutre. A typo "FC/5 x86_64" cause the CD to not prompt into
installation screen.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Download the torrent of Fedora Core 5 x86_64 CD
2. Look of the name of the disc 1
3.
  
Actual results:
The name is "FC/5 x86_64" causing the disc to not prompt in installation screen

Expected results:
THe name should be "FC_5 x86_64"

Additional info:
Comment 1 Luya Tshimbalanga 2006-04-20 19:28:12 UTC 
Further details. The problem is the torrent version which appears to be
corrupted. I tested iso downloaded from official and mirror sites without a
problem. That applied to the CD version of FC5 x86_64.
Comment 2 Warren Togami 2006-06-28 14:31:02 UTC 
Not sure why this is assigned to me.
Comment 3 Bill Nottingham 2007-09-24 17:10:22 UTC 
Is this fixed in F7? Obviously, we're not going to respin FC5 at this point.
Comment 4 Luya Tshimbalanga 2007-11-18 21:34:29 UTC 
Yeah, the issue has been fixed. This bug report can be closed as I have not seen
any problem.