Bug 81670 – Release notes for Red Hat 8.0 seems corrupt

Bug 81670 - Release notes for Red Hat 8.0 seems corrupt

Summary:	Release notes for Red Hat 8.0 seems corrupt

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Public Beta
Classification:	Retired
Component:	redhat-release (Show other bugs)
Sub Component:
Version:	phoebe
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Ed Bailey
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-01-12 11:20 EST by Peter van Egdom
Modified:	2008-05-01 11:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-01-13 14:08:44 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Peter van Egdom 2003-01-12 11:20:14 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:

The release notes for Red Hat 8.0 -
(/usr/share/doc/redhat-release-8.0.92/8.0/RELEASE-NOTES-i386) - seem to be corrupt.

It ends with the line :

 'o Two'

Of course it should continue with "o Two commands are available ... " with the
rest of the Red Hat 8.0 release notes.

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


How reproducible:
Always

Steps to Reproduce:
1. cat /usr/share/doc/redhat-release-8.0.92/8.0/RELEASE-NOTES-i386
2.
3.
    

Actual Results:  Looks broken

Expected Results:  Complete Red Hat 8.0 release notes should be included.

Additional info:

redhat-release-8.0.92-2.src.rpm

Comment 1 Ed Bailey 2003-01-13 14:08:44 EST

I haven't a clue as to what happened, but I've regenerated the 8.0 notes.  They
should appear in their entirety in the future.  Thanks for letting us know!

Note You need to log in before you can comment on or make changes to this bug.