Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 79618 - A typo in 4Suite package description
A typo in 4Suite package description
Status: CLOSED DUPLICATE of bug 107393
Product: Fedora
Classification: Fedora
Component: specspo (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Paul Cormier
: EasyFix
Depends On:
  Show dependency treegraph
Reported: 2002-12-13 21:06 EST by petrosyan
Modified: 2013-01-10 16:29 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:50:20 EST
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 petrosyan 2002-12-13 21:06:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
In sentence "4XPath is a library implementating the W3C's XPath language
for indicating and selecting portions of an XML document."

implementating -> implementing

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

How reproducible:

Steps to Reproduce:
rpm -qi 4Suite
Comment 1 petrosyan 2003-01-14 09:44:46 EST
this bug is still present in phoebe 4Suite-0.11.1-11
Comment 2 petrosyan 2003-04-01 15:41:12 EST
the bug is still present in Red Hat Linux 9 ( 4Suite-0.11.1-13 )
Comment 3 petrosyan 2003-07-09 23:05:08 EDT
the typo is still present in rawhide 4Suite-1.0-0.0.a1.i386.rpm
Comment 4 Craig Routledge 2004-02-13 14:23:07 EST
Typo is still present in development and FC1 versions

Comment 5 Miloslav Trmac 2004-03-08 09:17:18 EST
The 4Suite package is fine, this is a bug in specspo.
Comment 6 Miloslav Trmac 2004-04-17 09:20:41 EDT

*** This bug has been marked as a duplicate of 107393 ***
Comment 7 Red Hat Bugzilla 2006-02-21 13:50:20 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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