Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 353621 - Duplications and mention of Fedora 7
Duplications and mention of Fedora 7
Status: CLOSED DUPLICATE of bug 338261
Product: Fedora Documentation
Classification: Fedora
Component: release-notes (Show other bugs)
All Linux
low Severity urgent
: ---
: ---
Assigned To: Release Notes Tracker
Karsten Wade
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2007-10-26 01:47 EDT by Piete Brooks
Modified: 2007-10-26 02:19 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-26 02:19:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Piete Brooks 2007-10-26 01:47:04 EDT
Provide details here.  Do not change the blocking bug.
Comment 1 Piete Brooks 2007-10-26 01:51:07 EDT
(Sorry -- finger trouble -- sent before giving details)
http://docs.fedoraproject.org/release-notes/f8/en_US/ has:

2.2.2: Duplicate "A brand new graphical firewall configuration tool,
system-config-firewall, replaces system-config-securitylevel."

19.2: "Fedora 7"

24: Duplicate "The Fedora Project is driven" ... "Communicate." (although text
not identical)

Is this sort of thing useful? Shall I look for more?
Comment 2 Karsten Wade 2007-10-26 02:19:30 EDT
Definitely useful, thanks, but we think we caught all of these.  They are not
fixed in the final release package, but are fixed in CVS and are going out in a
zero-day package update for fedora-release-notes.

FYI, here are the four bugs filed for mistaken Fedora 7 references; if you see
one that is not that list, let us know.  However, you probably won't find
anything since Bart did a good search.


Thanks for the report. :)

*** This bug has been marked as a duplicate of 338261 ***

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